Language selection in valuelists

[byNetMan]

I have setup english and french in my data tables.
Now I would like to see the translated data of current selected language when using valuelists.
At the moment, only the data from the original table is displayed.

Is this possible?

Thanks

André

[shannah]

Currently the only way to translate valuelists is to move them into the database. I.e. use __sql__ in the valuelist definition and make sure that the tables are set up with translations like the rest of the apps tables are.

Hope this makes sense...

Possibly future versions will support translating valuelists directly in the valuelists.ini file but for now ...

-Steve

[byNetMan]

I am using database tables for my valuelists and they are all translated.
Is there a special way of formating the '__sql__' query in order for it to get the proper translation table?

André

[shannah]

This should work. Let me review the source and test just to confirm. I'll get back to you later today..

-Steve

[shannah]

Can you post relevant portions of your valuelists.ini file and describe your table structure a little so I can try to point out where the problem is?

-Steve

[byNetMan]

Here are a couple of entries from my valuelists.ini

[SafetyFeatures]
__sql__ = "SELECT featureID, feaLabel FROM feature WHERE featureCat = 'S'"

[InteriorFeatures]
__sql__ = "SELECT featureID, feaLabel FROM feature WHERE featureCat = 'I'"

I have 3 feature tables:
feature
feature_en
feature_fr

My understanding is that when you have
multilingual_content=1
the __sql__ query should be reading the language specific table.

André

[shannah]

Yes.. that's right. Upon inspection of the code it looks there is a small bug in dataface You can fix it by doing the following:

Open the Dataface/ValuelistTool.php file
Find the line:

Code: Select all

$res = mysql_query($value);


change it to

Code: Select all

$res = df_query($value);


Best regards

Steve

[byNetMan]

Hi Steve

I fixed the bug in ValuelistTool.php but it did not fix my problem.
In looking over your source code, now I believe that I must include the fields that use the valuelists into the language specific tables also.
If this is the case, then I need to find another solution since I don't want my clients to have to approve the translations every time they enter a new record.
Also, in looking at the source code, I've noticed that I can use the SET type of field for my data.
If you can confirm this, this will sove my problems.

Thanks for the help,

André

[shannah]

Ok.. sorry. In 0.7.1 there is one other place you need to change it:

In Dataface/Tables.php, in the function _loadValuelistsIniFile(), there is a line:

Code: Select all

$res = mysql_query($value, $this->db);


change it to

Code: Select all

$res = df_query($value);


[byNetMan]

Thanks Steve,

It works fine now.

I noticed that you are using Dataface_DB.cache for the sql queries but that it only holds the very latest queries.
You seem to have set a very short lifespan on the cache.
Is this intentional or is one of my settings not OK?

I'm being curious.

Thanks for the help.

André

[shannah]

Hi André,

Thanks for bringing this up. I have sort of been ignoring the cache as performance, by and large, has been pretty good, with or without the cache. There is most likely room for optimization and improvement. As we are currently revisiting the weblite translate service and modifying the business plan I will be doing another round of development on the translation components very soon and the caching will likely also be revisited.

Best regards

Steve