redrockbob

Last evening my site was updated to v2.0.3.
The issue has been resolved.

I had the same issue reported this afternoon.
Since I had received an email notice of the plugin update earlier today I suspected it might be the source of the issue.
Sure enough.
Much to my pleasant surprise, when I got back into the system I noticed that a plugin update was available and the comment associated with the update referenced the issue.
Well done!!!
Errors happen but its a pleasure to deal with a developer that is willing the admit the issue and provide a fix as quickly.
Great plugin & developer.
Thanks for what you do (for us).

@shinephp : Thank you for your response. Unless I can figure out how to remove all filters associated with active plugins, I will have to be content to have the logfile simply report version changes or additions/deletions to the list of all plugins.

@aitpro I wasn’t able to check. I cannot see the ownership in C-panel File browser and have not been able to get to the backend of the site (bluehost) because of a problem they were having which broke my SSH connection.

@aitpro You are correct. The error is gone in BPS 5.7.
I have been having accessing the back end of my site where I was planning on updating the ownership of the directory.
Thanks for the followup. It’s nice to see an ‘error free’ site.

Hi again Shea (@bungeshea)
I use phpmyadmin to query the options table before and after.

bob

@bungeshea Hi Shea. Thanks for the suggestion. I had high hopes. I tried attaching it to init and wp_loaded hooks and then ran each ‘run once’. Neither attempt was successful. Any additional suggestion would be appreciated. Thanks again for investigating this for me. bob

@helgatheviking Thanks for the update. WP-SUPER-CACHE allows me to selectively eliminate pages from the cache. Is there a ‘slug’ that could be used to exclude the menu?
Thanks again,
bob

yes, I am using wp-super-cache and caching only specific pages.

@carmpocalypse Yes. I did activate the Automatic Secret Keys updater. That very well could be the issue. I will try to verify it on a fresh local install.
Thanks very much for sharing your experience. I was beginning to think that I would have to exclude Sucuri from my planned (free) combination of plugins for the site I plan on deploying.

I traced the issue down to wp-config.php.
It was COMPLETELY EMPTY.
Can anyone explain why this may have happened?
Thanks in advance.

Bob