annieici

Hello, was there any solution or plugin conflict found relating to this? One of my client sites has just the lightbox plugin, it’s updated, and I’m seeing this error. I tried some updates and removed the cache, but nothing has helped yet.

I figured it out by making a sandbox/testing copy of the website and just turning off every plugin (except the WooCommerce/donation ones) until the error was gone.

A smaller size test would be using something like the Yoast Duplicate Post plugin to make a copy of the page, then turn off the Elementor editor for that duplicate page. Adjust that page until the donation form shows normally on the front end and test from there.

Hello,

I don’t know if leocertuche was able to discover/fix their bug, but I also recently encountered this error and it seemingly was not actually the cache. After testing plugin conflicts, I found that the Page Builder by SiteOrigins plugin was causing some type of conflict. I was able to avoid the error by turning off that page builder for the page I have the donations on.

If you have a page builder, I suggest making a duplicate of the page and removing the builder from that page specifically. It may be that something weird is messing with the checkout data.

Hope that helps!

Hello Alberto,

To confirm, it sounds like this plugin will no longer work with some payment methods, correct? Such as Authorize.net?

Thank you

This happened to me as well! I started a thread previously for a different issue only to find this issue as well. They resolved my previous issue very quickly, so hopefully it’s another relatively quick fix.

Follow up again: I believe this plugin may be interfering with the Authorize.net payment setup. I was notified that it was not working and looked into it, and when testing on a test domain, removing this plugin allowed the Authorize payment info to appear in checkout.

Thank you so much.

A follow-up question: Will this interfere with the actual renewal when it’s time for them to renew? For example, in a couple months will the system think it already renewed the subscriber and so will not submit the renewal?

Hello Alberto,

It appears that the orders have been created but not paid for me. I am using Authorize.net for my client, so there is no auto-pay at the moment. The orders are all listed On-Hold.

And thank you for the quick plugin update! I’m assuming it’s safe to update?

Thank you

It’s good to know my client isn’t the only one affected. We’re telling the subscribers to disregard any renewal invoices for now. I’m just glad we didn’t have the system set up to take the payment automatically, just invoice them.

Fantastic! Thank you so much.

-Annie