Translated versions of content with Pro Builder

[b_lynk]

Hello. We have translated this site (already) into French Canadian, and we are working on Translations into multiple other languages…currently French French, and Japanese.

Home | Webex Calling Help

https://staging-ciscochphd.kinsta.cloud/fr-ca/

Most of our content is built in default WP block (or classic) editor, and our Translation Vendor has RestAPI Access to pull/push/publish all of this to and from our site automatically.

We have developed an internal-process for the Global Elements (strings, menus, etc)…we basically export all the text-content (from English) into documents, send them to our vendor, and then rebuild (manually - for each language) with the copy provided.

The same manual-translation happens with Pro-Builder items (pages, headers, footers).

---

I’m running into an issue with our Pages (pro-builder) and the French language. Our process has been to edit the original (english) page (with pro)…and then to select the Flag-Icon > Create Copy of English…and that would give us a “translation” of that page - in the selected language.

This is worked perfectly for French Canadian…and is currently working for Japanese…but not with French.

Home | Webex Calling Help

---

I can clone English Headers/Footers (pro-builder) into FR, no issues.

When I try and use the existing English to create a French Page (pro builder) it seems to grab some random (unrelated) content and use that as the starting point.

---

Really wondering if you can jump in here and provide any insight into where we might resolve this issue?

[lely]

Hi @b_lynk,

I can’t find the settings why it is pointing to that specific page or why it is connected to homepage. What I found is Quick Page/Post Redirect Plugin with 301 redirection related to that page showing in the builder.

Could you try testing for a plugin conflict. You can do this by deactivating all third party plugins, and seeing if the problem remains. Specially Quick Page/Post Redirect Plugin. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.

Let us know how it goes!