Setup of Multilingual Cookie Consent
Permalink Browser Info Environment
I purchased this addon a while ago and now need to make the popup cookie consent support de_DE as well as English. That is, if someone goes to the "de_DE" branch of the site, they should see the text in this popup in German.
The GDPR interface directs me to the Concrete5 "Translate Site Interface", but I have absolutely no idea what to do with this - nor can I find any documentation. I tried downloading the "translation-de_DE.mo" file and put it into "application/languages/site" which now appears in this interface - but now what? If I click on the edit icon the resulting interface appears empty.
Any assistance would be sincerely appreciated!
Thanks,
Alex
The GDPR interface directs me to the Concrete5 "Translate Site Interface", but I have absolutely no idea what to do with this - nor can I find any documentation. I tried downloading the "translation-de_DE.mo" file and put it into "application/languages/site" which now appears in this interface - but now what? If I click on the edit icon the resulting interface appears empty.
Any assistance would be sincerely appreciated!
Thanks,
Alex
Type: | Pre-Sale |
---|---|
Status: | In Progress |
I managed to output the addon via the translate interface function in two languages (English and German).
But because you can only insert one single page for the "learn more"-link, also in the english version now is displayed (in my case) the german page.
Is there a possibility to prevent this behaviour in order to display the corresponding English privacy policy in the English version and the German version in the German privacy policy?
But because you can only insert one single page for the "learn more"-link, also in the english version now is displayed (in my case) the german page.
Is there a possibility to prevent this behaviour in order to display the corresponding English privacy policy in the English version and the German version in the German privacy policy?
I see what you mean! Good point. The UI doesn't support multiple links, you're right about that. As a workaround, would it help to clear the 'Read more page' link and hardcode the links in the Translation Site Interface instead?
Thanks for the input, I was thinking about hardcoding too, but I'm not that expert to do so, unfortunately
> Site translations are managed via the /dashboard/system/multilingual/translate_interface dashboard page. You first need to click the "Reload Strings" button, then you can translate the extracted strings.
If you hit that button, concrete5 is going to look through all source code and database tables for strings it can translate. Those are then bundled in a 'po' file. A PO file contains all the translatable strings. Once that file is generated, the strings can be translated via the "Site Translate Interface" page. Once done, you can make concrete5 write the changes. The PO file is then converted to an MO file, which is the compiled / final translation file.