luminsol

Now I get it ??

FYI, with the latest update of the theme 1.1, it seems to have corrected itself. No checksum mismatch is reported.

I did not reinstall the theme, but enabled auto updating of it. Not sure if that made a difference or something else did…

I didn’t know that. Thanks for the tip! Do you want me to mark this as resolved or leave it open?

Issue resolved. Thanks!

Yes it is fixed. Thank you very much!

Unfortunately I had to disable CF7 on the site.

Are you testing with free version? It looks like those hidden fields are things that are supported in the PRO version only?

Is there anything else I can do to help troubleshoot?

So I’ve disabled all plugins except CF7 and CF Conditional Fields, but it’s still displaying the errors.

I even set the theme back to Twenty Twenty. Same problem.

Thanks for confirming. I’m not running any other CF7 extensions on the site. I will try disabling my plugins one by one to see if I can isolate the offending plugin.

@clipper87 it’s a warning which you’ll find in error.log. You shouldn’t see it on the front end.

Thanks, it would be nice for performance purposes to look at entries in wp_options and set those not required at runtime to be autoloaded to false, if you have time ??

This looks like it’s been fixed in LsCache v3.

Thanks for confirming @sebastianulbert.

I managed to track down the issue. If you have Auto Purge Rules For Publish/Update enabled, it will purge all those pages as well.

They should really document that this is a side effect of the litespeed_purge_post API. Looking at the documentation alone, you would think it would ONLY purge the single post ID.

Hope this helps someone in the future!

From the new documentation, it looks to be

do_action( 'litespeed_purge_post', 'post_id' );

From my testing, the only problem is it seems to purge the whole cache rather than the specified post ID.

It would be good if you can confirm it’s not just me.

Thanks @lkraav for double checking, I agree with you.

Thanks for the super quick response.

The first error I had was trying to upgrade the plugin, whilst also have a Plugin Update notification active.

It killed WordPress, so I restored from backup, then deactivated the plugin and updated it.

An error of type E_ERROR was caused in line 46 of the file [shortened]/wp-content/plugins/notification/inc/functions/resolver.php. Error message: Uncaught Error: Class 'BracketSpace\Notification\Core\Resolver' not found in [shortened]/wp-content/plugins/notification/inc/functions/resolver.php:46
Stack trace:
#0 [shortened]/wp-content/plugins/notification/class/Abstracts/Carrier.php(261): notification_resolve('Plugin Updated ...', Object(BracketSpace\Notification\Defaults\Trigger\Plugin\Updated))
#1 [shortened]/wp-content/plugins/notification/class/Abstracts/Carrier.php(228): BracketSpace\Notification\Abstracts\Carrier->resolve_value('Plugin Updated ...', Object(BracketSpace\Notification\Defaults\Trigger\Plugin\Updated))
#2 [shortened]/wp-content/plugins/notification/class/Abstracts/Trigger.php(423): BracketSpace\Notification\Abstracts\Carrier->resolve_fields(Object(BracketSpace\Notification\Defaults\Trigger\Plugin\Updated))
#3 [shortened]/wp-content/plugins/notification/class/Abstracts/Trigger.php(623): BracketSpace\Notification\Abstracts\Trigger->resolve_fields()

The other issue was due to the coding of my custom triggers and the dependency on your plugin (order of plugins loading issue). I had to change it to be called on the notification/element action as well as wrapping it inside the action because of:

Error message: Uncaught Error: Class 'BracketSpace\Notification\Abstracts\Trigger' not found in...