fitwd

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 year, 4 months ago by fitwd.

@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?

@niklasinpsyde Thanks for the reply. I did have a PayPal payment (non-credit card) go through with no issues about 7 hours ago.

Following that, I had two credit card payments take place. They seem to have worked. However, for each order marked “processing” there appears a duplicate order (in woocommerce) marked “pending payment”. These entries have exactly the same timestamp.

Interesting about the 3D-Secure integration problem. I imagine having this process inserted into the pay flow could create unexpected issues both for the processor and the end user. Are you saying 3D secure might be why some of these issues are cropping up? How big of an issue has this become? I googled around regarding 3D secure and found information about when and where 3D secure implementation is required to be somewhat confusing.

There is a 3D secure section in the plugin settings under card processing but there’s no option to turn it on or off. Is 3DS mandatory at this time for all transactions?

Thanks for your time,
Tim

Edit: We are only using guest checkout at this time. So, no user registration/login is involved during checkout.

• This reply was modified 4 years, 10 months ago by fitwd.

Same issue here. Using Porto theme. I can confirm it’s making the ajax call and getting a response, but nothing appears below the search field.

Funny thing is, it works fine when in “theme options” mode but not outside of that.

Noticed that it is now working at http://yourmom.com.ar

How were you able to resolve the issue?

Thanks much,
Tim

• This reply was modified 5 years, 5 months ago by fitwd.