Subscribe: The Real Blogger Status
Added By: Feedage Forager Feedage Grade A rated
Language: English
blog owners  blog  blogger  blogs  content  dashboard  domain  error  https  new  page  pages  posts  publish  search 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: The Real Blogger Status

The Real Blogger Status

What Blogger won't tell you

Updated: 2018-03-22T22:19:19.797-07:00


Edited Posts Will Not Produce Updated Newsfeed Content


I've written a few posts about editing post content - and discuss clearing cache after editing, to see updates.Generally, my posts reference cached posts content. Sometimes, blog owners need to clear cached feed content, in addition to / instead of clearing cached post content.There is a difference between post content, and newsfeed content - and how both are cached. Newsfeed cache is not as frequent a concern.When we provide instructions to clear cached blog content, we reference browser cache.Clear cache - then restart the browser, and check again.or maybeClear cache, cookies, and sessions (yes, all 3) - then restart the browser, and check again.Posts, updated after published, may create a problem with the posts newsfeed. In some cases, updated posts may create an "out of sync" condition with the posts newsfeed, as well as the displayed content.If comparing post content and feed content is important, you need to synchronize the newsfeed with the posts. This will restart the newsfeed - and sync it with the posts.Deactivate the blog feeds.Publish a post - or delete a recently published post.Reactivate the blog feeds.Activate / Deactivate the blog feeds, using the "Allow Blog Feed" wizard.The "Allow Blog Feed" wizard, on the dashboard Settings - Other page, in the "Site feed" section, is used to activate and deactivate the newsfeeds.Look for "Site feed", and "Allow Blog Feed"."Site feed" is on the Settings - Other dashboard page.Open the drop down menu, and note the current setting. If you have "Custom" selected, dig deeper.There are a few selections, in "Allow Blog Feed". For consistent results, note what you have before Step #1 - and re select them after Step #3.This blog, like many others in Blogger, is "Always Under Construction".This post, like many earlier ones, was just published. Now, I plan to spend many long hours, reorganising and tweaking the content, phrasing, spelling, syntax - and correcting typos.If you wish, you can subscribe to any of several posts newsfeeds - and compare the newsfeed content in each, with the displayed posts content. The older any post is, the more changes will be made.The more revisions I make, the less this post, and the posts feed, will match when compared. Check it, for yourself.Maybe one day, I will need the feed, in this blog, be accurately updated to compare more closely to the updated posts. Many of my posts double in size, even after post publish edits are "complete".If you use email, and other feed subscriptions, to read new posts in this blog, you may be missing out on interesting details, added long after posts are published.Newsfeed content is published once, as each post is published.Post content may be out of sync with feed content, because post content and feed content is not updated at the same time.You can update your posts, when you wish. Newsfeed updates are published when the posts are published - and the cached newsfeed is not updated, when you edit a post after it is published.When you synchronise published posts content with displayed content, you generally clear browser cache. Newsfeed cache is not in the browser - so the latter instructions won't help with newsfeed cache.That is the basic procedure for syncing the blog content, and feed content. You may have other concerns, though, that might complicate the above procedure.The procedure is exciting - but painless.I initially published this post, without any photos - and we see my Reading List, an hour ago.And my Reading List, after I restarted my blog feed.It took all of 5 minutes, including making screen prints of my Reading List - before and after, to restart the newsfeeds.As always, I'll suggest that you Follow this post - and observe the changes. And watch for changes (unlikely) to the newsfeed.Many #Blogger problems, when being diagnosed, start with advice to clear browser cache (maybe, cache, cookies, and sessions). Not all problems involved the published posts - some involve the posts feed.You can't clear feed cache, as you can browser cache, because newsfeed content is not cached in the bro[...]

Publish To Your Readers In Multiple Languages


Some blog owners speak / write in multiple languages - and want to interact with their different readers, separately, in each different language.Blogger, and Google, support the need for publishing multiple blogs, each written in a different language. The "hreflang" tag, added to a blog, identifies other blogs, published to different languages, with identical or similar content.There are three ways to provide content, in multiple languages.Publish one blog, with posts published in different languages.Publish one blog, and add the Google Translate gadget.Publish multiple blogs, one language / blog, linked using "hreflang".You can publish a single blog with multiple posts written in different languages - if you wish.Mixing multiple posts in different languages creates a compromise.One blog, mixing posts written in different languages, will be a compromise. Each different world language has its own character set, phrasing, spelling, syntax, and other characteristics.If you publish extensively, you will get better results publishing multiple blogs, each blog with content in one language. Your readers will appreciate reading a blog, that's published in one language - their own language.Best results come from multiple blogs, in one language for each blog.Blogger lets us indicate a language for any blog, in Settings - Language and formatting. One blog == one language.If you want to publish content in multiple languages, and have everything properly indexed by the search engines, you can create an "hreflang" blog cluster - with each blog published in its own language.To get the best result from "hreflang", you publish similar content, equally to each blog - and add "hreflang" tags identically to each blog.If I was tri-lingual, I could publish a set of blogs in English, French, and Spanish.Si j'étais trilingue, je pourrais publier un ensemble de blogs en anglais, français et espagnol.Si fuera trilingüe, podría publicar un conjunto de blogs en inglés, francés y español.I could publish three blogs to BlogSpot.en-blogging-nitecruzr.blogspot.comfr-blogging-nitecruzr.blogspot.comes-blogging-nitecruzr.blogspot.comIn the template header, for each blog, I would add three complementary tags.Multiple blogs, properly intercnnected, gives improved search results.As any one blog in the cluster is being indexed, the "href=" in the tags links to the other two blogs - just like any three blogs being cross linked. This gives search indexing between all three blogs, equally.For improved search reputation, based on three "identical" blogs, this technique can't be beat.You can publish one blog, indexed in one language, and translated when needed.You don't have to use "hreflang", to publish content written in multiple languages. If you only want to write in one language, and let readers to read your blog in their own language, you can use Google Translate.Look in the sidebar, of this blog. Google Translate ("Translate Me") lets every world resident read a blog in their own language - when they select their language.Just add a Google Translate gadget to your one blog, using the "Add a Gadget" wizard, on the Layout dashboard page. Each reader, surfing to your one blog, can use the gadget to translate to their language, as necessary - as long as they:Understand the gadget header "Translate Me" (or however you name your gadget).Know to use the "Select Language" pull down list.Know how to locate their own language in the list.The "Google Translate" gadget is labeled in English. The French people use "français" when describing their naive tongue - and call our language "Anglais", not English.The language list, in French, will be in a different order. Other languages will be even more challenging. If you examine a language list, on a[...]

AdSense, Blogger Blogs, And Social Network Sharing


