Conversation
supportHello, I’m experiencing two separate plugin conflicts. Issue 1: Conflict with PW WooCommerce Gift Cards Pro (since v1.6.19) After filling in the required gift card fields (amount, recipient name, email address, etc.), customers are unable to add gift cards to the cart. The “Add to Cart” button does not respond or throws an error. This issue started appearing with version 1.6.19 and did not occur in earlier versions. Reverting to a version prior to 1.6.19 resolves the problem. Might be related to this topic . Issue 2: Conflict with Sendcloud (present before v1.6.19) Product weight data is not being passed correctly to Sendcloud. This issue was investigated and confirmed by Sendcloud’s support team. Their finding: the plugin is overriding or preventing product weight from being registered properly, making it impossible to retrieve the correct weight via the WooCommerce REST API, which is the method Sendcloud uses to import order details. As a result, shipping rates and label generation based on weight are unreliable. This issue predates v1.6.19 and has been present for longer. Could you please investigate both conflicts? Happy to provide additional debug logs, screenshots, or a staging environment if needed. Thank you. The page I need help with: [ log in to see the link]
Hi @foudelle Can you send me an exact link where I can test the gift card product?
Hi Maarten, Here is an example: https://www.foudelle.be/product/cadeaubon-digitaal/ This should work now, as I’ve rolled back the plugin to version 1.6.18.
Looking at the source code of your page, none of these fields are created by our plugin: https://i.snipboard.io/Of5oBw.jpg They are created by your gift card plugin. Am I missing something?
@maartenbelmans No, that’s absolutely correct. However, something has changed in the versions after 1.6.18 that conflicts with the gift cards plugin. Visitors are then shown a notification stating that the product cannot be added to the cary. After enabling and disabling all the plugins one by one, I was able to trace the problem back to this plugin, and specifically to the latest updates. This reply was modified 2 months, 2 weeks ago by Jonas .
Do you have a test/staging version of your site where this could be reproduced?
@maartenbelmans Yes, I do. Where can I send you the login credentials?
@foudelle Please confirm that the developer will not log into your site. They made a very serious mistake that could result in their plugin being removed from this site. @maartenbelmans 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.
Hi @foudelle Can you send me an exact link where I can test the gift card product?
Hi Maarten, Here is an example: https://www.foudelle.be/product/cadeaubon-digitaal/ This should work now, as I’ve rolled back the plugin to version 1.6.18.
Looking at the source code of your page, none of these fields are created by our plugin: https://i.snipboard.io/Of5oBw.jpg They are created by your gift card plugin. Am I missing something?
@maartenbelmans No, that’s absolutely correct. However, something has changed in the versions after 1.6.18 that conflicts with the gift cards plugin. Visitors are then shown a notification stating that the product cannot be added to the cary. After enabling and disabling all the plugins one by one, I was able to trace the problem back to this plugin, and specifically to the latest updates. This reply was modified 2 months, 2 weeks ago by Jonas .
Do you have a test/staging version of your site where this could be reproduced?
@maartenbelmans Yes, I do. Where can I send you the login credentials?
@foudelle Please confirm that the developer will not log into your site. They made a very serious mistake that could result in their plugin being removed from this site. @maartenbelmans 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.