Blogger Magic - Third Party Templates

There are millions of Blogger blog owners - and each owner has their own idea, how their blog should look.

Not every blog owner is willing to settle for using a Blogger supplied template. Some blog owners design their own templates - and others choose templates provided by non Blogger developers.

Some blog owners - even those with no technical background - choose third party supplied templates, and demand instructions in Blogger Help Forum: Learn More About Blogger. Not every blog owner can be supported, according to their personal level of need.

It's OK for you to install a new third party template, for your blog - though you should plan to do some extra work.

Third party templates should include some installation instructions.

A template publisher should provide instructions for uploading and installing their template. Installation procedures may vary, however.

• Easy install.
• Template restore.
• Template Edit HTML.

Easy install.

If the template publisher is honourable, using an install script, provided by the template publisher, can be the most reliable install procedure. A well written script can extract the template of your choice from the publishers library, copy it to your blog, and tweak the install to your satisfaction.

Giving control of your Blogger account, to an unknown third party, is not always the best idea, however.

Template restore.

If the template publisher provides a template as an XML file, and describes the template as "for Blogger", you can install the template from the dashboard. You will first download the template of your choice, to a local computer.

With a template downloaded locally, you use the Blogger "Backup / Restore" wizard, in the dashboard Template page.

Start with the dashboard Template page.

Hit the "Backup / Restore" button.

Hit the "Choose File" button.

Now, you have the file manager, provided with your computer. Select the file, containing the template just downloaded.



The "Backup / Restore" wizard is part of the Blogger dashboard. The template will be selected, using the file manager wizard on the computer being used.

Template Edit HTML.

This is the most universal procedure - if the template is provided as HTML. Just use the Blogger "Edit HTML" wizard, in the dashboard Template page.

The simplest install uses "Edit HTML", from the dashboard Template page.

Copy the HTML or Text file content, into the window.



In some cases, you may have to do some work, to use an HTML template.

It's your blog - and the template choice is yours too.

You can use any acceptable third party blog template. Many blog features will perform best, though, if you use the Blogger supplied post template.

To ensure up to date Blogger code, always refresh the post template, after installing a third party blog template.

And as always, I'll suggest that you backup the template, before and after installing a custom template.

If you install a third party template, you may have to support your blog, on your own.

Please understand that Blogger won't be able to support your third party template - that is the responsibility of the template publisher. Problems with your blog, after installing third party accessories, will be yours to resolve.

---

There are millions of #Blogger blog owners - and each owner is different. Blog design - and templates used - will vary similarly.

Some blog owners cannot be satisfied by the Blogger supplied template library - and require third party produced templates.

Read More

Atom Vs RSS - Choose One, Using FeedBurner

Occasionally, we see a blog owner in Blogger Help Forum: Learn More About Blogger, asking about newsfeed formats.

Which is better, for my readers - Atom or RSS? How do I choose, what to provide, in my blog?

The competing newsfeed formats - Atom and RSS - have been a part of Internet life, for many years. Both formats have their devotees - and this is why there are two formats.

Both formats have their own advantages - and disadvantages.

You can change the URL of a FeedBurner source feed, to select Atom or RSS feed formats, from your blog.

You can use FeedBurner, or edit the blog template, to select a feed format.

Use the FeedBurner "Edit Feed Details" wizard, if you redirect your blog feed to FeedBurner.

If you don't use FeedBurner, you can edit the blog template, and manually change feed URLs. Note this will involve editing the post template, to change some links in the blog. This is not a recommended solution.

You may choose from 5 blog posts feed URLs, provided by this blog. You can do the same, with your blog.

• Atom (classic): http://blogging.nitecruzr.net/atom.xml
• RSS (classic): http://blogging.nitecruzr.net/rss.xml
• Atom (autodiscovery default, new): http://blogging.nitecruzr.net/feeds/posts/default
• Atom (new): http://blogging.nitecruzr.net/feeds/posts/default?alt=atom
• RSS (new): http://blogging.nitecruzr.net/feeds/posts/default?alt=rss

