Yep, agree that this is a missing feature..
As far as I have looked at the code, there are a couple of ways to do it:
* add and remove info-entries in the WP database for each backup that is taken or deleted (which will make the last backup incomplete because the addition)
* add an extra file in the database backup directory for each backup, like the database file name .txt
I might do it myself… (have since a long time ago changed the part of the code that lists the backups, to show the true file name of the database backup file).
I have implemented backup commenting using the second method mentioned above.. if someone is interested..
* Comment field added for manual backups
* Comment by cron backups are set as “Cron backup at [date/time]”
A few other changes as well:
* “gzip” is now enabled as default
* in the manager, the buttons (“download”, “delete”, “restore”) also is above the list of backups
* when a manual backup has been made, a redirection is made to the “manage” page
As mentioned in the stylesheet-thread, the admin-interface now uses “database-admin-css.css” if it exists.
@peoy, interested to sent a Pull Request to https://github.com/lesterchan/wp-dbmanager? I see if I can merge those in =)
I’m not used to Git/Github, but as far as I can see, I’m not allowed to upload files to the project (“Uploads are disabled. File uploads require push access to this repository.”)
I’ve created a clone of the current version on Git, but that includes more changes than I’ve made (version 1.79, and I changed 1.78.1), so when I created the pull request in my copy, it seems to reverse changes between 1.78.1 and 1.79…
You have to fork the repo, then commit the code to your repo than submit a Pull Request =) I am trying as much as possible to adhere to https://make.wordpress.org/core/handbook/best-practices/coding-standards/php/ =)
maybe I got it right.. GitHub however thinks I modified all of the contents of the three slightly modified files..
https://github.com/peoyli/wp-dbmanager/tree/peoyli-patch-1
