Hello, it would be great if this plugin would be updated so that it works again.
Especially the support of the boxes at the checkout is necessary. Currently only the credit card payment method still works, all others no longer work.
For better assistance, can you provide screenshots showing the issue on your end? For screenshots, you may use https://snipboard.io – please follow the instructions on that page, then paste the URL in this thread.
Rest assured, I’ve tested the checkout block and can confirm that both the Card and Express Checkout options are functioning perfectly.
the problem is not with the credit card and express checkout, but with all other stripe payment options.
Youu can see from this example that giropay and ideal, for example, are not displayed. Only when I deactivate the blocks at the checkout are they displayed again
Hmm, checking this on my test site, it seems “iDEAL” and “giropay” are displaying as expected when using the checkout block:
I’d like to take a closer look at your sites current environment, as well as any errors being produced, please can you share the following:
System Status Report: you can find this via WooCommerce → Status. Select Get system report and then Download for Support. This will download a TXT file that has the contents of the SSR which you can then share with us here.
Fatal Error Log: Share a copy of any fatal error log found under WooCommerce → Status → Logs
Thank you for sending over the system status reports. However, we’re unable to access them as they require a password.
Please feel free to share it again via Mozilla Community Pastebin and share the link here. Remember, you can trim out any details you’d instead not share publicly, like the website URL.
I’ve checked your system status reports, and your current theme overrides the checkout and cart page template. I suspect your theme might not be fully compatible with the block, as you’re having this issue only with the block-based checkout. To fix this, would you mind temporarily switching your theme to Storefront to see if all the payment methods show up?
Additionally, from the error logs you’ve share, it seems there are two main issues.
The first one is related to an ArgumentCountError in the class-bulk-upgrader-skin.php file. This error usually occurs when a function expects a certain number of arguments but is given less. In this case, it seems that the sprintf function is expecting 3 arguments but is only receiving 2. It might be a plugin or theme that’s causing this issue. I recommend deactivating all plugins and switching to a default theme (like Storefront) to see if the issue persists.
The second error indicates a Call to an undefined function tinv_get_option() in the ti-woocommerce-wishlist.php file. This error typically happens when a plugin is deactivated or deleted, but something else (like your theme or another plugin) is still trying to access its functions. If you have recently uninstalled this plugin, please ensure all its files have been properly removed. If you’re still using the plugin, try reinstalling it.
Let us know how that goes. Looking forward to hearing from you!
Hello, before I started using Flatesome, I was using Storefront and had the same problem. I have also tested umpteen other themes, the same problem everywhere. In addition, the explanation is not logical, because other payment plugins have made an update for the support of blocks and since then everything works. PayPal Plugin also works. Bitcoin plugin works too. So why should the theme be to blame and only destroy certain plugins? Normal credit cards work just as well. Only the additional payment methods from Stripe do not work.
I have now deactivated blocks and everything works. It doesn’t look so good anymore, but it’s currently the only solution to the problem. Also because other plugins also have a problem with the blocks in the cart.
It seems you have decided to use the Checkout shortcode as a workaround, since the issue persists even with all plugins (except WooCommerce and WooCommerce Stripe Payment gateway) deactivated and the theme switched to Storefront, correct?
It may be helpful to check if this issue is present when using a different browser, it’s possible that a browser extension may be causing some sort of conflict here.
Also, if you’ve set up a staging site, you can try checking the browser console for any errors when in a conflict test environment. It may share some helpful details on what may be causing this particular issue, since we are unable to reproduce this on our end.
We’ll be here if you need any further help with this 🙂
