Social Icons

Pages

Showing posts with label Network Problems. Show all posts
Showing posts with label Network Problems. Show all posts

Sunday, 18 August 2013

Dynamic Template Instabilities Have Multiple Causes

For some time, we've been seeing reports, in Blogger Help Forum: Something Is Broken, about blogs using blogs using dynamic views, which display incompletely, and lack specific features.

Various blog owners have developed, and reported, a workaround to the problem, which involves using an unpublicised Blogger setting found in the template HTML code. This workaround sets a loading delay, known as Timeout.

There are several different causes of the dynamic view problem - some varying by the different blogs, others varying by the blog viewers - and some, varying by the Blogger / Google infrastructure. None of the causes will be universal in effect. This will result in varying success, when using a static Timeout setting as a workaround for the problems.

The current workaround for the problem - changing the Timeout setting - will have immediate success with some blog owners, partial or temporary solution with many, and no solution with others.

The inconsistency will come from the various causes of the latency - and from the variety of symptoms being reported. The latency is the cause for development of the Timeout tweak.


There are three details which cause latency, and which result in missing dynamic view content, of varying effect.
  • Complexity of blog content - unique to each blog.
  • Computer and network issues - unique to each different client computer.
  • Server and network issues - unique to the Blogger / Google networks and servers which support dynamic templates.

Complexity of blog content is the only detail which can be consistently resolved, by a change in the Timeout. As any dynamic template blog becomes more complex, increasing Timeout improves the chance that all blog content - including gadgets and template customisations - will be packaged before the blog is viewed. Each blog owner will be responsible for evaluating the need for this workaround, on an ongoing basis - based on current blog complexity.

Computer and network issues causes problems, that may be partially resolved, by the blog owners. Each blog owner can make the Timeout relevant to the known audience. Any blog, with an audience known to have problems, can be tuned by the blog owner, as necessary. Each blog owner will be responsible for evaluating the need for this workaround, on an ongoing basis - based on the needs of the majority of the known blog viewer audience.

Overall load on the Blogger / Google networks and servers causes problems that cannot be consistently resolved, by the blog owners. It's possible that some portion of the latency problem is regional in nature - in that Blogger / Google resources may not be evenly allocated, world wide, to support dynamic template use. Blogger / Google will be responsible for evaluating the need for this solution - based on current complaint level and load on network resources.

Any action taken by Blogger / Google will present a challenge, for several reasons. Note the problems discussed here are unique to dynamic views - because of the unique design of the dynamic templates.
  • The Timeout setting will have a global effect, for each blog with a problem - even though the problem may not be global.
  • As more blog owners resolve their immediate problems, by increasing the Timeout, this will put more load on Blogger / Google resources.
  • As more blog owners report their immediate problems solved, this will encourage still more blog owners to use dynamic templates, and to try increasing the Timeout on their blogs.
  • More blogs using dynamic templates will put still more load on Blogger / Google resources - and this will necessitate still more Timeout increases.
  • Some blog owners, using computers or Internet service particularly susceptible to causing the symptoms, may try the basic workaround ("500"), which may not produce results - and may falsely conclude that their symptoms are not caused by the problem. A few owners may persistently try "1000", or "2000" or higher - and may eventually observe an improvement - while other owners may not.

The only long term solutions to this problem lies with Blogger / Google. Blogger / Google has two options.
  • Halt or restrict customisations of dynamic templates.
  • Tune their network resources better, to make latency less of an issue.

The latter option will require supporting action, by blog owners and readers.
  • People who view blogs using dynamic templates have to tune their own computers and networks, so they do not contribute to the problem.
  • Some blog owners may have to accept reality - that their reader audience simply can't be properly served, given the level of customisation required by their blog design.

The bottom line is that some blogs will never be properly served, if the owners insist on using dynamic templates, and customising uncontrollably. Blogger / Google cannot provide the universal solution.

>> Top

Friday, 9 August 2013

Dynamic Template Instabilities Have Multiple Symptoms

Recently, we've been seeing a few reports, in Blogger Help Forum: Something Is Broken, about blogs using dynamic templates, which display incompletely, and lack specific features.

Various blog owners have developed, and reported, a workaround to the problem, which involves using an unpublicised Blogger setting found in the template HTML code. This workaround sets a loading delay, known as Timeout.

The currently recommended Timeout setting will force a fixed delay on blogs using the workaround, which may not be 100% effective in all cases. The effectiveness may vary, according to the specific problems reported by the various blog owners.

