In registration: Optional information fields doesn't translate In registration: Optional information fields doesn't translate
 

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

In registration: Optional information fields doesn't translate

Started by krampo, July 13, 2006, 04:26:00 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

krampo

When you try to register in other language than English, you get "Optional information" in your language, but all the fields (Location, Interests, ...) are still in English. I even downloaded clean cpg1.4.8 version, it's the same.

you can try to switch languages @ http://photo.krampo.info

Nibbler


krampo


Nibbler

They are probably left over from 1.3. Nothing to worry about.

loot

it is possible to translate die optional fields lfor example location<>Wohnort
i think the settings in the admin menu will be written into the sql database.
thx in advance

greetings loot


loot

hi,

thx for answering gaugau
But my question ist:
is there i possiblility to switch the userprofile like "Location" for mysite.com and mysite.de "Wohnort".
I think the prob is,that the description of that fields arent in language files.
Maybe i have to edit the sql query for that ...but how ?

thx in advance

greetings

loot


Joachim Müller

If you have a multilingual site (i.e. users both from Germany as well as international users speaking English), then you're right: the field labels don't translate, as the names reside in the database. Basically, everything that exists as textual content in the database goes untranslated - that's the case both for custom field names as well as image titles or descriptions. So you have the dilema not only for those field names, but for all content. The only easy workaround I could think of is labelling the fields in both languages (i.e. "Location/Wohnort"). Other solutions are doable but hard to accomplish (as they would require a lot of coding).

loot

hi,


jo ..all the other content i managed with :
<?php

switch ($CONFIG['lang']) {
   case 'english':
      echo '<a href="rules.php" align="center" target="_self">[Rules]</a> <a href="imprint.php" target="_self">[Imprint]</a></a> <a href="ppolicy.php" target="_self">[Privacy Policy]</a>';
   break;
   
   case 'german':
      echo '<a href="rules.php" align="center" target="_self">[Regeln]</a> <a href="impressum.php" target="_self">[Impressum]</a></a> <a href="datenschutz.php" target="_self">[Datenschutzerkl&auml;rung]</a>';
   break;
   
   default:
      echo '<a href="rules.php" align="center" target="_self">[Rules]</a> <a href="imprint.php" target="_self">[Imprint]</a></a> <a href="ppolicy.php" target="_self">[Privacy Policy]</a>';
}

?>


ill try a second register.php
maybe i can find ich workaround

thx for your help

greets,loot