Modified files

  • Resolved syzygist

    (@syzygist)


    3 months, 3 weeks ago

    Next time you decide to change files in the repo version, do it properly as an updated version. I did not appreciate having to review TEN! files flagged by Wordfence as modified for malicious code because you decided to change the wording on your promotional links and couldn’t be bothered to do it right. Not cool.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Ketan Patel

    (@patelketan)

    Hello,

    Sorry for the inconvenience, I understand your point…

    Thread Starter syzygist

    (@syzygist)

    I’m glad to hear it. When will the correctly updated version be posted?

    Thread Starter syzygist

    (@syzygist)

    This is NOT resolved!

    Plugin Contributor Ketan Patel

    (@patelketan)

    Hello,

    Can you please explain more details about your issue because at which point you are talking to me…

    Thanks,

    Thread Starter syzygist

    (@syzygist)

    Wordfence, a very popular WordPress security plugin with 5+million installations, has flagged 10 files from your plugin as having been changed from the version of those files in the WordPress repository. Flagging website plugin files that don’t match the version in the WordPress repository is meant to alert users that site files have been changed by malware or hackers, but can also be triggered when plugin authors make change to the plugin files in the WordPress repository without releasing them as a new version. This creates a lot of extra work for people who maintain websites, as they have to investigate ever file to determine whether the change is due to hacking, or poor practices by plugin authors. Please release any file changes as a new version of the plugin, don’t just change the files in the repository without doing that.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.