Hello tagDiv Support Team,
I am using the **Newspaper Theme** with the **tagDiv Composer** for page building and have chosen to use the **Polylang** plugin (free version) for multilingual content, as I am already committed to this tool. I understand your documentation primarily recommends WPML, but I am seeking a workaround/solution for Polylang.
**The Problem:**
When creating a new translation (e.g., from English to Hindi) for a page built entirely with the tagDiv Composer, the new page is created but the **Composer’s layout is blank**, requiring me to rebuild the entire page structure manually for every language.
**What I Have Tried (Based on Polylang best practices):**
1. I have set the Polylang synchronization option for **Custom fields** to be checked/active. This is normally what copies page builder data.
2. I have also checked **Taxonomies**, **Featured image**, and **Page template** synchronization.
**My Goal:**
Is there an officially recommended method or a known configuration setting within the tagDiv Theme Panel that ensures the entire **tagDiv Composer structure** (the shortcodes/page data) is copied over when using the Polylang translation feature, similar to how it works with WPML?
Specifically, where does the tagDiv Composer store its page data, and can this meta key be whitelisted or synchronized by Polylang?
Any guidance on maintaining page layouts across languages with Polylang would be highly appreciated.
Thank you!
Hello, Unfortunately I don’t know exactly how Polylang works, but if you want to translate a page or a cloud template from one language to another, what needs to be done is a duplicate of that page/template in another language, after which you will have to use tagDiv Composer to change the text and images, because these are not automatically translated and there is no manual translation system like for articles in the original language and the language you want to translate into.
Thank you!
