Our Reading Lists, Hijacked Yesteryear Spammers

I've been writing virtually spammer activities, in addition to virtually diverse blog hijacks, for about time. There's a special, rather devious weblog hijack, involving spammer activity, that we've been aware of, for about time. In Blogger Help Forum: Something Is Broken, nosotros occasionally run into the query

How create I larn rid of spam, inward my Reading List? I did non Follow this blog!

Nobody will, intentionally, Follow a weblog amount of spam. In about cases, though, people Follow blogs that are published yesteryear naive weblog owners, who convey been conned yesteryear the spammers, into working for them.

The never ending ask for more Followers, readers, search engine reputation, subscribers, in addition to traffic, is a ofttimes expressed draw of piece of occupation concern inward Blogger Help Forum: How Do I?.

In discussions exterior Blogger Help Forum, ane mightiness perchance uncovering suggestions of other, to a greater extent than imaginative ways to larn to a greater extent than traffic to your blog. With Blogger blogs, there's a very obscure in addition to easily used feature, that tin plough over the sack live on used to publicise your blog, randomly, to readers that yous would not, otherwise, address.

All that yous ask create is to redirect your weblog feed into a "feed redistribution cloud", that randomly redirects the readers of whatsoever blog, to viewing the feed from about other blog, similarly using the redirect.

By redirecting your readers, yous are exposing them to other blogs, randomly selected. Similarly, readers of other participating blogs are randomly redirected to your weblog - in addition to at that spot is the promised publicity for your blog.

This is such a bully idea, isn't it? Think again.

1. Your Followers (and subscribers) desire to read the feed from your blog - non from about random blog.
2. Many Blogger weblog owners don't role this feature.
3. Many users of this characteristic are non legitimate Blogger weblog owners, but publishers of spam blogs in addition to websites.
4. Should yous redirect your readers into a "feed redistribution cloud", the chances are greater that your readers volition live on reading a weblog published yesteryear a spammer.
5. No spammer volition redirect the feed from his blog. He's going to exceed away on all of his traffic, to himself
6. Since no existent people knowingly subscribe to feeds from spam blogs in addition to websites, your weblog won't live on getting whatsoever reciprocal crowd of eager would live on readers, originating from the spam blogs in addition to websites.
7. And, nosotros are here.

As a Follower (and non a weblog owner), having examined your Reading List in addition to flora yourself reading a weblog amount of spam - that yous sure did non Follow - what create yous do? It's a uncomplicated - but perchance ho-hum - chore to identify in addition to remove the weblog owned yesteryear the naive person, who was conned yesteryear the spammers, that yous are Following.

Having done that, why non become ane pace further, in addition to help us to assistance Blogger in addition to Google to interdict the spammer activity?

If yous tin plough over the sack position the URL of a blog, that yous are Following, that is redirecting its feed inward this manner, Blogger / Google tin plough over the sack position in addition to terminate whatsoever Google hosted blogs in addition to websites that are advertising this easy, random agency to publicise your weblog - that is but about other fob used yesteryear the spammers, into getting the naive weblog owners to create their dingy work.

All that nosotros ask is the URL of whatsoever blog, that yous were Following, that rudely redirects its subscribers (like you) into the "feed redistribution cloud". Blogger / Google tin plough over the sack create the rest.

You tin plough over the sack comment, hither - or foremost a discussion, inward Blogger Help Forum: Something Is Broken - it's your choice. Just assistance position the naive weblog owners.

Do your part, in addition to assistance us build clean upward the Blogger Blogosphere.

Attention Weblog Owners - Nobody Knows Your Blog

One confusion, which nosotros run into inwards Blogger Help Forum: Something Is Broken regularly, concerns weblog owners together with their agreement well-nigh search engine functionality.

I can't expose my blog!

This is oftentimes to a greater extent than completely expressed as

I can't expose my blog, listed inwards a Search Engine Results Page, when I search yesteryear URL (blog title, another obscure item ...)!

Equally every bit mystifying are people who report

I typed inwards the advert of some obscure porn concept, together with found my weblog listed. Why is my weblog listed amongst porn?

This occupation is partially caused yesteryear some browser producers, who confuse us yesteryear combining the browser address together with search windows. There are other reasons for the confusion, too.

When you lot accept a weblog amongst an established audience, together with you lot are able to examine demographic item found inwards diverse visitor logs together with meters, you'll detect activeness from diverse sources.

• Search engines together with like robotic indexing services.
• People, using newsfeed subscriptions, together with diverse newsfeed clients.
• People, pasting or typing the URL into the browser address window.
• People, clicking on links inwards bloglists (on other peoples blogs), together with bookmarks (in their personal browsers).

People using search engines expose your weblog from searching for content.

When the visitor log, that you lot are examining, provides you lot amongst item well-nigh your search engine traffic sources, you'll notice that most people using search engines expose your weblog when using search damage that reference weblog content. This is because people using search engines orbit non know well-nigh your blog, together with orbit non know (or attention about) the weblog name, title, or URL.

People who know how to utilisation their browser most effectively, together with already know well-nigh your blog, volition utilisation 1 of the latter iii services to expose your blog.

People who utilisation search engines orbit non know well-nigh your weblog - they desire content.

The people who utilisation search engines, for the most part, volition hold upward people who orbit non know your blog, or are looking for material other than - or inwards improver to - your blog. None of these people volition utilisation the weblog championship or URL, inwards their search activity.

If you lot are going to teach novel Followers, readers, subscribers, together with viewers inwards general, you lot accept to piece of work hard, appear inwards a skillful position, inwards a pop search engine results page, for some sum of time.

Use Search Console (pka Webmaster Tools) to stair out search indexing results.

If you're using a weblog URL search to stair out search engine indexing of your blog, utilisation the diagnostics inwards Google Webmaster Tools, for a to a greater extent than efficient together with objective analysis. If you're using a weblog URL search to stair out visitor perception of your blog, wise upward together with get to piece of work on your blog.

The Comment Notification Pick Is Dependent Area To The Realities Of Authentication, As Well As Cookie Filtering

Some weblog guests cannot empathize why they can't larn notifications, when somebody leaves a comment after them, attached to a post comment form.

Why don't I run into the selection to "Email follow-up comments to xxxxxxx@yyyyy.zzz"?

or maybe

I selected the selection to "Email follow-up comments to xxxxxxx@yyyyy.zzz", but I don't larn whatever reply notifications. Why am I beingness mistreated yesteryear Blogger?

These people produce non realise that comment follow-up notifications are dependent area to the same problems every bit the embedded comment form.

Many people, preparing to post a comment on their favourite blog, expect forwards to reading replies from other weblog guests - together with buy the farm confused when they produce non run into the selection to

Email follow-up comments to xxxxxxx@yyyyy.zzz

They don't realise that they volition exclusively run into that selection when they are logged inwards using a Blogger draw of piece of employment concern human relationship - together with when their login condition is available to the code behind the comment form. Like the wishing to post a comment, using one's Blogger / Google account, this selection requires availability of the Blogger login cookie, identifying the commenter every bit beingness logged in.

An incorrectly ready cookie filter tin either foreclose availability of the comment notification option, when using the embedded comment course of study (if "third political party cookies" are blocked) - or tin foreclose availability of the selection on whatever comment course of study (if cookies, inwards general, are blocked). In either case, the commenter volition live on treated, yesteryear the comment course of study code, every bit non beingness logged inwards - together with no selection volition live on provided.

Also, if the commenter is successfully logged in, but is non using a Blogger draw of piece of employment concern human relationship that's attached to an active e-mail address, he / she tin lead the notification option, but volition never have a notification. This is a typical problem, amongst a Blogger draw of piece of employment concern human relationship setup using a bogus e-mail address, whether accidentally or intentionally.

So, if you lot don't run into the notification selection when you lot post a comment - or if you lot lead the selection but never larn whatever email, don't straightaway together with unilaterally blame the Blogger commenting feature. Do only about research, before reporting your problem.

>> Top

The Novel Gui (2011) Is Instantly The Electrical Flow Gui

When the New Blogger GUI (2011) was first introduced, it was optional. New Blogger spider web log owners, together with other Blogger employment organization human relationship holders, would teach the (currently available) Classic GUI past times default, amongst the offer

Try the updated Blogger interface

at the tiptop of the dashboard. When inwards the "updated Blogger interface", nosotros would run into the reassuring link to

Switch back

at the tiptop of the spider web log listing or dashboard.

Blogger has at in 1 trial taken the adjacent step, to making the New GUI (2011) but The GUI. The "Switch back" link, at the top, is at in 1 trial gone. If yous desire to teach dorsum to the (former) Classic GUI, yous uncovering the gear ikon at the tiptop correct of the spider web log listing or dashboard display. Clicking on the gear, you'll run into a to a greater extent than robust pulldown menu, amongst the pick "Old Blogger interface".

An alternate fashion to deed forwards would live on to piece of work the New GUI Use URL

www.blogger.com/opt-in-new-ui.g?useNewUi=true

If yous are trying the "updated Blogger interface" from an out of engagement browser, yous may non live on able to access the gear icon. In this case, yous may uncovering the Classic GUI Recovery URL useful.

www.blogger.com/opt-in-new-ui.g?useNewUi=false

>> Top

Automatic Sharing Of Blogger Posts, To Google+

Today, nosotros see, inwards Blogger Buzz: Connect to Google+, a long awaited announcement, from Blogger.

