Plugin Scan returned Modified plugin files for readme.txt

  • Resolved Garrett Hyder

    (@garrett-eclipse)


    10 years, 8 months ago

    Hello,

    This isn’t a major issue but wanted to raise it to support so they’re aware. With the plugin scanning enabled I find alot of this warning and it leads me to believe it’s scanning against the wrong version of the WordPress version for the plugin.

    It states the readme.txt file is modified although I’ve made no changes to the plugin;
    Modified plugin file: wp-content/plugins/wp-property/readme.txt
    See screenshot, seems the readme in my install is correct but the version it’s matching against is a higher level…
    http://i.imgur.com/RQpWFyu.png

    As the screenshot shows the ‘Original version’ is actually a higher level than the installed…

    Do developers often update the readme available on a version after it’s release, this could possibly explain it. Just wanting to be sure there’s not a deeper issue where maybe it’s scanning against a later version of the plugin than that which is installed.

    Thanks

    https://wordpress.org/plugins/wordfence/

Viewing 2 replies - 1 through 2 (of 2 total)
  • WFSupport

    (@wfsupport)

    10 years, 8 months ago

    They do, though it is not very smart. It saves them the step of having to do a proper release but anything they change won’t help people whop have already installed it since they won’t get a notice about needing an upgrade. It makes verifying source code very hard since no version change is officially made.

    tim

    Thread Starter Garrett Hyder

    (@garrett-eclipse)

    10 years, 8 months ago

    Thanks Tim,

    I figured it might be something along those lines. Very frustrating but glad to know I can safely ignore.

    Cheers

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

The topic ‘Plugin Scan returned Modified plugin files for readme.txt’ is closed to new replies.