Many people who publish blogs also have FaceBook pages - and one of the easiest ways to get traffic, to the blog, is to share the blog to a FaceBook page.Some people want money for publishing their blogs. AdSense is a very popular way to earn from publishing. AdSense produces the best results, with lots of readers to read the blog, click on the ads, and buy the products and services advertised.FaceBook, and similar social network sharing services, is not the best choice for advertising a blog that uses AdSense ads.You can share your blog through social networks like FaceBook, if you wish.If you emphasise social network sharing when advertising your blog, you will have a large, unfocused following population. Many people who follow you won't be interested in the advertisements on the blog - and won't buy the products and services advertised.FaceBook and Twitter can provide traffic - but is it the right traffic?Some people will use social sharing, and urge their friends toRead my blog - and Like my FaceBook page!This will simply send a lot of traffic to the blog, to have people "Like" their FaceBook page. AdSense calls this invalid / low quality traffic - and rejects such blogs from their programme.Social networking, used to share a blog, sends lots of traffic to the blog - but is the traffic useful?.Google+, and the search engines, can provide relevant traffic. To develop a focused reader audience, publish informative, interesting, relevant, and unique posts. That encourages search engine activity - and gets search related traffic. If you emphasise search related traffic, you spend less time using FaceBook, and asking people to "Like" your blog.Search related traffic targets the blog subject - and the ads provided by AdSense are relevant to the blog subject. This produces readers who are interested in the blog subject, and in the ads - and who will click on the ads, read about the products and services, and buy the products and services advertised.With relevant traffic, the ad managers who provide the ads, for their company, are paid well - and AdSense can charge more for their ads, as the premium ad hosting service.You can encourage your readers to share your blog, as they like.This blog provides sharing to FaceBook, Google+, Pinterest, and Twitter - using two sharing toolbars. The native Blogger toolbar is linked from the "Share" caption, at the bottom of each post.I added the Blogger toolbar to this blog, using the "Show Share Buttons" selection in the "Configure Blog Posts" wizard. Later, I added my personal AddThis toolbar, that floats in the left edge of each display.Having added the toolbars, you have 8+ icons to choose from, to share this post and others.I routinely share new posts in this blog, to FaceBook, Google+, and Twitter. If this post, or any other, interests you, you are welcome to share to any of 4 social networks (linked from the Blogger toolbar), or any of 200 (linked from the AddThis toolbar).You can encourage sharing by your readers - if you include the AddThis, Blogger, and other third party sharing toolbars, in your blog.Use the social sharing buttons, if you wish - selectively.Both search engines and social sharing have their advantages - and disadvantages. You can get readers for your blog, using social networks - but try to get the right readers too.To get readers who click on the ads and buy the services and products advertised, publish quality content - and get the blog indexed by the search engines with good position. Spend less time getting readers to "Like" your FaceBook page.It's fun to advertise a #Blogger blog using social networking, like FaceBook - but if AdSense is part of the blog, you will get better results by publishing relevant and unique posts, and focusing on search engine indexing.[...]

HTTPS Availability For Custom Domain Published Blogs


After many years of waiting, people who publish blogs using custom domains can provide HTTPS connectivity, to their readers.Right now, HTTPS Availability / Redirect can be enabled, for custom domain published blogs, using Draft Blogger.Since Draft Blogger is used by Blogger for beta testing new features and problem fixes, you will do best using it selectively.Use Draft Blogger only to enable HTTPS Availability / Redirect.In this case, you use draft Blogger only for enabling HTTPS for your custom domain URL. This is a good time to use a second browser - either a different browser on this computer, any preferred browser on another computer, or this browser with an Incognito / Private window.Start by logging into Draft Blogger - using a second browser.The Settings - Basic dashboard page, in Draft Blogger, now has a new option.Select "Yes" for "HTTPS Availabiity" - and wait while the domain is setup with SSL.With "HTTPS Availability" enabled, Blogger has to obtain an SSL Certificate for your domain. This is not a casual formality. With many domain registrations, you might pay extra for a certificate.Once "HTTPS Availability" is activated, you'll have the "HTTPS Redirect" option.Allow half an hour after enabling "HTTPS Availability", then refresh the display. You should have "HTTPS Redirect" available - and if you wish, you can enable it.Success!Test the blog and domain, in the many URLs.With the blog published to the domain, and offering HTTPS connectivity, you'll have 6 URLs - all pointing to the blog. Make sure that all 6 work properly.Right now, my test blog does provide HTTPS connectivity / redirect - though this blog does not, since I don't want broken links to third party services. Using my test blog, I have 6 URLs to check. Note that this blog is published as "" - not "", or "".http://myspaceandmore.blogspot.comhttp://nitecruzr.nethttp://techdict.nitecruzr.nethttps://myspaceandmore.blogspot.comhttps://nitecruzr.nethttps://techdict.nitecruzr.netYour readers will be happiest, if all 6 URLs work - and all redirect to your blog. Again, your domain will probably use "www", in place of "blogging" or "techdict", in #3 and #6.Be prepared to re publish the blog, for best results.If you were using "HTTPS Redirect" for the BlogSpot URL, #2 and / or #5 many be "404". You may need to re publish the blog, and remove the BlogSpot "HTTP" to "HTTPS" redirect. The domain root redirect, and "HTTPS Redirect" for the domain, may conflict.Activate "HTTPS Redirect" for the domain, with the BlogSpot URL having "HTTPS Redirect" enabled - and you may see this.You will have 3 redirects, with HTTPS Redirect added.The BlogSpot to domain redirect.The domain root redirect.The "HTTP" to "HTTPS" redirect.All 3 redirects need to be addd in proper sequence - if you want the BlogSpot URLs, the domain root, and the published domain URL to all redirect to the blog.With both the BlogSpot redirect, the domain root redirect, and the HTTPS redirect enabled, you may see an error when addressing the domain root. In that case, you'll have to re publish the blog to the domain.Login to production Blogger ("").Publish the blog back to BlogSpot, by clicking on the "X".Disable “HTTPS”, if necessary.Re publish the blog to the "www" domain host.Select the domain root redirect.Blogger is not the last Internet service to provide "HTTPS" connectivity.If you enable "HTTPS Availability", and later "HTTPS Redirect", you'll probably have accessories and services that don't support HTTPS.Be selective when you use Page / Post / Template Editor, and see suggestions to "Fix" all links that continue to reference "HTTP" connectivity. If you routinely select "Fix" you will end up with broken links, for accessories and services that have not been upgraded.If you can deal with the details though, you'll have a secure domain, and can offer your readers SSL connectivity.If your #Blogger custom domain is setup proper[...]

Chrome Browser, And Elegant Disappearing Scroll Tabs


The disappearing scroll tab, in the latest Chrome browser version, is tres elegante - for some blog owners.Personally, I'm not convinced.Hover the cursor in the scroll tab area, to get the tab to pop out.If you use the Chrome browser, and the display content is longer (or wider) than one physical screen, you may not realise that.Some people may think that part of their blog - their post - or their template - has been lost.But, look again.Now, you see it.Now, you don't.If you use a "mouse" with a scroll wheel, this is not a problem. Start scrolling with the wheel, and the tab pops out.For folks who are accustomed to "grabbing" the tab, and dragging it downwards (sideways) to scroll, this is not a step forwards. If you want to read text, that's above the bottom of the blog, how do you scroll left to right, while reading a long line of text?Look at what our readers see.Now, you see it.Now, you don't.Where did the rest of my main page go??What our readers think, when using Chrome, is another question.I think that the scroll tab is another "well enough".Now, you see it.Now, you don't.Where is the rest of my post code? What the #@!!?At any rate, if you - or your readers - think that blog, post, or template content has mysteriously vanished, try using the scroll tab (if you can find the tab). You may find the "missing" content, right in front of you.The Chrome Engineers recently added an elegant enhancement to their browser. If you're not scrolling up and down (or right to left), you don't have to look at that nasty old scroll tab - even when using the #Blogger post editor.I'm not convinced that this is a step forward.[...]

Post Editor Displays A Bogus Error When Updating Posts


Some blog owners report a problem with editing posts, in post editor.With any changes made to a published post, an attempt to update shows another monolithic error.An error occurred while trying to save or publish your post. Please try again.But the mystery does not end there. Even seeing the error, a curious blog owner, refreshing the post as displayed, may find a surprise.Even with the mysterious error displayed, repeatedly, the changes just made may be visible in the post.In some cases, a new post editor session - or the post display refreshed - will even show the changes made.Even with the post editor showingAn error occurred while trying to save or publish your post. Please try may see your changes displayed, when you refresh the displayed post.I just updated my earlier post, Country Code Aliasing Is A Solution - Not A Problem.My personal and recent experience.The post, before being updated.I added the observation to the postBlogger has described the problem, as a solution to free expression and controversial the post.I just updated my post.Post Editor, showing the added observation.Then, I clicked "Update" - and waited for an eternity. No matter how many times I hit "Update", I see the same error.It's enough to make one pull hair, in anguish (as if, Chuck!).Post Editor, showing the added observation, after clicking "Update".But, the story does not end here.The post, after being updated - even with the bogus error message displayed.Surprise! See the added observation?Don't believe me? Examine my post, Country Code Aliasing Is A Solution - Not A Problem.If you see the error, don't give up!So, if you edit your post, and having made the necessary changes, you see the bad newsAn error occurred while trying to save or publish your post. Please try again.don't pull your hair in anguish, immediately.Refresh the post - then examine the updated display, and the change just made (in a separate tab / window). You may find your changes saved, as if nothing is wrong.And, it's the EverReady Bunny problem of the week.I was once again, updating my previous post, and idly wondering if this problem had been fixed - and hello!Post Editor, showing this error, after clicking "Update" - just as I updated my previous post.My previous post - updated, even with Post Editor displaying the error!This, too, may involve the Blogger / Google CDN - and delay in updating the Blogger database, between the nodes in the CDN.Just be careful when closing the post editor tab or window, with the warning about unsaved changes displayed.So, what to do, now? I couldn't even leave that window, to update this post - I had to Stay!And having updated this post, in this window, I have to close that window, with the changes maybe unsaved. But I'll re read the post as displayed, first.If you see a mysterious #Blogger Post Editor error "An error occurred while trying to save or publish your post. Please try again.", when trying to update a previously published post, repeatedly, take a moment and verify that the changes being made were NOT saved. You may be surprised!This, too, may involve the Blogger / Google CDN - and delay in updating the #Blogger database, between the nodes in the CDN.[...]

