Jason Ryan

@wp_media

Can you explain the logic with removing this option – which was merely a checkbox – and why it is not being added? The current admin bar link is completely useless and unnecessary and just adds clutter.

This is crazy to me.

@wp_media

Are there plans to bring this back? To have to go through 100+ website to add this code is not feasible.

Thanks

@themefic

Thanks for letting us know, we have hidden it already on a couple applications with CSS, but also know that for someone like me at a company that hosts and maintains over 200 client websites, they generally wouldn’t opt for a “pro” license unless it was absolutely needed or recommended by us, in which case we just hide all notices on the dashboard from 3rd party plugins.

Thank you @abuzon and @generosus for the kind words, it is greatly appreciated!

@perfectweb –

Please read the post linked below as well because what I offered was not related the root cause of the issue, it just happened to “coincidentally” fix it.

You can read the post here for the explanation of what happened:

https://www.ads-software.com/support/topic/ouch-unknown-file-in-wordpress-core-wp-v6-7/#post-18133230

@mmaunder –

Thank you for the explanation, however, with everyone being hit with emails about 2500+ files being marked as “High Severity” it is a serious concern – especially for us as we host and maintain over 200 client websites at the moment. Trying to determine who the culprit is and finding a resolution for this issue was priority.

“Once we discovered the issue we ran the process to completion manually which fixed the issue this time around.”

When was this discovered on your end? Because I seen posts in this Support Channel as along as 15-18 hours ago as of 7am EST this morning. Someone should’ve posted here as soon as it was discovered to avoid any tpye of “misinformation” as you called it. At the point when we discovered the issue this morning, a lot of time as passed with radio silence on your end.

“Actually what you’ve done is posted an incorrect description of the problem, and a fix that does not work because it’s completely unrelated to the issue. As I said, you think it worked because a coincidence occurred. And we now need to go in and correct any misunderstandings created around the frequency of firewall rules being deployed, what caused this issue, how to fix it (you don’t need to because we did on the back-end) and answer any questions around this that come up.”

It was something that worked and just happened to resolve the problem at the moment that helped to ease everyone’s mind and allow them to carry on about their day, including us, coincidence or not.

“This stuff gets indexed by the search engines, other users visit these posts, and then it significantly increases our support load as we have to correct the misunderstanding you’ve created. Jason calling you out in particular.”

Sure does, so that way the next time something similar pops up and they reach these posts, it is something they can rule out and move on to looking for the next resolution rather than wasting time with what “coincidently” worked here.

As far as this:

“Also the comment of “Wordfence changed this a bit ago where the rules are only updated once every 30 days” is wrong. We didn’t. Not even sure why you’d think that or post it.”

https://cln.sh/TZJxFSGLNNfG1DF4zJqV

Then maybe clarify your wording a little better, something has changed at some point because there was a time not so long ago where we weren’t being prompted with this everywhere. Happened around the same time where we’re linked off-site to obtain a Free license.

@generosus –

Well, if they don’t mind this support channel blowing up with every major and minor release, then that’s on them. I was kind enough to post a fix and post it to every support thread across www.ads-software.com to help others before they go and delete core files mistakenly.

An issue of this magnitude should not be taken lightly by the Wordfence team, hopefully some type of resolution is put into place, otherwise will have to look for an alternative. We have several Premium licenses and never had a real issue with this plugin up until now. We’ll see!

@generosus –

Agreed, the Wordfence team should at least very minimum put something in place in force a manual refresh of rules to account for Core updates to avoid this in the future, or just revert it back to the way it was previous to the 30 day check.

This caused such a panic on our end since we host and maintain over 200 client websites currently – luckily I was able to put 2 & 2 together when someone on another board mentioned that WF possibly hadn’t updated their file list for 6.7. Checked the Rules and reran another scan and voila!

Hello all –

Ok, so I have found that if you are using the Free version of Wordfence, the “Rules” are only updated every 30 days – which means that this is completely out of sync with the release of WP 6.7.

If you go to Wordfence -> All Options -> Advanced Firewall Options -> Manually Refresh Rules and then run a new Scan, this resolves the issue (tested one site thus far and seemed to do the trick).

Wordfence changed this a bit ago where the rules are only updated once every 30 days – not sure this was a great idea on Wordfence’s part.

Hello all –

I have found that if you are using the Free version of Wordfence, the “Rules” are only updated every 30 days – which means that this is completely out of sync with the release of WP 6.7.

If you go to Wordfence -> All Options -> Advanced Firewall Options -> Manually Refresh Rules and then run a new Scan, this resolves the issue (tested one site thus far and seemed to do the trick).

Wordfence changed this a bit ago where the rules are only updated once every 30 days – not sure this was a great idea on Wordfence’s part.

Hello all –

Ok, so I have found that if you are using the Free version of Wordfence, the “Rules” are only updated every 30 days – which means that this is completely out of sync with the release of WP 6.7.

If you go to Wordfence -> All Options -> Advanced Firewall Options -> Manually Refresh Rules and then run a new Scan, this resolves the issue (tested one site thus far and seemed to do the trick).

Wordfence changed this a bit ago where the rules are only updated once every 30 days – not sure this was a great idea on Wordfence’s part.

Hello @bunnycake –

The issue is that if you are using the Free version of Wordfence, the “Rules” are only updated every 30 days – which means that this is completely out of sync with the release of WP 6.7. DO NOT DELETE THESE FILES – they are actual WordPress Core files.

If you go to Wordfence -> All Options -> Advanced Firewall Options -> Manually Refresh Rules and then run a new Scan, this resolves the issue (tested one site thus far and seemed to do the trick).

Wordfence changed this a bit ago where the rules are only updated once every 30 days – not sure this was a great idea on Wordfence’s part.

@abuzon –

This is due to a caching plugin, our environment is using Redis Cache – which we had to manually FTP into the site and rename the object-cache.php file to disable it to regain access.

With Siteground’s own caching mechanism, you can probably just disable that in the backend to regain access again.

Hello all –

Ok, so I have found that if you are using the Free version of Wordfence, the “Rules” are only updated every 30 days – which means that this is completely out of sync with the release of WP 6.7.

If you go to Wordfence -> All Options -> Advanced Firewall Options -> Manually Refresh Rules and then run a new Scan, this resolves the issue (tested one site thus far and seemed to do the trick).

Wordfence changed this a bit ago where the rules are only updated once every 30 days – not sure this was a great idea on Wordfence’s part.

Hello all –

Ok, so I have found that if you are using the Free version of Wordfence, the “Rules” are only updated every 30 days – which means that this is completely out of sync with the release of WP 6.7.

If you go to Wordfence -> All Options -> Advanced Firewall Options -> Manually Refresh Rules and then run a new Scan, this resolves the issue (tested one site thus far and seemed to do the trick).

Wordfence changed this a bit ago where the rules are only updated once every 30 days – not sure this was a great idea on Wordfence’s part.