[SOLVED] Available language strings not used for CB Privacy

I am using the newes CB Privacy plugin and also the newest CB. According to my tests the language strings responsible for the mouse over info text here.....



are not working (= only appears in english language) although I found the responsible (and translated) strings in the file cbprivacy-language.php.

English:
'THIS_WILL_DISABLE_YOUR_ACCOUNT_AND_HIDE_ALL_PROFIL_cc8b0d' => 'This will disable your account and hide all profile information associated with it.',

German:
'THIS_WILL_DISABLE_YOUR_ACCOUNT_AND_HIDE_ALL_PROFIL_cc8b0d' => 'Dies deaktiviert das Konto und versteckt alle damit verbundenen Profilinformationen',

...I also tried to override these ID's in the correspinding CB language plugins .....no success

It's just the fields description. Did you change the description by editing the field within CB > Field Management? If so the language string won't work anymore. Some WYSIWYG editors will add extra characters like <p> around strings which can cause this.

Also please keep in mind you are a Developer subscriber and should be posting in questions you may have in the Developer support forums. Have moved your topic for you from the community forums.

I have let the field description untouched, it is still set to the original string:

But I looked into my older website release where this translation worked…..the ID I have used there was:


'Disable account, user profile, and related features.' => 'Konto mit Benutzerprofil und bezogenen Möglichkeiten deaktivieren.',


I tried this now ...and this works ….so the issue can be closed

Remark: may be the ID = THIS_WILL_DISABLE_YOUR_ACCOUNT_AND_HIDE_ALL_PROFIL_cc8b0d is used for something different?

regards

The language key as part of the default language files is as follows.


However as said above it is a field description, which has changed between releases at some point. Updating CB Privacy won't change your fields descriptions. It's likely you've a case of the old description being there and you're trying to translate the new language key, which isn't being used in your case (or vise verse).

OK - was definitely an update issue on my site as you said. After deinstalling the plugin and reinstalling it again it works perfect. THANKS for your help

regards