How to handle WordPress leftovers?

  • Resolved Marc Bijl

    (@newoceans)


    6 years, 11 months ago

    Scanning a brand new website, I get a bunch of warnings. It seems these are generated by leftovers of a WordPress 8 version, since the same issue occured here:

    https://www.ads-software.com/support/topic/worrying-flagged-issues/

    What is the best way to clean the WordPress core structure and files? Just deleting all the mentioned leftover files (and should I delete other files as well, may be)? Or ignore them and wait for a new WordPress version to clean these files? Something else; may be there’s a Wordfence option that handles these WP 4.8 to 4.9 update issues?

    This is my list of warnings:

    This email was sent from your website “FoodLab Limburg” by the Wordfence plugin.

    Wordfence found the following new issues on “FoodLab Limburg”.

    Alert generated at Thursday 14th of December 2017 at 02:31:12 PM

    Warnings:

    * Unknown file in WordPress core: wp-admin/css/press-this-editor-rtl.css

    * Unknown file in WordPress core: wp-admin/css/press-this-editor-rtl.min.css

    * Unknown file in WordPress core: wp-admin/css/press-this-editor.css

    * Unknown file in WordPress core: wp-admin/css/press-this-editor.min.css

    * Unknown file in WordPress core: wp-admin/css/press-this-rtl.css

    * Unknown file in WordPress core: wp-admin/css/press-this-rtl.min.css

    * Unknown file in WordPress core: wp-admin/css/press-this.css

    * Unknown file in WordPress core: wp-admin/css/press-this.min.css

    * Unknown file in WordPress core: wp-admin/includes/class-wp-press-this.php

    * Unknown file in WordPress core: wp-admin/js/bookmarklet.js

    * Unknown file in WordPress core: wp-admin/js/bookmarklet.min.js

    * Unknown file in WordPress core: wp-admin/js/press-this.js

    * Unknown file in WordPress core: wp-admin/js/press-this.min.js

    * Unknown file in WordPress core: wp-includes/js/mediaelement/background.png

    * Unknown file in WordPress core: wp-includes/js/mediaelement/bigplay.png

    * Unknown file in WordPress core: wp-includes/js/mediaelement/bigplay.svg

    * Unknown file in WordPress core: wp-includes/js/mediaelement/controls.png

    * Unknown file in WordPress core: wp-includes/js/mediaelement/controls.svg

    * Unknown file in WordPress core: wp-includes/js/mediaelement/flashmediaelement.swf

    * Unknown file in WordPress core: wp-includes/js/mediaelement/froogaloop.min.js

    * Unknown file in WordPress core: wp-includes/js/mediaelement/jumpforward.png

    * Unknown file in WordPress core: wp-includes/js/mediaelement/loading.gif

    * Unknown file in WordPress core: wp-includes/js/mediaelement/silverlightmediaelement.xap

    * Unknown file in WordPress core: wp-includes/js/mediaelement/skipback.png

    * Unknown file in WordPress core: wp-includes/js/plupload/plupload.flash.swf

    * Unknown file in WordPress core: wp-includes/js/plupload/plupload.full.min.js

    * Unknown file in WordPress core: wp-includes/js/plupload/plupload.silverlight.xap

    * Unknown file in WordPress core: wp-includes/js/swfupload/plugins/swfupload.cookies.js

    * Unknown file in WordPress core: wp-includes/js/swfupload/plugins/swfupload.queue.js

    * Unknown file in WordPress core: wp-includes/js/swfupload/plugins/swfupload.speed.js

    * Unknown file in WordPress core: wp-includes/js/swfupload/plugins/swfupload.swfobject.js

    * Unknown file in WordPress core: wp-includes/js/swfupload/swfupload.swf

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)

  • Hi,
    Re-installing WordPress via the Dashboard won’t clean these files, also waiting for the next update will be pointless because the same error will happen again, by default WordPress updates should remove these files automatically unless something wrong happened during the update (for example, broken file permissions, restricted rules set by your hosting provider) so I don’t think there is anything you can do now except deleting these files manually or check “Select for bulk delete” on each of these files in the scan result then click on “Bulk Operations” and choose “Bulk Delete Selected Files”.

    Thanks.

    Thread Starter Marc Bijl

    (@newoceans)

    Hi @wfalaa, thnx for the reply and explanation.

    Guess these files are leftovers, because I used an installation through the hosting provider; they have a kind of control panel where WordPress can be installed.

    Anyway: deleting these files is allright for me; however how do I know if these files once were core files, and are not core anymore, so I can delete them safely; or might these files from malware/virus/something like that? How to find out?

    Maybe try installing a fresh copy of wordpress into another folder and do a directory compare to your current site.

    Thread Starter Marc Bijl

    (@newoceans)

    Yeah, that might be a good one, thnx!

    Exactly, that’s a good advice if they are many files as I see in this thread, otherwise, you can check the latest WordPress files in the WordPress subversion repository.

    Thanks.

    Thread Starter Marc Bijl

    (@newoceans)

    Hi @wfalaa, thnx for the reply and link. What do I see exactly on the page you’re linking to: the files of the latest/current WordPress version?

    I’m not very familiar with digging through WordPress files…

    ??

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘How to handle WordPress leftovers?’ is closed to new replies.