Translatability of the template code field

Since in some cases it may be necessary for different languages to use different template codes due to the use of individual links etc., it would be very helpful if the template code field could also be configured as editable or overridable in alternative language versions in the TCA.

mentioned in issue #162 (closed)

changed milestone to %4.1.0

Could be implemented with the translation behaviour flags in TYPO3 where you can say if a default value should be taken from the default language or should be overwritten. Only relevant for the template code and not all colors and such stuff. Not sure if this is already possible with TYPO3 8.

assigned to @Mateev

Done, will be added to the next version

closed

mentioned in commit 350a8bd6

Just for the record

In one of the TYPO3 Systems we are using, there is a 'leichte sprache' language configured. As you can imagine, leichte Sprache means, that not all content elements are translatable since they are to complex or legal texts that can not be modified and are therefore not present when this second language is active.

That is why the 2nd langugaue is configured as Fallback: Freemode

Since I'm not able to create a cookie opt-in record with a specific sys_languague_uid I have to create a translation of the default language:

When I set the Translation Behaviour of the fields Overwrite Template and Template Code (HTML...) to use value of default language the template code field gets emptied on save. I can work around this by configuring both fields as explicitly custom:

So all in all it isn't a big problem for me. Just wanted to let you know. I know that TYPO3's transalation behaviour is a pain and probably most of the TYPO3 instances use a strict fallback behaviour.

changed milestone to %4.2.0

Hi @christian.richter thanks for raising the issue. There was actually a bug in how we saved the template code upon the initial creation of the object that was causing this. It has been fixed now and will be released in the next version.

You could, however, still have the old broken state. Saving the entries once again should be able to fix it though.

To manually fix your data, you can simply re-save your configuration in the default language and then go in the database copy the template_html, iframe_html, iframe_replacement_html, banner_html field values to the translation records in the tx_sgcookieoptin_domain_model_optin table