Starting today, if yous bring linked your spider web log to your Google+ describe concern human relationship yous volition last presented alongside a prefilled Google+ percentage box forthwith afterwards publishing a post. The percentage box volition incorporate a +snippet of your post service that yous tin percentage alongside your circles on Google+.

So, this is my exam of the novel feature.

This was kickoff a alive test, using my nous Blogger account. I spent the amend utilization of i lx minutes migrating my Blogger describe concern human relationship to utilization my Google+ profile. Having done that, I at nowadays compose my kickoff Blogger spider web log post, spell using my Google+ profile - as well as now, I volition run across how good Blogger as well as Google+ are integrated.

From looking closely at the moving-picture demonstrate inwards the Buzz post, it looks similar the promised popup window, "Share on Google+", is a characteristic that's built into The New GUI. Since I stay underwhelmed yesteryear the New GUI, this Blogger describe concern human relationship remains nether the Classic GUI. And, having hitting "Publish Post", I saw no novel "Share on Google+" popup window.

To utilization the Blogger to Google+ Automatic Sharing, yous must produce iii things.

1. From your Classic GUI Dashboard, or Settings wizard, choose "Try the updated Blogger interface".
2. From the gear icon, choose "Connect to Google+".
3. In Settings - Posts as well as comments, ready "Share to Google+" to "Yes".

Fortunately, it's possible to utilization the Share selection inwards the Posts list, for the post service inwards question, as well as percentage this post service from around other Blogger describe concern human relationship that is inwards my nous Google+ account's circles. Using the "Extended Circles" target, from my exam Blogger account, got the chore done. Looking inwards my Stream, I run across the novel post service snippet, shared every bit promised.

You'll banker's complaint that "Share to Google+" will, yesteryear default, percentage to the nous Google+ profile name. If yous bring created Google+ Pages (alternate identities) attached to your Google+ Profile, yous tin share to a Google+ Page.

This procedure is non genuinely automatic. If completely automatic, in that place should last around mapping of a Label inwards the post, to choose i or to a greater extent than pre chosen Circles. When this post service was published, FeedBurner redirected this post, from the posts feed, to my Twitter account. Surely, Google+ could render the same possibility.

But, what nosotros bring today is an first-class start.

>> Top

Owners Of Blogs, Alongside Images Inwards The Header, Study Changes Inwards Header Appearance

During the yesteryear few days, we're seeing a few reports inwards Blogger Help Forum: Something Is Broken, from owners of blogs that job an icon inwards the header, instead of or inwards add-on to, evidently text, claiming changes inwards the appearance of the header. The exact job study varies - that the icon has been resized, has shifted inwards position, has move yesteryear away pixelated, or has exactly disappeared.

We convey a rollup discussion, where nosotros are requesting details from each someone observing this job inwards their blog.

1. What is the URL of the blog?
2. What exact symptom are you lot observing, that's a problem?
3. Does the spider web log job a Blogger or 3rd political party template?
4. Does the spider web log job a Designer or Layout template?
5. Has the spider web log been configured for a Dynamic template?
6. How did you lot setup the image, that is inwards job on your blog? Did you lot job the Layout "Configure Header" wizard, did you lot upload the icon using the post service editor "Insert image" wizard, or other?
7. If you lot used the "Configure Header" wizard, which Image / Placement options did you lot select?
   • From your computer.
   • From the web.
   • Behind championship too description
   • Instead of championship too description
   • Have description placed afterward the image
   • Shrink to fit
8. Can you lot honor the icon on your computer? If so, what is the refer of the file, every bit uploaded? Is it a .bmp, .jpg, .png, what?
9. When you lot setup / uploaded the image, what browser (name too version) was used?
10. What browser (name, too version) are you lot using, right now, where the job is visible?

If you lot tin render details, delight create then every bit best every bit you lot are able, either hither or inwards the rollup discussion.

In cases where the URL of the icon inwards job tin endure edited, you lot may endure able to function or then your problem, yesteryear editing the precise URL. It appears that images hosted yesteryear Picasa, which are currently stored inwards a diverseness of sizes (which you lot may run into when you lot job "Insert image", for instance), are at in i lawsuit selected inwards a unlike way, when you lot create non explicitly choose the right size for your purpose.

Look at the icon at the elevation of the screen. If you lot were to hold off at it's URL, you lot would see:

https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj9BwVdtm4TV84AnJgV3JOqaLKcjyZbqZeKDPxm8Ar_icEne6K-uEiPnXdZ3Ea_zP1JGW-ylAfkE5JQWcyWDt2ZWoJ2FtLNQwaD_zBm0WmQTqkY9Zygrom2DXex9mtn48FsM9cchysrl0pd/s1600-r/RBS+Header+4a.gif

If that icon had been uploaded using the electrical flow "Insert image" magician (in post service editor), or the "Configure Header" magician (in "Page Elements"), it mightiness convey the URL

http://1.bp.blogspot.com/_pzC_7PLtN-0/R_buGAu4D3I/AAAAAAAABCI/wxcsyLm3DoE/RBS%2BHeader%2B4a.gif

If the latter URL was correct, at that topographic point would endure iv aliases available:

• Small: http://1.bp.blogspot.com/_pzC_7PLtN-0/R_buGAu4D3I/AAAAAAAABCI/wxcsyLm3DoE/S160/RBS%2BHeader%2B4a.gif
• Medium: http://1.bp.blogspot.com/_pzC_7PLtN-0/R_buGAu4D3I/AAAAAAAABCI/wxcsyLm3DoE/S320/RBS%2BHeader%2B4a.gif
• Large: http://1.bp.blogspot.com/_pzC_7PLtN-0/R_buGAu4D3I/AAAAAAAABCI/wxcsyLm3DoE/S640/RBS%2BHeader%2B4a.gif
• Full Size: http://1.bp.blogspot.com/_pzC_7PLtN-0/R_buGAu4D3I/AAAAAAAABCI/wxcsyLm3DoE/S1600/RBS%2BHeader%2B4a.gif

If I had this job amongst my header image, I would edit the URL, inwards the template, too I would replace:

http://1.bp.blogspot.com/_pzC_7PLtN-0/R_buGAu4D3I/AAAAAAAABCI/wxcsyLm3DoE/RBS%2BHeader%2B4a.gif

with

http://1.bp.blogspot.com/_pzC_7PLtN-0/R_buGAu4D3I/AAAAAAAABCI/wxcsyLm3DoE/S1600/RBS%2BHeader%2B4a.gif

If your spider web log has this problem, you lot may endure able to similarly edit your spider web log - using "Configure Header" or "Edit HTML" - too function or then your problem. If you lot job "Edit HTML", I suggest, every bit usual, that you lot backup the template - before too after making this tweak.

>> Top

Blogger Magic - Reporting Abusive Blogs Or People

The Internet Is a wonderful affair - it has brought many people, from many lands, together, ignoring geographic in addition to political limitations. Unfortunately, "many people, from many lands" is non e'er a adept thing. In whatever grouping of people, at that spot volition hold out people who ambit non know or sympathise each other - in addition to at that spot volition hold out conflict.

Blogger / Google has given us tools to study a problem, when nosotros sense conflict - in addition to when that conflict involves someone else, misusing a Blogger blog. These tools were developed on an "as needed" reason - then don't hold off them to hold out good defined, in addition to good instructed, inward every occupation which you lot may have. And, you lot convey to utilisation these tools correctly - they are non magic.

If you lot study a problem, amongst a spider web log or a person, you lot convey to study the occupation properly - in addition to you lot convey to sympathise the limitations, both legal in addition to realistic. Abuse reporting is non magic - you lot cannot moving ridge a magic wand, in addition to brand your problems become away.

There are several possibilities, which you lot require to consider.

• DMCA Violation. Influenza A virus subtype H5N1 DMCA Violation complaint is for obvious, in addition to definable copyright or trademark violations. Influenza A virus subtype H5N1 DMCA Violation electrical load tin flame hold out filed against whatever Blogger / non Blogger spider web log or website.
• Blogger / Google TOS Offense. Influenza A virus subtype H5N1 TOS Offense complaint is for whatever Blogger blog, which is offensive inward specific categories. Influenza A virus subtype H5N1 TOS Offense electrical load tin flame hold out filed against a Blogger spider web log or Google website, only.
• Any other complaint, that you lot may have, is a civil issue - betwixt you, in addition to the offending parties. Blogger / Google cannot assist you, inward this case.

Use the right form, in addition to the right reporting selection. We convey the DMCA Violation Report, in addition to the "Report Abuse" wizard, in addition to they each have a dissimilar purpose. Within "Report Abuse", at that spot are distinct reporting categories. When you lot study a problem, you lot require to utilisation 1 wizard, or the other - in addition to to select the right categories, when available.

If you lot submit repeated in addition to blatantly inappropriate reports, you lot may hold out perceived equally a spammer, conducting a denial of service attack against the reporting procedure - then submit 1 complaint, properly chosen in addition to written.

Be realistic. Blogger / Google has to investigate, in addition to verify your electrical load - in addition to the other political party inward the dispute has to convey a peril to defend himself. This volition require fourth dimension - in addition to may non ambit favourable results, for you, personally.

Don't hold off miracles. Any immediate in addition to physical problems require to hold out reported to your local police describe agency, equally they are the ones responsible for your physical safety. And when you lot bargain amongst an Internet based threat, think that at that spot are many website hosts. Just because Blogger / Google is existence used, right now, inward your personal situation, does non hateful that your aggressor volition entirely utilisation Blogger / Google, inward the future.

