• I have updated about 40 sites this evening to WP 6.6. After update, performing a scan using Wordfence to compare files against those in the repository, all of the sites have the same 4 warnings:

    * Old WordPress core file not removed during update: wp-includes/blocks/block/editor-rtl.css

    * Old WordPress core file not removed during update: wp-includes/blocks/block/editor-rtl.min.css

    * Old WordPress core file not removed during update: wp-includes/blocks/block/editor.css

    * Old WordPress core file not removed during update: wp-includes/blocks/block/editor.min.css

    This is showing on 40 sites across 3 different hosts. Is this an issue with the WordPress update or is it a false positive by Wordfence?

    The topic has also been posted on the Wordfence support forum: https://www.ads-software.com/support/topic/old-wordpress-core-file-not-removed-during-update-7/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator Dion Hulse

    (@dd32)

    Meta Developer

    Hi,

    This indeed a “problem” but not a cause for concern.

    WordPress 6.6 did not properly remove these old WP 6.5 files during upgrade, and WordFence has decided to throw an alert about this.

    It’s not a problem for your site, and when 6.6.1 is released, these files will automatically be cleaned up.

    I’ve filed a core issue to ensure this is resolved as part of 6.6.1.

    Hi, should we manually delete this files or it would be perjudicial? thanks!

    HI.. I’ve updated only one site running Wordfence to WP6.6 and I’ve manually removed the files from Wordfence.. Is this the right way..?

    From the shell you could do this:

    Navigated to the site that had the issue:

    cd /var/www/yourwebsite.com/public_html/wp-includes/blocks/block/

    From there just enter in the command below and all files that needed to be removed will be removed:

    rm -rf editor.css editor.min.css editor-rtl.css editor-rtl .min.css

    From Wordfence dashboard:

    Just click on the file and there should be a DELETE FILE button just press it.

    I work in my shell so I do the shell route to make sure they are really deleted.

    Regards.

    TSX

    • This reply was modified 4 months, 1 week ago by techspecx.
Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.