zackeryfretty

Thank you!

Both for fixing it so quickly and for making this handy plugin, very useful when things are otherwise undocumented. ??

It’s already fixed in 1.6.30.

Just to follow up on this I was able to get it resolved with the help of Beaver Builder’s support.

Here’s the snippet that fixed it, I hope it helps someone in the future!:

$actions = array(
  'fl_builder_cache_cleared',
  'fl_builder_after_save_layout',
  'fl_builder_after_save_user_template',
);

foreach( $actions as $action ) {
  add_action( $action, function() {
    do_action( 'swcfpc_purge_cache' );
  });
}

Yes! We do own the plugin and are doing so, just responded here because it’s what came up while searching the error. ??

We are also (and still) seeing this issue with Custom Start Date for WooCommerce Subscriptions while using the latest version.

• This reply was modified 9 months, 2 weeks ago by zackeryfretty.

Thanks for the reply, Peter!

I had posted here because I wanted to see if any other users might have had similar issues, but I can totally do a support ticket if the issue persists.

For now I’ve whitelisted the IPs for JetPack from 2FA for XML-RPC and also turned “Learning Mode” back on for 24 hours.

Hope that’ll do the trick! ??

One of our sites has the same issue with that file appearing in WordFence.

Interestingly enough it is hosted at SiteGround as well and also using SG Optimizer. I know they’ve denied it being the platform a few times but it’s an interesting coincidence. ??

Happy to help!

Hey @anakdelgado,

Did you ever find a resolution to this with SiteGround? We’ve got a site that’s recently started having these issues — and I too suspect it’s hosting related. ??

Thanks for your help, Pepe!

I wasn’t referring to that thread specifically – but yes – ultimately that is the same filter that I am attempting to use and having issues with.

I’m able to recreate the issue even when I throttle things back to only WooCommerce active on Twenty Twenty.

Here’s my system report — I did censor out our URL and a few internal deactivated plugins for privacy reasons, that’ll expire in 2 weeks.

The need is pretty straight forward, we do NOT want people to be automatically logged into the account created at checkout. That’s all!

Thanks again.

• This reply was modified 1 year, 9 months ago by zackeryfretty.

Sorry to skip over a few of your questions — but — I think I was able to dig a little deeper and narrow down the issue more.

It seems like issue happens *specifically* when Pods Framework, ConvertKit, and Classic Editor are all installed. If I deactivate Pods *or* ConvertKit everything works completely fine.

The only optimization plugin installed is WP Rocket – but – deactivating it doesn’t seem to make a difference, best I can narrow it down is those 3.

We’re using the latest version of WordPress, ConvertKit, and Pods.

Thank you for your continued support. ??

• This reply was modified 2 years, 1 month ago by zackeryfretty. Reason: Typo

I’m seeing the same issue – and – as @nathaningram said “5.5.21” is the first version that didn’t cause the same error when adding new posts.

The v2.2.1 that was just pushed out resolves this issue, thanks!

Can confirm. ??

On second look, seems like this is related to jQuery Migrate being removed recently, seems this plugin hasn’t been updated for quite some time.

Are you still planning on updating this?