Hmmm, this is strange since the changes where quite small. Do you see any additional errors in the debug mode beside of the “gzopen failed”?
There are no errors or warnings in the debug mode, even the gzopen-problem isn’t mentioned.
But after executing the debug mode theres a new problem. Now it says that the last sitemap generation could not be finished and that I should try to raise the memory limit. But there is no save button any more on the configuration page.
Any ideas???
Thanks for your help!
Seems to be a problem with the “Contact Form 7” – Plugin (http://ideasilo.wordpress.com/2007/04/30/contact-form-7/). When I deactivate this plugin, everything works fine again.
As of the compatibility list of CF7, V3.1.2 is compatible with it and worked fine for me in the past.
So although the changes in V3.1.3 are quite small, anything seems to be compete with the CF7-Plugin.
it is doing the same thing for me. I have tried to put it into 3 new sites this week and I get the same message.
I had problems with the v3.1.3 also now I’m Back using v3.1.2
I didn’t get any errors in text like code problems.
After manual ftp upgrade I ran (rebuild the sitemap manually) and it when to a white page thanking for a previous donation. I saw activity in the status bar of my browser. I was running way to long and by the pattern it looked to me that it was caught in a loop.
I went back and (used the debug function) but got no errors there. I clicked rebuild and the bottom of the debug function results page and then clicked (Back) from the same area. It looked like it did it because the date and time where current. But where it says –
# Google was successfully notified about changes.
# MSN was successfully notified about changes.
# Ask.com was successfully notified about changes.
These lines where (RED) and instead of saying – “was successfully notified about changes” it said something like they moved there page.
So I reloaded v3.1.2 and everything works fine with the last version.
My blog mentioned above is WordPress 2.5.something but I upgraded a 2.7.0 blog earlier and i just tried the manual build and it did the same thing. So now they’re both o v3.1.2 but it’s no big deal to me. I’m sure the fix will come.
Hi there
I want to add that I have been having exactly the same problem as some of the others when I asked to rebuild the sitemap manually –
Fatal error: Out of memory (allocated 42991616) (tried to allocate 64 bytes) in……….wp-includes/functions.php on line 2913 (I left out part of the file path for security reasons)
and this is what it also said on the main page of the plug-in:
* The last run didn’t finish! Maybe you can raise the memory or time limit for PHP scripts. Learn more
* The last known memory usage of the script was 17MB, the limit of your server is 64M.
* The last known execution time of the script was 0.76 seconds, the limit of your server is 120 seconds.
* The script stopped around post number 1207 (+/- 100)
after updating to the latest version. I have had to delete the plug-in because even after deleting and then uploading a fresh version I still receive the same errors and it put my site into error with automatic API posting and also I couldn’t delete any posts.
I tried all sorts of things such as creating a compressed .gz version and even though it created it and I could see it in my cpanel the site itself never went out of error until I deleted the plug-in. Until I deleted the plug-in I couldn’t delete a post and the API could begin to post again.
I have found that two of my sites have been ok with the v3.1.3 but I am loath to update my other sites as I don’t want this problem to occur again as I spent many hours on it, over the last couple of days, including chatting and emailing with my host trying to sort out if I needed more memory.
My wordpress version is 2.7.1
I would be interested to know what is causing this to happen.
Cheers
Viv
Has any one heard if this issue has been fixed. I haven’t been able to track down any mention of it. I really don’t want to find out by reinstalling it. Finding out it’s not and need to go back to a previous version.
Krangewarefahrer put me on the right track with this. For me, it was the Quick Contact plugin (http://quickcontact.squarecompass.com/documentation/installation/) that was causing the error. Disabling it fixed the problem. So my suggestion is try to disable any contact forms to rebuild the sitemap, then enable them again if you need them.
