Comentarios en: Actualización Importante: Google (XML) Sitemaps Generator con Soporte de qTranslate (Versión 3.1.6.3)

Por: NeoEGM

NeoEGM — Tue, 10 Aug 2010 03:48:44 +0000

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…

Por: Blutarsky

Blutarsky — Mon, 09 Aug 2010 22:16:47 +0000

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?

Por: NeoEGM

NeoEGM — Mon, 09 Aug 2010 22:08:26 +0000

I’m using WordPress 3.0.1 with the latest version of qTranslate and the XML Sitemaps plugin is working without problems…
Greetings!

Por: JC

JC — Mon, 09 Aug 2010 16:48:50 +0000

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?

Por: Blutarsky

Blutarsky — Fri, 25 Jun 2010 09:13:23 +0000

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

Por: NeoEGM

NeoEGM — Fri, 25 Jun 2010 07:02:49 +0000

Exactly, no time limit via shell. I don’t know about the memory limit, it depends on your config!

Por: Blutarsky

Blutarsky — Fri, 18 Jun 2010 08:20:05 +0000

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).

Por: NeoEGM

NeoEGM — Fri, 18 Jun 2010 03:33:12 +0000

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)…

Por: Blutarsky

Blutarsky — Thu, 17 Jun 2010 22:38:17 +0000

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

Por: NeoEGM

NeoEGM — Thu, 17 Jun 2010 21:16:35 +0000

Hi, sorry for the delay. I’ve been quite busy these days…

Have you made any advance on this?

Por: Blutarsky

Blutarsky — Wed, 09 Jun 2010 20:53:10 +0000

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…

Por: NeoEGM

NeoEGM — Wed, 09 Jun 2010 20:34:33 +0000

The new limits were not applied…

Do you have access to php.ini?

If so, you could modify the right there…
Otherwise, you can do it in the .htaccess file…

Por: Blutarsky

Blutarsky — Wed, 09 Jun 2010 20:32:20 +0000

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)

Por: NeoEGM

NeoEGM — Wed, 09 Jun 2010 20:16:08 +0000

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.

Por: Blutarsky

Blutarsky — Wed, 09 Jun 2010 20:12:19 +0000

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?

Por: NeoEGM

NeoEGM — Wed, 09 Jun 2010 20:07:26 +0000

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.

Por: Blutarsky

Blutarsky — Wed, 09 Jun 2010 20:04:27 +0000

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

Por: NeoEGM

NeoEGM — Wed, 09 Jun 2010 18:05:01 +0000

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!

Por: Blutarsky

Blutarsky — Sun, 06 Jun 2010 08:08:23 +0000

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

Por: NeoEGM

NeoEGM — Sat, 05 Jun 2010 18:48:50 +0000

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!