V 2.0 is BROKEN for Elementor

It’s very short-sighted of Clover to release a plugin that isn’t compatible with the largest page builder plugin in the WordPress universe – Elementor.

It’s unconscionable that you force updates on users and disable the old plugin.

I just restored to the previous version 1.0.12 today, and it is no longer working (but it worked yesterday, prior to the last 2.0 auto push).

Hi Invision-Studios

Thank you for reaching out. Sorry to hear you’re having these issues. WooCommerce has made Block Checkout the native experience and our priority is to maintain compatibility with WooCommerce. Given the circumstances, we recommend reaching out to the support team for the Elementor plugin, as they will be better positioned to assist with any compatibility concerns or conflicts specific to their product. If there’s anything further we can do to assist, please feel free to let us know.

• This reply was modified 1 month, 3 weeks ago by Clover eCommerce.
• This reply was modified 1 month, 3 weeks ago by Clover eCommerce.

Really? I’ve got multiple websites running using various page editors (WPBakery, Elementor, SiteOrigin) other than Blocks and checkouts are all working fine under woopayments/stripe and/or paypal. I think Clover POS is good stuff but this plugin… wow.

Changing the checkout and cart pages to the Gutenberg editor as per your instructions has not resolved the issue. There’s no payment options showing up. Any other ideas?

@fitwd Somehow I got Clover Payments 2.0 to work with Elementor. All of our sites run on Elementor Pro. We had disabled Gutenberg with a plugin because it’s such a pain. I had to disable that plugin, then re-authenticate Clover; now it’s working fine. Of course the layout changes slightly.

NOTE that just the grey boxes for card info, etc would show up on the checkout page, and not be selectable prior to making this change.

I’m still upset that Clover would push the plugin update automatically and break our websites. At the very least, they could have added a warning that the old plugin was about to be disabled.

@invision-studios Thank you for the additional info. Had been running “Classic Editor” to effectively disable the block editor. This particular site is using SiteOrigin Page Builder. The only thing on the page is the shortcode, “[woocommerce_checkout]”. Nonetheless, I disabled the plugin, switched the page over to the block editor, re-pasted the shortcode in and saved it. Not sure what you meant by “re-authenticate Clover”. So, I deleted and reinstalled the Clover plugin. Then I reentered the API info and switched it back on. Unfortunately everything’s still the same.

Interesting that you at least saw the payment box (even though it was greyed out). I’m not seeing any payment box – before or after these changes. I’ve got debugging on and am checking the log files without result. On checkout, having not inputted any payment info, the clover log shows, “WARNING Transaction could not be processed: Clover Token does not exist.”

Thanks again for the reply.

Rant Portion for @cloverecommerce
At this point I’m going to advise my client to switch to Stripe, give this plugin a one star rating and move on. I almost never leave a negative review for a plugin. Whereas many plugins are essentially free and are supported by the hard work developers, if I don’t like something I just try something else. I’m sure you guys work hard (I’m not totally unsympathetic here) but the Clover plugin is not free. They’ve been taking a bite out of every sale as a payment processor. Now they’ve left a lot people hanging with this who are losing money and time. Depending on how much they have of either this could seriously affect their businesses. It would be a no-brainer for Clover to assume that plenty of folks are using something other than blocks (just check the plugin rating for Gutenberg) and to make sure this thing worked in those cases. To release this with no warning and follow up with, “Well, you need to switch to blocks for this to work because that’s the standard now.” just isn’t fair. And don’t pass the buck to woocommerce. Like I said, all my other ecommerce sites are working fine. Native experience?

I asked ChatGPT to give me stats on page builders. Elementor is apparently used almost twice as much as Gutenberg, and as ChatGPT says, LEADS THE MARKET.

As of June 2024, the market share of major WordPress page builders is as follows:

• Elementor: 8.83%
• WordPress Block Editor (Gutenberg): 4.94%
• WPBakery: 3.66%
• Divi: 2.16%
• Beaver Builder: 0.41%
• WordPress Site Editor: 0.38%
• SiteOrigin Page Builder: 0.31%
• Oxygen: 0.15%
• Themify Builder: 0.08%
• Thrive Architect: 0.07%

These figures represent the proportion of all websites using each page builder.

It’s noteworthy that Elementor leads the market, with a significant user base.

@fitwd I did exactly what you did – disable the Classic Editor plugin (to enable Gutenberg). By re-authenticate I mean regenerating a new API code on the Clover site. I tried to convince the client to switch back to Stripe but he wants to collect all sales into a single merchant account. He uses Clover for his brick and mortar business.

Sounds like Clover just didn’t do any research before they decided to “upgrade.” Still, the biggest sin, is forcing the auto-update on everyone.

I’m facing the same problem with my Elementor site: https://www.fightingcolors.com
Clover’s advice was to: https://www.ads-software.com/plugins/clover-payments-for-woocommerce/#installation

“Transform into blocks”
I don’t see such a button or link. Where may I find it.

Will that break my Elementor page?

I did get it working. @invision-studios Thanks again. On the positive side I must admit, the new payment form really does look a lot nicer. I felt the old one, while serviceable, did not inspire much consumer confidence. So, @cloverecommerce nice job on that score. I appreciate it.

@perkinz Click the settings icon in the lower left corner of the Elementor sidebar and go to page options. There should be an option there to switch to blocks. See: https://docs.liquid-themes.com/article/570-hub-elementor-how-to-enable-page-blocks for a visual.

Remember to use the actual “Checkout Block” and not the [woocommerce-checkout] shortcode.

2025-01-13 – version 2.1.0

• Added – Support for shortcode (classic) Checkout

@cloverecommerce You guys are awesome. Thank you!

• This reply was modified 1 month, 2 weeks ago by fitwd.

Woocommerce Version 2.1 support for classic  and block checkout pages  
We are excited to announce the release of version 2.1 of the Clover Plugin for WooCommerce, which resolves the recent issue related to the classic checkout that some merchants have encountered.

What’s New?

• The new version includes support for the classic checkout option.
• Bock-based checkout page design will function as it typically does.
• Merchants and developers can now toggle between classic and block-based designs based on their e-commerce store needs.

Action Required:
The plugin will automatically install if Auto-updates are enabled. Otherwise, you can install the latest version, 2.1, by going to your WordPress dashboard and then clicking on Plugins -> Install Plugin -> Update Clover Payments for WooCommerce.

Thank you for your continued support. We look forward to hearing from you.

Thanks for making this update. Greatly appreciated.

Hi @invision-studios and @fitwd – like @perkinz, I also do not see the transform to block option for the checkout widget in page settings. I am using a custom theme based off of the elementor hello theme. I recently rebuilt the site where the clover payment plugin worked most of the time, with the customify theme, but now that the site is built with elementor, not so much. The checkout page produces a ‘critical error’ at the top whenever someone tries to process a payment. I tested after deactivating most themes and it still happens.

I am trying to create the checkout page with the checkout widget and convert it to blocks, but I don’t seem to have that option in the elementor page settings, as you described earlier. I am also looking for a plugin to do this. @invision-studios you mentioned ‘additional plugins’ at the top.

I’d like to revert back to 1.0.12 just to get the thing working again, although I generally do not like to do that. Where can I find that version to revert back to? Thanks for your help.