1797 issues…

  • Resolved Pat

    (@patrickhaond)


    1 year ago

    Hi there.

    I am having big trouble with my website and after severl backups test, now when I use scan function of Wordfence I get 1779 results.

    A lot of files problem in wp-admin or wp-includes like that.

    WordPress core file modified: wp-includes/rest-api/endpoints/class-wp-rest-widgets-controller.php
    WordPress core file modified: wp-includes/js/underscore.min.js
    WordPress core file modified: wp-includes/js/utils.min.js

    or

    WordPress core file modified: wp-admin/css/themes-rtl.css

    * WordPress core file modified: wp-admin/css/themes-rtl.min.css

    * WordPress core file modified: wp-admin/css/themes.css

    * WordPress core file modified: wp-admin/css/themes.min.css

    What should I do ? Delete all wp-includes files and folders and use the wordpress files from installation pack ?

    Thanks for any help.

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @patrickhaond, thanks for the detailed message.

    Have you run a second scan manually since these results? I ask because this looks like something that may come up in some cases immediately after a WordPress update. As you’ve restored a backup you could be seeing something similar that will not be alerted with another scan.

    If you have, and the results above still show up, drop us a diagnostic report to wftest @ wordfence . com directly using the link at the top of the Wordfence > Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    I should be able to see the scan results there to better find out what might be happening.

    NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

    Thanks,
    Peter.

    Thread Starter Pat

    (@patrickhaond)

    Thank you @wfpeter for your answer!
    Finally I made a full restore and I think I found out the initial problem.
    When I updated WordPress there was a serious conflict with Polylang, which was not up to date either.
    So I first update Polylang and then WordPress and now everything seems ok!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘1797 issues…’ is closed to new replies.
  • In: Plugins
  • 2 replies
  • 2 participants
  • Last reply from: Pat
  • Last activity: 1 year ago
  • Status: resolved