The Blogger / Google CDN, And Logout Problems


Recently, we've been seeing queries from some anxious blog ownersWhy should I have to sign out a total of three, four, or more times?With blogs that use a template that shows the navbar, the owner may logout, using the "Sign out" link - but the navbar may continue to suggest that they remain loggedin.This problem may start with how we connect to Blogger, as part of the mysterious Internet cloud.Blogger provides multiple connection points ("nodes") to their databases, through the Blogger / Google Content Distribution Network ("CDN"), in many different cities worldwide.Generally, a blog owner will connect to Blogger, using the closest CDN node. Thanks to Internet Protocol networking with Multipath Routing, the "closest" node won't always be the node with the shortest distance, "as the crow flies", from the owner.Determining logical distance between 2 computers involves more detail than simple geographical distance. Some blog owners will be equally "close" to multiple nodes - and this is where the problem starts.All Blogger databases, in all CDN nodes, won't update immediately.If a blog owner logs out from Blogger, when connected to one node, the Blogger database in other nodes won't always be updated immediately, to reflect the log out status. The CDN nodes update each other periodically - and there is always going to be some delay between updates.The logical distance between a blog owner and a nearby node can change - and a different node may become "closer", at any time. With multiple nodes equally "close", the slightest change in the network between the blog owner and any "close" nodes can make the blog owner connect to a different node. The blog owner can fluctuate between 2, 3, or more "close" nodes, within seconds. If the blog owner logs out while connected to one node, then re connects to a second node - before the first node updates with the second - the owner will appear to be still logged in.Different CDN nodes may show a blog owner as logged in, until updated.In some cases, the owner can continue to appear as "logged in", when connected to a different node. After logout (log out, signout, sign out) using the "Sign out" link, and the display refreshes, the navbar status will continue to display the account name and "Sign out" link.Some blog owners will be equally "close" to multiple nodes. They may go through 2, 3, or more sign outs - until all nearby nodes are properly updated, or updated by repeated "Sign out".Long ago, update delay led to a different mysterious problem.Long ago, blog owners reported the mysterious adviceYou have logged out from another location. Do you want to log in again?Now, they continue to see the navbar "Sign out" link.This monolithic error used to make many scream, in anguish.Previous advice, to workaround the mysterious "You have logged out from another location. Do you want to log in again?", may work for the logout problem.Check cookie and script filters.Clear cache, cookies, and sessions (yes, all 3).Restart the browser.Click on the link below, to login to Blogger.https://www.blogger.comA similar example of CDN node update delay involves post editor / template editor.I see this problem currently, when updating posts. I update my posts, frequently - and see this error message, almost daily.An error occurred while trying to save or publish your post. Please try again.Post Editor, showing another monolithic error, after clicking "Update" - just as I updated this post.There's nothing to do now, but hope for the best. The above procedure may or may not fix this problem.Template editor will be subject to the same frustration. Any Blogger dashboard change that involves significant delay between opening and saving changes (such as editing) will have a similar problem potential. And here may be one more detail that affects stability of long term draft mode post editor sessions.If you connect to multiple CDN nodes, while[...]

Make Your Blog Searchable - Where To Start


Making a blog searchable is the first step in getting search traffic, and readers, for our blogs - when we want them visible to the public.Not all blog owners want their blogs visible to everybody. Complementing the ability to publish a blog, and have it visible only to invited readers, Blogger gives us the ability to make the blog invisible, to the search engines.If we want readers for a blog, and do not have a private reader audience in mind, we first make it visible to the search engines.The Privacy wizard, on the Blogger dashboard, lets us choose whether to make a blog visible to the search engines.Start with the dashboard Settings - Basic page, and Edit the Privacy setting.Select "Yes" for both options - if you want the blog indexed.Select "Yes" for both options, if you want the blog indexed. This is how you start getting search traffic, and readers, for your blog.Add your blog to our listings?Let search engines find your blog?And click "Save changes".Having made the blog visible to the search engines, continue by publishing lots of informative, interesting, and unique content. Make it a blog that people will read - and that search engines will index.If you prefer the blog to be invisible or private, on the other hand, select "No" for both options. Then continue by developing your private audience, as you like.There are more settings - for owners who want to fine tune search engine access. Both the Blogger dashboard Settings - "Search preferences" page, and the "Google Search console" (previously known as "Webmaster Tools"), have a rich collection of settings, complementing "Privacy".If you really want to fine tune these settings, look at the Settings - "Search preferences" page, and the "Crawlers and indexing" section - but read and heed the serious advice.Warning! Use with caution. Incorrect use of these features can result in your blog being ignored by search engines.You can read more advice in Blogger: Help people find your blog on search engines - and Webmasters: Search Engine Optimization (SEO) Starter Guide. And you'll find Webmaster Central: Crawling, Indexing, and Ranking and Webmaster Central: Search Console useful for personal advice, complementing Blogger Help Forum.Since Webmaster Forums supports owners of static websites, as well as owners of Blogger blogs (and other blogs), not all Search Console / Webmaster advice and tools will be useful for Blogger blogs. Be selective when considering Webmaster instructions - and ask questions in Blogger Help Forum, any time you feel the need.The "Privacy" wizard is where you start - and similarly where some blog owners should stop.The Blogger "Privacy" wizard, on the "Basic" Settings page, provides the start to getting a blog indexed by the search engines - when we want a blog indexed. Not all blog owners want their blog indexed - and that need makes the "Privacy" settings relevant.[...]

The Real Blogger Status Moves Into The Future


Several months ago, I took a leap into the future, and upgraded this blog to use a "Responsive" class template.There are four "Responsive" templates - Contempo, Soho, Emporio, and Notable. The differences between the four include more than merely the visible design. My serious opinion about template choice is that two people, each starting a blog about the same subject, and using the same source of content, will still have different perspectives - and each will probably choose a different template.Anybody who asks me, bluntlyWhich template is a better choice, for my blog?Gets my facetious replyWhatever template encourages you to write more original and quality content, in your blog, is best for your blog.It's your blog. Your blog is valuable, because of the content.Our clean, exciting new look.Our boring previous look.If you want more advice, I'll offer you my four "Responsive" class test templates - Contempo Test, Soho Test, Emporio Test, and Notable Test. You can examine this post, and compare the visible differences, on each of the four.See the linklist "Responsive Templates Tests", in the pop out sidebar? You need to click on the "hamburger" icon, in the upper right corner of the screen, to see the sidebar.Click on the "hamburger" icon, to open the sidebar.The "hamburger" icon is in the upper right corner.The sidebar, normally hidden, to let the post content be more readable on a tiny "phone" display.The "pop out" sidebar is one majorly innovative design feature, that helps the "Responsive" class templates replace the "Layout" / "Designer" class templates, and their special "Mobile" template.The pop out sidebar is only visible, when you want to access sidebar content, by clicking on the "hamburger" icon.Now, you see it.Now, you don't.Click on the tiny "right arrow" icon, to hide the sidebar, when the sidebar is open.Besides the "Mobile" template that is now redundant, there are significant differences between the four "Responsive" templates, that may encourage choice of one or the other. As I continue to upgrade the older posts in this blog, to look better using "Notable", I'll start discussing the advantages and disadvantages of each.If this interests you, move your blog forward, by choosing an exciting "Responsive" class template, from the dashboard "Theme" page.Pick one of the new and exciting "Responsive" class templates - Contempo, Soho, Emporio, Notable.If necessary, setup your own test blog set, with your own test posts - and compare your content on the different templates, to see what your blog will look like. Or, you can use my sidebar menu "Responsive Templates Test" - and look at my four test blogs.My personal choice of the "Notable" Responsive template, was not immediate - it took several days, and some experimentation using various tests - and my 4 test blogs. You can take your time - and change your template, as you feel the need.The Real Blogger Status has moved into the future - and is now using a new #Blogger supplied "Responsive" class template. It's going to take some work, to make the blog truly look good under "Notable" - but progress always has a price.[...]

