• I can’t find anything original to say in addition to what has already been said about this lifesaving plugin. So, instead I’ll add a suggestion based on an observation: I also have Wordfence running, and it pointed out that the UpdraftPlus plugin had changed its content from the canonical version, stored on the WP repo. I suspect the UpdraftPlus author discovered a little something to tweak and added that to the repository, only to find out it was a premature upload. Please don’t do that again – I had to manually clear (i.e. okay) UpdraftPlus as having non-harmful changes. Others with active file content security scans will undoubtedly agree. Having said that, that’s a marginal observation; it doesn’t affect the core functionality.

Viewing 1 replies (of 1 total)
  • Plugin Author David Anderson / Team Updraft

    (@davidanderson)

    Hi nv1962,

    Thanks for the positive review!

    From time to time, tiny bugs are discovered that don’t warrant releasing a new version. (Too many new versions lead to users complaining about the frequency of updates). So, plugin authors will change the existing version, without bumping the version number. I maintain around 100 WordPress websites, and can testify that plugin authors do this quite a lot – and this covers big plugins (e.g. WooCommerce do it a lot) and small. Thus, I’d say that WordFence need to change their algorithm to take account of this reality – instead of testing the installed plugin against the *current* wordpress.org download, they should be testing it against the wordpress.org download *from the date the plugin was actually installed on your website*, because their current algorithm gives false positives in this way. If I bump the UpdraftPlus version number for tiny tweaks (perhaps a bug fix which may affect only 0.1% of users), then I get significantly more complaints than I do from WordFence users who don’t like the false positive.

    Best wishes,
    David

Viewing 1 replies (of 1 total)

The topic ‘A must-have plugin’ is closed to new replies.