Hi Andreas,
thanks for your answer!
Yes, they have been translated already. Problem is, that they always fall back to the original language.
My guess is that this happens every time a translation process is issued. So that's why I would like to exclude them from the translations.
Best,
Bernd
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Madrid (GMT+02:00)
Hi Bernd,
my colleague Andreas is unavailable today, therefore I take this ticket over.
We don’t have a built-in way to exclude content from translation. Do you have a staging site where we could run some tests?
I would eventually also need to request temporary access (WP-Admin and FTP) to your site
– preferably to a test site where the problem has been replicated if possible –
in order to be of better help and check if some configurations might need to be changed
Your next answer will be private which means only you and I have access to it.
❌ Please backup your database and website ❌
✙ I would additionally need your permission to de-activate and re-activate Plugins and the Theme, and to change configurations on the site. This is also a reason the backup is really important.
✙ Please add the Links to the […] Edit Screen, the Page/Post where you insert the […] and the corresponding Front End Page/Screen
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Madrid (GMT+02:00)
Hi Bernd,
thanks for the access.
EN: hidden link
DE: hidden link
As far as I can see, there is no global content defined anymore in the German version. It also uses different shortcodes, which explains the differences in output. Since you're not using the WPML Editor (based on your configuration), everything is managed manually through the WP editor within Avada. That means there's no synchronization for this content, so there's also no need to "exclude" anything. You can simply add a new global element for the German version, as you are using the manual translation mode.
Maybe I should have pointed you to a specific post... yes, we do have global elements. For example in the post titled "Denmark's Largest Refinery Focuses on Digitalization" - see the attached screenshot. There's more global elements here but the one that I marked always falls back to english in the german translation.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Madrid (GMT+02:00)
Hi Bernd,
Just to clarify — it’s not actually falling back; the Global Elements are simply not defined in the DE version. Also, since you're using the EPML Editor, the sync isn’t handled automatically by WPML. You need to handle all in the Page Builder manually.
1) Assign the Global Elements manually in the DE version.
2) Make a small update to the English content afterwards and check if the Global Elements stay assigned.
thanks for your help! Your answer pointed me in the right direction, I guess. I think the problem is within our translation workflow. I've scheduled a meeting with our editors to go through the process together.
For the time being, I close this ticket. If I still run into problems, I'll open another one.
Thanks again and best regards,
Bernd
