Translated custom fields do not always show translated content on the front-end

This support ticket is created 5 years, 4 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

This topic is split from https://toolset.com/forums/topic/toolset-custom-fields-group-not-showing-on-second-language-post-editor/

Sun	Mon	Tue	Wed	Thu	Fri	Sat
8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	-	-
13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	-	-

Supporter timezone: America/New_York (GMT-04:00)

Tagged: Post-relationship, Setting up custom fields, Types plugin

This topic contains 2 replies, has 2 voices.

Last updated by Christian Cox 5 years, 2 months ago.

Assisted by: Christian Cox.

Author

Posts

December 20, 2018 at 4:54 pm #1170680

benC-15

4) Related to 3), for some facilities the address gets translated, but for others it doesn't - and it's not clear what's causing the difference. E.g. see The Veranda (Repulse Bay), where the address is shown in English on the Chinese page, vs Theo Mistral.

December 20, 2018 at 8:21 pm #1170750

Christian Cox

Okay I'm able to see what you're describing here, and I'm fairly confident this is a symptom of the same problem. The translation settings for the custom fields are not saving consistently. If I set some field to be translatable, others are automatically marked not translatable by the system. This is currently under investigation by our team, and I'm reporting this symptom of the problem as well.

February 13, 2019 at 2:56 pm #1200054

Christian Cox

This one should have been resolved in the WPML 4.2.0 release. Can you verify and let me know?

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.