BuddyPress x-Profile radio checkbox

I guess, it needs more integration then: https://qtranslatexteam.wordpress.com/integration/. If you figure it out, make sure to submit the solution to BuddyPress and copy us: https://qtranslatexteam.wordpress.com/contact-us/

Thanks for your quick response. I really like this plugin. I have no experience with integration yet, but I did manage to quickly add language buttons to the xprofile edit page – never thought I would even get this far! I really don’t mind using encoding, but the problem occurs when saving the options as a buddypress member on the front end (it does work in backend!) – will more json integration help with this? I believe it may not.

From what I can now understand, on frontend member form save, buddypress xprofile checks radio/checkbox values against backend values which are encoded and do not match frontend translated values, producing the error. In fact, if other matching non encoded radio/checkbox values exist in backend, they will be selected instead and no errors returned. Maybe I can try disabling that check function in xprofile, or can some JSON integration solve this?

Another possibility: prevent radio/checkbox html value=”” from being filtered and translated. Used Firebug to test this, works – but I don’t know how to implement it yet.

Followup:

Is there a way to prevent string from being decoded on frontend?

If the full string was displayed in name input of the frontend edit group buddypress page, I could at least have members enter codes to input multilingual titles.

Every way I try to print group name there, it it always translated.

Sorry, my last comment was unrelated with previous topic

I am not sure, this sounds like a complex issue, because front end expects everything to be translated to the current language and no multilingual values can be used at front end. Are you saying that BuddyPress uses translatable strings for the value attribute of checkboxes? This should not be a case. You may talk to the authors then, they really should design it in a way that attribute “value” would be a language neutral key, if I understood the problem correctly.

If you think that qtx may do something about it, then describe specific problem reproducing steps under a configuration with minimum active plugins and using standard theme in an issue at GitHub, where we track bugs and improvement requests.

Hey efrap, did you find a solution? (It also has with dropdown list.)

Sorry, never did.

Could you please, give the steps to reproduce the problem? Assume we have no knowledge about BuddyPress at all. Explain as for absolute dummies ?? Provide links of pages where to go, what to type, what to click, what to look for.