What Is The Mysterious Custom Domain "Error 12"?


Both the historically infamous "Another blog ..", and the currently infamous "Error 12", are part of the custom domain publishing process.Similar to the mysterious "bX" codes being an enhanced version of "We're sorry, but we were unable to complete your request.", "Error 12" (and variants) is an enhanced version of the monolithic "Another blog or Google Site is already using this address."."Another blog" (which was generally seen during use of the Blogger Publishing wizard) is complemented by the equally annoying "Not found" (which is generally seen after Publishing is used).The "Another blog ..." / "Not Found" condition is not desirable - for a working domain.The condition, in general, appears to be an unavoidable result of the flexible Blogger custom domain design. A Blogger custom domain published blog can be one host in a domain cluster, that can also include a Tumblr blog, a WordPress blog, any number of third party hosted websites - and even an odd feature like a forum.Blogger custom domain publishing is a powerful feature.Blogger custom domains can be purchased from (almost) any registrar - and can use DNS provided by (virtually) any DNS host. It's more powerful than competing Internet services. Use of "CNAME" referral, to connect the blog and domain, is innovative, and smart.Custom domain publishing does some of the domain processing from your computer - instead of solely from Google. Use of your computer, unfortunately, involves computers and networks uncontrolled by Google - and may lead to occasional database corruption, and to "Another blog". Custom domain publishing depends upon DNS - and DNS is an Internet service controlled by neither Google or any blog owner."Another blog" and "Not found" are two displays, caused by one problem.The mysterious "Server Not Found", seen occasionally, is similar to the classic "Another blog ..." error.In many cases, righteous DNS addressing is present - but broken links, in the Google database, leave the blog displayed as “Not found”. "Another blog" is seen by the blog owner, when publishing - and "Not found" is typically seen by would be blog readers, and search engines, after publishing.An experienced blog owner would generally prefer the former, to the latter. The owner, when seeing "Another blog", can fix the problems - so prospective readers and search engines can view the blog, without seeing "Not Found"."Error 12" is the best known, but not the only, "Error"."Error 12" is the best known "Error" - but not the only one. There appear to actually be several dozen different variants of "Error 12", which refer to problems with the Publishing dashboard wizard. We've seen "Error 32", at least.32 "Error" codes is nowhere as complex as 36^6 "bX" codes - but it's a start.An example of the infamous "Error 12", seen long ago.Earlier, "Error 12" was seen when domain ownership verification was needed, when publishing to newly setup domains. We have, during the past year, seen reports of Publishing problems labeled "Error 13", "Error 14", and "Error 32"."Error 12", in reality, is not an actual error condition - it is simply a domain, requiring normal ownership verification. Recently, the "Error 12" label was removed from the "domain ownership verification is needed" display - and now, we simply see the label "Third party domain settings"."Error 13", "Error 14", and "Error 32" appear to also involve domain ownership verification - but with slightly different circumstances. There may also be some "Error" numbers which involve features other than domain ownership verification. And some "bX" codes are caused by bogus DNS addressing, encountered during custom domain publishing - like various "Error" codes.The "Error 12" seen now, with verification instructions re written - and without the "Error 12" label.Ownership verification has[...]

Photobucket Drops Free Image Display, Outside Their Website


One of the most popular third party image hosting services, for Blogger blogs, recently changed their photo hosting service.Photobcket no longer allows embedding of their hosted photos on third party websites, for free accounts. They now require a $399 / year membership, for accounts with photos shared outside their website.Some Blogger blog owners, publishing blogs which use third party templates that feature images - decorations, illustrations, and wallpaper - hosted by Photobucket - now see their blogs decorated by various demands.PLEASE UPDATE YOUR ACCOUNT TO ENABLE THIRD PARTY HOSTINGThis is (was) a small image, tiled (repeated horizontally and vertically), to fill a larger space. It's now a PhotoBucket ad, similarly tiled.In many cases, this is simply a third party supplied template, using wallpaper designed by the template publisher. The template publisher used PhotoBucket, to host the image.The blog owner, and others, now face the need to pay dearly, to publish their blogs using their current templates.Whether the template objects were created by you - or by the supplier of a shiny third party template - if the images are hosted by Photobucket, they are now unusable, on your blog.Photobucket, a US-based image and video-hosting website founded in 2003, quietly changed its policy late last month to prevent users from hosting their content on third-party websites unless they pay a $US400 ($526) annual fee.Photobucket published a brief blog post, on June 26, referring to the service change - buried deep in their website.We have updated our Terms of Service, effective June 20, 2017. Please take a moment to review our updated terms and policies as they may affect your account.If your blog uses a third party template with PhotoBucket hosted images, the account in question won't be yours - but your blog will still be affected. You're going to have to find out how your template designer is going to support their product.Third party template publishers now need to convert their templates, to use images hosted by other services. And Blogger blog owners may need to find other image hosting.Blogger blog owners, who use third party templates in their blogs, may need different templates. Not all third party template publishers may be able to support their templates, and this change.The simplest solution is to switch back to a Blogger standard and supported template, using the dashboard Theme page. If you've had your current template for a while, you may not know what possibilities have been added, to the Blogger template selections.Photobucket, a popular third party image hosting service used by many #Blogger blogs, originally allowed their hosted images to be embedded or hot linked on Blogger and many other websites. They recently started requiring a $400 USD / year membership, for images to be displayed outside their website.Many Blogger blogs, with third party templates that use Photobucket hosted images, now have broken templates.[...]

Does Your Blog Need HTML Validation?


A few blog owners are concerned about blog network performance - and spend time validating and tweaking the template, based on advice from various third party services. I don't know how to use W3C Validation, there are always errors displayed for my blog!And we see periodic questions about validation - and sometimes reports about broken templates, with blog owners following the validation advice, blindly.W3C Validation produces hundreds of errors, for every blog page.I Tried Validation, For This Blog.I used to tear my hair out, trying to fix my W3C validation errors, for this blog.Check out the validation log, for this blog, as an example. See the size of the scroll tab? That's a 20 page report - of critical errors, in the blog home page.See the size of the scroll tab? This display shows just the first page, of 20 or so.Validation Is Useful, For Static Websites.W3C validation is designed for HTML based, static websites - that are centrally located. Blogger blogs are XML based, and dynamic - and use the Google Content Delivery Network, which serves each blog from hundreds of different data centres, worldwide, depending upon the location of each individual reader.With the Google CDN delivering content locally, to many readers, distance related network issues are less important - and with Blogger templates being maintained and tested by Blogger Engineering, a lot of the issues identified by validation are not easily resolved by the typical blog owner.If you publish a Blogger blog, using a Blogger supplied template, work on content. Blogger manages the network settings, relevant to your blog, as it is served by the Google Content Delivery Network. You publish your blog - and let Blogger / Google worry about the networks, the servers, and the templates.Custom / Third Party Templates May Benefit, In Specific CasesIt's possible that some blogs with third party templates, and non Blogger standard code, may benefit from validation.If your blog has a non Blogger template, you could check out Blogger Developers or Stack Overflow - and ask for advice there. Or, try contacting the person / site that provided you with the template, and see what they can tell you.But with a blog with a supported Blogger template, concentrate on content. Don't tweak the template HTML, unless necessary. Leave Blogger / Google to worry about network issues and the template.Some #Blogger blog owners concern themselves about third party network performance analysis. Learn why some performance analysis advice may be unnecessary - and can be harmful to your blog.[...]

