[lingben]

been using revisr, a free plugin that not only does the same thing and more but it has been out for almost a year now with regular upgrades and feature adds:

https://wordpress.org/plugins/revisr/

will take a look at this to see how it compares

[borekb]

Revisr is a fine plugin and it does many things nicely. However, it is vastly different from VersionPress, as described here:

http://blog.versionpress.net/2015/01/versionpress-vs-revisr/

[lingben]

revisr has automatic change tracking btw

[borekb]

Really? Last time I checked it was manual commits only. Still, the way they track database is very different from how VersionPress does it. But as I said, I'm glad Revisr exists, it is a great tool for certain scenarios.

[lingben]

https://revisr.io/revisr-v1-9-3-released/

https://wordpress.org/plugins/revisr/faq/

How does Revisr handle the database?

You have complete control, and can decide whether you want to track the entire database, just certain tables, or if you don't want to track the database at all. Then, during a backup, the tracked database tables are exported via "mysqldump". When importing or restoring the database to an earlier commit, Revisr first takes a backup of the existing database, creating a restore point from immediately before the import that can be reverted to if needed.

You can also set a "Development URL" that will be automatically replaced in the database during import- allowing for backups and restores that work on both your dev and live environments.

[borekb]

VersionPress' automatic change tracking means that new commit is created after every logical change to the site, e.g., after you update a post, update a plugin or just about anything. Revisr, if nothing changed recently, only creates commits when you manually say so. That's a difference.