Do you really want to select Atom or RSS this way?

FeedBurner has two services, that let you mix and match Atom vs RSS.

• SmartFeed dynamically serves the right choice - Atom vs RSS.
• Convert Format Burner lets you statically select one format, or another.

Using either service, FeedBurner selects the desired feed format for you - regardless which Original Feed URL you provide, in "Edit Feed Details". Just give FeedBurner the default feed URL for your blog " ... /feeds/posts/default" - and let FeedBurner do the work, depending upon the service that you select.

You activate either service from the FeedBurner dashboard "Optimize" tab. Note that you should choose only one service, for each FeedBurner feed provided.

Important: We recommend not using this service if you use SmartFeed. SmartFeed will override any Convert Format settings in order to make your feed compatible with all feed readers, whether they support Atom, RSS, or both.

"SmartFeed" selects the best format, dynamically.

For the best experience by all readers, SmartFeed will automatically provide the feed format favoured by any feed reader used - as each reader views your feed.

Translates your feed on-the-fly into a format (RSS or Atom) compatible with your visitors' feed reader application.

Enable SmartFeed - and let FeedBurner choose the best format, for each different feed reader being used.



"Convert Format Burner" lets you choose the format - and version.

If the choice of feed format (Atom, RSS) - and even choice of format version (Atom 0.3, Atom 1.0, RSS 1.0, RSS 2.0) - matters to you, you can use Convert Format Burner, and select a specific format and version.

Nine flavors of RSS and now two formats of Atom ... who has time to keep track of it all? FeedBurner does! Let us convert your feed to any of the format choices listed below.

Enable Convert Format Burner - and you choose what feed format and version gets served, to all feed readers.



You can have multiple feeds, and multiple FeedBurner outputs.

If you have conflicting requirements, you can always setup multiple different FeedBurner feeds - and use different feed service options, for different feeds. You can then provide each feed in a consistent display, using the "BrowserFriendly" service.

---

If you want to serve the right newsfeed format from a #Blogger blog, you can either tweak the code in the blog template - or you can use a #FeedBurner feed, and activate the "SmartFeed" or "Format Burner" service. Using FeedBurner is a simpler choice, than the template editor.

Read More

Some bX Codes Caused By Zero Alpha ("rgba") Value

We're seeing a few reports of bX codes, that are not solved by simply resetting the template - and do not involve the mysterious "500 Internal Server Error".

In some cases, the blog owner may see a bX code when trying to use "Configure Blog Posts", or another Layout gadget wizard. If the blog itself can be viewed, and Template HTML Editor is usable, the bX error may come from use of a "0" Alpha color setting.

Blogger Engineering is aware of the problem, and has suggested that a fix is being developed. While we await the necessary fix, we may need to work around the problem.

The suggestion by Blogger Engineering is that we use a "Transparent" option, instead of "0" alpha value.

It seems that this issue is triggered by color variables with a value that has zero alpha, e.g. 'rgba(0, 0, 0, 0)'.

Some gadgets, and template sections, have the "transparent" selection in their color setup. Not all have this option, however. Some template CSS rules are not so easily edited.

The problem here is the "rgba" 4th value of "0" - ie, the "alpha" "0" value. The simplest solution is to change the "0" to a non zero value - without changing the "rgb" values.

The simplest solution, to get "Configure Blog Posts" or any other affected gadget usable, may be to use Template Editor, and change the values, directly. Look at every CSS rule, that has an "rgba" setting - and look for a 4th value of "0".

• For "rgba(0, 0, 0, 0)" - Change to "rgba(0, 0, 0, .1)".
• For "rgba(255, 255, 0, 0)" - Change to "rgba(255, 255, 0, .1)".
• For "rgba(255, 255, 255, 0)" - Change to "rgba(255, 255, 255, .1)".

