Blogger Atom Server

Hey James,

Sorry to hear you are getting that error.
Are there any steps you are doing that always cause this?
(so I can reproduce it).

I'm currently re-writting the blogger support for the new Blogger API (in beta), and really want to fix these issues, just need to know what causes them :)

This was not an identical incident. See below.

Started up PerFormancing. Clicked on empty title box and an Alert Dialog box came up saying "There was a possible error contacting Atom Server."

Typed a Test title and a Test message, clicked box for Post as Draft. Clicked Publish To - Received identical Alert Dialog box.

The posting did not arrive at Blogger.com's dashboard.

This time there was no comment in the alert box concerning dom.

Jed, I do not know what is causing it to occur and why it behaves differently and sometimes does not occur at all.

This time I got the dom complaint. It also said that the server might be down.

However, I can go in and out of blogger's dashboard and do whatever with no problems.

Error:
Type Error: dom has no properties

James

I get the Atom error described by Shewmaker on a daily basis. Probably every third time I use Performancing. Seems to be something going wrong in the communications. I can almost always log into blogger the old fashioned way, so it does not appear to be a full blogger outage if that's any help.

I have the same problem. I have three blogs that I typically post to through blogger and receive the same error messages just as shewmaker described. I am still able to go through blogger dashboard and create/edit posts.

Thanks for the resports.
I hope to fix this for the new Blogger API (now in beta), but need as much info as possible.

Could there be something in your posts that is common when this happens, or does it seem more like a communication or server error with blogger?

If anyone is interested, please PM me as I'm working on a new build for blogger beta support, and it will give a much more detailed issue when that error is found so we can figure out what is causing it.

Any testers would be most appreciated.

Cheers
-Jed

Using my "debug build" it seems Blogger is sending back a
"Status code 1-500-13"

The interesting part here is that an error code 500-13 is usually an ASP HTTP Error that means "Server is Busy".

If I'm write, this brings up two questions
1) What is google doing using ASP and IIS servers?
2) Why in the world can they not handle the load?

I guess this would make sense as to why it seems really random, but damn.. that's some pretty crappy work on bloggers part.

Edit You can read more about this issue here:
"HTTP Error 500-13 - Server too busy"

I wonder if the new blogger api will either have an upgraded IIS server (6.0 or later) or if google is migrating it to python and Linux.

It definitely seems like a communications error when I experience it.

I just experienced the same problem. I typed in a blog entry and hit publish. I got the popup alert saying "There was a possible error contacting the ATOM server"

I checked my blog, and nothing was published. I am adding this note because I am not using the new beta blogger, but my old standby. (I have not figured out the difference yet, or how the two interact, but that is something for a google search :)

Note: I am having no problems accessing my blogger dashboard But i am also getting an error #5 when I try to post with Blogger for Word... So it could be a problem on my computer...Nope - fixed Word issue with a re-install..

SUCCESS: I un-installed proformancing - restarted firefox - re-installed proformancing - restarted firefox again - and it is working with no errors (and I didn't loose any info :)

Leapoffaaaith,
I honestly don't think re-installing pff did anything for you. Again the problem appears to be a "server busy" response, something I will make much more clear in the next release. For me personally, I only see the error on peak hours (between 4:00pm and 7:00pm) which I guess might make sense if more people blog at that time.

I'm very hopeful that with the new Blogger API (in beta), now that it is part of Google proper and their servers, these issues will be fixed. I should have a blogger beta enabled dev build soon and will be sending it out to volunteer testers, so we will know soon :)

My blogs are not converted over to the "new" api, however for the last 2 weeks I cannot use performancing at any time and post to blogger. I always 100% of the time get this error. I have tried from 4 different computers, they all exhibit the same problem, at the same time blogger itself has seemed much more reliable...

I don't know how I can help fix this, would a packet trace of the communication help?

Maybe it was something that got messed up in the update from 1.2 to 1.3? or whatever the update was that came out recently...

I just performed the same operation that leapoffaith did, and now performancing is working again...

Very spotty.

Sometimes I get through. Most times I do not.

"There was a possible error contacting the Atom server"

"The server might be down or unresponsive: Error: TypeError: dom has no properties"

I can log in and post with no problem from Blogger's interface.

Hope you can fix this soon, as I have truly come to rely on Performancing ...

Regards,
George

Hi guys.

Thanks for the feedback. Yes, current blogger support is bad, I am very sorry.
I am working on new builds that will support the new blogger api (currently in beta) and hope to make it as rock solid as their (sometimes flakey) service will allow me.

Things are looking good so far.
Thanks for the patience.

"I un-installed proformancing - restarted firefox - re-installed proformancing - restarted firefox again - and it is working with no errors"

i did the same thing - it worked for a bit but went back to being tempermental.

Yeah, blogger is slowly messing up the old atom api bad... although the new one seems to working great (with latest pff deb build).

Wondering if I can save to my beta.blogger.com account as a draft. I move around to different computers frequently.

Yes, but not in PFF 1.3
This will be fixed in 1.3.5 which will be out really really soon (within 2 days).

Hi, I get the "There was a possible error contacting Atom Server" errors with performancing, but also with ecto which I use as a desktop tool. I'm about to try with MarsEdit. But I think it must be something at Blogger's end. I'm not on blogger beta by the way, and it works fine if I log in to blogger itself

@tomroper: Please check out the latest beta and let me know if that fixes it. It should fix blogger support for both Beta and Non beta.
You can get it here: http://performancing.com/node/5174

I'm having similar problems. Performancing sez I need to re-add my blog due to API changes. So I try that, adding my blog address and login info and such, and consistently get back this error message:

Alert
Woops, you found a Blogger error
, plese contact the author at
'performancing.com/forum/firefox/'
and give the following info
TypeError: dom has no properties 960

That's exactly how it appears, down to the misspellings. So I'm stuck. For now, I'm actually composing entries using Performancing, then cutting and pasting into Blogger. Kind of a pain, but it works. Looking forward to a fix!

Thanks for letting me know.
Could you PM me your blogs URL, also what version of PFF and OS you are using?
That would help me fix the issue. Thanks!

-Jed

I am having the same problem now, half a year later. Was it fixed at all? Is there any available fix I could use? Thanks!