Skip to main content

FTP Publishing - August 2008

So once again this week, we have various bloggers, publishing (wanting to do so, any way) to remote servers using FTP, and complaining of the well known error
Your publish is taking longer than expected.


Sometimes, having reported this to Blogger, a Blogger employee will come back almost immediately with
We reset the server, and you should be good to go.
Other times, this symptom will drag on for days, and weeks. Occasionally - and keep an open mind here - problems with the host server can contribute to this error.

While awaiting action by Blogger, you might do yourself and others a favour, and provide details of your problem (as best you are able).
  1. Name of host server and connection type (FTP / SFTP).
  2. Geographical location of host server.
  3. Path, within the FTP server, of the blog.
  4. URL of blog.
  5. Name of template.
  6. How many posts in the blog?
  7. How many posts / days of posts in the main page?
  8. How many photos (average / best guess) in a typical post?
  9. How many photos (best guess) in the blog, but not in posts?
  10. How old is the blog?
  11. How is the blog archived (weekly, monthly, yearly)?
  12. How many posts (average / best guess) / archive period?
  13. What size (average / best guess) are your photos (160, 320, 480, 1600)?
  14. How many labels defined in the blog?
  15. How many posts / label, and labels / post (average / best guess)?


Note that
  • Blogs published by FTP use HTML and static publishing.
  • The number and average size of statically published pages will affect the amount of time required to publish your blog.
  • Each archive link, and each different label link, will be one more statically published page. The more posts in an archive, or the more posts with a given label, will make that static archive or label page larger.
  • The amount of time required to publish the blog will, in turn, affect how likely you are to see the mentioned error
    Your publish is taking longer than expected.

Considering all of the details, is it any wonder that you don't see that message more often? These are some reasons why I suspect that moving to custom domain publishing makes more sense, as your blog gets larger.

>> (Update 8/25 05:00): We see one example of where the host server was involved in the problem, and in finding a solution for the problem.

>> Top

Comments

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.