Hi,

My client reported she couldn't translate the profile fields, only the profile categories. So I've done some debugging, I refreshed the strings, cleared caches and nothing helped. After changing i18nstrings.module on line #371 from i18nstrings_update_strings($context, $object->$property); to i18nstrings_update($context, $object->$property); all translatable strings started showing up under admin/build/translate/search when limiting search to: profile. Everything works now.

Then I changed the module back to it's original state and things were still ok.

Cheers

Cheers

CommentFileSizeAuthor
#1 i18n.strings.profile.patch475 bytesbartezz

Comments

bartezz’s picture

bartezz commented
StatusFileSize
new i18n.strings.profile.patch475 bytes

Ok on second check changing it back to i18nstrings_update_string($context, $object->$property); was not a good idea. Upon flushing caches everything was gone again.

I believe the code should be as provided in the patch as this solves all issues for me when translating profile fields. (field explanations couldn't be translated either but solved this with this patch; http://drupal.org/node/803110#comment-3374102).

Cheers

aacraig’s picture

aacraig commented

I can confirm the same problem.

I have enabled Profile translation and created a multi-line text field. Insert English text in the field and save. Searching for that string results in no hits.

Applying the patch above does not help.

bartezz’s picture

bartezz commented

Did you clear caches after applying? Haven't had problems since!

aacraig’s picture

aacraig commented

Here's the entire process I went through, with no success:

enable Profile translation
clear cache
create a text profile field
create a user
enter some text in the profile field
view the user profile in English
view the user profile in another language (in my case, Italian)
search for a string from that text in the translation interface
get no results.

I'm viewing the profile in the other language to ensure that it gets stored in the strings database.

What am I missing here?

bartezz’s picture

bartezz commented

Hmm that's odd, that's basically how I'm doing it.

Are you searching by string? Try searching for every string from profile module (radio button).

Cheers

aacraig’s picture

aacraig commented

No difference, unfortunately.

iamEAP’s picture

iamEAP commented

This should probably be made more obvious by displaying the source string with newlines intact.

Edit: that's a core issue. See #1358862: "Original text" on string translation form truncates useful formatting

liquidcms’s picture

liquidcms commented

i am just trying out translatable fields for the first time; but pretty sure this is not correct:

"search for a string from that text in the translation interface"

field info should not be translatable strings; it should field/node content.

jose reyero’s picture

jose reyero commented
Status: Active » Closed (won't fix)

This is how this module works and no, we are not translating field values (content).

Plus there will be no new features in 6.x version.