Hi,
could you click on the “debug function” link and have a look at the “Errors, Warnings, Notices” section?
Best regards,
Arne
It’s empty. I already checked that before posting.
And another update, it’s seems to be getting worse. I was able to get it to run when I limited the posts to about 300. Now, it’s failing at 100 posts. Makes no sense.
Can someone zip up the previous version of this and send it to me? I want to see if maybe it’s just this latest version that was released on 3/3/08.
Can someone zip up the previous version
It won’t make any affect. As I’m also experiencing the same problem, right after upgrading to WordPress 2.5. Earlier on WordPress 2.3.3, I was able to generate sitemap with just one click and withing 15-35 sec.
I had trouble also. When I added a site map to google webmaster tools it was getting a 303 error code. I had noticed a drop in site traffic since up-grading to 2.5 but since I turned off the sitemap and and deleted to site map files (xml/gz), my site traffic is on the increase again.
Ok, well I guess I’m not alone. Is there another Sitemap plugin that actually works with 2.5. This one was great, but completely useless to me now.
I chmoded the sitemap.xml and the zippd sitemap to 766, then it worked.
This plugin works fine, unfortunately it uses a lot of resources. Try to increase your memory via php.ini or tick “Build the sitemap in a background process”.
ThorHammer wins. Changing the permissions on the two output files makes it work correctly again. Thank you.
Permissions are correct & “Build the sitemap in a background process” is ticked. Eventhough, it doesn’t work in WordPress 2.5
Earlier in WordPress 2.3.3, I was able to generate sitemap with just one click under 5-15 seconds. Now after upgrading, I only gets “last run didn’t finish” error.
@rdkr
Where you turned off and deleted sitemap files in “WordPress” or “Google Webmaster Tools”?
Rok
I deleted both of them.
“
Permissions are correct & “Build the sitemap in a background process” is ticked. Eventhough, it doesn’t work in WordPress 2.5
Earlier in WordPress 2.3.3, I was able to generate sitemap with just one click under 5-15 seconds. Now after upgrading, I only gets “last run didn’t finish” error.
@rdkr
Where you turned off and deleted sitemap files in “WordPress” or “Google Webmaster Tools”?
”
I get the following notice:
Notice: Undefined index: path in /home/ajkcoza/public_html/wp-admin/includes/file.php on line 25
Hi all,
thanks for the feedback! There was a change in the WordPress 2.5 caching system which resulted in a database query for every post when the sitemap was created. Because of this, it is likely that the script run into the memory or time limit.
I’ve added a workaround in the new 3.0.3.2 release which fixes this issue. You can get it here:
http://downloads.wordpress.org/plugin/google-sitemap-generator.3.0.3.2.zip
I’m also working on the new major version of the plugin which is split into several files, so only the PHP code which is needed for the current request is loaded. That means that only a very small “code loader” is active on every page load and the sitemap generator itself is just loaded when you really want to rebuild the sitemap.
You can help me by testing the new test release (also known as “development version”). Note that this version might not work completly, but it would be great if you help me and report what’s not working 🙂
The current development version is always here:
http://downloads.wordpress.org/plugin/google-sitemap-generator.zip
Please note that if you update to this version, the plugin should be automatically disabled afterwards since the filename of the core plugin file changed. You’ll need to activate it again at the plugin page.
Thanks and best regards,
Arne
Hi,
I have tried 3.0.3.2 and 3.0.3.3, and I see this error with WordPress 2.5.1:
“Notice: Undefined index: path in /blog/wp-admin/includes/file.php on line 25”
My blog is hosted on Yahoo.
Thanks in advance.
-peeds
This plugin is making my server CPU skyhigh since I ugraded for wp 2.5.
Im looking for an option for generating my sitemaps manually.
