Temporary Access to your system
Please provide access to your system (wp-admin and ftp) so that I can further investigate this particular problem. The fields to provide this data are included in a private section that I will open for your next response. You can find it above the comments area. The information in this private section is only visible between WPML Support and you.
Please also tell me which product to test with and any coupon data I should use to see the issue.
Is this a development or live site? Am I permitted to temporarily activate/deactivate plugins as I troubleshoot this issue?
This seems to be a compatibility issue with the plugin that is providing you with the taxonomy "Brands". I suppose it is : YITH WooCommerce Brands Add-on Premium
Normally, we require the coupon to be "not translatable" and the different language views of the coupon details (i.e. usage restrictions) will place the language-dependent version of the product or category in the details depending on the active admin language when you edit the coupon.
However, in your case, the custom taxonomy "Brand" is not handled by WCML.
The only way I could get any coupon to be applied to an Arabic "Brand" was to :
- temporarily set the "Coupon" post type to be "Translatable".
- Then define a new coupon "Amnya2" with the Arabic language active and select the Arabic translation of "Amnya".
- Set the "Coupon" post type back to "Do not translate".
Now you can see that the coupon "Amnya2" is applied to the Brand.
I understand that this is not the solution you are looking for but it higlights the issue at hand which is that WCML and your "Brands" taxonomy are not compatible.
These are tested as compatible with WCML solution.
If you insist on using the plugin you already have, I have to warn you that the compatibiltiy process can be long and may not ever reach a resolution. We require a working relationship with the plugin author, a sufficient market demand from our clients, and that the issue not be so complex to resolve.
The process asks that you recreate the issue on a new sandbox site that I will provide. I will confirm the issue and then escalate it to our compatibility team who will then decide whether to investigate it/resolve it or not.
For this reason, I would suggest if you could see if another plugin that is already tested might work for your installation.
I wait for your news and if I should provide to you a sandbox site to begin the compatibility process.
