Replies: 1 comment
-
This was brought from a support ticket on wordpress.org: https://wordpress.org/support/topic/translating-options-in-a-custom-post-type-dropdown-field?replies=2 For their uses, it really needed to be a custom taxonomy or relationship to another Pod as the users would need to be able to edit the options and asking a user to go into the Manage Pods, Manage Fields and edit the field for options is not exactly a good idea. Not sure how this one would work with PolyLang since the 'options' are actually at the field level in the configuration of the Simple Custom Defined List (ie they're not part of the meta data of the resulting posts, this is in the pods config for the field. |
Beta Was this translation helpful? Give feedback.
-
Simple Custom Defined List Relationship not offering Polylang translation submitted via Slack by jimtrue
Workaround
This may not be fixed for a while, so if you are needing a Simple Custom Defined List to be translated, would suggest either using a Taxonomy or a relationship to a Custom Post Type to manage those 'options' in your List. You can translate the Custom Post Type and the Taxonomy naturally using WPML or Polylang.
Beta Was this translation helpful? Give feedback.
All reactions