Might be due to the new security features added in the plugin.
Please read the first question in https://ww.wp.xz.cn/plugins/wp-dbmanager/faq/. It should set some light on how to debug it.
I found a partial solution and perhaps exposed other problems by inserting the echo $command statement as you instruct.
After looking at my public site which does work (and where your plugin autodetected the paths it needed), in DB Options, the instruction to enter the ‘path’ to mysqldump and mysql led me to leave off the actual names of the executables.
Adding them resulted in three things happening on the Database -> Backup DB admin page:
1. Unzipped backups now work.
2. Zipped backups do not work.
3. There are now red error messages saying “MYSQL dump path does NOT exist. …” and “MYSQL path does NOT exist. … ” Both of these messages are wrong because the backups now work.
I’m good with this for my development environment but it exposes some problems you may want to investigate.
Thanks for the prompt help.
Because on production you are using Linux whereas on your dev you are using Windows?
To be honest, I did not test on Windows because I have no Windows environment to test with.
The reason why I asked you to echo the $command is so that you can run the command on Command Prompt (on Dev) to see what is the error to get. The error given by the error is meant to be vague.
True, my production environment is probably Linux since I use a commercial hosting company (Bluehost) but am using XAMPP in a Windows 7 environment for development.
Hi pastorjim,
This should fix the problem. Take a look at:
https://ww.wp.xz.cn/support/topic/problem-solved-on-xampp?replies=2
Regards
