I am trying to:
Translate custom fields with WPML. After translation is takes the translation to both language. In other words, if it is in dutch it shows the dutch translation on the english site. If i change the english translation it shows on the dutch site.
Link to a page where the issue can be seen:
Dutch version hidden link
English version hidden link
English page hidden link
Dutch page hidden link
Taxonomy works fine
I expected to see:
English version
Instead, I got:
Dutch version
This is likely an issue with how WPML allocates the translations, not with the Fields of Toolset.
In WPML exist troubleshooting steps but those need to be followed with the careful instructions of a WPML expert
(The steps are under WPML > Support > Troubleshooting, but as suggested I would not perform them without consulting a WPML expert first)
On my local testes, translating the Fields works fine, if I select to translate them, and then use the Translation editor to translate those to another language.
I use languages in directories but that should not make any difference.
I think, WPML somehow mixed up the language information here - and likely this should also show on the very post itself?
What's also possible is that you use the ShortCodes in Translated Content Templates, or other approaches to translate and display the content.
Is it possible to make a test on the site
- create a CT (Content Template) that shows those contents and display the posts with it
- create a default language post which is displayed with this CT
- translate it inclusive its fields to the secondary language
This should work on both languages.
If not, then something with the WPML settings likely is wrong, or eventually, you translate the Content Template to other languages?
Hi Beda,
Thanks for the quick reply. I had same feeling not showing the translated page but as you can see here
English page hidden link
Dutch page hidden link
it works with the "vakgebieden" so something is working.
Working with the CT is not a option as i understand from previous support its not working with eliminator page builder as i use this for the project.
No idea what to do with ask WMPL what they think
cheers
OK, I need to look at this as locally it's working fine.
Please allow me to:
- create a Test Field Group
- In it, a test Single Line field
- A test Post with this field
- translate the post and the field to another language (please set the user up to be able to translate)
This can also be done with existing setup and content, however, in both cases, please acknowledge that it affects the site, hence a test instance would be the adequate place to do this.
Then, after my tests and findings, you could adjust the live site.
If you have no such test instance another approach is this https://toolset.com/faq/provide-supporters-copy-site/, or that I do the edits on the live site, which is the less preferred and would require explicit permission from you.
I enabled all required private fields for you to choose the specific option.
My issue is resolved now. Thank you!