When Correcting A DNS "CNAME", Maybe Delete Before Adding


Very few registrars allow multiple "CNAME" addresses, for a single DNS host.When I diagnose DNS address problems, I generally recommendAdd the addresses highlighted in green.Remove the addresses highlighted in red.I find that it helps to have the old address visible, while the new address is being composed. This does not always produce the desired result, unfortunately.Many registrars do not allow multiple "CNAME" addresses, for DNS hosts - and the zone editors reject new address attempts.When DNS addresses for a Blogger custom domain need to be corrected, I recommend Add the addresses highlighted in green.Remove the addresses highlighted in red.I recommend correction in this order, so the blog owner can view the current (incorrect) addresses, while adding new (correct) addresses. This compensates for various zone editor syntax oddities.Making corrections in this order - adding correct addresses, then removing incorrect addresses - does not always produce the anticipated results. If the zone editor checks as each individual address change is made, we see the result."That name is reserved (already in use)."Some zone editors check, immediately, when a second "CNAME" is entered, for a given "Host" address. When multiple "CNAME"s are forbidden, and the zone editor checks for multiple "CNAME"s immediately, we have a problem.Other zone editors check for a correct address complement, when Saving multiple zone editor changes - after all additions and removals are successfully made and verified. These zone editors do not present a challenge - as long as the blog owner removes all incorrect addresses.When the incorrect addresses are not removed properly, we see the result.That name is reserved (already in use).This leads the blog owner to cancel the recommended correction - and we wait, in vain, for the domain to come online.In a worse case scenario, we can even end up with another case of "Another blog ...".Right now, though, we can only diagnose the problem, one domain at a time.Some registrars have zone editors which forbid multiple "CNAME"s for specific addresses - and check, one entry at a time, for mistakes. This may cause a problem, with a #Blogger blog owner making custom domain DNS address corrections, when instructed to "Add addresses highlighted in green.", then "Delete addresses highlighted in red."[...]

The "My blogs" Dashboard Page Has Been Replaced


Earlier this year, Blogger upgraded their dashboard - and eliminated the opening "My blogs" / "Reading List" page.They changed from a dashboard home page, listing all blogs owned by a given Blogger account - to a home page, showing the dashboard for the most recently updated blog.To the dashboard menu for the blog displayed, they added a pulldown blog selector list. If you want the dashboard for a different blog, or need a different important "My blogs" function, you use the selector list.Previously, to work on different blogs, I would repeatedly use the dashboard Home page. The dashboard home page contained "My blogs" and "Reading List". Each "My blogs" entry had links to half a dozen different important dashboard pages, for each blog.The "My blogs" menu has been replaced by a pull down blog selector list, which overlays the existing dashboard menu - giving the appearance of a single dashboard page, for all blogs. The list links to all blogs owned by the account (active, and deleted / locked) - and lets the owner access the dashboard for a different blog, when desired.For blog owners with only one blog, the selector list is not important. The list becomes important, when the dashboard for a second blog - or the "Deleted Blogs" / "New Blog" dashboard wizard - is needed.Some blog owners - unaware of this change - may see this as another variant of "missing blog".Here's the new "My blogs" list."Your blogs live here" - behind the blog title and pulldown arrow.It's all there - really!There is now no dashboard home page, with "My blogs".Previously, we had a dashboard Home page, with "My blogs" and "Reading List".Each "My blogs" menu entry gave access to half a dozen different dashboard pages, for each blog.Each "My blogs" menu entry had half a dozen different dashboard links, for each blog in the list. The links were both excessive, and insufficient.The menu entry links had a hodge podge of styles of buttons / captions / link display styles.The half a dozen links provided access to a small subset of useful dashboard menu pages.The "My blogs" list was long, and randomly sequenced.Some blog owners would have enjoyed having different or more menu pages directly accessible from "My blogs". And we asked, many times, for an alphabetical "My blogs" list.Instead of making "My blogs" more complicated, Blogger replaced the "My blogs" menu. We now have a "My blogs" list, accessed from any dashboard menu page.Here's the options, on the new "My blogs" list.The new dropdown list includes several important options.All active blogs ("My blogs").All inactive blogs ("Deleted blogs").The "New blog" link ("Create a blog")."My blogs" and "Deleted blogs" are now part of the same alphabetical list, with each deleted / locked blog indicated.You can now switch between any specific dashboard pages, for any blogs in "My blogs", using the selector list. Now, the dashboard home page is the dashboard menu, for the blog most recently accessed.With the list closed, the blog title will be plain text. See "The Real Blogger...", at the upper left of the dashboard?From any dashboard page, click on the blog title or down arrow - and there is the "My blogs" menu. Then select any blog title, in the list.With the list open, you'll see the blog title "The Real Blogger..." changes to a button.Use "My blogs", and examine the same dashboard page for different blogs."My blogs" is now a blog selector list, for the dashboard page, being displayed. You can switch between different blogs, and stay on any specific dashboard page. And "My blogs" is now in alphabetical order.From any dashboard menu page, you can open "My blogs".Then select any blog, in the list.And, you have the complementary dashboard page, for th[...]

Blog PageView Counts, And Social Sharing Activity


Ever since 2009, when Blogger introduced the Stats visitor activity counter, blog owners have been reporting inconsistencies between Stats and other visitor activity counters.Recently, Google+ changed their +1 counter. Now, we wait for Blogger Engineering to update their +1 per post display counters, which use the +1 counts from Google+.Blog owners continue to report various Stats inaccuracies - such as discrepancies between Stats pageview counts, and the various social sharing counters. They fail to observe the functional differences between the various activity counters - and similarly, between Stats counts and social sharing metrics, such as Google+ +1 counts. Stats pageview counts and Google+ +1 counts compare no better, than Stats and various other visitor activity counters.Social sharing contributes to your blog reputation, in a number of ways. Some social sharing relationships, compared with blog activity counters, may lead to confusion.Social networking activity counts will resemble blog visitor activity counts - with the activity mentioning the blog.There will be differences, between the two, however. The differences will contribute to perceived blog visitor activity count inaccuracy. You will have Followers - in asymmetrical and symmetrical relationships.You will have Followers - in direct, and indirect relationships.Not all Followers will read your blog posts.Some folks who do read your blog posts will be invisible, to you.The bottom line is reputation, for you and for your blog.You will have Followers - in asymmetrical and symmetrical relationships.Social sharing helps to connect people, through their interests.You may read some posts in your Google+ stream, which will interest you. Some people will contribute many posts that interest you - and you will decide to Follow them. Those people may observe your activity, and decide to Follow you, in a symmetrical relationship.You won't Follow everybody, symmetrically. Nobody can Follow everybody - or even everybody who Follows them.Some people will share few interests with you, and have many interests that you don't have. You won't Follow those people. Similarly, some people who you Follow won't Follow you, because you don't interest them.You will have Followers - in direct, and indirect relationships.If you use FaceBook or Google+ enough, you will see random posts in your stream - and decide to Follow some authors. Similarly, some of the people who see your posts, in their streams, will decide to Follow you.You will +1 / Like / re share some posts from your Followers - and some of your Followers will do the same, with your posts, directly. Some folks who Follow your Followers - not you, directly - will +1 / Like / re share your posts, indirectly.Not all Followers will read your blog posts.If you spend time reading your activity notifications, you may observe that some Followers may +1, like, and / or re share, your various stream posts - including some stream posts which reference your blog posts. You may also observe that some activity takes place seconds, or minutes, after you share or re share a stream post.Your ability to observe, and to react, will depend upon your relationship with each Follower - direct vs indirect, and asymmetrical vs symmetrical.When a stream post is liked or re shared shortly after you share it, it's possible that your Follower did not spend a lot of time reading the content of the post. If your share included a reference to your blog post, it's likely that they did not read your blog post - even though they contributed a +1 / like / re share of your stream post.Even though your direct Followers may not all read your blog posts, their Followers (you[...]

