About translating flexicontent fields configuration parameters via Falang

Any news because I am stuck with pages not translated anymore.

Hello

about copy button not working

the textarea form element
origText_attribs

appears twice inside the HTML code,
(name="origText_attribs" appears 2 times)
deleting one of them seems to fix the copy button
- this is something that falang author should examine, why same form element name is used twice ?

about the display as parameters-area instead of textarea, i don't know, we always had this as "textarea"

I transmitted the message to the developer and he told me the next version is already corrected. But he found the problem when there is no translation visible. “The problem actually it's when there are php code in the attribs value of the fields”

Hello

you mean custom PHP code as parameter value ?
i guess there is some issue with escaping it

there is little we can do inside FC about it
if you do not need PHP code inside parameter then avoid it so that you can translate the field

or just do not use falang for some field
use language string for field label
and language strings inside field parameters, most / all parameters that have custom text, can take a language string

OK I understand but the problem is that there is always php code inside the parameter values even if I don't use it (your default values)

It seems that I can't translate the one I saved since the introduction of the default php code (maybe) because I don't have explanation why some are displaying well and other not.

Hello

go and edit the field

- enable custom code
- remove the code from the parameter
- disable custom code

save the field
this will save empty value into the parameter

until you re-edit and re-save the field, the value will remain empty
and you can translate the field