Not really translatable

Hi Iurie,

Thanks for the report of the text-domain inconsistencies. I’m not sure why your fixes have failed, but it could be to do with the plugin’s pot file. Could you try your translation with the development version from the Github repo?
https://github.com/christianwach/bp-xprofile-wp-user-sync

There’s a “download zip” link on the right hand side – you may need to rename the enclosing folder once you’ve unpacked it.

Cheers, Christian

The fields are created when the plugin is first installed and the name of the field is stored in the database. You will need to deactivate and delete the original plugin for the change to take effect when new fields are created. This, however, will “orphan” existing data.

The situation is a bit of a fiddle because the field data is not deleted when the fields are deleted and because the plugin stores data about the fields in order to try and allow the field definition data to survive plugin deactivation and reactivation. Unfortunately, because your fields were originally named incorrectly (for you), that original naming will survive without intervention.

In essence, there are two conflicting processes at work here: (a) to retain existing definitions (b) to fix incorrect definitions. I think your best bet (if you want to keep the field data linked to the field definitions) is to manually change the field names in the database via PhpMyAdmin or suchlike. If it’s a clean install, then the delete and reinstall route should also work.

Cheers, Christian