News:

cpg1.5.46 Security release - upgrade mandatory!The Coppermine development team is releasing a security update for Coppermine in order to counter recently discovered vulnerabilities. It is important that all users who run version cpg1.5.44 or older update to this latest version as soon as possible.[more]

Changes:- Added support for the new plugin installer- Added svn headers as this plugin has been added to svn- Added Announcement thread -links to configuration.php

This version is taken from svn, so it includes Joachim's code optimisations in codebase.php. I didn't add the svn headers to the index.html since it is empty and its purpose is to disable diroctory viewing of my plugin.

This is the spanish translation. However the plugin information keeps showing in English in Coppermine's plugin admin page - it reads the description field in the configuration.php file, doesn't it?.

The plugin information is read from configuration.php but that information is static; always in English. I may change this if needed with the coming update of my plugin (see the edit in the initial post).

I just added the code tags to your posting. I haven't removed an attachment. How could there be translation for a plugin that doesn't feature i18n? As suggested in Geo IP Lookup - check from which country your visitors come from, you're welcome to add i18n for this plugin - that's dead easy, but won't help much, as this plugin doesn't have a config screen or similar - all the end user can do is install it.

I did some modifications in my personal copy of the plugin, and I don't know if they can be interesting for anybody.

Original plugin had some sentences written in the configuration.php file. I could easily translate them in my but new versions of the plugin will ruin that work. So I put them in the spanish.php and english.php files, and for the rest of languages I provide a default value. It isn't needed when all messages are translated in every language file.

So I put them in the spanish.php and english.php files, and for the rest of languages I provide a default value. It isn't needed when all messages are translated in every language file.

Thanks for your effort. My plugin (as Coppermine) has already a language fallback, so there is no need for if ( is_null($description)) function, which can be removed as soon as the needed text is defined in english.php. I won't made those changes to my 1.x version of my plugin because I want to concentrate 100% to the coming v. 2.0 plugin which will add support for other trackers too. However, I will make the configuration.php translateable in my v. 2.0 plugin.

Thanks for your effort. My plugin (as Coppermine) has already a language fallback, so there is no need for if ( is_null($description)) function, which can be removed as soon as the needed text is defined in english.php.

I won't made those changes to my 1.x version of my plugin because I want to concentrate 100% to the coming v. 2.0 plugin which will add support for other trackers too.

Very interesting: I had in mind to try to include utm_* and user-defined GA variables specially for postcards sent by coppermine. But it will be in the long term, again because of my lack of PHP skills. And i'm concentrating on translation - at least I feel I can help that way. Just for curiosity: can you advance which ones are you thinking about?