The New Followers Gadget - Blocking Followers


With the pre 2016 Followers gadget, the Followers population for a blog was managed through an Options link on the Followers gadget.This required the blog owner to sign into the Followers gadget, to access the Options link. Authentication - and an owner specific Options menu - is no longer a pert of the Followers gadget.It is possible to Block Followers, from a blog - the option is just not part of the Followers gadget, any more.Previously, the option to Block a Follower was part of the Options menu, in the Followers gadget.To ensure that only a blog administrator was able to Block a Follower - or do various other blog to viewer functions - the Block option was part of a complex wizard, accessed by a blog administrator.This required the ability to authenticate a viewer - separately from the Blogger / Google login. This, in turn, made the Followers gadget complicated - and lead to occasional malfunctions. To simplify the Followers gadget, there is no need to login to the gadget, any more.Now, the ability to Block unwanted Followers is part of a blog administrator Stats page. On the Stats Overview page, look for the Followers count.The number which displays the Followers count is now a link. Clicking on the number, one can access the "Manage followers" wizard.This blog has 4,954 Followers. Click on "4,954" (right now).And there is the "Manage followers for The Real Blogger Status" wizard. Each Follower now has a "Block" button, plainly visible.Since only a blog administrator has access to the Stats dashboard page, there is no need for a separate Followers login. Just click on the Followers count, on the Overview page.And the Followers gadget has only one option - the button, immediately visible to each blog viewer.Follow (if not currently Following).Unfollow (if currently Following).The Follow / Unfollow button applies to administrators, authors, and readers alike. Now, there is no need to identify a person as related to a blog - except as whether this person is currently Following the blog.Simplicity - for blog administrators, blog viewers, and Blogger developers.When the #Blogger Followers gadget was re written in 2016, the "Options" menu - and the need to login to Following separately - was removed from the gadget.The ability to Block selected Followers, previously part of the Options wizard, is now part of the Stats dashboard page. [...]

Comment Publishing Preview, And "Error 400"


We're seeing a problem with Blogger Hosted Comments - and "Bad Request Error 400", following the use of the comment "Preview" feature.When a blog owner or reader composes a long or important comment, use of the Preview feature is normal. Right now, after hitting "Publish", following a successful Preview, one frequently sees the bad news.Bad RequestError 400There is a workaround for this annoyance - and it's not difficult to use.Until Blogger Engineers fix the "Error 400" problem, there is a workaround - and the workaround adds very little time to comment publishing.The most obvious alternative would be to not use Preview. But how well can you eyeball your comment, without Preview?If you find it inconvenient to eyeball check a comment without using Preview, it's a small effort to copy then paste, before Publishing. Just a little planning, before composing, lets you copy then paste.OMG, where is my comment? All my work, gone??Opening a new tab / window lets you publish, after the preview / edit cycles (and avoid the "Error 400"), when composing an important or long comment.Here's the key to the workaround. "Open link in new tab" - a context menu option, for any link.With most browsers, you'll either "Alt" click or right click on the link, to get the context menu.Recover the comment content, if you're looking at the "Error 400".Open the post, where a comment is needed.Open a comment composition window, in a new tab / window.Compose the comment, carefully edited.When satisfied by the Preview display, click Edit once more.Copy the edited comment.Close that browser tab / window.Open a comment composition window, again.Immediately paste into the new comment composition window.Immediately Publish.Done.Recover the comment content, if you're looking at the "Error 400".If you're looking at the "Error 400" display, right now, refresh the display and follow the prompts. Recover the comment composition window, with your work in progress. Skip ahead, to Step #6.Open the post, where a comment is needed.Start with a post - and the "Post a Comment" link at the bottom of the post.Open a comment composition window, in a new tab / window.Click on the "Post a Comment" link - and use the "Open in new tab / window" browser option. With most browsers, you'll either "Alt" click or right click on the link, to get the context menu - and the "Open in new tab" / "Open in new window" option.Compose the comment, carefully edited.Use Preview and Edit, and the composition window, as necessary. Compose, preview, and edit - until your comment is properly phrased.When satisfied by the Preview display, click Edit once more.If it's an important or long comment, you'll use the Preview - Edit sequence, a few times. Just finish, with a final "Edit".Copy the edited comment.From the comment composition window, hit "Ctrl - A" to select everything as edited, then "Ctrl - C" to copy.Close that browser tab / window.Close the tab / window - and bid farewell to the carefully written content, and the Bad Request.Open a comment composition window, again.Click on "Post a Comment" from the displayed post - again, using "New tab / window". You will have an empty comment composition window.Immediately paste into the new comment composition window.Immediately paste the copied comment ("Ctrl - V") into the empty comment composition window.Immediately Publish.You already previewed and edited your comment - now, Publish.Done.The comment publishes - and, you're done.Do this a few times - you'll see that this adds maybe 30 seconds to the comment composition / preview / edit cycle.How long does it take to compose (preview, edit) a comment, to [...]

One Cause Of The Monolithic Error "No posts."


One of the most obscure Blogger error messages - next to "Another blog ..." - is the monolithic advice seen on main page display of some blogs.No posts.or maybeThere's nothing here!What can you say, to a blog owner who has started a new blog, and spent days publishing blog content - only to view the blog, and see "No posts." - or "There's nothing here!"?In some cases, a blog may actually contain no posts - even after days spent publishing content.Some blog owners may confuse pages ("static pages"), and posts ("dynamic pages") - and spend days publishing blog content, as static pages. Other blog owners, though having just started their first blog, may be experienced webmasters with one or more websites published for years - and publish blog content as pages, by preference.Whether owned by a true newbie, or an experienced webmaster, a blog which is constructed using static pages will display the main page asNo posts.or maybeThere's nothing here!By default, the main page display will only show posts. Pages were originally provided, as a Blogger feature, because some blog owners wanted some posts that were not indexed in an archive, label, or main page sequence.When you are queried by an anxious blog ownerWhy does my blog displayNo posts.Where are my posts?What can you do?You need to compare "sitemap.xml" and "sitemap-pages.xml". In some cases, you'll find "sitemap.xml" to be empty - and "sitemap-pages,xml" to list static pages. Occam's Razor wins again.Some blogs may be truly empty.Some blogs will only have pages for blog content - and no posts.Some blogs will only contain static pages - and the main page will show "No posts.".If your blog does this, you can redirect the home page to a given static page - and add links between the static pages. Or, republish the pages as posts, if convenient.If you want a main page with multiple posts, maybe using Jump Break to make the main page look cleaner, you will have to publish your blog content as posts.The monolithic error "No posts." causes extreme anguish, to a #Blogger blog owner who has just spent days publishing content. In some cases, there is a simple explanation.[...]

AdSense - Eligibility For Ads Is Based On Content


