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

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

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

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

Unfold Widgets Selectively, Instead Of All At Once

The new Template HTML Editor has been with us for just under 2 weeks.

Not every blog owner sees the new editor as an improvement. Some folks don't understand how to find the code sections, where they need to apply changes - and would probably be happier if "Expand All Widgets" were an option.

Like the old saying goes, you just cannot please everybody.

Fortunately, with this change, it's not difficult to find the code sections that need changing - you just do a little bit of research, before using "Edit HTML".

With the old editor, finding a section that needed changing could be a bit frustrating - though simple, given enough time.

1. Hit "Expand Widget Templates".
2. Search for a recognisable section of code.
3. Try very carefully, to find the right section of code.
4. Be careful, and don't select the wrong section of code.

With the new editor, you have a bit more work to do - and what you have to do appears to be simply repetitive.

1. Find a folded code section.
2. Unfold the section that's folded.
3. Repeat, until everything is visible.
4. Search for a recognisable section of code.
5. Try very carefully, to find the right section of code.
6. Be careful, and don't select the wrong section of code.

Instead of spending so much time unfolding, searching, and rechecking everything, why not do some research? Figure out what needs changing. Look at the display on the dashboard Layout wizard (previously called "Page Elements"). Identify the widget to be changed, using both the relative position on the page, and the title.

Find the widget id, by looking at the widget to be changed, then at the URL behind the "Edit" link. If you're editing the post template, you'll be looking at "Blog Posts", which has the widgetID of "Blog1". Click here, for instructions on determining the widget id.

Once you have the widgetID, for the specific widget that you need to modify, go to the Template "Edit HTML" wizard, use the "Jump to widget" pull down list, select the widget by widgetID, and there it is. Now, unfold that widget, and do what you have to do.

Isn't that simpler, when you think about it?

>> Top

All Template Changes Won't Always Be Visible, When The Blog Is Published

Not all blog owners appreciate the differences between using the various template wizards, and what they will actually see, once the blog is published.

The confusion about the various template wizards, and what is actually seen, expressed in Blogger Help Forum: Something Is Broken, is numerous.

Why aren't my changes to the template being saved?

This question is expressed in a number of ways - and has a number of causes.

There are a number of causes of template problems, in general.

• Some problem are caused by Blogger Engineering, as they manage the Blogger application.
• Some problems are caused by the blog owners, as they use (and yes, misuse) the Blogger application.
• Some problems are simply caused by the perception of the blog owners, and will never be resolved, to everybody's expectations.

If you're viewing this blog using a desktop / laptop computer, with a "normal" browser, and you can find the "View Source" control, take a look at the source for this page. Compare what you see there with the display in the Template "Edit HTML" wizard (and allow for some confusion, when using "Edit HTML").

• If you have a "normal" browser, and are viewing this blog in a "Designer" / "Layout" template, you'll see a lot of the same code, in both "Edit HTML" and "View Source".
• If you have a "normal" browser, and are viewing this blog in a "Dynamic" template, you'll see very little of the same code, in both "Edit HTML" and "View Source".
• If you have a "normal" browser, and are viewing this blog using a redirected "mobile" browser view, you'll see very little of the same code, in both "Edit HTML" and "View Source".
• If you're using a "mobile" computer, you probably won't even have an option to "View Source".

The bulk of the options in the Template "Edit HTML" wizard, in the "Layout" wizard, and in the Template Designer, are intended to change the "Designer" / "Layout" template views. The three wizards have much less effect, against the "Dynamic" / "Mobile" template views.

If you tweak the CSS settings in "Edit HTML" or the Template Designer - or if you change the layout using "Layout" or the Template Designer - you may not see all of the changes reflected in either a Dynamic or Mobile view.

Sometimes, this is because you have already tweaked the template improperly, preventing the wizard from saving your latest changes. Other times, it may be simply because the Dynamic and Mobile templates are not designed to let you tweak the settings in question.

We've also seen vague suggestions that having the mobile template active can cause the Template Designer font and style selections to be non operational. Font settings, made using the Template Designer, won't be saved and won't appear in the blog, when published. Right now, we're unsure whether the Live Preview window updates reliably.

