This thread is resolved. Here is a description of the problem and solution.
Problem:
Types Select field display values should display as translated but are displaying in the original language.
Solution:
This was a bug, fixed in Types 3.0.5
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.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| - | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | - |
| - | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | - |
Supporter timezone: Europe/London (GMT+00:00)
This topic contains 7 replies, has 2 voices.
Last updated by 6 years, 5 months ago.
Assisted by: Nigel.
Suddenly the translations for custom fields has stopped working. We use WPML for translations. The custom field in this example is translated via String translation. The value of this custom select field is the same in the original and the translation, it's just the display text that should have a translation.
I've tried to remove the translation from String translation and then add it again, but without luck.
The problem applies to all custom fields, not just the one shown in the example.
Check out the beautiful mashup of screenshots.
