put lang variables in categories or picture titles? put lang variables in categories or picture titles?
 

News:

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

Main Menu

put lang variables in categories or picture titles?

Started by Quinti, May 31, 2006, 05:00:45 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Quinti

Hi people
a question:

is possible create new language variables, and put it in the categories or title descriptions?
i probe it, for example in langs/galician.php:

$varnewtitlecategoryone= 'my language description';

and then
in the category, put

<?php $varnewtitlecategoryone ?>


but no run jiji
are there any way to insert anything of code in the forms, category form, picture title form, etc..?

thank u very much
and greetings!

Paver

First of all, it would be dangerous to allow PHP code in form fields.

Secondly, nearly all output is done through function calls, which would require a "global $varnewtitlecategoryone" declaration in the function, before that variable would be available for output.

I think it should be possible to set up a code that would give a sanitized way of accessing language variables.

But I guess I don't understand what use this would have.  Would users use these variables?  Would you need a dictionary of available language variables that available to use in such a system?

Joachim Müller

As far as I can see, Quinti is trying to create a multi-lingual version of coppermine, with textual content (that should reside in the database) residing in the language file instead. It would be incredibly hard to provide translations of dynamic content (e.g. category names, album names, titles, description etc.) for many languages. This has been requested before, but would result in huge performance penalties, cluttered code and little use for most.
Bottom line: currently not possible, unless you're willing to make huge changes to the core code.