If you lot don't abide by a clear in addition to good defined reporting category for your electrical load - or if you lot don't larn immediate or favourable results subsequently submitting your complaint, you lot may ambit best to hire a lawyer - in addition to when you lot do, lead 1 who is experienced inward Internet legal situations.

>> Top

Abuse Reporting - Precision Is Required

Every day, inwards Blogger Help Forum: Something Is Broken, nosotros encounter the complaint

I've been reporting this abuse to Google for a week, as well as I accept even then to encounter a reply - or a result. What is upwardly amongst that?

This is maybe somebody who does non know what abuse category to role - or who maybe can't uncovering the correct category.

Over a twelvemonth ago, nosotros learned the divergence betwixt Defamation as well as Impersonation.

• Defamation (ridicule, slander, trash talk) is a civil offense, as well as requires that yous hire a lawyer.
• Impersonation (identity theft) is a TOS offense, as well as tin flaming outcome inwards termination of an offending blog.

Impersonation is one of viii categories, each good defined. When yous study a serious offense, that tin flaming accept legal consequences - such every bit Impersonation, which tin flaming outcome inwards Google terminating an offending weblog - your study has to last carefully scrutinised past times Google Legal.

Similarly, if yous study a weblog for publishing individual information, the nature of the reported "private" data volition last verified. DMCA complaints are handled exterior Google - as well as must last reported with absolute precision, as well as attending to detail.

If yous study ane category, because "it was the closest choice that I could find", as well as Google Legal finds no travail for action, your study gets ignored. If yous study the same employment repeatedly, yous may become onto a listing that yous don't desire to last on.

The bottom business hither - if yous accept a problem, brand certain that your employment fits the chosen category, accurately. Don't simply guess, hither - yous won't acquire anything out of the experience, except frustration.

Abuse Reporting - Personal Vs Individual Information

One interesting representative of the lack of precision inwards abuse reporting involves the nature of individual information

When volition Google create something virtually this weblog that is publishing individual information virtually me? They bring my domicile address, my Social Security Number, my telephone number, for everyone to see!

This mortal does non seem to empathise the divergence betwixt personal, too private, information.

One of the categories, inwards Blogger Help: Report Abuse, is

Posting of individual information

You tin study whatsoever blog, genuinely publishing individual information virtually you. Unfortunately, everything that is personal to yous may non live on private.

Anybody amongst Internet access, too perchance too an active banking concern card, tin access all sorts of personal information virtually you. Your name, domicile address, trouble organisation address, brand too model of your car(s) - too yes, your telephone issue - is all visible, inwards 1 or to a greater extent than publicly accessible online databases.

Under the Health Insurance Portability too Accountability Act of 1996 (aka HIPAA), medical records of United States of America citizens are considered individual information - too anyone publishing a weblog identifying local residents, who latterly had sure as shooting medical tests performed, would probable detect their weblog deleted, promptly enough.

On the other hand, getting a weblog deleted, when it but contains a directory of residents listing name, address, too telephone number, would likely require a determination from a local court, because none of this is individual (though it is personal).

But await - there's more.

If yous successfully larn your cite too address considered private, yesteryear a court, volition it actually live on private? If your cite too address becomes business office of a courtroom decision, anybody amongst access to courtroom documents tin detect it. And again, anybody amongst Internet access too the correct banking concern bill of fare tin search it out.

Face it - nada - but maybe HIPAA protected medical records - is genuinely private. Your might to bring Blogger / Google delete an offending blog, non withstanding.

>> Top

Bloggers Trying To Login, Seeing The Page Isn't Redirecting Properly, Revisited

For unopen to fourth dimension recently, we've been seeing numerous reports from people inwards Blogger Help Forum: Something Is Broken, unable to successfully login to Blogger.

I cannot log into Blogger - I proceed getting this error

The page isn't redirecting properly.

Firefox has detected that the server is redirecting the asking for this address inwards a manner that volition never complete.

In a few cases, nosotros identified the underlying campaign of the work every bit disabling or refusing to receive got cookies, or like overly aggressive layered safety procedures too settings. Feedback from unopen to forum members, who were able to supply details, suggests unopen to other cause. The work may endure simpler - or to a greater extent than complex - to resolve.

Some of the forum members, who reported this problem, every bit good reported a work alongside their Google+ accounts. Blogger spider web log owners, attempting to login to a Blogger describe organisation human relationship which uses a Google+ profile, generate a redirect to the Google+ servers. If the associated Google+ describe organisation human relationship has a problem, you lot receive got unopen to other campaign of the redirection problem.

The solution hither is uncomplicated - take the Google+ association. Unfortunately, this tin endure done alone when logged inwards to the Blogger / Google account.

1. Fix the work alongside the Google+ account. It may endure possible, alternately, to revert from a Google+ profile, to a Google profile.
2. Login to Blogger, too to Google.
3. Transfer ownership of the blog(s), using the Permissions wizard too using two form out browsers or computers.
4. Remember that you are at 1 time responsible for maintaining ii Google accounts.
5. Done.

But await - why non simplify - merely a bit?

1. Fix the work alongside the Google+ account.
2. Change your Blogger describe organisation human relationship dorsum to using a Classic Blogger profile.

Or, fifty-fifty simpler.

1. Fix the work alongside the Google+ account.

If you lot tin ready the Google+ describe organisation human relationship problem, don't worry virtually the Blogger problem. Get back to work, on your blog. And don't produce anything to intermission your Google+ account.

>> Top

Post Editor Preview Mode, Inwards The Novel Blogger Gui

We're seeing a few reports from weblog owners having problems amongst Previewing their posts, using Post Editor inward the New Blogger GUI.

I can't preview my weblog post, spell I am composing it!

It appears that Blogger has changed the New GUI Post Editor, to opened upwards the Preview window inward a popup, instead of a novel tab or window.

Almost all browsers, yesteryear default, block popup windows. If you lot desire to role Preview Mode, inward the New GUI, you'll convey to banking corporation jibe all relevant filters, in addition to ensure that popup windows are allowed. It's possible that Blogger decided that a popup window was easier to render than a assort tab / window, involving cross-site scripting, equally the Template Designer Live Preview currently requires.

>> Top

Blog Owners Reporting Diverse Safety Related Issues, This Week

This week, nosotros are seeing diverse reports from people who are reporting dissimilar problems alongside Blogger - all problems which were associated alongside safety issues inwards the past. In the past times duad days, we've seen several reports of problems alongside Commenting, together with alongside Stats - both problems which were known, inwards the somewhat distant past, to hold upwards caused past times filtering of cookies together with / or scripts.

Those details, inwards themselves, would in all probability hold upwards only coincidental - except that end Tuesday, 4/10/2012, was Patch Tuesday - together with I convey seen online discussions past times diverse Microsoft safety experts, suggesting that about pregnant changes were made to Microsoft Windows safety components.

I'll authorities annotation during that during the forthwith previous past times few weeks, nosotros convey seen really few reports of problems alongside commenting, together with alongside Stats. The massive degree of complaints close both concerns, seen during the latter months of 2011, convey been tranquillity of late - until this week.

I myself awoke this morn to discovery this computer, having updated together with restarted during the previous night. Looking at a Microsoft Patch Summary, 1 tin run across references to about interesting changes.

I don't mean value that it's terribly imaginative to advise that about of us may discovery about strange changes inwards safety on our computers, installed inwards the end duad days.

>> Top

Blogger Blogs Displaying Mysterious Transparent Boxes, Roofing Weblog Content

We're seeing a steady inundation of occupation reports most diverse Blogger blogs that bring developed a mysterious transparent box, roofing to a greater extent than or less component of the weblog surface when displayed. Some blogs display the box for all views, others for principal page sentiment only, as well as nonetheless others for specific private posts. The box may hold upwardly visible at the summit of the page or inwards the center - as well as may scroll amongst the screen, or may stay fixed relative to the display. In many cases, it blocks of import weblog content, as well as / or prevents clicking on crucial links.

Initial observations, during the forthwith previous 2 - 3 days. referred to a "FaceBook or similar Social Networking gadget". Digging deeper, as well as looking closely at reported cases, nosotros tin laissez passer on the sack await for the occupation itself.

After repeated exam of multiple cases, we're seeing a to a greater extent than specific pattern, inwards the occupation source code. Using a text browser tool, nosotros respect the next code (with gratis occupation breaks added for readability), which appears to hold upwardly the marrow of the problem.

<div id="fb-root"></div><script> (function(d, s, id) {   var js, fjs = d.getElementsByTagName(s)[0];   if (d.getElementById(id)) return;   js = d.createElement(s); js.id = id;   js.src = "//connect.facebook.net/en_US/all.js#xfbml=1";   fjs.parentNode.insertBefore(js, fjs); }(document, 'script', 'facebook-jssdk')); </script><br /> <div class="fb-like" data-href="https://www.facebook.com/xxxxxxxxxxx" data-send="false" data-show-faces="true"  data-width="450"></div> 

(Note that "xxxxxxxxxxx" volition hold upwardly the FaceBook user name, providing the proper addressing to the concern human relationship where the "Like" transaction is targeted).

The occupation appears to involve the FaceBook Like accessory. It's possible that FaceBook Support tin laissez passer on the sack render a ameliorate diagnosis - but for correct now, I'll but advise removal of the higher upwardly code. In the cases where the code was installed into an empty HTML / JavaScript gadget (and amongst no other accessories installed in that place also), I'll advise removal of the gadget containing the code.