Many blog owners want the legendary wealth, from publishing a Blogger blog, and adding AdSense ads.Not everybody understands the AdSense review process - and the fact that "Congratulations!" is only the beginning.There are actually 4 steps in the review process, which must complete successfully, to provide paying ads for your blog.This is what you see, with a new blog.Each review step follows the previous step, one by one.Automated blog size analysis.Manual ad placement and content analysis.Automated blog content analysis.Automated assignment of available ads to blog pages.Automated blog size analysis.With a Blogger hosted AdSense account, Blogger checks each blog, periodically. When your blog is eligible to apply for AdSense, based on age and size, you see the legendary "Congratulations!" offer.This is what you see, with an eligible blog.You now have a working "Earnings" dashboard page - and can select ad placement options, and apply.You have to place ads, before you apply, and evaluation can start.This is the beginning of your road to riches - but only the beginning.Manual ad placement and content analysis.After you position the ads and apply using "Earnings", you wait for approval during the "2 to 3 week" evaluation period. Until people decide that the blog is well written, with consistent and easy navigation, and properly located ads - and contains material that is informative, interesting, and unique, AdSense won't place paying ads in the blog.Any ads visible, after you select ad placement, will be public service announcements. You won't earn any money, with PSAs displayed. Some blog owners will see blank spaces, where ads are supposed to appear.Automated blog content analysis.Following approval, the AdSense crawler has to analyse post content, so actual paying ads can be chosen.If content cannot be analysed, paying ads can't be chosen.The AdSense crawler can't navigate this blog, with numbered pages.Blogs that use JavaScript, to link pages, are a problem when the blog is being crawled. This includes the Blogger dynamic templates, and some "Responsive" class templates - and third party templates with features like numbered pages.Post content only accessible behind JavaScript can't be read, by the AdSense crawler. You may receive a rejection, based on "difficult navigation" or "inaccessible content".Automated assignment of available ads to blog pages.Following post content analysis, available paying ads are assigned, on a page by page basis. AdSense won't sell ads for prohibited or unwanted content.If paying ads are not available, to match the content as analysed, the blog won't get paying ads - and won't make money.The bottom line.Until actual paying ads are placed into the blog, you can't start to make money. And paying ads won't be added, until the blog is ready.As usual, I'll advise you to start a blog with informative, interesting, and unique content - published regularly. And keep publishing, frequently.And, wait patiently.Some new #Blogger blog owners setup their blogs - and wonder, immediately, why they aren't seeing paying ads on their blogs. They fail to understand that ads only appear on blogs after several careful evaluation processes.[...]

Custom Domain Publishing, And DNS Latency


The Internet is diverse and large - and the Internet directory system, aka the DNS Infrastructure, supports the diversity and size.When we setup a new domain, the registrar frequently advises us to wait patiently, before continuing.Congrats on your new domain! Now, we suggest that you wait 24 - 48 hours for the new domain to propagate, before trying to publish to the domain.When we update a domain - and add or delete a single DNS address - we won't always get advice about waiting, from the registrar.Responsible helpers will occasionally provide advice to be patient, in Blogger Help Forum: Get Help with an Issue.After you correct the addresses, please wait 8 hours (2 x "14400" seconds) before continuing. This will let all DNS servers on the Internet receive the corrected addresses.This advice is generally given, for domains that use a 4 hour ("14400" second) or greater Time To Live or TTL.Many registrars use a 1 ("3600") or 2 ("7200") hour TTL, for individual domain DNS addresses. Domains with 2 hour or less TTL generally do not require latency advice, because most forum topics take more than 2 - 4 hours to complete.Adding a domain - and updating a domain - involve different latency.The difference between "new domain" and "domain update" advice - and irregular presence of either - causes confusion.Some advice about domain updates involves unnecessary waiting. In other cases, new domain owners jump right in, and try using their new domains, immediately - and regret later.Moving too quickly, with Blogger custom domain publishing, can lead to Google database corruption. Fear of the apocryphal "Another blog ..." error - and similar Blogger access disruptions - leads many technical helpers to routinely advise unnecessary waiting periods.People who make changes, and see their changes work immediately, cause similar confusion. Somebody who is advised to wait 2 to 4 hours, before publishing the blog to the domain - and who observe that the domain, perversely, is immediately operational - may misunderstand.Remember that everybody who wants to read a blog won't have the same DNS service. Differences between one reader (or search engine), and another, will cause various confusions.Waiting too long wastes time - but not waiting long enough can cause worse problems. For best results, there will be unnecessary waiting, sometimes.Just be aware of the different latency periods - and try to provide relevant advice.Domain addition latency can be 24 to 48 hours ("86400" to "172800" seconds).Domain update latency can be 10 minutes, to 48 hours ("600" to "172800" seconds).Domain addition latency can be 24 to 48 hours ("86400" to "172800" seconds).Domain addition latency results from the different name servers - and server owners and update policies - all over the Internet. Any given name server updates their local domain master database periodically, by retrieving the zone file from the various master name servers.If the domain master database on a given server is updated daily - and if your domain was setup 1 minute after the daily update, your domain will not be added to that server until the next daily update.Now consider that there are thousands of name servers, owned by hundreds of registrars, ISPs, and other Internet services. All local name servers are updated on a schedule considered appropriate, by the owner of each service.For best results, your domain needs to be indexed on any name server that might be used by any one of your readers - or any one of the search engines that provide necessary search results, for an[...]

Custom Domains And HTTPS Redirection Code


As most of us know, Blogger HTTPS support does not include custom domain publishing.The advantages offered by HTTPS access are widely advertised - and have led to envy between blog owners who publish to custom domains, and native BlogSpot blog owners proudly advertising their new HTTPS connectivity.Long ago, we saw possibly malicious code which helps our readers avoid using country code aliases, to read our blogs from an aliased country. Recently, there was dodgy code which blocked HTTPS mode, to read a customised blog.Now, we have custom code to force HTTPS access, for BlogSpot published blogs.Along with providing code to help blog owners avoid country local domain aliasing, some marginally helpful hackers are providing code to help blog owners force reader access to HTTPS.Some blog owners always wanted HTTPS to be used, to access their blog.Some blog owners wanted their readers always using HTTPS to access their blogs, before forced HTTPS access became an option. They Googled, and found, semi helpful hackers who provide clever code to force the "HTTP --> HTTPS" redirection. This is clever code - when only BlogSpot access is involved. When you add BlogSpot to custom domain redirection, it becomes another "404".Adding this clever code is an excellent solution - until the blog owner forgets about it, and later upgrades to a non BlogSpot custom domain.With a custom domain published blog, the redirection becomes a problem.The added code contains no exception to permit custom domain published blogs to remain in HTTP mode. When accessing an otherwise properly setup custom domain published blog, from a reader using the "" URL, this prevents the BlogSpot to domain redirect from operating.BlogSpot URLs, which should redirect to the HTTP published custom domain URL, instead redirect to a non existent HTTPS URL - and result in another "404". As the custom domain URL becomes more commonly used for a recently published blog, confusion increases when the rarer BlogSpot URL reference is encountered.My blog has been using the domain URL for months, why is this happening now?The problem involves dual redirection - to "https:" mode, and to the custom domain.After painful problem diagnosis, we find the clever redirection code buried in template HTML - and we see that the blog reader is starting from the BlogSpot URL, and using the BlogSpot to domain redirection, to access the blog.With blog access redirected to "https:" mode, then subsequently to the custom domain URL, the readers sees a "404" - because the custom domain URL is not available as "https:" content.This problem will become increasingly rarer - but not extinct.As self caused custom domain victims become rarer, this way of breaking ones own blog will become more obscure - and it's likely that some cases [...]

Revert A Page / Post To Draft Status


Sometimes, we need to remove a page or post from a blog - but prefer to not delete it.There are various reasons for not wanting to delete a page / post immediately or permanently - maybe when removing a post for problem diagnosis, or to change the URL to match the publish date. Reverting to draft status is easily reversed, and has no permanent side effects.When you want to quickly - but not permanently - remove a page or post, you can revert to draft status.Reverting to draft status is convenient, safe, and simple.You can revert a page or post using Page / Post Editor, or the Pages / Posts dashboard page.Revert, using the Pages / Posts dashboard pages.Revert, using the Page Editor / Post Editor.Revert, using the Pages / Posts dashboard pages.The Pages / Posts dashboard page is a menu. Simply select one or more pages or posts, then click "Revert to draft". Click on "Yes" to verify. and you're done.Hit "Revert to draft", after selecting a page or post.Revert, using the Page Editor / Post Editor.Any time that you are editing a previously published page or post, click "Revert to draft". And you're done.Hit "Revert to draft", when in page / post editor.And when you're done, you're done.Once a post is newly draft, it's offline. Page / post content in cache on your readers's computers will be readable until it expires. New readers, on the other hand, will see a "404" immediately.You can recover the post with the URL - or rename to a new URL.If you revert to draft - then later, re publish without changing the title, you will get the same post, with the same URL, back. If you change the title with the post in draft status, you get the same post content, under a new URL, when you re publish.If you do the latter by mistake - then discover the mistake later, you can recover the mistake by merging the new and previous URLs. Just add a custom redirect from the new to old URL (or vice versa).Review / Recover The Draft Inventory, With One Mouse ClickAny time that you need, review the inventory of Draft posts. Just click on "Draft" under "Posts". You can Edit then Publish - or just Publish, immediately.Check out the current Draft posts complement, from Pages or Posts - Draft. Then recover one or more.Just select one or more posts, then "Publish".Or edit a page or post, then Publish.Either way, you can recover any pages or posts, reverted, easily enough - as long as you revert them, instead of deleting them.Just understand the possibilities.Reverting a #Blogger blog post to draft status is a quick, yet reversible, way to take a post offline. The URL will be recovered, automatically - as long as you do not change the title.[...]

