Background of the issue:
I am trying to use the WPML string plugin, but it is causing a conflict that prevents email notifications from being sent when using 'Bulk Actions' on the order page. If I disable the WPML plugin, the issue is resolved. The issue can be seen at the following link: hidden link
Symptoms:
The email notifications are not being sent when using 'Bulk Actions' at the order page due to a conflict with the WPML string plugin.
Questions:
How can I resolve the conflict between WPML string plugin and the email notification feature?
Is there a workaround to send email notifications without disabling the WPML plugin?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Madrid (GMT+02:00)
Hi,
could you let me know which plugin you’re using for the email notifications? Please keep in mind that compatibility issues usually work in both directions. If one component is deactivated, the problem might disappear, but that doesn’t necessarily mean WPML is the cause.
1) Could you please provide some screenshots or a short screen recording that shows the error?
2) How exactly are you using the "Bulk Actions" to send mail notifications? For example, are you updating the order status or performing another action?
The problem is your plugin because I disabled all plugin except wpml plugin and the plugin which I use to create the custom order status and the issue persist.
I have made this two minutes video to show the issue: hidden link
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Madrid (GMT+02:00)
Hi,
I think there’s a bit of a misunderstanding about how compatibility works in general. Let me clarify: as I mentioned, a compatibility issue can occur in both directions. Just because the issue disappears when WPML is deactivated, it doesn’t automatically mean that WPML (or another plugin) is the culprit. It only means that certain code is no longer running at that moment, so the incompatibility doesn’t appear. In that case, no multilingual functionality or function call is happening.
That’s why we need to test further to identify the exact cause and determine how it can be prevented. Please note that the plugin you mentioned has not been tested with WPML, so we don’t have prior experience regarding the extent of its multilingual support.
In situations like this, our typical approach is as follows:
1) Reproduce the issue with your help.
2) Investigate whether a code-level workaround is possible.
3) If a workaround is identified, it may require the plugin’s developers to update their code to ensure full compatibility with WPML.
In most cases, compatibility fixes need to be implemented directly by the plugin authors, as their code must interact correctly with WPML via our API.
Let’s move forward by confirming the exact issue:
1) Please install the affected plugin that’s causing the incompatibility in this isolated Sandbox environment: hidden link. (Note: WPML, WooCommerce, and a mail logging plugin are already active.)
2) Add your custom states and check if the issue can be reproduced.
3) If the issue occurs, we’ll escalate it to our Compatibility team to investigate a possible workaround and reach out to the authors if needed.
Feel free to reach out to the authors and invite them to join our Go-Global Program, where we help plugin developers get certified for WPML compatibility.
By joining the program, they'll gain direct access to our developers for support with integration—just like many other plugins that have successfully completed the process: See examples.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Madrid (GMT+02:00)
Hi,
I’m sorry, but we can’t accept site clones for compatibility reproductions. We can only investigate these kinds of issues if they are reproduced from scratch in our isolated Sandbox environment. Please note that this workflow has been tested and proven in thousands of cases over the years.
A clone is useful when we investigate an issue directly, but in this case, we need a clean reproduction to confirm where the compatibility issue originates—separate from your own settings, additional plugins/themes, or custom modifications.
I did the settings in your Sandbox environment and it works fine. I don't understand. Both sites, the sandbox and my cloned site have exactly the same 7 plugins active. I even set the same Theme for my clone site (Twenty Twenty-One). Capture: hidden link
Capture of the plugins active in my cloned site: hidden link
Important: If the "WPML Multilingual & Multicurrency for WooCommerce" plugin is disabled the email notifications are sent correctly.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Madrid (GMT+02:00)
Thanks, Walter!
That’s exactly why we use the Sandbox as part of our workflow—otherwise, we might end up troubleshooting a compatibility issue that doesn’t actually exist.
In this case, if all settings and plugins are identical, the issue is likely related to something on your server. I did notice a minor version difference in WooCommerce Multilingual: on the Sandbox, I updated it from 5.5.2 to 5.5.2.1, same version as your own server uses.
Could you please test again to see if the problem only occurs with that specific version? At the moment, that’s the only difference I can identify.
Please also double-check that there’s nothing interfering from the server side, such as object cache etc or similar services. As best, get in touch with DinaHosting and let them confirm all is off.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Madrid (GMT+02:00)
Hi,
thanks for the information — that helps us exclude a compatibility issue.
2) My hosting is running on PHP Version 8.2. Can you tell me which PHP version run your Sandbox?
Our Sandbox system is running PHP 8.1.2. You can confirm this on hidden link">this page.
However, if the PHP version would be the issue, you most likely would have some deprecation notices or warnings in your site's debug.log. You can check that as described here.
3) Should I check for the PHP Variables values? Like: max_execution_time, memory_limit, etc.
This information would also appear in the WordPress debug.log, but based on what we see, it doesn’t seem related. The process in question isn’t particularly resource-intensive, and any relevant PHP variable issues (e.g., memory_limit, max_execution_time) would typically show up there as warnings as well.
If the logs don’t reveal anything specific, please share a Duplicator package of your site so we can debug further. Please note, however, that we cannot guarantee a solution if a third-party plugin is involved and the issue cannot be clearly reproduced as a confirmed bug.
As the next step, I would test first locally to check whether the behavior occurs in a different hosting environment or only on your current setup.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Madrid (GMT+02:00)
Hi!
Correct, you didn’t provide credentials for the mentioned installation. However, you can either create a package using WP All-in-One Migration or share the database dump along with the FTP files, and I’ll deploy the package manually.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Madrid (GMT+02:00)
Hello,
Please provide the site package as described. The issue itself is clear, but without a copy we cannot debug it. I can only confirm that it works when WooCommerce Multilingual is deactivated.
If we can’t reproduce the problem from scratch to verify a compatibility issue, the variables will need to be debugged through a code analysis to determine exactly what the Order Status plugin does when the function runs.
