Fatal Error – WordPress memory exhausted [Google XML sitemaps generator]

Recently I have upgraded to wordpress 2.8. From then onwards I had problems with Google XML sitemaps generator plugin. This plugin is the most popular and must wordpress plugin without which it’s impossible to top Google search results. Here is the problem that I came across when I tried to rebuild the sitemap manually.

Fatal error: Allowed memory size of 262144 bytes exhausted (tried to allocate 541 bytes) in /home/pcaddons/public_html/wp-includes/link-template.php on line 113

When I go to XML sitemap plugin configuration page I found these lines

# 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 14.75MB, the limit of your server is 128M.
# The last known execution time of the script was 0.02 seconds, the limit of your server is 120 seconds.
# The script stopped around post number 36 (+/- 100)

I never faced this problem in wordpress 2.7. Also I’m not that much familiar with wordpress. So I was stuck in between and looked here and there on google but only in vain. So I tried to solve it manually and to my surprise I solved it. May be you came here to find a solution to a similar problem and you came to the right place.

I use Global translator plugin to reach millions of people around the globe. Global Translator plugin has an option of integrating sitemap. If you select that, then the posts that are translated by Global translator plugin are added to sitemap. Don’t know why? but Global translator plugin is the culprit in my case. At that time Global translator was not compatible with wordpress 2.8. But an update is released which says it to be compatible with wordpress 2.8. But the problem is not solved with that new plugin too. There is some compatibility issue going on in between Global translator and Google XML sitemap plugin. To rebuild your sitemap successfully, you should not use sitemap integration option in Global translator. This should solve your problem. Hope the developers fix this issue soon! Alternatively, you can checkout what WordPress people say about this (http://wordpress.org/support/topic/279132?replies=5).

You may also like...

Histats.com © 2005