WooCommerce Stripe Gateway Conflict with Flatsome theme
-
WooCommerce Stripe Gateway plugin Conflict with the Flatsome theme, causing the coupon and Apply coupon button to disappear on cart page.
- This topic was modified 4 months, 4 weeks ago by gabbit.
-
Same problem – only way to fix it is to use the legacy stripe checkout option! Can someone look into this?
Thank you for contacting Woo support.
I understand you are facing a problem with the Flatsome theme where the coupon and apply coupon buttons disappear on the cart page.
Since this problem is specific to the Flatsome theme, I suggest you contact Flatsome support and ask about them about this issue.
Please let me know what they have to say about this.
I will be happy to assist you further if there is anything to be done on the WooCommerce end.Looking forward to your response. ??
Best regards.
@doublezed2 the plugin seems to hide the coupon form with JS by adding
display: none;
literally with$( 'form.checkout_coupon' ).hide().on( 'submit', this.submit );
- This reply was modified 4 months, 3 weeks ago by Jim.
when i switched the plugin to another Stripe Gateway plugin, the issue solved, abviously it is not the Flatsome theme’s problem.
Hi @gabbit
I tried replicating the issue using various themes, such as Storefront, Twenty Twenty-Four, Astra, Blocksy, GeneratePress, and Botiga, but I couldn’t. Everything seems to be working fine.
Since it especially happens with the Flatsome theme, some of the custom code in the theme definitely conflicts with it. It would be best to reach out to the plugin developer for further assistance.
However, if you believe it is a bug in our plugin that needs fixing, I’d recommend you submit a bug report to our GitHub repo here. This way, our developer can review it and provide further insights.
I wish I could help more, but hopefully, this gets you going in the right direction to get some further insight/information.
@gabbit
You can try adding this CSS so it stays visible, since they hide it with JavaScript code as I mentioned above:form.checkout_coupon?{
display: block !important;
}YES , the CSS can make the button stays visible, but the cart total can not refresh
@shameemreza @jimapp rather than pointing us all into different directions could you two maybe liaise and identify HOW to fix this issue on your end?
Otherwise I am afraid I’ll have to switch to a different payment provider and theme as it currently feels like you are both blaming the other development team rather than work together to identify and fix the issue. ??After inspection and debugging, we see that the plugin loads the
checkout.js
JavaScript file from WooCommerce on the cart page, which is initially not to be expected as it is a file meant to be loaded on the checkout page.The script includes
$( 'form.checkout_coupon' ).hide().on( 'submit', this.submit );
which will make the current reported behavior and targets the coupon form on the cart.One way to prevent the script from interfering in the meantime is to change a class name in the template
flatsome/woocommerce/cart/cart.php line 223
:from:
<form class="checkout_coupon mb-0" method="post">
to:<form class="ux-cart-coupon mb-0" method="post">
Best regards- This reply was modified 4 months, 3 weeks ago by Jim.
@jimapp so why is this only impacting flatsome and not various themes, such as Storefront, Twenty Twenty-Four, Astra, Blocksy, GeneratePress, and Botiga as tested by Woo Support?
Are you sure that your theme is using the current most up to date cart template? And if not should this not be patched through a flatsome update rather than asking us to create a child theme?@doublezed2 can you have a look at the statement of @jimapp that your plugin is loading unexpected javascript on the cart page?
Howdy y’all ??
WooCommerce Stripe Gateway plugin Conflict with the Flatsome theme, causing the coupon and Apply coupon button to disappear on cart page.
Could you elaborate further on when this started happening, @gabbit ? Was it after an update, perhaps? If so, what update?
While I read there was a chance to test with a different plugin, I could not find any details if the WooCommerce Stripe Payment Gateway plugin was working as expected with a different theme active on your site.
Just to clarify, as this issue appears to be theme-specific, did you already have a chance to reach out to its support channel about this issue, or otherwise?
Our team tried replicating the issue with a variety of other themes, block-based or otherwise, to no avail.
There might be internal documentation on supported Stripe plugins, as I could not find any reference in its changelog.
Feel free to reach out to Flatsome’s support channel (linked here), as they would be in a better position to assist you.
I trust this provides clarity.
Hey @anastas10s
If you look further up in the thread?@jimapp?(one of the developers behind flatsome!) has already identified that this is being caused by unexpected loading of JavaScript by the stripe plugin. And has told us to reach out to you guys to get it fixed.
This only happens when the new stripe checkout experience is active in the stripe plugin. Can I check you all tested it with the new checkout experience active? As this is what seems to hide the coupon field!
Quite frankly at a loss here as to how to proceed considering you guys keep sending us back to flatsome and flatsome keeps sending us back to you guys. Maybe it’s time for one of your team to talk to @jimapp directly? ??
Thanks,
Marc
- This reply was modified 4 months, 3 weeks ago by Medran.
Hey, @medran!
Can I check you all tested it with the new checkout experience active?
Of course! Here’s a video of me testing on my site with three different themes: https://www.loom.com/share/56b165dac8934c81bf9d9093f069e669?sid=21a6f629-6a74-4960-8ca1-f3462af7fa00
Quite frankly at a loss here as to how to proceed considering you guys keep sending us back to flatsome and flatsome keeps sending us back to you guys.
I understand this is a frustrating situation. But since we are not able to replicate this with other themes, and the issue only happens with Flatsome, then they need to check what is going on on their side that is triggering this issue.
Have you contacted their support (linked here)?
Have a wonderful day!
hi @carolm29
to be quite honest what is so frustrating is that I’ve now not once, twice but three times pointed out that one of their developers actually commented on this exact post after all of us flagged the issue.
ive also highlighted to you that in this thread he has given you the exact details of what’s causing the issue and has said it has to be fixed by yourself not by them as it’s loading a Java script file that should not be loaded on the basket page but only on the checkout page.
please note this is a specific issue of the old woocom basket page not the new block one!
- You must be logged in to reply to this topic.