I have looked into it and it would seem i am unable to access the files in the revisr-backups folder.
When i try to interate through the files in the folder i am only shown the .htaccess and index.php files, even though there is a bunch of SQL files as well.
I can access the files from the URL that
"{$this->backup_dir}revisr_$table.sql"
generates. Even though file_exists() says there is no file at that location…
I tried to create a file in the folder and i could get that without a problem, but the files created by the program is non-existing to the program.
Im running it through XAMPP, btw
And more info.
It would seem that it removes the files from the backup folder, searches after them, in which case it fails, and then puts them back into the folder (Guessing from the git repository)
So, all in all, it would seem the verify_backup function fails as there is no files to check on, thus returning a false.
I could use some guidance as to how i can get this to work.
Hello,
The partial pull issue you mentioned is related to an open issue that has been resolved in development and will be included in the next release.
First, it looks like you need to specify your MySQL path in order to get backups to work.
Then, it looks like you’re having an authentication issue with Bitbucket and/or GitHub. You’ll need to make sure that you get a “Success!” message when entering your “Remote URL” in the “Remote Setttings”.
More info on that can be found in the documentation.
Let me know if you have any further questions, thanks!
Right, i am getting a success on backing up the database when pull, though no changes to my DB was made.
I found out that git throws a 128 error as a last status entry in the dashboard, which seems to be the only issue at the moment (Assuming that this error is why the database is unchanged, even though it gives a “backed up successfully” message)
Hi,
If you have the “Import DB when pulling changes?” checkbox checked, it will backup the database before every pull in case there are new DB changes to be imported. Also, when you hit the “Backup Database” button, it commits the changes to any tables you’re tracking for you.
Does your issue persist with the latest version (1.9.2)? If so, do you get any more detailed errors?
