Blogger.com has suddenly started returning a horrible error when my blog client tries to create a post with the Atom protocol. The client has been working fine for months and months and months.
Whe I try to create a post I get the following response:
Exception caught but no reason given: com.google.blogger.exceptions.PostNotFoundException
Since I suspected that my client was broken, I also tried to create an Atom Entry with curl . I got the same error:
> Blogger.com has suddenly started returning a horrible error when my > blog client tries to create a post with the Atom protocol. The client > has been working fine for months and months and months.
> Whe I try to create a post I get the following response:
> Exception caught but no reason given: > com.google.blogger.exceptions.PostNotFoundException
> Since I suspected that my client was broken, I also tried to create an > Atom Entry with curl . I got the same error:
it's sunday 1139 CST. that bug must be a monster bug from outter space, as the problem continues to dampen our blogging spirits. can you give us an about time when this will be fixed?
Steve Jenson wrote: > This is a bug. I am working to fix it. Sorry for the trouble.
> Thanks, > Steve
> On 3/31/06, odacrem <paulmerc...@gmail.com> wrote:
> > hello,
> > Blogger.com has suddenly started returning a horrible error when my > > blog client tries to create a post with the Atom protocol. The client > > has been working fine for months and months and months.
> > Whe I try to create a post I get the following response:
> > Exception caught but no reason given: > > com.google.blogger.exceptions.PostNotFoundException
> > Since I suspected that my client was broken, I also tried to create an > > Atom Entry with curl . I got the same error:
I'm having the same problem. Just wondering if there is any estimation on when this bug is going to be fixed, or if there is another work-around that can be used for the time-being?
I too, am using PHP's curl library to connect to blogger.com, and not really doing anything incredibly complicated. I just really need to have posting start working again.
The wget.exe client I am using is suddenly returning a 404 error when I post to the website. This stopped working on March 31st after more than half a year of daily automated posts. Something has obviously broken.
Looks like I'm not the only one with this issue.
FYI, the wget.exe command line arguments I'm using are as follows:
If this was to happen at my company, and the admin let this problem hang around for four days with no action, someone would be demoted or fired. Of course, I don't know how severe this is, and maybe I'm not being generous enough. But this is very frustrating. I've already wasted a lot of time investigating this.
> Blogger.com has suddenly started returning a horrible error when my > blog client tries to create a post with the Atom protocol. The client > has been working fine for months and months and months.
> Whe I try to create a post I get the following response:
> Exception caught but no reason given: > com.google.blogger.exceptions.PostNotFoundException
> Since I suspected that my client was broken, I also tried to create an > Atom Entry with curl . I got the same error:
> The wget.exe client I am using is suddenly returning a 404 error when I > post to the website. This stopped working on March 31st after more than > half a year of daily automated posts. Something has obviously broken.
> Looks like I'm not the only one with this issue.
> FYI, the wget.exe command line arguments I'm using are as follows:
> If this was to happen at my company, and the admin let this problem > hang around for four days with no action, someone would be demoted or > fired. Of course, I don't know how severe this is, and maybe I'm not > being generous enough. But this is very frustrating. I've already > wasted a lot of time investigating this.
> odacrem wrote: > > hello,
> > Blogger.com has suddenly started returning a horrible error when my > > blog client tries to create a post with the Atom protocol. The client > > has been working fine for months and months and months.
> > Whe I try to create a post I get the following response:
> > Exception caught but no reason given: > > com.google.blogger.exceptions.PostNotFoundException
> > Since I suspected that my client was broken, I also tried to create an > > Atom Entry with curl . I got the same error:
This is the error I got also (client is MarsEdit.app) Status code: 404 Succeeded: NO --Fault Error-- Fault code: 404 Fault string: Exception caught but no reason given: com.google.blogger.exceptions.PostNotFoundException Response text: Exception caught but no reason given: com.google.blogger.exceptions.PostNotFoundException
You beat me to it! Yes, I pushed a patch 10 minutes ago. There are still a few unresolved issues but this fixes the major problem that you all are seeing. Later in the week, there will be a patch pushed for
1) extra div's showing up 2) NullPointerException if posting an entry without a body (no <content> tag).
|