If y'all tin laissez passer on the sack lay the occupation gadget inwards your blog, y'all tin laissez passer on the sack edit the gadget, as well as Remove it.

As an alternate solution, y'all may add together CSS which volition cover the boxes. Only fourth dimension volition tell, if this is a ameliorate option for many weblog owners. Using the "Add CSS" wizard inwards the Template Designer Advanced menu, add together the following:

#fb_xdm_frame_http, #fb_xdm_frame_https {  display:none !important; } 

Depending upon your marker of technical comfort as well as expertise, y'all may elect whatever i of 3 solutions.

1. Remove the entire HTML gadget.
2. Remove the specific occupation code.
3. Add CSS to cover the problem.

It's your blog, as well as your accessories.

Note that subsequently y'all add together or take the code inwards question, as well as relieve the changes, y'all volition involve to clear browser cache as well as restart the browser, to accurately examine success inwards resolving the problem.

>> Top

The Simplicity Of A Custom Domain Setup

Custom domain publishing is a rattling elementary means to give your Blogger spider web log a non BlogSpot URL - when y'all follow the recommended procedure.

Along amongst the simplicity, you'll abide by rather stiff requirements, when any alternative procedure is used.

Too many spider web log owners, unfamiliar amongst the complexity of the custom domain infrastructure, endeavour to "fly past times the topographic point of their pants", when they meet a requirement that they don't understand.

Improper domain setup, caused past times bad decisions, is how many custom domain publishing problems start.

First, empathise some of the close mutual mistakes, made past times equally good many spider web log owners. Blog owners inward the USA may use Google Domains, though others must buy direct from a registrar.

That reality does non modify whatsoever of the necessities of proper domain setup, however. Substituting for "Buy a domain", Blogger offers instructions, inward How gain I purpose a custom domain cite for my blog?.

There are 3 - as well as entirely 3 - supported DNS Models.

To empathise the significance of the mistakes that are usually made, starting fourth dimension empathise the iii basic DNS models, involved inward custom domain publishing.

1. Published To Domain Root - Symmetrical DNS Configuration. The close obvious configuration uses a symmetrical DNS structure - dual "CNAME" referrals.
   

   mydomain.com. 3600 IN CNAME ghs.google.com. www.mydomain.com. 3600 IN CNAME ghs.google.com.

2. Published To Domain Root - Asymmetrical DNS Configuration, aka "Google Apps". If y'all receive got a domain amongst email, FTP, as well as other possible auxiliary services, y'all purpose an asymmetrical structure, which use Google Apps to allow y'all add together auxiliary services, amongst quadruple DNS server redundancy.
   

   mydomain.com.  3600 IN H5N1 216.239.32.21 mydomain.com.  3600 IN H5N1 216.239.34.21 mydomain.com.  3600 IN H5N1 216.239.36.21 mydomain.com.  3600 IN H5N1 216.239.38.21 www.mydomain.com. 3600 IN CNAME ghs.google.com.

3. Published To Non Root Virtual Host. If y'all wishing to add together an additional spider web log to the domain, perhaps to add your Blogger spider web log to your spider web site, y'all setup an additional virtual host.
   

   blog.mydomain.com. 3600 IN CNAME ghs.google.com.

The "Buy a domain" magician produces an Asymmetrical Configuration. Choice of whatsoever 1 of the iii inward a higher house models determines what URL y'all may let on the blog.

The published URL, when setup wrong, produces close symptoms.

The published URL is 1 of the close frequent causes of problems. Do non brand whatsoever of these mistakes.

• Only let on to a URL defined past times "CNAME" referral to "ghs.google.com".
  The referral target, spelled properly, is essential.
  
  
  • Only ghs.google.com
  • Not ghs.l.google.com
  • Not www.ghs.google.com
  • Not ghs.blogger.com
  • Not ghs.blogspot.com
  • Not ghs.gogle.com
  • Not ghs.gooogle.com
  • Not whatsoever of a myriad other variations inward spelling.
• Do non let on to a URL defined past times "A" referral to the "216.239.nn.21" servers.
• The "CNAME" referral must target "ghs.google.com", absolutely.
  • Only ghs.google.com
  • Not ghs.google.com.yourdomain.com
  Understand how to define an absolute referral target.
• The "CNAME" referral must target "ghs.google.com", directly.
  • Only ghs.google.com
  • Not yourdomain.com
  Do non target the domain root, or whatsoever other indirect address.
• Understand how to define a referral host.
• Only let on to a referral host using lower illustration letters.

The domain root, inward an asymmetrical DNS model, is similarly crucial.

If y'all purpose an asymmetrical DNS addressing, target entirely the 4 Google servers, equally "A" referrals.

 216.239.32.21 216.239.34.21 216.239.36.21 216.239.38.21 

Use of these 4 servers is rattling specific. Do non brand these mistakes.

• Do non render these servers equally "nameservers", equally y'all setup your domain. If your registrar is demanding "nameservers", y'all request to check your annotation / receipt, as well as ensure that y'all did non but pay for "Name Registration", instead of for "DNS Hosting".
  
  You request your ain "DNS Hosting", equally Google does non render DNS hosting for somebody domains. If necessary, purpose a (free) third political party DNS hosting service.
• Do non let on to the URL referred to the 4 servers. Those servers may entirely hold out used to redirect the secondary URL to the published URL.
• Do non include a server provided past times your registrar - either substituted for whatsoever 1 of the four, or inward improver to the four.
• Do non include whatsoever of the three before used Google servers.
  

  mydomain.com. 3600 IN H5N1 64.233.179.121
  mydomain.com. 3600 IN H5N1 66.249.81.121
  mydomain.com. 3600 IN H5N1 72.14.207.121

  Those servers are offline - gain non include them inward your DNS addresses.
• For best results, always include all 4 servers.
• Understand how to properly define a referral host.
• Though the domain origin must hold out setup, properly, for a stable custom domain.

The "CNAME" to "ghs.google.com" is sufficient, for the published URL.

If y'all purpose "CNAME" referral for whatsoever host, entirely purpose 1 "CNAME" referral - gain non add together a complementary "A" or "CNAME" address, for that host.

 www.mydomain.com. 3600 IN CNAME ghs.google.com. 

This is all that is needed.

• A mo "CNAME" referral is non helpful - as well as is not supported past times many registrars.

  www.mydomain.com. 3600 IN CNAME ghs.google.com.
  www.mydomain.com. 3600 IN CNAME ns1.googleghs.com.

  This is non helpful.
• An additional "A" referral is non helpful - as well as is non supported past times many registrars.

  www.mydomain.com. 3600 IN CNAME ghs.google.com.
  www.mydomain.com. 3600 IN H5N1 64.233.179.121

  This is non helpful.
• You will, however, in all probability request a mo "CNAME" for domain ownership verification. You cannot bypass this requirement - when it is required.

If y'all must setup the domain yourself, instead of using "Buy a domain", learn the rules - none of them are optional. If y'all follow the rules, y'all receive got a much improve run a hazard of having a reliable as well as working domain - instead of eventually seeing the good known "Another blog ..." or "404 Server Not Found".

Blogger Limits: Pages - Dynamic As Well As Static

We come across periodic show of the confusion close the differences betwixt dynamic too static pages, expressed every bit boundary uncertainties inwards manages dynamic too static pages too thence transparently, non everybody realises where the limits are.

---

(Update 2014/11): This boundary has been relaxed - but it does non seem to hold upward gone, entirely.

---

Blogger has limited the number of static pages - Pages entries created every bit "Blank page", past times the Pages editor inwards the New GUI.

The boundary on static pages is a resources issue. Static pages require specific resources, pre allocated to every weblog - too increasing the number of static pages, similar increasing the boundary on number of labels, would convey to hold upward made to all blogs. Such resources are limited, simply every bit everything is limited, inwards around way.

Learn the dissimilar possibilities for dynamic too static pages - too your weblog has a virtually limitless potential for expansion.

Even if you lot tin convey only upward to xx static pages, you lot tin index an unlimited total of dynamic pages, using the Pages gadget, too adding "Web address" entries. You are limited only past times the infinite used past times the weblog header tabs, or past times the sidebar based gadget.

• Individual posts.
• Label searches.
• Archive indexes.
• Other blogs too websites.

There is no limit, for dynamic pages. Those items are dynamic, because 1 time you lot add together a dynamic entry, it links to content that is constantly changing, without the remove to operate the Pages editor.

So sympathise the differences betwixt dynamic too static pages - too know where the limits are, too where they are not.

After Setting Upwards Your Custom Domain Dns Addresses, Ever Verify Your Work

So many problems alongside custom domain publishing showtime alongside incorrectly setup DNS addresses. Sometimes the problems showtime alongside misunderstanding almost the stiff requirements of DNS addresses, other times misunderstanding almost how to purpose the Domain Manager tools provided - as well as sometimes the registrar gets involved, as well as causes problems.

Many times, I'll offering advice inward Blogger Help Forum: Something Is Broken, as well as the reply volition signal the confusion.

Here's a screenshot of my settings - I can't run into a problem!

or

I but got my registrar to setup the DNS addresses, every bit you lot gave me. Surely, they are right?

But nosotros diagnose the problem, as well as honour that the addresses are even as well as thus wrong.

In business, nosotros larn of the importance of using good known, touchstone testing procedures. People setting upwards a custom domain would produce good to larn this concept, also.

