I am getting this (attached)error message after trying to create a sitemap using the Simple Google Sitemap V1.6 plugin.

Is this a permision issue within the theme? I don't think it's the plugin as I tried a few different ones and they all had a similar error message.

Any help or direction would be greatly appreciated as my experience in this area is very limited.

I just installed on WP 3.01 and Atahualpa 3.5.3 with no problems.

I just tried updating to wp 3.0.1, which failed and now I can't get into my site! Get this message.

Briefly unavailable for scheduled maintenance. Check back in a minute.

Ughh!

It's back, any idea why the instal failed?

Ata 3.4.5.

When you update WP it creates a maintenance file which will give you that message until it's done. It looks like your server just took a bit longer to get rid of the maintenance file. Does the sitemap plugin work now?

I still can't get the update to work, it failed again. I was trying the automatic update method, shouyld I try uploading it (ftp) to wp content?

Thanks for your help Larry, I'm still learning

What happens when you try to update? How are you doing the update?

It says "update failed" I am using the automatic update method

I am guessing that it may be a memory issue on the host. Also do you know what version of PHP and MySQL they are running?

I spoke to him today, he has updated many sites to 3.0.1 on the server. I uploaded the wp 3.0.1 folder to the public html folder but nothing has changed.

headache...........

I don't know how to direct you. I would do a manual upgrade per the instructions on WordPress.org. Let us know how it goes.

the original message was about a plugin, not wordpress or the theme.
1) deactivate the plugin - any problems?
2) activate the plugin - change to twentyten theme - any problems

if the answer to (1) is NO and the answer to (2) YES then this is a plugin problem. Go check with th e plugin's author and see if it s still supported

Good catch JD. I should reread threads from time to time. It will be interesting to see if this is the issue.