And recently, uncontrolled customisation of the blog accessory complement, and of the dynamic template code, have caused instability in network access, when viewing blogs using dynamic views.

>> Top

The Option To "Expand Widget Templates", In The Template "Edit HTML" Wizard, Is No More

One of the more confusing features of the Blogger Template "Edit HTML" wizard, used to be the option to

Expand Widget Templates

With the new "Edit HTML" wizard, that option is not needed. Given the choice to "Expand Widget Templates", the typical blog owner was frequently caught between a rock, and a hard place, when editing gadgets.

• Don't use the option - and the gadget code section, which was to be edited, remained concealed.
• Use the option - and all gadget code sections were expanded, revealing all gadget code.

This frequently left the owner with either no information - or too much information, from which to work. Broken templates, caused by improper template HTML edits, were common.

The new Template "Edit HTML" wizard replaces the single "Expand Widget Templates" option with selective widget expansion. Now referred to as "folded" code, a concealed widget code section is identified by a fold marker ("sideways arrow icon"), next to the line number.

The code inside the widget is folded by default.

Clicking on any fold marker, the concealed gadget code section is revealed. If the now revealed code section itself contains concealed code sections, those sections are displayed as folded, and can then be revealed - if necessary, and only if necessary.

Thus we can eliminate unnecessary depth (internal gadget code sections) and width (additional gadget code sections) from being displayed when we only need to edit a specific gadget, at a given level of complexity. This will make it easier to identify and to edit the necessary lines of code, and to avoid editing lines of code which should not be edited.

If you're looking for a specific section of the template - for instance, the CSS rules - you may find that section folded also. CSS rules, for instance, are at the top of the template.

<b:skin>---</b:skin>

and

<b:template-skin>---</b:template-skin>

On the other hand, if you're looking for the content of an HTML / JavaScript gadget, that's still edited from the specific gadget in the Layout wizard.

<data:content/>

Gadget content is not folded.

Hopefully, we'll soon see less problem reports, in Blogger Help Forum: Something Is Broken, about broken templates - though we will probably continue to see confusion, about templates that only appear to be broken.

As always, if you change template code, remember to clear browser cache and restart the browser, before concluding that your changes were not effective.

>> Top

The LightBox Image Display Option Stopped Working, Recently

Last week, the popular display option, Lightbox, used for showing full size images in Blogger blogs, stopped working.

Anxious blog owners reported that full size images are now being displayed in a normal browser window, with the browser back arrow required to return to the blog display - instead of the elegant black background overlay with the mysterious "X" which closes the overlay. The problem appears to affect all images in the blogs affected.

An immediate sampling of the forum problem reports suggested that it's likely that all Blogger blogs are affected. Since not all blogs may contain enough images, and be owned by people who are attentive enough, we are not seeing massive volumes of problem reports.

We did open a rollup discussion, in Blogger Help Forum: Something Is Broken, where we are gathering a good sample of the blogs involved. To date, no obvious affinity has been discovered, in the over 100 responses posted.

Today, we have a mysterious suggestion, posted in a forum discussion, which may provide a workaround for the problem.

We are advised to add a brief snippet of code to the template.

<script src='http://www.blogger.com/static/v1/jsbin/2321381434-lbx__fr.js' type='text/javascript'/>

The snippet in question is added to the very end of the template, using the "Edit HTML" option, in the dashboard Template wizard, after </body>, and before </html>.

</script>
</body>
<script src='http://www.blogger.com/static/v1/jsbin/2321381434-lbx__fr.js' type='text/javascript'></script>
</html>

I added this snippet of code to the template for this blog. I don't use a lot of images in this blog - but you may examine one previous post, where you will find a picture. If you click on that one picture, you will see the full size image displayed in Lightbox format - which was not the case, earlier today.

The code snippet in question is hosted in "blogger.com", so it should be safe. And, it's not difficult to add - or to remove. That said, I have no idea if it may conflict with other code - so anything is possible. It is marginally more reliable than third party code.

I've done no further testing of this fix, so I'll await your feedback. You may comment here - or in the rollup discussion.