Blogger Magic - Move Content Between Blogs


Some blog owners, who publish multiple blogs with different subjects, may decide that some subjects would be better discussed in a different blog.With various posts published in one blog, the owner may decide that those posts should be published in a different blog, to continue discussion. The question now is how to move posts, from one blog to another?The dashboard "Export / Import" feature, which is now labeled "Import & back up", lets us copy pages and posts from one blog to another. Just copying all pages and posts, though, will create problems with duplicated content.If you are going to move specific posts from one blog to another - and continue to publish both blogs - you have to add extra steps to the process.Use "Import & back up", on the Settings - Other dashboard page.Export all content from the first blog.Import all exported content, to the second blog, as "Imported".Publish imported content, selectively, in the second blog.Delete content re published, from the first blog.Setup custom 404 or custom redirects, from the first blog.Remove imported yet un published content, from the second blog.Export all content from the first blog.Using the "Import & back up" wizard, on the dashboard Settings - Other page for the first blog, click "Back up Content". This will export all pages and posts, in the blog, to the file which you select.To make it easier, label the posts that you want to "move" to the other blog, before you start "Back up Content".I labeled my posts "Move".Now, "Back up Content", from the first blog.Use the file manager provided by your operating system, to create or select a file / folder, and actually save the file.Import all exported content, to the second blog, as "Imported".Using the "Import & back up" wizard, on the dashboard Settings - Other page for the second blog, click "Import Content" - then find and select the file just created. This will import all pages and posts, as exported from the first blog - and place the imported pages and posts in the special "Imported" status, on the Pages and the Posts dashboard pages.Continue with "Import Content", to the second blog.Select the file that you just created, above.And having Imported everything, there are the posts - including those labeled "Move".Publish imported content, selectively, in the second blog.Using the "Pages" and "Posts" dashboard pages, select the newly activated "Imported" menu, as you wish. This will list all imported pages and posts, in turn.Find the pages and posts that you want moved, select them, and click "Publish". If you labeled the posts to be "moved", simply display, and Publish, all posts with the designated label.And, I Published the posts labeled to be "moved".Note that, once Published, the "Imported" status is cleared.Delete or revert content re published, from the first blog.To prevent problems with search engines detecting duplicate content, you can delete or revert to draft status, each post in the first blog, the you just re published in the second blog. If you revert to draft status, you will have backed up content and a recoverable page / post URL.Again, if you labeled the posts, you can delete or revert posts using the label.Setup custom 404 or custom redirects, from the first blog.You cannot use a custom redirect to automatically redirect from the first blog to the second. You can, however, setup a custom 404 page, in the first blog - or make custom redirects to a custom 404 page, in the first blog - advising the r[...]

Act Immediately, When Invited


Some moments come fleetingly, and never again.One such moment may be, when you receive a blog membership invitation.The purpose of this message is to inform you that xxxxxxx has invited you to join their private blog "xxxxx xxxxx". To accept this invitation, click on the button below.orThe purpose of this message is to inform you that yyyyyyy has invited you to contribute to their blog "yyyyy yyyyy". To accept this invitation, click on the button below.Unless you know the blog owner, this may be your one chance.If you get an invitation to be a designated reader on a private blog - or an author on either a private or team blog - decide, and act as soon as possible.Any invitation that you get will be temporary. Blog membership invitations expire, after a fixed amount of time.Accept the invitation, to view and note the URL.If the blog is private, and you accept the invitation as a reader, make a note of the URL too.Long ago, you might get a "preview link" in the invitation - allowing you to view the blog, and bookmark / copy the URL for later. The "preview link" feature was abused by too many owners - and appears to be gone now.No preview = no URL until after you accept the invitation.Become an author, on a team blog!Become a reader, on a private blog!There's a limited amount of detail, in the invitation.How useful is either invitation, if you don't accept, when viewed later? You can get the owner name (as provided by the owner), and the blog title - and that's it. Invitations contain only the author name, the blog title, and a membership token.A reader invitation, for a private blog, may not produce an entry in the dashboard "My blogs" list.Both author and reader invitations will expire.Act promptly, for best result.If you get an invitation, and you file it away so you can "think about it", don't think about it too long.Once the token expires - and if you don't know the owner - you'll not be able to contact the owner. And until you accept the invitation - and actually view then bookmark the blog - you won't find out the URL.Act quickly - or never.If you get an invitation to be an author on a private or team #Blogger blog, or a reader on a private blog, act promptly. Invitations expire too soon - they contain few details - and won't be very useful later.!category-topic/blogger/z-lKeqO-ssA[...]

Blogger Magic - Adding Label Search URLs


One of the simplest ways to make a blog useful is to add label searches.Adding label searches, in page / post text, is not easy - unless you know how to build the URLs. Here's a label search from this blog. that I want, when using that label search, is to add another reference to my "Blogger Magic" post series."Blogger Magic" emphasises how easy it is, to use Blogger. How easy is it, to remember that syntax - to add a label link? Maybe, a "Blogger Magic" reference, in this post?When you read a blog post, that has label references, look at the bottom of the post.Please note the advice, at the bottom of the post.Look in the post footer, for the "Labels" section.Here's the bottom of another post, from this blog.Here's the bottom of this post.Note that not all blogs will provide a "Labels" posts section. That is an owner choice.Look at a label link, in the "Labels" section of the post - when provided.There's the bottom of two of my "Label Search" posts - "Blogger Magic - A Blog Within A Blog", followed by this post "Blogger Magic - Adding Label Search URLs". Now, look at the Labels links.In most blogs, the Labels links would be labeled "Labels". I call mine "Topics". As owner of this blog, that is my personal choice.Also, in most blogs, the "Labels" section will be found, in the post footer. Some blog owners have chosen to position their "Labels" in the post header. This, too, is their choice - and carries with it, some risk.See "Label Search"?Look in the browser status area, when hovering over the link caption.Look at the "Topics" section. See "Label Search"? Hover the mouse cursor, over the "Label Search" link.See the label search URL, in the browser status area?Look in the browser status area, when hovering over the link caption.Hover the mouse over "Label Search", and look in the browser status SearchFor a blog using an HTTPS redirect, you might see a slightly different URL.If this blog uses the "HTTPS: Redirect" option, you might see it slightly differently. on either of the above 2 links. OK, I cheated with the second link - since this blog, right now, does not support HTTPS - and I obviously don't want you looking at an HTTPS Error display.Whether HTTP - or HTTPS - is in use, there is the label search link.Whichever you see - and decide to use - with your blog, there is a label search URL. Now, get a label search URL from your blog - and use the URL, in another page or post in your blog.This post opens many links in new tabs / windows, intentionally.BTW - and if you have clicked on any of the links above - and since you have apparently read to this point - I have to warn you that many of the links, above, are intentionally coded to open in a new tab / window. That is necessary, based on the nature of the links in this post.Many of the links in this post are clickable, simply to illustrate to you the content in label searches - as opposed to links which lead you to additional information in the blog. So as not to lead you away from this post, you should not lose context after clicking on a link - as long as you simply close the new (illustrative) tab / window.My sincere apologies, if my seemingly gratuitous opening of new tabs / windows inconveniences or offends you.Some #Blogger blog owners w[...]