Skip to main content

FTP Publishing - August 2009

This week, we are seeing the return of the well known FTP Publishing symptom
Publishing your blog is taking longer than expected. To continue waiting for it to finish, click here.


There are several threads in Blogger Help Forum, reporting this problem with various amounts of detail.

If you are suffering from this problem, please provide details of your experience, to help Blogger Support get a start diagnosing the problem.
  • The blog BlogSpot URL (if applicable).
  • The blog domain URL.
  • The name of the server hosting company, or URL of the host server.
  • The Blogger FTP server setting value.
as part of your problem report. If you're able, work with the server support staff, and examine the server activity and firewall logs, and see what is seen from the server perspective too.

(Update 8/4 6:30): One blogger has found a possible workaround by adjusting the value of the "FTP Path" setting, relative to the "Blog URL" setting.
With the trailing slash in the Blog URL an FTP Path in the format web/html/www/ would work.

Without the trailing slash in the Blog URL the FTP Path needed to be in the format www/ to work!


>> Top

Comments

Healthy Life said…
but can you give me the email id to whom i should send the details so that my issue get solves one and for all
Nitecruzr said…
No, I cannot provide an email id to whom you should send the details, because, and I will repeat this yet again, FTP Publishing problems are not the fault of only Blogger. FTP Publishing problems are the result of compromises by Blogger, due to the necessity of supporting connections with hundreds of different remote servers.

Every day, new remote servers come online, and others go offline, and Blogger has to constantly tweak their code. And sometimes, stuff stops working because of what Blogger does, other times, it's because of what we do, or what the remote host support staff does (and there are hundreds of remote hosts, each with different policies).

So no, there is no email id to whom you should send the details.

Post them in Blogger Help Forum, and be patient.
Bobby John said…
I was having the same problem and was looking around for a fix for a while. For me, I noticed the permissions on my files (blog.html, individual blog posts, and archive posts) had permission set to read only (444). I added permission to write on the file (644) and it worked fine. Hope it helps someone.

Popular posts from this blog

What's The URL Of My Blog?

We see the plea for help, periodicallyI need the URL of my blog, so I can give it to my friends. Help!Who's buried in Grant's Tomb, after all?No Chuck, be polite.OK, OK. The title of this blog is "The Real Blogger Status", and the title of this post is "What's The URL Of My Blog?".

Leave Comments Here

Like any blogger, I appreciate polite comments, when they are relevant to the blog, and posted to the relevant article in the right blog. If you want to ask me a question thats relevant to blogging, but you can't find the right post to start with (I haven't written about everything blogger related, yet, nor the way things are going I don't expect to either), ask your questions here, or leave an entry in my guestbook.

As noted above, please note my commenting policy. If you post a comment to this post, I will probably treat it as a "Contact Me" post. If you have an issue that's relevant to any technical issue in the blog, please leave a comment on the specific post, not here. This post is for general comments, and for non posted contact to me.

If the form below does not work for you, check your third party cookies setting!

For actual technical issues, note that peer support in Blogger Help Forum: Something Is Broken, or Nitecruzr Dot Net - Blogging is, almos…

What Is "ghs.google.com" vs. "ghs.googlehosted.com"?

With Google Domains registered custom domains becoming more normal, we are seeing one odd attention to detail, expressed as confusion in Blogger Help Forum: Learn More About Blogger.My website uses "ghs.google.com" - am I supposed to use "ghs.googlehosted.com", instead?It's good to be attentive to detail, particularly with custom domain publishing. This is one detail that may not require immediate attention, however.