Adam Nowak

I am experiencing this issue as well. He does not mean all the backups are in the same folder in dropbox, he means that the backups are shown in the updraft plus interface after a restoration. Usually it lists the last few, now my existing backups section is showing 250 backups. How do you rescan so that the correct backups are associated. Rescan remote storage did nothing. I fear clicking the delete button.

Stealth’s solution worked just great to get rid of the error. Font awesome’s programming is smart enough to tell you as well. The booked plugin author obviously cant keep the plugin up to date nor get the spelling right. Fortawesome:

Warning right on the plugins page: “Great Scott! The active version of the Font Awesome plugin is being loaded by this plugin or theme: /var/www/wp-content/plugins/booked/vendor/fortawesome/wordpress-fontawesome/ since it’s the newest (ver. 4.2.0). We recommend you update the plugin above to the latest version. In the meantime, we’ll use that newer version for editing your Font Awesome settings so you’ll be sure to hit 88mph with those icons.”

The link in the plugin update message about this is a 404. I’m not updating yet until I’m confident this is squared away, what’s up with the 404?

I am having this issue as well, and the site is using Booked. Anyone find a fix? The site uses elementor, and the font awesome plugin is not installed.

I am still having this issue. I do maintenance for clients and after update to wp 5.8 none of these sites will load the settings page: /wp-admin/options-general.php?page=rlrsssl_really_simple_ssl

As I said, there are no errors and the wp debug log file was not created since it wasn’t throwing errors. I don’t have time this week to track this down, but next week I will be doing more investigating.

My reply via email didn’t post. There are no errors in any logs, the datacenters didn’t find any either. WP debug log was not created when the issue happens, so nothing there.

I did not roll it back. It seemed to be functioning after reinstall, just cant get to settings page.

That was sketchy since the ?page=rlrsssl_really_simple_ssl page is not working. Luckily I had a backup to restore to get the mixed content filter working again.

Reinstalling did not fix the issue. This is the third website I have updated that developed this issue.

I am experiencing the same issue. Toolbar went away.

That is the issue, trying to set it to be none. I think there will be a filter in future WP to set this. https://core.trac.www.ads-software.com/attachment/ticket/37000/pluggable.diff

I’m having similar issues in multisite. Trying to add the SameSite=none flag to cookie headers, did you find a solution.

No response in a week for me. Might want to just start a new thread on it. Pretty sure it is execution order of that sendNoCacheHeaders function

I am having this issue as well. I don’t think it is a whitespace issue. The all the lines in this function fire the warning. It is probably an execution order thing:

/**
* Sends no-cache headers.
*
* @since 151220 Enhancing no-cache headers.
*/
public function sendNoCacheHeaders()
{
header_remove(‘Last-Modified’);
header(‘Expires: Wed, 11 Jan 1984 05:00:00 GMT’);
header(‘Cache-Control: no-cache, must-revalidate, max-age=0’);
header(‘Pragma: no-cache’);
}

Before I do this, I am worried about the individual sites. There are a couple hundred. Will de-activating and re-activating reset the: Enable Rename Login Page Feature?

When we first took the network live, each individual site had to go to the brute force page and set the renamed login url. The last thing I want to do is break the network if this reverts to the default login. Any suggestions on that. I know the plugin was storing this data for site ID =1, but is it now creating tables for each site on the network? I just want to be sure I don’t loose all 200 sites renamed login page data.