PHP Warning

Hi:

Are you running any 5.x components at all? Maybe old plugins or themes or custom code?

Also, since that line has to do with rewrites, maybe go to the WordPress permalinks page and just save the permalinks again (that’s a long shot but its a few seconds to try).

Thanks.

PS: I assume you’re running SP 6.5?

Thanks for the very quick reply. I’ve no custom code, but I did have old plugins and themes (although none of the plugins were active). However, I was very careful to follow the upgrade steps.

I was running version 6.4 because I couldn’t upgrade to 6.5 (see below).

Unfortunately, the problem prevents me from logging into the WP admin, so it’s not easy to test the issue. (I can log in if I rename the simplepress folder and therefore disable the plugin.) With SimplePress activated I did try renaming the sp-resources folder because all the themes etc. in there seemed very old, but that didn’t help.

After deactivating SimplePress I was then able to update it. Reactivating 6.5 did allow me into the admin, though. (Perhaps because I already had a log-on cookie?)

I was then able to update the SP plugins, although I had significant difficulty in doing so as I frequently got the message that the plugin was already at the latest version. I was doing them one at a time to see which might be causing the problem. I discovered that after updating one plugin from update-core.php I had to visit the SimplePress plugins page before I could update another. I then end I gave up doing them one at a time and just did them all together.

However, none of this helped. Nor did visiting the permalinks settings page.

It sounds like you’ve done a decent amount of troubleshooting already so it just leaves us with the more aggressive troubleshooting steps.

Lets see if you can get the base plugin to not throw the error without any themes or plugins. Can you disable all the Simple:Press plugins and switch the simple:press theme to either barebones or modern 2020?

Then, if you still continue to encounter the issue, you’ll need to temporarily disable the wp plugins and switch the wp theme to a basic one like 2019 or 2020.

After doing all that, does the error still show up?

Thanks.

PS: It might be easier to have your host copy the site to a staging site and then do the troubleshooting there – this way you don’t have to turn things back and you can narrow down the problem before applying to your live site.

My apologies. The first steps didn’t look like they had worked because of some super-aggressive caching from my webhost. I’ve cleared that, and the error seems to have gone.

Ah, that’s great. Thanks for updating the thread – its much appreciated!