WooCommerce add Wholesale Role Conflict

Loco Translate does not remove any roles, and I don’t see how it could affect the functionality of your plugin.

It adds its own role called “translator” and a capability called “loco_admin”. This is only done when they are absent and is the extent of its involvement in site permissions.

If you can find any evidence of this plugin breaking another plugin’s permissions, please report it as a bug.

if the loco plugin deactivated the wholesaleRole is visible in the admin view. And is the plugin activated the wholesalerole is hidden. How can i send you more information about this. Do you need any fieldname where the role is displayed?

I have said that my plugin does not modify roles. If you have evidence of it, you need to demonstrate it. I can’t tell you how to do that because you’re the person experiencing it, not me.

I don’t understand your terminology either. Roles exist or don’t exist. I don’t follow your comments about roles being deactivated or hidden, or your reference to field names.

Here this example in the html code it will translated the option parameter
without loco plugin, the WholeSale Customer is there
<option value=”wholesale_customer” selected=””>Wholesale Customer</option>

and with the loco plugin, the wholesale customer role is hidden
<option value=”wholesale_customer” ausgew?hlt=””>Wholesale Customer</option>

It sounds to me like translating certain strings that shouldn’t be translated is breaking functionality. Loco Translate does not choose what strings are translated, the code author does.

In your example: Why would the author of that form allow the HTML “selected” attribute to be translated? That’s very weird behaviour. There is no such HTML attribute as “ausgew?hlt” so it will break the form element. i.e. prevent it actually being pre-selected on page load. Possibly why you are losing your roles when you save.

Your problem doesn’t seem related to to my plugin. It seems related to either bad internationalization or perhaps some other plugin automatically translating things it shouldn’t. I can’t really guess, but what you’ve shown me isn’t evidence that my plugin is doing anything it shouldn’t.

I’m marking this as resolved as you’ve not followed up and the issue seems to be bad i18n practice.

Yes thanks, only for the record.
Here is my solution, the corresponding plugin is chosen in the Loco plugin and the translation is changed from selected and “ausgew?hlt” back to selected.