Mert Yaz?c?o?lu

So sorry for the late reply, I’m glad to hear it’s resolved ??

1. Currently, the only way to download a backup is using an FTP client but downloading right from the browser makes so much sense so I’m adding it to my list for the next version ??

2. That is weird actually, will have a look at that.

Thank you very much for dropping by and sharing your experience!

You should not be seeing Forbidden errors and the only solution I can provide is to check file permissions and security settings on your server. (mod_security, Suhosin etc.)

I have been trying to reproduce this error but no luck so far. I will let you know when a more specific solution is available.

Your hosting company can do it for you then ??

Most likely mod_security is causing this error. Try temporarily disabling mod_security or using it with a less strict configuration.

I’m deeply sorry to see that it didn’t work well for you. I hope I can manage to reproduce the error myself and fix it in the upcoming versions.

Thanks for trying WordPress Move and sharing your experience!

You got those PHP Warnings because the plugin was unable to read some of the directories. The solution I provided just makes the plugin ignore unreadable directories so if they were because of unreadable directories, you will most likely have a backup missing some of the directories.

Similarly, the last error you mentioned indicates another permission issue. Make sure your permissions are set properly so that the plugin can read and write backup files successfully.

Find the following in libs/functions-file-backup.php on line 69:

foreach ( glob( $directory . "/*" ) as $file ) {

Replace it with this:

$f = glob( $directory . "/*" );
if ( is_array( $f ) )
foreach ( $f as $file ) {

And try again. This should solve it ??

I assume this one is resolved.

You are absolutely right, the database prefix should be specifically definable by the user. Thanks a lot for pointing this out, it would never come into my mind ?? I will add an option to set the database prefix in the upcoming version.

The path should be written by starting from the top directory that your FTP account has access to. Typing it wrong causes backup files to be transferred elsewhere so I’m not really happy how it works right now. Need to figure out a better way to do it ??

Thanks a lot for sharing your experience and suggestions, much appreciated!

You need to give some details first:

– What do you mean by “crashed”?
– What were you trying to do? (Change Domain Name, Migrate)

Actually the minimum requirement is WordPress 3.2, not WordPress 3.3. If you are running a version older than 3.2, it won’t work properly.

You are getting this error, because your web server does not have the permission to write to /tmp directory which is needed to create backup files.

Don’t you think trying to use a plugin on a non-compatible WordPress version and telling others to “be aware” is misleading ??

Did you have a look at BuddyPress ScholarPress Courseware for BuddyPress? ??

I assume this one is resolved.

Actually, it should have never created a file with the name Backup-13227252171.zip as it lacks the chunk id in its file name. All your files are divided into zip files that have chunk ids in their file names and since the one that failed doesn’t have one, there is no need to worry. Things like this are likely to happen due to the complicated nature of the file systems ??