stephen87

me too, back to 5.2.0. thanks for the info on what version works.

Agreed, its such an important plugin too.

Do you know which file they changed to fix it? Feeling a bit cheated that updating woocommerce caused this error a few days after my subscription expired to the plugins support.

I will renew during their next sale as I always do

SOLVED.

I just needed to add selector to the custom css option (elementor pro) to hide the H3 in the sidebar only.

selector .ez-toc-heading-level-3 {
    display: none;
}

Regular version, non premium. Thanks for the quick support.

This might help

The scheduled event, campaign_monitor_woocommerce_sync, is late to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.

p.s plugin is working fine for me after you updated it 6 months ago, just noticed this error with the new wordpress health check feature and thought i would add it here to help

You were 100% correct Steven.

Thanks for the quick response. Fantastic plugin btw

Thanks for replying.

It broke again, surprise surprise. I submitted a support ticket but think I will start looking for an alternative company

and here we are, a month later and its stopped working yet again.

Thank you, I will update our settings to a lower request limit.

The response code is 200, I wonder if this has something to do with cloudflare.

Chrome Developer Network Tab shows this for mysite.com/careers/7/

link: <https://www.mysite.com/wp-json/&gt;; rel=”https://api.w.org/&#8221;, <https://www.mysite.com/?p=7171&gt;; rel=shortlink
server: cloudflare
status: 200

https://www.mysite.com/?p=7171 is https://www.mysite.com/careers/

Hello, thanks for the quick reply! Perhaps I worded it wrong, sorry!

What I meant to say is hundreds of .css files were created for each page this bot hit.

I can see them in the Autoptimize Settings -> CriticalCSS Tab & at criticalcss.com/generate

Each hit added another job to the cron queue which caused my CPU to spike

Image – https://prnt.sc/q95obt

Just an update for those who have a similar issue. I know how annoying it is to google a problem only to find a SOLVED message but no actual fix.

After speaking with Woocommerce.com directly it turns out the latest update stopped virtual products from sending addresses to paypal.

You need to add some code to your functions.php

Since WooCommerce 3.7, there was a change included through which the address would not be sent to PayPal if the product is non-shippable. If you would like additional history about this change you can find this here: https://github.com/woocommerce/woocommerce/pull/23773

You can override this change and force WooCommerce to send address to PayPal even when the product is non-shippable using the function code here: https://gist.githubusercontent.com/madeincosmos/93a65a39a90e14c9c3076589d2ee1aac/raw/098391e578f3ce24796d2f946353cb253cf0008e/functions.php

You can add the code as it is in your theme’s functions.php file or using a plugin like Code Snippets.

Bump, any ideas guys?

Thanks for clearing this up, I totally misunderstood.

I assumed there was an issue with AO not passing on the cached version.

I tried to check google but the results for “?ao_noptirocket=1” are just peoples open queue logs haha

Thanks for replying and for creating such a great plugin.

Have a fantastic week

I copied over the default WP tables only to a new fresh wordpress install on my localmachine.

Im guessing im going to have to dig into wp_posts and remove anything thats not part of the new site.

(not looking forward to monday!)