Selection saving translated value not {lang_xxx}

[dmerritt]

Hi,

I'm using OR UMP for the first time. The version I'm using is 2.5.8 (although the multilingual add_on says 2.0.0).

I have created a new field of type select list, with the field caption set to {lang_type}. The field elements are added as {lang_zzz}||{lang_yyy}.

When I add a new listing, the selection list is populated correctly based on the two languages I'm using, however when I save the listing the value saved on the DB is of the translated value, rather than {lang_xxx} for example.

This means when I view the listing in either language the value is always the same (the translated value from when the listing was first created).

What have I done wrong?

Thanks in advance.

Darren

[ebmarques]

Hi Darren,

I'm using OR UMP for the first time. The version I'm using is 2.5.8 (although the multilingual add_on says 2.0.0).

The latest UMP version is 2.5.8
The latest multilingual add-on version is 2.1.1 - so you should use the Add-on Manager to update the add-on.

I have created a new field of type select list, with the field caption set to {lang_type}. The field elements are added as {lang_zzz}||{lang_yyy}.
When I add a new listing, the selection list is populated correctly based on the two languages I'm using, however when I save the listing the value saved on the DB is of the translated value, rather than {lang_xxx} for example.
This means when I view the listing in either language the value is always the same (the translated value from when the listing was first created).
What have I done wrong?

Assuming you are talking ONLY about backend... there is no way to translate any listing value AFTER you create or edit a listing (because the backend is not fully templated).
It will always display the value stored at the database - I mean, at the database Open-Realty saves the translation of the lang tag and not the lang tag itself.
So you are doing nothing wrong.

Eduardo

[dmerritt]

Hi Eduardo,

Thanks for your help.
I tried to update it through the add-on manager, but got the following error.

Fatal error: Call to undefined function curl_init() in /var/www/marina_or/include/addon_manager.inc.php on line 55

Any ideas?

Thanks Darren

[dmerritt]

Hi Eduardo

I found the reason for my addon manager problem in the hugh post, so I'll try that.
Apologies for not looking there first.

Thanks Darren

[dmerritt]

Hi Eduardo,

I have upgraded to version 2.1.1, but still have an issue. It maybe related to what you have said already, but on the FRONT END the value from this selection list is shown in the language it was created in, when you switch to another language the value remains unchanged.

Are you saying that it's not possible to add a field using selection list and have the value translated into another language on the Front end? Is it not like the Community and home features, which do get translated?

Thanks Again.

Darren

[ebmarques]

Are you saying that it's not possible to add a field using selection list and have the value translated into another language on the Front end?

No... I said it for the backend.
At frontend, you can use a multilingual add-on tag to have those field values translated: {addon_multilingual_field_FIELDNAME}

Eduardo