SomeUser2012

Ok I got it resolved…

I’ve spoken to my webhoster and they suggested changing the owner of the folder backups from ftp-user to php-user through their webftp interface (using chown).

Now it runs like a charm with 755.

Hi Michael,

thanks for your quick response, but unfortunately it didn’t resolve my problem.

I’ve already tried that as well and 766 still throws the above mentioned error message on the “backup settings“-page.

However with 766 I’m able to see the “backup now“-page and start the backup process manually, by clicking on the “start backup”-button.

But when doing so, it just shows the message

“Your backup has been scheduled and is waiting for WordPress to start it. This could take a few minutes, so now is a good time to go and grab a cup of coffee.”

but it doesn’t start the process.

Also, while in this state I click on the Backup settings or premium extensions page and go back to the backup now page and it says:

“No backup in progess.” again.

Just for the record, when using 777 everything works perfectly fine, it creates a perfect backup in my dropbox folder including the database dump…

Did anyone else have experienced those problems on WordPress 3.4.1 ?

Any other ideas?