I am trying to: Use the custom field name as a translatable label for the field (WPML installed and custom field name is translated in the string translation) in my PHP code but the translation is not working when I use 'output'=>'html' but only when I use 'output'=>'raw'. Is this a know bug?
Yes I checked on this for you and what you need to do is to translate every instance of the Field Name in string translations and it should show up translated.
Thanks Shane but I have already done that. That's why I'm saying that when I use 'output'=>'raw' I can see the translated string but when I use 'output'=>'html' the field name remains in the original language.
Unfortunately I'm doing my tests locally. I will try to move it to the live site but until then can you think of what else I should check? If you tell me that 'output'=>'html' should also show the translated field name as 'output'=>'raw' does there has to me something wrong with my settings. Default language is Greek and additional language is English but the Toolset custom fields are created with english field names and then translated to Greek as the WPML instructions point.
I dont believe that it should matter much, however i'm not an expert on WPML to say whether or not the default language will affect such a setting. However once the correct language is being provided it should work as intended.
All I did in string translations is to translate every instance of the field name that I could find.
I'll enable the private fields for your next response, so please let me know as soon as you're able to provide the credentials.