Cloud template saved as base 64 conflicting with WPML

Posted in: Newspaper
Post count: 40

Hello,
I am using latest WPML and Newspaper.
One of my templates (header template) is saved as base64. Not some fields, but the whole content of the template is base64.

In case when some field is coded as base64, there is a solution at WPML site though editing custom XML configuration file and adding “encoding=base64” to the particular fields. I had this issue with footer template and it was resolved.

But in case when whole template is saved as base64, WPML cannot read it.

Do you know any solution to this problem? Why some templates are saved as base64 and is there a way to avoid it and save normally?

Post count: 35449

Hi,
Yes, indeed all the content in the cloud header is encoded in base64.
Normally, if you want the header to be used in several languages, this can be done very simply, using certain settings in WPML that offer the possibility of having a cloud header in each language – https://forum.tagdiv.com/using-theme-translations-together-wpml/
Another solution would be to use an online decoder – https://www.base64decode.org/
Thank you!

Post count: 40

Hello Calin,

Thanks for your reply.

1. I read the guide at the link you offered. However, I did not find anything about how to cope with header cloud templates. Moreover, the guide is outdated, and I cannot follow it. The guide shows a screenshot from the cloud template page, where there is a possibility to add new languages (clicking on a plus icon). However, in the latest version of TagDiv/WPML there is no such possibility (see the screenshot at the link https://prnt.sc/uXbaWpcIw1vi).
To add another language I use WPML’s translation management menu. But the header cannot be sent because of base64 encoding.

2. Another solution with online decoder I don’t understand. I have decoded the content of the header cloud template. And what do I do with the decoded text? I can see there a lot of base64 decoded attributes, such as tdc_css, flex_width, f_descr_font_size, content_general and others. Some of them are located under the tags, which are not existing in the custom XML configuration tab. Do I have to add all of them (including new tags) to custom XML or what?

Post count: 35449

Hello,

To translate the cloud header, the best solution for our theme is to translate/duplicate the cloud header for each language.
Indeed there have a few changes in the theme for cloud templates. Now you need to click on edit cloud template – https://i.imgur.com/8krRGsa.pnghttps://i.imgur.com/J9SUPAz.png

Thank you!

Post count: 40

Hello
You say that I need to translate/duplicate cloud header for each language.
But as I wrote above, that is my problem. I cannot do it because the header is encoded in base64.
I was promised compatibility of Newspaper theme with WPML but it does not look to be fully compatible. How can I translate/duplicate cloud header from one language to another language?

Regarding your new procedure, I tried it. But the theme leads me to the translation screen with only one field: name of the header template.
Please see the screenshot:
https://prnt.sc/1kY-7ny3kdBh

I

Post count: 35449

Hi,
Cloud template translation will not actually translate the text as strings from it, but will make a cloud header for each individual language, and this can be edited with the composer and the text changed.
If you can, please contact us via email (contact@tagdiv.com) and we’ll check the situation.
Thank you!

Post count: 40

Hello,
Noted. So, I can translate all cloud templates except for header.

Viewing 7 posts - 1 through 7 (of 7 total)
The forum ‘Newspaper’ is closed to new topics and replies.