Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter kdr22

    (@kdr22)

    Thread Starter kdr22

    (@kdr22)

    Wordfence makes the following note regarding scanning core files;

    Scan core files against repository version for changes
    This scan checks if your core files match what exists in the official WordPress core repository.

    If your files have changed then it’s likely that either you have modified them yourself, which is highly unusual and not recommended, or your WordPress installation has been infected by malware which has modified your core files.

    If changes have occurred, Wordfence gives you the opportunity to see what those changes are being doing a “diff” which is short for “differences”. We will show you a syntactically highlighted display of the differences between your core files and the official WordPress core files that are distributed.

    Note that this automatically detects which version of WordPress you are running and will compare your core files to the appropriate version. This version detection and comparison with a the correct version in the repository also applies to theme and plugins below.

    So how does one access the DIFF? I didn’t see any such prompt.

    Same issue here, though only one file. This started with the 6.1.11 update and still persists after the 6.1.12 update.

    Unknown file in WordPress core: wp-includes/theme-compat/comments-popup.php

    Filename: wp-includes/theme-compat/comments-popup.php
    File type: Core
    Issue first detected: 18 mins ago.
    Severity: Warning
    Status New

    I attempted to delete the file from Wordfence as well as manually and receive the following error message;

    An error occurred
    Could not delete file wp-includes/theme-compat/comments-popup.php. The error was: unlink(/home/content/p3pnexwpnas01_data02/82/2972482/html/wp-includes/theme-compat/comments-popup.php): Permission denied

    My site is hosted w/ GoDaddy using their “managed” WordPress hosting.

    Thread Starter kdr22

    (@kdr22)

    Nevermind, I found the problem… DOOOH!

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