Martin Bailey

Hi Mirza,

I appreciate you getting back to me on this, but I could not wait any longer for this business-critical fix. Yesterday I bought a different snippet plugin and manually migrated all of my snippets over. I have now deleted your plugin, so if it’s only me having problems, feel free to close this issue.

Regards,
Martin.

Hi Team,

It’s been almost a week since I reported this problem. I have customers waiting for a number of pages that I have to get published, but they rely on your plugin. Please let me know how long you expect to take to either fix this issue or let me know your thoughts.

Thank you.

Martin Bailey.

I’m getting this message too. I’m based in Japan, but my server is in the US, which I think should be where you are checking, so I don’t understand why this error is being displayed. Is it checking my physical location? And is Japan really not supported?

Update: I found that this URL was being blocked by my Content Security Policy. Adding this to the connect-src solved the problem for me.

https://cdn.ampproject.org

• This reply was modified 3 years, 4 months ago by Martin Bailey.
• This reply was modified 3 years, 4 months ago by Martin Bailey.

This is happening for me too. Very annoying.

There’s probably a database option that needs to be turned off, but I don’t see why your clients should be the ones to look into and provide solutions for this stuff. It happens way too often with WooCommerce.

Please provide details of how to turn this off in the database, and I’ll give that a try and let you know, but ideally, it should be fixed in a plugin update and one more click on the interface.

@enjoymmstudio I used phpMyAdmin which is part of my website’s admin console on the backend, not WordPress. I then just located the table and record that needed to be changed and updated it, and saved the record.

You’re very welcome @junkofdavid2. I’m pleased your issue is fixed too, regardless of how it got fixed. Maybe my issue was pure coincidence as well. It’s hard to tell in the complicated web we weave with WordPress and all of these plugins. ??

@junkofdavid2, are you seeing a database update notice from WooCoomerce? I was and fixed that and it fixed this issue with the LiteSpeed Cache plugin breaking Subscriptions too, so I thought I’d let you know.

——

I noticed that after a WooCommerce update I was constantly getting this notice in my WordPress admin console, with a Thanks button:

WooCommerce database update complete. Thank you for updating to the latest version!

I pressed the Thanks button many times but the notice always comes back. I don’t know how or why this is causing the problems with WooCommerce Subscriptions when the LiteSpeed Cache plugin is active, but I looked into how to fix the Notice not going away and found that in my database, in the xxx_wc_admin_notes table if I updated wc-update-db-reminder from unactioned to actioned and saved the record, the Notice stopped reappearing.

After doing that, I was able to turn the LiteSpeed Cache plugin back on, and the WooCommerce Subscriptions continued to work fine. I have no idea of the relationship, but this worked for me.

In case anyone looks at this, I noticed that after a WooCommerce update I was constantly getting this notice in my WordPress admin console, with a Thanks button:

WooCommerce database update complete. Thank you for updating to the latest version!

I pressed the Thanks button many times but the notice always comes back. I don’t know how or why this is causing the problems with WooCommerce Subscriptions when the LiteSpeed Cache plugin is active, but I looked into how to fix the Notice not going away and found that in my database, in the xxx_wc_admin_notes table if I updated wc-update-db-reminder from unactioned to actioned and saved the record, the Notice stopped reappearing.

After doing that, I was able to turn the LiteSpeed Cache plugin back on, and the WooCommerce Subscriptions continued to work fine. I have no idea of the relationship, but this worked for me.

Sure, I just joined as Martin Bailey.

I’ve just lost an entire day troubleshooting this same issue. The only way I can get WooCommerce subscriptions to work at the moment is to deactivate the WordPress Litespeed Cache plugin completely.

I’ve tried with both the WooCommerce StoreFront theme and Bridge from Qode, my usual theme. The problem happens with both.

• This reply was modified 4 years, 2 months ago by Martin Bailey.

OK, I figured it out. I’m using Max Mega Menu for my top menu, and until now I had to uncheck the Font Awesome 5 checkbox because enqueuing Font Awesome there caused a conflict. Just now though I tried checking that on, for the first time in probably three years, and the Font Awesome icons came back. I’m not sure what changed to cause this, but it’s working again now. We can call off the dogs.

I just figured out that if I change the human readable kit name to the alphanumeric code for my kit, I can access it without issues. Not sure if that is expected, or if a link is broken on the font awesome site.

Now I need to find out where to change that on my site.

This problem has just kept me up half the night and I’ve lost a number of sales. I started getting this error and it greys out all of my WooCommerce payment methods, not just Stripe.

stripe-payment-request.min.js?ver=4.2.3:1 Uncaught TypeError: Cannot read property ‘order_data’ of null
at Object.startPaymentRequest (stripe-payment-request.min.js?ver=4.2.3:1)
at Object.success (stripe-payment-request.min.js?ver=4.2.3:1)
at i (jquery.js?ver=1.12.4-wp:2)
at Object.fireWith [as resolveWith] (jquery.js?ver=1.12.4-wp:2)
at x (jquery.js?ver=1.12.4-wp:4)
at XMLHttpRequest.c (jquery.js?ver=1.12.4-wp:4)

I just deactivated all plugins except WooCommerce and the payment gateways worked again, and the error stopped. I gradually activated the plugins, and the error started again as soon as I activate NextGen Gallery and your Pro plugin. I did that testing on a staging site, but then went to my production site, and deactivated the two NextGen plugins, and my WooCommerce gateways came back to life. The error has stopped.

Now I have to either get a fix for this really quickly, or I need to replace all of my Portfolio galleries with another gallery system. This will take me at least another day, and I have deadlines today.

Regards,
Martin.

Hi qtwrk,

OK, I’ve just done that.

Regards,
Martin.

Hi Team,

So, things are gradually getting worse. I think I recall seeing a fix earlier this week referencing my user name, but A) the featured photo links are still gradually being changed to the cdn subdomain in the post meta table, and B) I just published this week’s post, and even after using Search Regex to change the cdn subdomain back to my sites URL, I’m now getting the og:image error permanently. See here: https://developers.facebook.com/tools/debug/sharing/?q=https%3A%2F%2Fmbp.ac%2F673

If I disable the CDN in the LiteSpeed Cache plugin, the og:image problems does not occur.

Regards,
Martin.