Skip to main content

Layouts Templates Use Dynamic HTML, And Dynamic Server Access

Every week or so, someone writes
I do not understand why Blogger tells me that I cannot change my layout using the GUI template wizard (add gadgets, use Labels fully, have the "Next Post" / "Previous Post" links, restrict blog access, ...), simply because my blog is not hosted on a Google server. Why do FTP published blogs get second class treatment?
with the implication being that Blogger is shortchanging FTP published blogs, to coerce their owners into publishing on a Google server, either to Blog*Spot, or to a Custom Domain.

The answer here is a bit simpler. You can't use a Layouts template, or the GUI features, because a Layouts template is written in dynamic HTML. Dynamic HTML requires that the server with the blog content (ie Blogger) be accessed by the blog reader, as the blog is being read.

When you publish by FTP, to a server distant from Blogger, you are publishing statically. The publishing process sets up the blog on the distant server once, and all access to the blog is against a static image on that server.

One blog post could be displayed as a post page, as part of an archive page, as part of a label search page (and with any number of labels relevant), or as part of the main page - you can't publish all of the possibilities statically. You have to build each page dynamically, based upon the link just clicked on. That requires access to the blog content - and that won't happen with an FTP host server, because the blog content is on Blogger, which is another server far away.

It's not a conspiracy, nor a coercive tactic, just a technical impossibility. If you have a blog with a classic template, consider upgrading your blog to a layouts template. If you are using a classic template because you like HTML based blogs, upgrade to layouts anyway - and combine the layouts template with your current HTML code.

>> Top

Comments

Janice said…
I followed this link from the Google Groups page, where it tells me that I must log in and then tells me that my name is already in use and can't be used. (Although it's in use by me.)

At any rate I wanted to say thanks for the information about using the custom layout feature. I assumed when it mentioned a custom domain that it meant just that... and that it could be hosted anywhere.
Thanks again,
Janice
Chuck said…
Thanks for the update, Janice. This is a source of confusion occasionally, which is why I wrote Publishing Your Blog Externally
Thank you for the tip, It worked!

Popular posts from this blog

Custom Domain Migration - Managing The Traffic

Your blog depends upon traffic for its success.

Anything that affects the traffic to your blog, such as any change in the URL, affects the success of your blog. Publishing the blog to a custom domain, like renaming the blog, will affect traffic to your blog. The effects of the change will vary from blog to blog, because of the different traffic to every different blog.Followers. People who find your blog because of recommendations by other people.Search engines. Robotic processes which methodically surf your blog, and provide dynamic indexing to people who search for information.Subscribers. People who read your content from their newsfeed reader, such as the dashboard Reading List.Viewers. People who read your content from their browser.No two blogs are the same - and no two blogs will have the same combinations of traffic sources.

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.