Problems reported by blog owners, which involve dynamic templates, center around several distinct areas.
  • Absence of comments, displayed after the posts.
  • Absence of multiple gadgets, in the popout sidebar.
  • Absence of Pages entries in the display header bar.
  • Absence of Posts ("No Posts Found"), with blogs heavy on photos.
  • Absence of template tweaks, applied using "Add CSS".
  • Absence of template tweaks, applied using "Edit HTML".
Each of these different symptoms will be caused by different needs, in publishing a blog - and the different symptoms will be observed by owners with different technical skill level.

Absence of multiple gadgets, in the popout sidebar is probably common to most blogs, as most blogs have more than one accessory gadget. Blog owners reporting this problem may be of very low technical skill level - and will likely have problems applying the workaround.

This problem may be more common than problem reports would imply - as not everybody with a blog, with this problem, will observe the unusually short accessory tab when the accessory bar is docked.

Absence of comments, displayed after the posts will be observed by blog owners who focus on comments, as part of their networking strategy. This will generally involve the more popular blogs (with lots of comments, making their absence more noticeable). Blog owners reporting this problem may be of low technical skill level - and may have problems applying the workaround.

This problem may be more common than problem reports would imply - as not everybody with a blog, with this problem, will observe the absence of comments, displayed after the posts. Some owners, with blogs which receive less comments than others, may not even care.

Absence of Pages entries in the display header bar will be reported by blog owners who have setup a complex structure of dynamic and static pages, and a Pages index to index the pages. The blog owners reporting this will have medium skill level, with the ability to use the Pages wizard. These owners may not necessarily have the ability - or desire - to use the Template Editor effectively. Some of these owners may have problems applying the workaround.

Absence of Posts ("No Posts Found"), with blogs heavy on photos, will be visible in blogs using "Flipcard", "Snapshot", and similar views. Blog owners reporting this problem may be publishing photoblogs. These blog owners will be those who spend a lot of time providing photos - and who may not notice other symptoms, like missing header or sidebar features. These blog owners may be of low technical skill level - and may have problems applying the workaround.

Absence of template tweaks, applied using "Add CSS" will be reported by blog owners who carefully applied appearance and style tweaks, using the Template Designer. The blog owners who apply these tweaks will have medium technical skill level, and the ability to use the "Add CSS" feature in the Template Designer. Some of these owners may have problems applying the workaround.

Absence of template tweaks, applied using "Edit HTML" will be reported by blog owners who customised the blog appearance, using the Template Editor. These blog owners will be of the highest technical skill level. These owners should have no problem applying the workaround.

With the assortment of problems to be fixed by Blogger Engineering, we will likely see each problem worked on, separately. As each problem is solved, we'll likely see new problems become more visible - and existing problems become more urgent, in the eyes of the blog owners.

The number of different possible symptoms, in combination with the number of possible causes of the problems, will create an apparently infinite number of differing complaints - and inconsistent visibility of the problems. Blogger Engineering will be busy, for a while, resolving these problems.

>> Top

Sunday, 4 August 2013

Dynamic Templates, And Network Problems - #2

We're been getting problem reports in Blogger Help Forum: Something Is Broken, from various dissatisfied blog owners, who chose a dynamic template for their blog.

The problems reported involve various symptoms.
  • Blogs displayed will lack various gadgets, in the slideout gadget bar.
  • Some blogs, when customised, will display using default layout and template settings.
  • Some customisations, applied recently, just won't show up.
Various blog owners have discovered a solution, based on code present in newer dynamic templates. This solution has been publicised, in forum discussions - and in various blogs and web sites.
<script language='javascript' type='text/javascript'>
setTimeout(function() {
blogger.ui().configure().view();
}, 1000);
</script>
The solution, as proposed, involves a very simple change - but the change won't be immediately, or permanently, 100% effective.

The solution, being publicised by various blog owners and forum helpers, involves a very simple change, using the template editor.
Once you have a secured a back up of your blog template, click on Edit HTML and you will see the html editor come up. Scroll down to the bottom of your template to where you see code that looks like this.
<script language='javascript' type='text/javascript'>
setTimeout(function() {
blogger.ui().configure().view();
}, 0);
</script>
Change the 0 to 1000 so it looks like this.
<script language='javascript' type='text/javascript'>
setTimeout(function() {
blogger.ui().configure().view();
}, 1000);
</script>
Click on Save Template.
Here, as always, I will strongly recommend that you backup the template, twice - before, and after, you make this template change.

