Important Update: Google (XML) Sitemaps Generator with qTranslate support (Version 3.1.6.3)

wordpress-logo-notext-rgb[1]

I’ve just released the version 3.1.6.3 of the Google (XML) Sitemaps Generator with qTranslate Support WordPress Plugin.

Two important things have been fixed:

  • Support for blogs without qTranslate (it won’t give fatal errors anymore)
  • Correct naming of the plugin in the WordPress Repository (as “Google XML Sitemaps with qTranslate Support”). The incorrect naming may cause the ones who have downloaded previous versions of the plugins to get updated to the original version (the one that does not support qTranslate).

I really recommend updating since you may not receive the notifications for this version of the plugin but for the original one (which does not support qTranslate).

You can download the latest version from the original post page:

Support appreciated!

All the content offered in this website is, except noted otherwise, of free nature. This means you can share it wherever you want if you do it freely and stating its source.

If it was useful for you and you’d like to contribute, you can make a donation or, at least, visit one of our advertisers of your choice; they are all around the site.

Incoming search terms for the article:



25 Responses to “Important Update: Google (XML) Sitemaps Generator with qTranslate support (Version 3.1.6.3)”


  • hi there
    your update is cretaing out of memory errors, do you plan on updating newer releases, too? cheers, m

  • Hi there mate I’m getting errors continuously when trying to generate the sitemap:

    * 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 40.75MB, the limit of your server is 64M.
    * The last known execution time of the script was 58.71 seconds, the limit of your server is 120 seconds.
    * The script stopped around post number 4140 (+/- 100)
    * If you changed something on your server or blog, you should rebuild the sitemap manually.
    * If you encounter any problems with the build process you can use the debug function to get more information.

    BTW Arnee’s versions seems far away… did you stop updating?

    • Hi Blutarsky,

      Thanks for your comment!
      It’s been some time since your last message…

      I’ve not updated it for some time since I’ve been quite busy and no one had reported any problem. I’ll update it soon, so you can check whether your problem was related with a fixed bug.
      I’m using for my site the same version I’ve published, running on WordPress 2.82.

      Greetings!

  • Hi there, I have patched the code in sitemap-core.php, using a versioning tool and stuffing your code into the original one. Seems working.

    I have also tried to investigate why the tool suffers from performance. Currently I have to limit posts to 3500 otherwise the plugin fails.

    It’s the original’s plugin problem, nothing due to your customization

    • Oh, so that’s quite problematic…

      Have you tried increasing the executiion time/memory limit for the sitemap generating script?
      Anyway it doesn’t seem to have reached them but, who knows….

      You can do something like this:
      ini_set(‘memory_limit’, ‘128M’);
      set_time_limit(5*60);

      Perhaps it’s a problem with a specific post, I wouldn’t know exactly…

      Take a look on that and tell me!
      Greetings!

  • I’m running XML Sitemap Generator for WordPress 3.2.4 patched with your code.
    When an error occurs the scripts states that the server limits are set to 64M + 120 secs, but the last marks before the script halts are quite lower

    • Sure, but you don’t really know whether it didn’t want to allocate a massive amount of memory just before crashing…

      You could try to raise the limits using the code I posted you just to discard an option…

      If it doesn’t work, we could try to find another kind of solution.
      Greetings.

  • Whys does the plugin allocates a lot of memory?
    Digging into the code, whenever a valid URL is found, it is wrote to an output file using basic or gzipped version…
    Is there any big array involved? It doesn’t look like it.
    Maybe those file writes are actually “buffered” from the operating system, and held in memory until the sitemap files are closed?

    • Some of the script actions depend on the configuration of the webserver…

      Every file operation is buffered, but the buffers are commonly quite small (4Kb)…
      On the other hand, the gzip compression might be quite expensive depending on the chunk size and other variables.

      Anyway, I’m not stating it’s really a memory problem, but I think it would be a wise choice to discard it completely by raising the memory limit, at least once…

      Greetings.

  • I’ve tried your tip but got the same error:

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

  • My site is running on a shared config. No access to php.ini.
    I’ve tried to modify the .htaccess file but issued some errors…

  • No! I have installed xdebug to try to debug the plugin. I can’t understand where memory grows in the code…

    • Then perhaps it’s not a memory growth problem…
      You don’t have shell access to your hosting, don’t you?
      If you do have, you could try running the update script directly via command line (no time limit)…

  • I have a shell access and I can launch updates via cron/curl. Does this mean there will not be any time limit? How about the memory issue? (on my local install the script uses some 74MB, while on the remote host the limit is set to 64MB).

  • I think that the memory problem will be there, but the limit alternative sounds great!

  • Does it support WP 3.0.1 with the latest build of qTranslate?

    Quin just released the build that supports WP 3.0.1. Shall you?

  • Neo, how do you cope those updates?
    I’m still on 2.9.2, and every upgrade terrifies me!
    How do you ensure your install won’t spoil?

    • I just backup everything, ensure that qTranslate keeps working, cross fingers and update…
      I can survive without my other plugins ’till I fix them or ther authors do it…
      If it doesn’t, I rollback and then trace the problem…
      But it has almost never happened…

Leave a Reply to JC