I have not tested the files with field values. (I will need to do this later, though).
Now that I think of it, it is quite likely that field values cannot be easily translated fith the fish. The selects will probably translate well after removing the bugs taht you pointed out. However, the chosen values are saved to the comprofiler table in the following format: title1|*|title2|*|title3, and renderes by exploding the string. This process does not involve using the field_values table and hence joomfish cannot translate.
I made a feature request a long time ago, but it was rejected. Perhaps time to reopen?
forge.joomla.org/sf/go/artf2445?nav=1
mikko
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
I would setup all selectable or multi-selectable field values as language strings.
So, if for example you have a multiselect field for languages you should setup the allowable values (when defining the CB field) as _UE_LANG_1, _UE_LANG_2, etc. Then just add these values with the correct translations to your language files.
Please Log in to join the conversation.
nant wrote:
I would setup all selectable or multi-selectable field values as language strings.
So, if for example you have a multiselect field for languages you should setup the allowable values (when defining the CB field) as _UE_LANG_1, _UE_LANG_2, etc. Then just add these values with the correct translations to your language files.
This is a solution, but for my use (and perhaps many other) joomfish translation would be much better. The reason for this is that I have select fields which that can accept new values entered by users. For some selects there is an option called "new.." and selecting that option triggers a prompt asking for a new value. These values then go to aproval and translation work flow where the administrator needs to do a bit of work for them. For the people that do this work on one of my sites, it is much easier to translate with joomfish than hardcode each translation to a language file every time someone enters a new value.
It would be possible to make a component which cretes translations to the language file, but this would be a potential security risk and much more work than making the fields work with ids rather than titles.
-Mikko
Please Log in to join the conversation.
I think this is a general problem with the fish. As this post is linked from the forge i like to express that I had problems with "custom values" (combined) in fields, when trying to translate them in some components like facile forms, uhp, noahs classifieds, CB which are still not fishable.
Please Log in to join the conversation.