phd38

I corrected the last “fatal” listed in your log.

Trying to understand why issues with the SQL reported items. Question : following which action did you get this message ?

– Enabling the plugin ?
– Using the plugin ?
– In this case performing which action ?

I uploaded the 4.0 Beta here :

http://downloads.wordpress.org/plugin/wp-mediatagger.zip

Note this is a development version.

Is this delay longer when it leads to 404s ?

If it works sometime it’s probably because the server is less loaded by other users, and able to respond faster, without exceeding the timeout.

I am working since Christmas on the version 4.0 of the MediaTagger plugin.

I re-engineering it to have it embedded in an object instead of a set of routines. This will minimize the risk of conflict with any other piece of code.

One thing we can try is to have you installing this 4.0* beta (it’s still in english, I did not complete the localization to other language but it should not bother) and check if you still face the same issue.

Hello,

I never tried with such a huge number of photos. In case of database query timeout, I would expect a server timeout message, not a 404.

Concerning the memory allocation, the structure created in the plugin points to the different photos, which are then loaded on demand.

Hello,

The localization is parametrized thanks to the standard WordPress procedure, based on

define (‘WPLANG’, ‘fr_FR’);
(file wp-config.php)

Without this define the plugin will work with its native lang, ie english US. Thanks to this define, the plugin will work on the lookup table mediatagger-fr_FR.po.

Although this variable is usually static, I assume that if it is reset dynamically by the site depending on the visitor lang, it should work.

Could someone confirm ?