tmuka

I encountered this same error message on a site, and reverting the search-exclude plugin to v2.1.5 removed the error message.

I used the wp-cli to rollback.
wp plugin install search-exclude --version=2.1.5 --force

working for me too. thanks for the quick fix!

I just reverted after getting that same error too. Thanks

@robert681 I started encountering the same exact PHP error and the patch fixed it for me. Thanks!

Glad to see it looks like this issue is already fixed! I can confirm it only affected my user with the Creative Cloud subscription with the Adobe Acrobat Chrome plugin active. It didn’t affect Chrome’s built in pdf renderer.

weird. it seems at least 3 comments on this thread disappeared today… hopefully just a glitch in the support forums!

I had previously tried the “reset setting” which didn’t work, and after that, double checked the wsal_events-nav-type option didn’t exist, which didn’t help. The patched version fixed my critical error too. Thanks!

Thank you!

WordFence is alerting about this on our sites with the initial reported diff of the repo version vs the installed version with the same version tag. The only diff is “Tested up to: 5.8” on the installed versions, and “Tested up to 6.1” on the repo code version… Since the packaged release zip was never updated, even updating the plugin doesn’t update the “outdated” file.

It appears that the Elementor 3.7.2 update fixed my compatibility issue with Elements Plus 2.15!

Sure thing. There is no issue when creating a new page, only when editing an existing page.

Disabling “Elementor Pro” fixed the issue, as does disabling “Elements Plus!”

I’m not sure how to tell what widgets are from Elements Plus! The client said they mostly use the content scheduling features to make future changes automatically.

It got cut off above. I’m using PHP 8.0.16.

for now I added this code on line 37 to stop the fatal errors.
if(! is_numeric($sessions) || $sessions == 0 ){ return false; }

• This reply was modified 2 years, 8 months ago by tmuka.

Thanks, @chrisvrichardson, that fixed it! Working fine now (using PHP 8).

I Appreciate the quick fix!

thanks for the quick fix!

that error broke our sites too.