A transparency setting of ".1" should be visually close to "0" - and should get the blog in question back online and updatable. And after Blogger Engineering fixes their gadget / template editor code, to accept the "0" value - and if the ".1" creates a noticeably unacceptable condition - this can be corrected, when necessary.

It's possible that this error, being seen, is part of a larger problem. You may need a persistent solution.

---

Some #Blogger bX codes, being seen in the forums right now, do not appear to involve terminal template corruption, and the mysterious "500 Internal Server Error". Some bX codes can be easily corrected, when they involve a "0 alpha" value (a CSS color rule involving an "rgba" setting).

When the Template Editor is usable, a simple search and replace for "rgba(nn, nn, nn, 0)" to "rgba(nn, nn, nn, .1)" may be sufficient to correct the error.

Read More

Recovering A Broken Template, Using "Edit HTML"

I have, for a long time, recommended regular template backups, for those who like to tweak the template.

Normal backup uses the "Backup" wizard, on the dashboard Template page. When backed up, an XML file, containing the template code, is extracted and saved locally. To restore, the "Restore" wizard is used and a previous Backup XML file selected.

That's how Backup / Restore should work - but it isn't always that easy.

With the current wave of bX codes, being used to diagnose the "Error 500", the Template dashboard page may not be accessible.

This is the case even attempting direct access, using the navbar "Design" link, or a hand generated equivalent.

With some blogs, the Template Editor may be OK - with the Template page broken.

For some blog owners who cannot use the dashboard Template page, the Template Editor aka Template "Edit HTML" may be accessible. This will require using a hand generated URL - since there is no direct link to the Template Editor.

If the Template Editor can be accessed directly, the blog owner may be able to continue.

1. Access the Template Editor for the broken blog, in one browser window.
2. Setup a new blog, using a clean template, in a second browser window.
3. Access the Template Editor for the new blog.
4. Copy the new blog template, to the broken blog.
5. Save the now recovered current blog template.
6. Refresh the post template.
7. Clear cache, cookies, and sessions, restart the browser, and try again.

The blog owner has a possible solution, in this case.



Access the Template Editor for the broken blog, in one browser window.

Use a hand generated URL, to access the Template Editor. If you can do this much, you are well on the way to getting your blog back.

If you truly feel the need, you can backup what's there, before you paste over what you have. Ctrl - A then Ctrl - C to copy - then Ctrl - V, into a new text document - that you can save, at your convenience.

Setup a new blog, using a clean template, in a second browser window.

Blogs are free, so make a new one. Select the "Simple" template, for best results.

Access the Template Editor for the new blog.

For the new blog, you can use the dashboard menu, and Template - "Edit HTML".

Copy the new blog template, to the broken blog.

With the Template Editor window for the new blog, containing a valid template, copy its contents (Ctrl - A then Ctrl - C) - into the Template Editor window for the broken blog (Ctrl - A then Ctrl - V).

Save the now recovered current blog template.

Hit "Save template". And say a brief prayer.

Refresh the post template.

This may not be necessary - but you should consider it. It has saved a few blogs.

Clear cache, cookies, and sessions, restart the browser, and try again.

This is always a good idea, when clearing bX codes.

It's a workaround - not perfect, but it may get the blog going again.

This is not a perfect solution. If you are tired of the bX codes, and if this will get your blog operational, you may find it useful, however. It's also possible that this error is part of a larger problem - and you need a persistent solution.

If you have a template back up, you can apply that after the blog is back in service. And your readers have stopped emailing you with angry complaints. Just use a clean backup.

And test your tweaks, going forward, more carefully.

---

Some bX codes, being used to diagnose the "Error 500" condition in #Blogger blogs with broken templates, affect the dashboard Template page. Blogs which have broken Template pages cannot be recovered by getting a new template.

In some cases, with the Template page unusable, it may be possible to directly access the Template Editor - then paste a separately developed clean template into the "Edit HTML" window, and correct the problem.

Read More

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

Read More

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

Read More

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

Read More

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.

Read More