No more spinner of death.With dynamic HTML, blogs are published as the reader reads them, and in small portions, selectively. When you update your blog - add a post, change the template, etc - all that changes is the source code. The source code is rendered into actual web site pages as the readers read the blog.
Since most readers will be reading the same portion of the blog - the main page - this makes sense. Publish what's needed, as needed. The larger the blog gets, the more that this makes sense. The older posts, that nobody reads but occasionally, publish later.
This requires web servers that can access the blog code, and publish on the fly, which is simple for blogs published on BlogSpot. For blogs published to non-BlogSpot servers, ie by FTP publishing, this won't be so simple. Blogger has to allow for old fashioned static publishing, for blogs published to other web servers.
Which brings back the old Spinner of Death, now repackaged as a simple advisory message
Your publishing is taking longer than expected. To continue waiting for it to finish, click here.And the larger the blog, the longer the publishing takes, and the more this message is being seen. It's also possible that less servers are being made available to handle FTP publishing, or maybe more blogs are being published by FTP, which means that more sharing of servers is done during FTP publishing. This will make everybody's FTP publishing take longer.
Then too, it's possible that people who publish externally tend to have larger blogs. The older (and larger) blogs may be owned by more experienced bloggers. Publishing externally isn't something done by those with less experience.
Maybe you, the owner of a blog published by FTP, would benefit from watching how the publishing takes place. Short of examining FTP publishing logs on Blogger.Com (right), you'll have to settle for looking at the logs provided by the owner of the server that hosts your blog, if anything is available there.
Or maybe you can simulate the publishing process. When you backup your blog, you're effectively publishing it to your local server. HTTrack, and similar mirroring products, effectively publish your blog locally, though as a client side process.
With your blog published once to your external server, and your readers able to access it there, try republishing it back to BlogSpot, under any URL that's available. Once you have it published back to BlogSpot, try mirroring it, using HTTrack or a similar product.
What you see may make you understand why you see
Your publishing is taking longer than expected. To continue waiting for it to finish, click here.more often.