Hi Jim,
Is this a brand new install on a site that’s never had UD before? Any other relevant info? I’m trying to reproduce this, but without success so far.
David
P.S. Also two more questions:
1) if you go to your UD settings page, and into the ‘expert’ section (at the bottom), then what is shown under ‘Backup directory:’ ?
2) If you install the plugin ‘SQL Executioner’, and use it to run this SQL, then what is the results?
SELECT * FROM wp_options WHERE option_name=’updraft_dir’;
(You may need to change the wp_ in that above line to match what is in your wp-config.php file, if the value of $table_prefix in that file is not wp_).
Best wishes,
David
Thanks for the pointer. The expert settings section is showing wp_content/updraft.
I’m doing a backup at the moment so I’ll change it after it ends. Will restore work if I change it?
I’m backing up before I install WP 3.6.1 so I don’t want to get things to get messy in case I have to restore.
Hi Jim,
Is this a brand new install on a site that’s never had UD before? Or was UD upgraded from a previous version?
David
I think I had installed updraft before but at that time I couldn’t get it to connect to google drive. I re-installed yesterday and I’m now using dropbox instead as updraft still can’t connect to google drive. I think the problem is the ISP service we have because I have updraft installed on a VPS we have with a different provider and the google drive functionality works fine.
Hi Jim,
I’ve worked it out now. This sequence of events triggers the problem:
1) Install UpdraftPlus before version 1.7.18
2) De-install it
3) Remove the directory wp-content/updraft
4) Install 1.7.18
Once your backup has finished, to fix things up, do this, in this order:
1) Open the UpdraftPlus settings page, and go into the ‘expert settings’
2) Via FTP, copy wp-content/wp-content/updraft to wp-content/updraft
3) In the expert settings, change wp-content/updraft to updraft
4) Save settings
5) Via FTP, remove wp-content/wp-content/updraft from the filesystem
Then, all should be fine. I’ve also tweaked the existing 1.7.18 release so that new people downloading it will not have this problem (it will detect the scenario and deal with it correctly).
Best wishes,
David
Thanks for your lightening quick diagnosis, reply and fix.
Jim