This solution - changing the Timeout setting - will have immediate success with some blog owners, partial or temporary solution with many, and no solution with others.

The number of possible causes of the problems, in combination with the variety of possible symptoms, will create a visibly infinite number of differing complaints - and some complaints will continue, even with the workaround applied. Blogger Engineering will be busy, for a while, resolving these problems.

Once again, I'll suggest that you consider the functional and historical reasons for existence of the dynamic templates. Consider exercising some restraint, when customising your blog. Be part of the solution.

>> Top

Thursday, 11 July 2013

Dynamic Templates, And Network Problems

We're getting a few problem reports, in Blogger Help Forum: Something Is Broken, from blog owners who chose a dynamic view for their blog.
My layout has one colour - yet when I view my blog, it's another colour. The accessory bar is missing gadgets - and there are various tweaks missing. I tried updating, using the Template designer, unsuccessfully. When I finished updating, the preview looked good - but when I saved and viewed my blog, it was still incomplete.

This blog owner, like many owners, may not understand the unique design of the dynamic templates - nor how the design affects what is seen by the readers.

The complexity of a Blogger blog is not truly appreciated by anybody, until possibly when a blog has to be backed up or re built.

There are many components of a Blogger blog - not just the comments, posts, and template.
  • Accessories.
  • Comments.
  • Decorations.
  • Gadgets.
  • Posts.
  • Layout / Template.
  • Third party hosted accessories and tweaks.
  • URL.

With a non dynamic ("Designer" or "Layout") template, the blog is packaged for viewing, from the many components, on the Blogger servers. When you get a page of a blog, on your computer, it's already packaged - and what you see is immediately ready for viewing.

With a dynamic template, the comments, the posts, the template, and the various other components all arrive separately from the various Google and non Google servers, which provide the blog content - and the blog page is packaged, for viewing, on your computer.

If any piece of the package does not arrive at your computer as soon as the other content, the blog page is packaged, from what is available - but it's going to be missing pieces.

This is why some folks see the posts without the tweaks applied using Template Designer - or the layout lacks a key improvement made using "Edit HTML" - or maybe the accessory bar is short. A piece of the package did not arrive, before the packaging was complete - and the blog was displayed, incomplete.

The alternative would be to have the packaging process wait longer - but how long do you want to wait? What happens if your computer (or your reader's computer) cannot connect to one key Blogger server, to download that one essential component?

How long should a moron wait, before giving up, and asking for details? Or at least clearing cache, and restarting the browser, before trying again?

Packaging a blog page, on the reader's computers, has benefits - and drawbacks. If you occasionally see an inconsistency in your blog, imagine your various readers, with some seeing your tweaks and others seeing only a basic (Blogger standard) template - and you never knowing what everybody is seeing.

For best results, you need to keep the dynamic views simple.
(Update August 2013): We have a workaround to the problem - but the workaround is not going to be 100% consistently effective. The lack of consistency is going to be especially noticeable, because of the several different symptoms being reported.
>> Top

Friday, 31 May 2013

When Using Template "Edit HTML", The Edit Window Remains Blank

Since Blogger released their improved Template Editor, blog owners have been reporting a new, transient problem.
I click on "Edit HTML", and the editing display opens - but the HTML window remains blank.

Generally, you may wait a few seconds, and the HTML window will fill with the content. With enough patience, you'll see the content arrive - eventually.

Unfortunately, waiting won't always provide a solution.

Sometimes, you see the Template Editor display open, with a blank HTML window - and you wait patiently, with no result.

With the Template Editor display (common to every blog, and requiring no security) - and the Template HTML (unique to every blog, and requiring security) - coming from different servers - there's always the possibility that a dropped connection, from the Template HTML server, may cause the browser to time out.

In many cases, this will be a transient error. All that you need to do is to refresh the display.
  • Try a browser refresh. F5, or maybe Shift - F5, forces a refresh, in most browsers.
  • Restart the Template Editor. Click on Template, then "Edit HTML", again.
  • In extreme cases, clear cache, cookies, and authenticated sessions (since this is secure content, you'll need a new authenticated session) - then restart the browser, and start over.

If the lost connection is not transient, your Internet service may be part of the problem. If a simple refresh does not solve the problem for you, you may want to look at the MTU setting, on your computer.

An overly ambitious Maximum MTU setting could cause a chronic or persistent dropped connection, with the Template HTML server. Lowering the Max MTU setting could resolve this symptom.

>> Top