• Resolved cdgweb

    (@cdgweb)


    Wordfence is shooting me a notification from every single site I manage telling me “wp-content/plugins/all-in-one-seo-pack/all_in_one_seo_pack.php” on my installation doesn’t match the one currently in the repository.

    Did you make a change and not update the version number? (all sites are running the latest version, updated a few days ago)

    https://www.ads-software.com/plugins/all-in-one-seo-pack/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Steve M

    (@wpsmort)

    The current version is v2.2.7.6.2 which you can see here – https://www.ads-software.com/plugins/all-in-one-seo-pack/

    I’d say this is a Wordfence issue.

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    Hi cdgweb,

    What is WordFence checking it against?

    The All in One SEO Pack installed on your site is from the latest tag (2.2.7.6.2). If it’s checking against trunk, which is the development version, it will show differences as we’ve made various updates to trunk that haven’t been pushed to a new version yet.

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    Does it give any more specifics about the difference? This could also be due to a recent hotfix we did which will be in the next version.

    Either way, I’d say 99.99% chance there is no actual problem, other than working out false positives. I’ve emailed Wordfence about it.

    Thread Starter cdgweb

    (@cdgweb)

    Wordfence is comparing the file on the server with the file on the repository.

    This file belongs to plugin "All In One SEO Pack" version "2.2.7.6.2" and has been modified from the file that is distributed by www.ads-software.com for this version. Please use the link to see how the file has changed. If you have modified this file yourself, you can safely ignore this warning. If you see a lot of changed files in a plugin that have been made by the author, then try uninstalling and reinstalling the plugin to force an upgrade. Doing this is a workaround for plugin authors who don't manage their code correctly. [See our FAQ on www.wordfence.com for more info]

    Specific file differences as seen here: https://www.evernote.com/l/ACF8twBpuDRIH7_k1JFGkgksUVFNzQ8SWs8

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    Ok thank you for the additional info. That’s for the recent hotfix I pushed recently.

    You can either safely ignore the message or else uninstall and reinstall the plugin (or wait for the next version).

    BTW, regarding that message from WordFence, it’s not that the code is incorrectly managed, it’s rare circumstances necessitated a change being made that didn’t warrant a new release. It’s only an issue if you’re running something like WordFence which checks for that sort of thing. ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘"Modified plugin file"’ is closed to new replies.