Fields translation fallacy.. Not truly multilingual. – UserPro Forums

Fields translation fallacy.. Not truly multilingual.

ianstudio — Wed, 29 Oct 2014 13:36:08 +0000

Do you admit that the form fields titles in the back-end can only exist in one language/version ? And that if I translate them as per your explanation in the back-end (basically change their text), they will then look the same in all languages when switching languages using WPML as these fields titles do not use the .mo .po files and thus can only exist in a single version ? So as a closing statement: do you agree that this plugin is not really multilingual ?!

Yes I am upset. Cannot get a clear answer from you guys on this matter and it has been weeks now that I try.

Reply To: Fields translation fallacy.. Not truly multilingual.

UserPro Support Team — Thu, 30 Oct 2014 05:46:52 +0000

Hello Ian ,
The labels are fetched from the database , when we initially chenge the labels they get save din the database and it cannot be changed dynamically in a multilingual platform .
Thank you!

Reply To: Fields translation fallacy.. Not truly multilingual.

ianstudio — Thu, 30 Oct 2014 06:26:40 +0000

Well, then if you want “us” to be able to use this plugin you need to rebuild the system differently and make the labels fetched from the .mo .po files so that they can be translated.

I cannot tell my clients that part of their website cannot be translated (in those cases I wanted to use the plugin for: containing WooCommerce shops) and that their own clients will have to register and look at their accounts’ content like their Billing Addresses, Shipping Addresses etc in a language that does to match their own and the rest of their user interface.

To me that’s a major problem and I obviously cannot use this plugin.

Reply To: Fields translation fallacy.. Not truly multilingual.

ianstudio — Sun, 02 Nov 2014 10:20:55 +0000

Is there any hope that you may face this issue and use .mo .po files for the fields labels in the future so as to make it truly multilingual and WPML-compliant or should I just give up on this plugin ? :0(

I find it silly for such a “detail” and sad considering the hopes I had for it ..but it’s like telling a client.. “oh well, the menus in your site will be the same for all visitors in any language”.. That would be silly.

If you guys were americans I could almost understand that you would not care about true multilingual support and stay in your own bubble world.

Reply To: Fields translation fallacy.. Not truly multilingual.

activatonline — Wed, 17 Dec 2014 11:45:15 +0000

is this trouble solved ? I am in the same situation…