I accept a various assortment of online tools, which I purpose for diagnosing custom domain publishing problems. Here are 3 (as always, inward alphabetical order), which I purpose to examine as well as verify DNS addresses.

• Kloth Dig.
• Name.com Dig / Who.Is Lookup.
• WebMaster Toolkit Dig.

Each tool complements the other ii - none of them are a replacement for the other two.

Kloth Dig

• Lets you lot re-create as well as glue the output, easily.
• Lets you lot Dig the domain root, or whatsoever specific aliases.
• Lets you lot choose what host to perform the Dig.

Name.com Dig / Who.Is Lookup

• Lets you lot cheque results promptly, non waiting for TTL to expire.
• Lets you lot reference the outcome using an included URL.
• Lets you lot produce a Who Is lookup, to complement the Dig.

WebMaster Toolkit Dig

• Lets you lot re-create as well as glue the output, easily.
• Lets you lot Dig the domain root, or whatsoever specific aliases.
• Lets you lot reference the outcome using an included URL.

Prompt Verification Is Essential.
When you lot brand changes to the DNS addresses, you lot volition desire to cheque your results, promptly - waiting for DNS cache to expire, varying according to TTL, causes confusion. The Name.com Dig accesses the domain master copy server, as well as thus you lot tin strength out by as well as large run into results promptly. To cross cheque the Name.com Dig, you lot tin strength out purpose the Kloth Dig - as well as reference the domain master copy server, explicitly.

All Domain Hosts Must Be Verified.
When you lot brand changes to a Non Root Virtual Host, you'll demand to Dig the results. Both Kloth as well as WebMaster Toolkit allow you lot specify the host name, to target inward the Dig, as well as thus you lot tin strength out target whatsoever host - non but the domain source as well as "www" aliases.

Ability To Copy And Paste Results Is Useful.
It is useful to re-create as well as glue the results from whatsoever Dig transaction. Both Kloth as well as WebMaster Toolkit Digs render results that are non tabular array bound, as well as tin strength out hold out easily copied as well as pasted.

Ability To Reference The Result In The URL Is Useful.
It is useful to salvage a i click link to cheque Dig results, to avoid having to repeatedly glue or type a domain URL to hold out checked. Both Name.com as well as WebMaster Toolkit render results that tin strength out hold out checked past times clicking on a link, which you lot tin strength out bookmark.

A WhoIs Lookup Is Useful
Many times, the domain status, examined using a WhoIs lookup, provides an essential clue. Both when a domain buy is unsuccessful, as well as when a domain registration has expired, a Name.com Who.Is Lookup volition atomic number 82 to the occupation diagnosis.

Each of these tools render vital details as well as features, that the others produce non provide. And each of these tools, used properly, tin strength out assist individual to avoid posting inward Blogger Help Forum: Something Is Broken, frantically hollo for for help.

>> Top

Referer Spam Cannot Locomote Blocked, Immediately

That is the unfortunate truth.

Every day, around novel fellow member of it does non reverberate existent traffic, the side yesteryear side query is

So why doesn't Google block it? Why should I accept it polluting my Stats displays, as well as endure unable to let on actual traffic inward my counts?

and the unfortunate truth is precisely that Google cannot block it, because it's non significantly unlike from normal traffic - as well as the insignificant departure is non easily detected.

Referer spam cannot endure identified, because it is identical inward construction to legitimate Stats pageviews - as well as because its content changes, constantly.

What does a normal spider web log page "pageview request" hold back like?

When yous click on a link from, say, a postal service inward Blogger Help Forum: Something Is Broken, to this article, your estimator sends a unmarried message to the Blogger server, containing 3 essential details.

1. The IP address of your computer.
2. The URL of a forum discussion, which contains a link to this article.
3. The URL of this article.

From the message, the Blogger server creates a server activeness record.

1. An IP address.
2. The URL of the page containing a link to the webpage requested.
3. The URL of the webpage requested.

That server activeness record, inward the Stats display for the blog, is known equally a "pageview".

Finally, the Blogger server starts sending spider web page content dorsum to your computer, as well as thence your estimator tin display this article to you. As the webpage content is sent dorsum to your computer, your estimator receives, as well as displays, the received content - as well as asks for to a greater extent than content.

What does a referer spam "pageview request" hold back like?

Simple enough? So, what is referer spam? Simply, a unmarried message from a spammer computer, to the Blogger computer, containing 3 essential details.

1. An IP address - possibly, but non predictably, of their computer.
2. The URL of the website existence pimped (the spammed website).
3. The URL of the spider web log existence spammed (your blog).

From the message, the Blogger server creates a server activeness record.

1. An IP address.
2. The URL of the page (supposedly) containing a link to the webpage requested.
3. The URL of the webpage (supposedly) requested.

That server activeness record, inward the Stats display for the blog, is likewise known equally a "pageview".

Finally, the Blogger server starts sending spider web page content dorsum to the IP address provided. If the IP address does refer to the spammers computer, what is received is precisely ignored. The spammer estimator moves on, as well as sends around other imitation pageview message to around other server - maybe referencing this blog.

The "pageview request" is generated, earlier referer spam discontinues.

The employment is precisely that no spider web server tin let on a message from a customer computer, that results inward a reply that is precisely ignored. Web traffic is lossy, as well as clients drib offline constantly. Even if the reply could endure detected equally ignored, the ignored asking mightiness even as well as thence reverberate legitimate activity, initiated yesteryear a customer that forthwith went offline.

There is precisely no fashion for Google to block the spam - because the spam is precisely i message that results inward a response, yesteryear the Blogger server, that is later on ignored yesteryear the customer computer.

That's it.

So why can't Google block the numbers generated yesteryear may non actually stand upwards for actual spam. They can, precisely equally easily, reverberate intense, legitimate activity - or perhaps a devious attack against a legitimate website.

Google tin solely let on referer spam inward context, against multiple blogs.

Specific pageview counts as well as details are observed inward context - are blocked solely after the same activeness is observed against multiple blogs, over long periods of fourth dimension (similar, inward concept, to the numbers are removed, retroactively.

All of this is a uncomplicated unavoidable side effect, of spider web log owners needing site activeness figures that are not affected yesteryear script filtering yesteryear the spider web log readers, complicated yesteryear fraudulent activeness yesteryear hackers as well as spammers.

Referer spam is non unique to Blogger - it is precisely tuned to abuse Stats logs.

Please regime annotation that referer spam did non outset amongst Blogger - it's an Internet broad problem. Even though it appears mindless as well as random, around of it is craftily designed as well as executed.

For a comprehensive hold back at how referer spam works, exterior Blogger, encounter Wikipedia: Referer spam.

The employment hither is threefold.

1. Too many spider web log owners obsess over raw pageview counts.
2. Too many spider web log owners produce non sympathise the origins of referer spam.
3. Too many spider web log owners are non interested inward agreement the existent problem.

That's it!

Better Top Away Into The Novel Blogger Gui Before Long - Together With Country Blogger What Problems You Lot Find

The New Blogger GUI (2011) was pushed out, during the yesteryear week, to a issue of spider web log owners - together with the complaints are showing upwards inward Blogger Help Forum: Something Is Broken. Some are polite.

Please, Blogger - allow us the choice of staying amongst the quondam format.

and approximately less polite

Are y'all listening Google? Your novel interface SUCKS!

Only i matter is obvious - many people, all of a precipitous finding themselves using the New GUI, produce non similar the New GUI.

Unfortunately, at that topographic point are existent reasons why the New GUI has been developed - together with those reasons are non going to croak away. The New GUI is hither - to stay. Right now, comprehensive together with objective criticism is needed, to convince Blogger to croak far ameliorate - earlier they withdraw the Classic GUI altogether.

Both major together with tike features, developed of late yesteryear other groups inward Blogger, together with yesteryear other divisions of Google, are integrated into the New GUI.

• Blogger Dynamic Templates, together with the supporting separation of the Layout together with Template card options.
• Google+.
• Better Post Editor.
• Better back upwards for non BlogSpot (aka "custom domain") publishing.
• Blogs accessed nether Country Code TLD Aliases.

We've seen evidence of all of these efforts, recently.

As long every bit Blogger has to maintain 2 GUI versions, they volition bring to motion slower to maintain both versions working. Staff has to hold out employed to both maintain both versions, together with maintain the diverse features inward both versions working together. As long every bit at that topographic point are 2 versions of the GUI, approximately staff, that should hold out improving the New GUI, is going to hold out busy supporting the Classic GUI.

One of the causes, of approximately New GUI problems, involves people switching dorsum together with forth betwixt the 2 GUIs, to ameliorate purpose the features that they prefer. If y'all bring observed problems amongst your spider web log recently

• Custom Domain Publishing.
• Post Editor paragraphing.
• Post Editor advance postal service scheduling.

you are perhaps observing a work caused yesteryear conflicting code inward the 2 GUI versions. Until everybody is using the same GUI version, the conflicting code volition croak on to drive problems - together with approximately Blogger Support staff volition bring to pass fourth dimension identifying together with patching the problems.

Yet, at that topographic point are features that are acquaint inward the Classic GUI, that need to hold out added to the New GUI, earlier substantial numbers of people tin laissez passer on notice foremost using the New GUI. In guild to position those features, plenty people bring to foremost using the New GUI - together with allow Blogger know what features are missing, that involve to hold out provided, immediately.

We bring a work rollup discussion, currently hosted inward Blogger Help Forum: Something Is Broken, where nosotros am actively soliciting comments from people who bring tried the New Blogger GUI. Please maintain your comments brief, polite, together with on topic.

Just bear witness to brand your comments before it's also late - when The New Blogger Interface becomes The Blogger Interface.

>> Top

Before Publishing Dorsum To Blogspot, Become The Dns Addresses Right

One problem, occasionally seen inwards Blogger Help Forum: Something Is Broken, involves spider web log owners preparing to re role their custom domain for publishing their website - together with who instantly involve to issue their Blogger spider web log dorsum to BlogSpot.

I involve to reuse my domain for my website - only when I travail to re issue my blog, I hold seeing

Another spider web log is already hosted at this address.

How tin I larn my spider web log dorsum online?

When nosotros expect at the domain, together with the DNS addresses, nosotros run into the domain pointing to the website, already. And this is where many custom domain publishing problems start.

Any fourth dimension yous brand whatever alter to a blog, that involves custom domain publishing, the changes volition become much to a greater extent than smoothly amongst the domain properly pointing to the blog.

Whether yous are setting upwards a novel custom domain publishing, changing a custom domain publishing, or perhaps removing a custom domain publishing, the publishing procedure plant much meliorate amongst the domain properly redirected to the Google database.

One of the causes of the mysterious message

Another spider web log is already hosted at this address

comes from the domain non beingness properly redirected to the Google servers. When the Blogger re publishing procedure can't conk on because the domain DNS addresses are non correct, the procedure terminates amongst an error. Whenever whatever database alter terminates amongst an error, it's e'er possible that the procedure may non build clean upwards afterward itself earlier ending - together with artifacts (aka broken pointers) volition live on left behind inwards the database.

The side past times side fourth dimension that yous travail to re issue the spider web log - or when yous (or your readers) travail to stance the spider web log - yous (or they) volition see, notwithstanding again

Another spider web log is already hosted at this address.

or an alternate

Server Not Found Error 404

When that happens, yous accept alone 1 alternative - recycle the domain settings - together with pray to the deity of your choice.

The latter processes are non known to live on 100% effective. The best way to bargain amongst them is to never bargain amongst them - to non start past times causing a problem. That agency to e'er hold the domain DNS addresses righteous, whenever maintaining a custom domain published blog.

If yous are going to role your domain for a non Blogger website, e'er publish your Blogger spider web log dorsum to BlogSpot, first. Then, verify the condition of the blog. Finally, together with amongst no problems discovered, alter the DNS addresses.

Adding An Html / Javascript / Text Gadget?

An interesting combat of confusion is seen, occasionally, inwards Blogger Help Forum: Something Is Broken.

I added a gadget using code from a tertiary political party website - but the novel gadget shows the code, instead of the gadget content, when I persuasion my blog!

This is someone who was confused yesteryear the options offered yesteryear the gadget setup wizard.

When you lot add together an HTML / JavaScript, or a Text, gadget to a blog, you lot tin larn strange results.

"Add a Gadget" provides the "HTML / JavaScript" as well as "Text" gadgets - your choice.

The captions as well as labels inwards the "Configure HTML/JavaScript" or "Configure Text" sorcerer tin survive a combat confusing. From the "Add a Gadget" wizard, you lot tin direct either an "HTML/JavaScript" gadget ("Configure HTML/JavaScript") or a "Text" gadget ("Configure Text").

The "HTML / JavaScript" as well as "Text" gadgets are identical - excepting the title.

Both the "Configure HTML/JavaScript" as well as "Configure Text" wizards purpose the same code - the alone departure betwixt the 2 is the header.

• Configure HTML/JavaScript
• Configure Text

Everything else is the same. Either sorcerer tin practise an "HTML / JavaScript" gadget (in HTML mode) - or a "Text" gadget (in Text mode) - equally you lot wish.

• When the sorcerer is inwards HTML mode, the caption at the upper correct edge of the Content window volition read "Rich Text". Positioning the cursor over "Rich Text" (and noting that the cursor does non alter to a pointer), as well as clicking on "Rich Text", brings upward the Text agency of the wizard.
• When the sorcerer is inwards Text mode, the caption volition read "Edit Html" - as well as clicking on "Edit Html" puts the sorcerer into HTML mode, again.

The championship of the sorcerer does non change, when switching modes.

The header of the sorcerer - "Configure HTML/JavaScript" or "Configure Text" - volition stay equally it was when the sorcerer was opened, ignoring whatever agency changes. The caption, at the upper correct edge of the Content window, is what matters.

• If you lot desire to add together code (HTML / JavaScript), you lot volition desire the caption to read "Rich Text".
• If you lot desire to add together text (Rich Text), you lot volition desire the caption to read "Edit Html".

Being inwards the incorrect agency volition create inconsistent as well as strange results.

If you're inwards the incorrect mode, you'll survive able to come inwards a express total of content - but amongst strange results.

• If you're inwards HTML agency (with "Rich Text" showing), you'll survive able to come inwards text - to a express degree. HTML is only fancy text, amongst tags (special keywords as well as symbols).
• The HTML editor toolbar volition lack a few buttons - as well as using particular characters similar ampersand ("&"), greater than (">") - as well as less than ("<"), volition create random as well as unpredictable results.
• If you're inwards Text agency (with "Edit html" showing), you'll survive able to come inwards the HTML code - but when the spider web log is displayed, you'll come across code (which is exactly text) inwards house of a working gadget.

If you lot exactly added a novel gadget - as well as ended upward amongst visible code, when you lot tried to setup an HTML gadget - directly you lot know why. Similarly, if the "Save" push is directly broken, as well as you lot are trying to add or update a Text gadget.

This is ane of several possible causes of problems seen when adding / updating the HTML / JavaScript / Text gadgets.

Continued Inability To Update The Labels Gadget, Amongst A Large Partial List

In February, nosotros observed that diverse weblog owners were reporting problems amongst updating label too link lists. We setup a occupation rollup inwards Blogger Help Forum: Something Is Broken, where nosotros observed a pocket-size simply pregnant disclose of reports from unhappy weblog owners, unable to update the gadgets on their blogs.

Last month, Blogger Support supposedly resolved the reported problem, too the book of occupation reports dropped significantly. The problem, however, has non been eliminated.

The occupation amongst updating diverse accessory gadgets, initially reported several months ago, is soundless introduce inwards diverse Blogger blogs - though significantly reduced - next an improvement concluding month.

This weblog has a sum of 626 labels defined, inwards the diverse posts. If I desire to spare my readers (slightly) from an excessively long listing of labels, I tin plow over the axe edit the listing too selectively display exclusively pregnant ones. I cannot display all pregnant ones, unfortunately. I currently accept 501 of 626 labels selected for display.

If I edit my label list, inwards "Select labels to show", I tin plow over the axe direct whatsoever 1 of the remaining 125 labels. Having hitting the tiny "Done" caption at the bottom left of the window, I am left amongst "Configure Labels". If I hitting "Save", the before reported occupation continues - the xanthous "Saving ..." flag pops up, too the gadget hangs spell saving.

If I hitting Cancel, too edit the listing again, I tin plow over the axe de direct whatsoever 1 label, too salve the list, successfully - 1 time again amongst just 501 labels selected. Then adding whatsoever 1 label, too attempting to Save 1 time more, the gadget volition 1 time again hang. The bottom occupation is that I tin plow over the axe selectively display 501 labels - too no more.

I accept observed this occupation inwards both Chrome too Firefox (V11 too V12) - too using both the Classic too New GUIs. With upwards to 501 labels selected, no problem. With whatsoever to a greater extent than than 501 labels selected - big problem. During the by month, later I outset observed this problem, I added one-half a dozen novel labels, to accomplish the electrical flow sum of 626. The occupation has express me to 501 selected labels, consistently, regardless of the sum number.

Various reports, inwards both this blog, too inwards [Problem Rollup] Updating Label List Gadget Hangs, signal that other weblog owners are soundless observing this problem. It's becoming increasingly obvious that this occupation soundless exists in

• BlogLists.
• Label Lists.
• LinkLists.

>> Top

Enom Hosted Custom Domains Showing Intermittent Connectivity Issues

We are seeing reports from owners of several Blogger blogs, published to custom domains, of intermittent connectivity problems, reported inward Blogger Help Forum: Something Is Broken.

Recently, I convey been unable to charge my custom domain weblog www.mydomain.com. My browsers (whether Chrome, Firefox, Safari, etc.) all rate me they are "unable to uncovering the server". Various online utilities study problems also. I am able to instruct to Blogger together with my dashboard for the blog, but cypher volition charge the page. All other services on my figurer look to endure working normally.

The work appears to endure somewhat intermittent together with varying across dissimilar ISPs, together with diverse online utilities which I use.

The domains existence reported all look to endure registered amongst eNom - together with at start glance, domain registration appears normal. We convey to create simply about detailed investigation to position a consistent detail, which appears to endure mutual to all individually reported domains.

At start glance, the typical eNom registered domain - fifty-fifty those amongst this reported work - appears to endure normal.

REGISTRY WHOIS FOR mydomain.com  Registrar: ENOM, INC. Whois Server: whois.enom.com Referral URL: http://www.enom.com Status: clientTransferProhibited  Expiration Date: 2013-04-10 Creation Date: 2012-04-10 Last Update Date: 2012-04-10  Name Servers:     dns1.name-services.com     dns2.name-services.com     dns3.name-services.com     dns4.name-services.com     dns5.name-services.com 

The clue to this work is seen inward the concluding sentence, inward the higher upwards example.

The work appears to endure somewhat intermittent together with varying across dissimilar ISPs, together with diverse online utilities which I use.

eNom uses v DNS servers. We tin cheque the output from each of the v servers, using the Kloth online Dig utility, together with specifying each server, inward turn.

• Domain: mydomain.com
• Server: dns1.name-services.com
• Query: H5N1 (IPv4 address)

and repeat for dns2.name-services.com etc.

Running a Dig against each of the v servers, nosotros tin encounter a consistency problem. Here is a re-create of the v Dig logs, concatenated.

-----------------------------------------------------------------------       dns1.name-services.com Dig Log   ; <<>> DiG 9.3.2 <<>> @dns1.name-services.com mydomain.com H5N1  ; (1 server found)  ;; global options:  printcmd  ;; Got answer:  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43536  ;; flags: qr aa; QUERY: 1, ANSWER: 4, AUTHORITY: 5, ADDITIONAL: v    ;; QUESTION SECTION:  ;mydomain.com.  IN H5N1    ;; ANSWER SECTION:  mydomain.com. 1800 IN H5N1 216.239.32.21  mydomain.com. 1800 IN H5N1 216.239.34.21  mydomain.com. 1800 IN H5N1 216.239.36.21  mydomain.com. 1800 IN H5N1 216.239.38.21    ;; AUTHORITY SECTION:  mydomain.com. 3600 IN NS dns1.name-services.com.  mydomain.com. 3600 IN NS dns2.name-services.com.  mydomain.com. 3600 IN NS dns3.name-services.com.  mydomain.com. 3600 IN NS dns4.name-services.com.  mydomain.com. 3600 IN NS dns5.name-services.com.    ;; ADDITIONAL SECTION:  dns1.name-services.com. 3600 IN H5N1 98.124.192.1  dns2.name-services.com. 3600 IN H5N1 98.124.197.1  dns3.name-services.com. 3600 IN H5N1 98.124.193.1  dns4.name-services.com. 3600 IN H5N1 98.124.194.1  dns5.name-services.com. 3600 IN H5N1 98.124.196.1  -----------------------------------------------------------------------       dns2.name-services.com Dig Log       ; <<>> DiG 9.3.2 <<>> @dns2.name-services.com mydomain.com H5N1  ; (1 server found)  ;; global options:  printcmd  ;; Got answer:  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51481  ;; flags: qr aa rd; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0    ;; QUESTION SECTION:  ;mydomain.com.  IN H5N1    ;; ANSWER SECTION:  mydomain.com. 1800 IN H5N1 216.239.36.21  mydomain.com. 1800 IN H5N1 216.239.32.21  mydomain.com. 1800 IN H5N1 216.239.38.21  mydomain.com. 1800 IN H5N1 216.239.34.21  -----------------------------------------------------------------------       dns3.name-services.com Dig Log   ; <<>> DiG 9.3.2 <<>> @dns3.name-services.com mydomain.com H5N1  ; (1 server found)  ;; global options:  printcmd  ;; Got answer:  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9542  ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0    ;; QUESTION SECTION:  ;mydomain.com.  IN H5N1    ;; AUTHORITY SECTION:  com.   3601 IN SOA dns1.name-services.com. info.name-services.com. 2010 10001 1801 604801 181  -----------------------------------------------------------------------       dns4.name-services.com Dig Log     ; <<>> DiG 9.3.2 <<>> @dns4.name-services.com mydomain.com H5N1  ; (1 server found)  ;; global options:  printcmd  ;; Got answer:  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2101  ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0    ;; QUESTION SECTION:  ;mydomain.com.  IN H5N1    ;; AUTHORITY SECTION:  com.   3601 IN SOA dns1.name-services.com. info.name-services.com. 2010 10001 1801 604801 181  -----------------------------------------------------------------------       dns5.name-services.com Dig Log    ; <<>> DiG 9.3.2 <<>> @dns5.name-services.com mydomain.com H5N1  ; (1 server found)  ;; global options:  printcmd  ;; Got answer:  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13658  ;; flags: qr aa; QUERY: 1, ANSWER: 4, AUTHORITY: 5, ADDITIONAL: v    ;; QUESTION SECTION:  ;mydomain.com.  IN H5N1    ;; ANSWER SECTION:  mydomain.com. 1800 IN H5N1 216.239.32.21  mydomain.com. 1800 IN H5N1 216.239.34.21  mydomain.com. 1800 IN H5N1 216.239.36.21  mydomain.com. 1800 IN H5N1 216.239.38.21    ;; AUTHORITY SECTION:  mydomain.com. 3600 IN NS dns1.name-services.com.  mydomain.com. 3600 IN NS dns2.name-services.com.  mydomain.com. 3600 IN NS dns3.name-services.com.  mydomain.com. 3600 IN NS dns4.name-services.com.  mydomain.com. 3600 IN NS dns5.name-services.com.    ;; ADDITIONAL SECTION:  dns1.name-services.com. 3600 IN H5N1 98.124.192.1  dns2.name-services.com. 3600 IN H5N1 98.124.197.1  dns3.name-services.com. 3600 IN H5N1 98.124.193.1  dns4.name-services.com. 3600 IN H5N1 98.124.194.1  dns5.name-services.com. 3600 IN H5N1 98.124.196.1  ----------------------------------------------------------------------- 

Examine the Dig logs from "dns3.name-services.com." together with "dns3.name-services.com.". See the reply from those servers, which returns exclusively an "SOA" for the ".com" Top Level Domain? This is consistent of a domain, improperly setup past times the registrar. In the cases reported inward Blogger Help Forum: Something Is Broken, my reply is simple.

In your case, servers #3 together with #4 create non look to properly recognise your domain. Any online service, quest either server #3 or #4 for your domain addresses, volition likely convey problems. This may explicate your inconsistent access problem. As the registered domain owner, you lot demand to contact eNom Customer Support. Show them the Dig logs from the v servers, together with inquire them why servers #3 together with #4 seem to convey a work serving your DNS addresses.

The work appears to involve domains setup on 4/9/2012 - 4/10/2012. Hopefully, plenty domain owners volition study their problems to eNom Customer Support, then this work tin endure investigated together with resolved.

---

(Update 6/18): With a modest but a useful diagnostic tool, to analyse DNS inconsistencies similar this.

---

>> Top

Mass Confusion Caused Past Times Legacy Concern Human Relationship Migration

In 2012, Blogger started the side yesteryear side stage of the Legacy Account migration process.

For several days, nosotros saw majority confusion, inwards Blogger Help Forum: Something Is Broken.

Why am I getting this email? Is it a scam?

and

I can't migrate my account!

and

I migrated my account, too my blogs disappeared from my dashboard!!

The people targeted inwards the email were registered owners of legacy (pre 2006) Blogger accounts, created earlier Blogger started using Google (email address based) accounts.

The confused owners are like to the ones amongst whom nosotros accept been dealing for several months, unable to find access to their long dormant Blogger / Google accounts.

Many practice non recollect creating accounts, others don't recollect the login details, which are essential to spider web log control.

Both the spider web log owners, too Blogger, contributed to the confusion.

The confusion was caused jointly yesteryear Blogger, too yesteryear the spider web log owners. And, it was not a surprise, to Blogger Support.

The confusion started amongst the history of the migration.

• In 2007, Blogger offered the chance to transfer command of owned blogs, to a novel Google based account, when mortal attempted to login to their legacy Blogger account.
• People never logging inwards to Blogger afterwards 2007 never got the offering to migrate.
• Some people elected to non migrate - but setup novel Google accounts too manually transferred command of their blogs - too left some legacy accounts inactive too without whatever owned blogs.
• Last year, Blogger warned people that the terminate of life, of the legacy accounts, was inevitable.

  For a number of technical too operational reasons, we’ve decided to finally terminate our back upward for migrating legacy accounts too blogs afterwards December 5th, 2011. So if y'all accept a Blogger concern human relationship too haven’t logged inwards since 2007, y'all volition lose access to the concern human relationship too associated content permanently unless y'all update to the Google Account organization earlier December 5th.

• Last week, Blogger took the side yesteryear side step.

  You are receiving this message because your e-mail address is associated amongst an unmigrated legacy Blogger account. As nosotros announced inwards Apr of lastly year, legacy accounts volition no longer live accessible afterwards May 30th, 2012 unless they are updated to the Google Account system. Any spider web log content associated amongst this concern human relationship volition also live unmodifiable afterwards that date.

• The emails went to registered owners of all unmigrated legacy accounts, whether or non whatever concern human relationship owned a blog.

The confusion was magnified yesteryear issues caused yesteryear the diverse spider web log owners.

• Blogger insists on making it slow to practice a Blogger account, oftentimes resulting inwards non intentional creation of multiple Blogger accounts. Some people, for instance, may accept created Blogger accounts to post comments, on other blogs.
• Some people receiving the e-mail had stopped using Blogger, long ago.
• Other people had continued using Blogger, but amongst newly created Blogger accounts - too only ignored the unused legacy accounts.
• Many people, overlooking the fact that the migration had started inwards 2007, became unhappy that they were given exclusively 1 calendar month to conclude what they had been given, to appointment - v years.
• Too many people, non having used their legacy accounts since 2006, were unable to recollect the concern human relationship advert or password, too were forced to purpose the "Forgot your password?" wizard.
• Some people, anxiously awaiting the arrival of the password reset email, constitute that this critical e-mail is subject to e-mail spam filters - too now, to email spoofing filters (and the ii are non the same).
• Some people managing to consummate the migration - but amongst their blogs owned yesteryear a dissever (newer) Google based Blogger concern human relationship - watched inwards horror equally their blogs appeared to disappear from their dashboards. The migration created a novel account, leaving their of import blogs owned yesteryear their previously created Blogger / Google account, which became inaccessible to them.

The confusion continued, amongst multiple scenarios.

The history, addition the issues, resulted inwards several scenarios - each resulting inwards an unhappy concern human relationship owner.

• Owners amongst a migrated previously legacy Blogger concern human relationship (created inwards 2007), too 1 or to a greater extent than un migrated legacy Blogger accounts. These people accept 1 or to a greater extent than legacy Blogger accounts (that they don't know about), addition an already migrated previously legacy concern human relationship (that can't live migrated, again).
• Owners amongst a Google based Blogger concern human relationship (created inwards 2007), too 1 or to a greater extent than un migrated legacy Blogger accounts. These people accept 1 or to a greater extent than legacy Blogger accounts (that they don't know about), addition a Google based Blogger concern human relationship (that can't live migrated).
• Owners amongst a unmarried un migrated legacy Blogger account, unable to migrate because of forgotten concern human relationship advert or password. These people accept a legacy Blogger concern human relationship (that tin live migrated, if they know the concern human relationship name, too the password).
• Owners amongst a single, newly migrated legacy Blogger concern human relationship (created this week, amongst no blogs), too a previously migrated or created Google concern human relationship (created inwards 2007, amongst the owned blogs). These people are straightaway logged inwards to Blogger amongst a novel Blogger account, too cannot access their blogs, owned yesteryear their previous Blogger account.

The unhappy recipients of the email, next the instructions provided to them, posted their complaints inwards Blogger Help Forum: Something Is Broken.

If y'all accept questions, delight see our Help Forum at http://www.google.com/appserve/mkt/OKddNnCN05400K too practice a message amongst [legacy Account] inwards the dependent land line.

Confusion was magnified yesteryear forum complaints, too inability to help.

The confusion spread, equally the forums became saturated yesteryear the complaints. Not all complaints used the "[legacy Account]" tag, suggested inwards the instructions. This motivated diverse forum helpers to purpose fuzzy processing techniques inwards sorting diverse forum complaints, too some non legacy issues were treated equally legacy issues. Other legacy issues were overlooked, inwards the book of posts.

Blogger Support, becoming aware of the numbers of complaints, created a legacy Account FAQ, too started answering questions, posted inwards the FAQ. And the frustration became expressed inwards various FAQ responses.

This is clearly non working out good for Blogger. In the truthful concern world, heads whorl when fails are too thence epic.

This spider web log possessor is overlooking the history too the issues, too making no acknowledgement of his contribution to the problem.

---

(Update 2012/04/30 10:00): Blogger Support has straightaway provided a form, for any legacy concern human relationship possessor to use, to asking details.

---

Mass Confusion Caused By Legacy Account Migration


Challenges Created By Legacy Account Migration

Blogger Provides Details Close Un Migrated Legacy Accounts

Blogger Support, inwards observing the confusion caused past times the recent email most unmigrated legacy Blogger accounts, has taken activity to trim down the confusion.

For the people unsure or unaware of what un migrated legacy accounts they may have, they at nowadays have got a "Blogger legacy delineate of piece of employment organisation human relationship information request" form. It's a really uncomplicated course of report - simply you lot volition hold upward expected to practice patience, earlier you lot have actual detail.

Retrieving details most un migrated legacy accounts is really simple, for whatever delineate of piece of employment organisation human relationship owner, having received e-mail most an "unmigrated legacy Blogger account".

Provide the e-mail address, where you lot received the "unmigrated accounts notice".


You similar a shot larn a uncomplicated acknowledgement.


The procedure of retrieving the legacy delineate of piece of employment organisation human relationship details is non automated. Once you lot submit your e-mail address, in addition to larn the uncomplicated acknowledgement, you lot may have got to hold off two or three days, earlier you lot larn e-mail alongside the anxiously awaited details. But you lot have got a calendar month to larn the migration completed.

So larn started, this calendar week - in addition to larn this component subdivision of your life out of the way.

The Limits Inward Your Blogger Blog

One interesting question, seen occasionally inward Blogger Help Forum: How Do I?, seems to focus non on what tin forcefulness out survive done - simply on what can't.

What are the limits, that apply to my Blogger blog?

Some people are accustomed to dealing amongst resources limits, imposed on websites hosted past times paid hosting services, which meter service based on bandwidth together with storage infinite used past times a spider web log or website.

Blogger / Google does non pass fourth dimension monitoring our blogs, together with what resources nosotros use. Neither bandwidth or storage size are limited. However, at that topographic point are some limits on the content, which may limit increase of our blogs. If we're aware of these limits, nosotros tin forcefulness out travel around them.

There are no existent limits on resources, used past times our blogs. There are limits on how nosotros role our blogs, though.

Auto Pagination is a network resources limiting feature which dynamically decides how much of our blogs tin forcefulness out survive made visible to our readers, at 1 time. Use of the new, dynamic templates tin forcefulness out avoid limits imposed past times auto pagination.

Picasa, the Google photograph hosting service, does accept a bound on storage space. You tin forcefulness out pay a modest fee for additional storage infinite - or you lot tin forcefulness out role whatever of diverse tertiary political party photograph hosting services.

It's non technically possible to accuse our readers for access or role of Blogger services - together with Blogger / Google has, at to the lowest degree inward the past, specifically forbidden us to accuse for role of their services. We are explicitly forbidden against using a Blogger spider web log to brand money, using adult content.

Do non role Blogger every bit a agency to brand coin on adult content. For example, don't exercise blogs where a pregnant per centum of the content is ads or links to commercial porn sites.

Besides the existent effects of auto pagination, together with photograph storage limits, at that topographic point are a few well defined limits together with requirements, which touching on Blogger spider web log content together with usage.

• Age. Blogger draw of piece of occupation organization human relationship holders (and thus, spider web log owners) must survive accurately province your birthdate, when setting upwardly a Blogger account. Google has a to a greater extent than flexible historic flow policy, which varies past times province together with past times product.


• Blog Content. Each spider web log page - unmarried post, archive page, or principal page ing - tin forcefulness out accept a maximum of 1MB of spider web log content. If you lot care most your readers at all, this bound volition survive pretty difficult to reach. Use common feel most the content of the blog. Auto Pagination automatically limits the expose of posts that volition display, on 1 physical page.


• Blog Creation Count. There are genuinely several limits, which bargain amongst excessive spider web log creation - some may involve action past times other people, affecting your personal mightiness to exercise novel blogs.


• Blog Following Count. You tin forcefulness out Follow a maximum of 300 blogs, nether 1 Blogger account.


• Blog Membership Count. Influenza A virus subtype H5N1 world spider web log tin forcefulness out accept up to 100 members total - including the owner, plus administrators together with authors. Influenza A virus subtype H5N1 private spider web log has the same bound - which includes designated readers.


• Blog Ownership Count. You tin forcefulness out setup a maximum of 100 blogs, nether a unmarried Blogger account. I passed this bound a piece ago, together with then I accept to rename diverse attempt out blogs, when I setup a novel test.


• Comment Length. Comments tin forcefulness out survive no to a greater extent than than 4,096 characters long.


• Image (Photos / Pictures) Storage. All images / photos / pictures, uploaded using the "Insert image" push clit inward Blogger post service editor, are hosted past times Picasa. See Picasa Help: Free storage limits for details on their limits. See Picasa Accounts: Picasa Web Albums Storage Usage, at whatever time, to banking concern stand upwardly for electrical flow use, nether your Google account.


• Labels. Each spider web log post service tin forcefulness out accept a amount of 200 characters of labels, including " " together with ",". Each post service tin forcefulness out accept a maximum of xx labels, together with each spider web log tin forcefulness out accept a maximum of 5,000 labels.


• Posts. There is no bound on the expose of posts inward a blog. If you lot role labels, you lot volition likely meet a label limit, every bit you lot add together posts, when the spider web log becomes exceedingly large.


• Private Blog Membership. Influenza A virus subtype H5N1 private spider web log tin forcefulness out accept up to 100 members - including administrators, authors, together with designated readers (aka "Guests"). This expose is not e'er available to all blogs. If you lot require to distribute content to to a greater extent than than 99 carefully chosen friends, you lot tin forcefulness out use Google+ together with 1 or to a greater extent than express membership Circles.


• Static Pages (aka "Pages"). You may accept whatever expose of static pages inward whatever spider web log - the limit, which used to survive 20, was lifted inward 2014. You tin forcefulness out index whatever expose of "Pages" every bit "link address" entries, together with link to label searches, private posts, together with other blogs together with websites.


• Video Size. Using Blogger post service editor, you lot may upload videos no larger than 100MB.

Blogger Help: What are the limits on my Blogger account? provides a to a greater extent than comprehensive list, and, to a greater extent than importantly, points out the limits that exercise non exist. Yet this article is non completely authoritative; at that topographic point are a span sections at that topographic point that deport updating. For Google services that require storage, you lot tin forcefulness out proactively monitor storage usage using the "Basic storage usage" wizard.

For additional together with upwardly to appointment advice, you lot may desire to periodically reference Blogger Content Policy, together with Google Terms of Service.