Translating option page fields content #956

Open
Julianoe opened this Issue Apr 19, 2017 · 2 comments

Comments

Projects
None yet
2 participants

I'm opening this thread for discussion among CMB2 users: what are the uses you made of CMB2 in the case of option pages translation? What is for you the best practice for making the content of fields in an option page multilingual?

I can't wrap my head around how to make it very simple; i want to avoid at all costs the necessity to use WPML String Translations plugin interface for example which is a pain in the ass for the end user.

What do you think? What are your practices in that case?

Contributor

tw2113 commented Apr 19, 2017

Valid question(s) here, and one that I think merits staying on GitHub here, as an overall potential enhancement.

Any time things are being stored in the options table, internationalizing the values are always a challenge. I am going through the same with "Custom Post Type UI" with WebDevStudios. Different plugin, but still ends up storing strings in the options table that would potentially need internationalized for admin area visitors.

Some details :

I'm really searching this matter everywhere (wpml forums, stackexanche, reddit...) but can't find real discussions on this. I mean the end-user/not technical user of a website (e.g.marketing person) whose job is only to fill the content, create products or posts etc... could have to provide information in a options page (or anywhere that uses the wp-options database table).

In this type of use case the user has usually a clean interface and easy to use buttons for translating a post/product. Why should they go to a complex "string translation" page just to translate a field containing a basic text... ? :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment