Hello @jaspash,
I hope you are doing well.
Note: In a clean environment (WP + WooCommerce + Storefront + our plugin), we could not reproduce the issue.
#1. To provide you with the best support, please repeat the test on a staging site with only WooCommerce, Storefront, and our plugin. Indicate the versions of WP, Woo, and our plugin, and whether HPOS is ON/OFF.
#2. Record a short clip showing:
Orders → Bulk actions → Change status to… (specify the status).
WooCommerce → Emails: that email enabled.
WooCommerce → Status → Scheduled Actions / Logs: if email tasks are being created/failed.
Include screenshots if possible.
We are here to help you.
Best regards, peace!
Hello,
I create a staging site and did the “disable all plugins and enable one per one” and found that there is compatibility issue between your plugin and WPML plugins.
The wpml plugin support told me that the issue is in your plugin.
Is your plugin compatible with WPML? Can you take a look at this please?
I can provide credentials to you for my staging site.
Please, let me know.
Regards,
-
This reply was modified 8 months, 3 weeks ago by
jaspash.
I can provide credentials to you for my staging site.
Please do not. If it is believed that they accepted that, they get banned and their plugin can be removed from this site.
NOTE: they did not ask for that and I am just explaining that if they did (they did not) this would be the reply to them.
While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.
If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.
Thankfully are other ways to get information you need:
- Ask the user to install the Health Check plugin and get the data that way.
- Ask for a link to the http://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
- Ask the user to create and post a link to their phpinfo(); output.
- Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
- Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site visitors).
- Ask the user for the step-by-step directions on how they can reproduce the problem.
You get the idea.
We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.
When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.
So please don’t offer, it could get them into trouble.
Hello,
Thank you @moderator for clarifying this very important point.
@jaspash, to confirm: we do not request credentials here. We will keep all support public so that other users can benefit from the thread; that is the spirit of the community.
We will review it internally and update this thread with any findings.
To proceed, please share the versions of WordPress, WooCommerce, our plugin, and WPML (Sitepress, String Translation, WCML), if HPOS is enabled, the Bulk Action and exact statuses, and what appears in WooCommerce > Status > Scheduled Actions / Logs right after the change.
Best regards, peace!
-
This reply was modified 8 months, 3 weeks ago by
mathdaniel.
Hello there,
I found tha the problem is a conflict between your plugin and the WPML plugin. I opened a ticket with the guys at wpml support site. You can see the ticket here: https://wpml.org/forums/topic/wpml-string-plugin-create-a-conflict-for-other-plugin-to-work/
I have the latest versions of wpml plugins:
– WPML Multilingual CMS – 4.8.1
– WPML String Translation – 3.4.0
I will let you know as soon as I get more information for this issue.
Regards, Walter.
-
This reply was modified 8 months, 3 weeks ago by jaspash.
-
This reply was modified 8 months, 3 weeks ago by jaspash.
-
This reply was modified 8 months, 3 weeks ago by jaspash.
Hello,
I hope you are doing well.
Thank you for this information you shared with us; it has been referred to the team. After the review, we will return to this thread!
Have a great day.
Best regards, peace!
Hello,
We found the cause of this issue. Your plugin is using a function which is a reserved function for WPML plugin. You can see more information here: https://wpml.org/forums/topic/wpml-string-plugin-create-a-conflict-for-other-plugin-to-work/?paged=2#post-17429287
Based on Wpml supporter, this hook fix the issue. Please let me know if you can apply this patch in your next update.
add_action('woocommerce_order_status_changed', function() {
$tag= 'woocommerce_order_status_changed';
$prio= 10;
$callbacks= $GLOBALS['wp_filter'][$tag]->callbacks[$prio] ?? [];
foreach($callbacksas$cb) {
$f= $cb['function'];
if(is_array($f) && is_object($f[0]) && $f[1] === 'comments_language') {
remove_action($tag, $f, $prio);
}
}
}, 0);
Hello @jaspash ,
I hope you are doing well.
Thank you once again for your participation and for sharing this. The team works based on sprints and prioritizes needs according to the analysis. As I mentioned earlier, this was already on the list.
Now we are adding what you provided, and we will get back to you with a response in this same thread!
Have a great day.
Best regards, peace!
