Support » Plugins » WP Backup/Restore new version

  • There is a new version of Wp Backup and Restore available which is completely integerated into the WordPress admin interface and controlled by user levels.
    Features include, as before, backup and restore of your WordPress database on the fly and backup of your WordPress directory for local storage. Very easy install. Please post bugs on here.
    Peace
    Download location: http://dinki.mine.nu/word/b2-img/wp_backup.zip
    Found a small bug. If you had downloaded the files before this message appeared in the thread, please re-download.

Viewing 15 replies - 31 through 45 (of 77 total)
  • No hurry….just suggestions. 🙂 Keep up the good work!

    I’m getting the following error on these:
    Warning: fopen(/public/html/griffey/wp/backup/02032004wordpress.sql): failed to open stream: Permission denied in /public/html/griffey/wp/wp-admin/backupRestore.php on line 217
    Warning: fwrite(): supplied argument is not a valid stream resource in /public/html/griffey/wp/wp-admin/backupRestore.php on line 218
    Backup Successful.
    It says its successful, but of course, I get no files in the backup folder
    any ideas?
    Jason

    @griffey: Thats a permission problem. Please make sure the backup folder you created has the requierd write permissions by the web server.

    I couldn’t get this wp_backup working, but wp_backup11 worked perfectly first time. Thanks!

    Better late than never:
    LL, the 1.1 version of the hack works perfectly. I really appreciate your work.
    Now, maybe, I’ll dare an upgrade 🙂

    Permission error? I’ve CHMOD’d the “backup” folder to 766, and still getting errors.
    Is there some possibility that the actual folder path is wrong? Where does the script pull the folder path from?
    Again, the errors:
    Warning: fopen(/public/html/griffey/wp/backup/02032004wordpress.sql): failed to open stream: Permission denied in /public/html/griffey/wp/wp-admin/backupRestore.php on line 217
    Warning: fwrite(): supplied argument is not a valid stream resource in /public/html/griffey/wp/wp-admin/backupRestore.php on line 218
    Backup Successful.
    Jason

    Ok, that said:
    I found the $path variable setting in the bvars.php file, but am unsure about how exactly that’s pulling the info. That _might_ be where this is messing up for me.

    A “permission denied” in line 217 can mean a couple of different things.
    1) Permissions for the backup folder are incorrect (but you have said that those are set to be 766)
    2) The backup folder is in the wrong path. It has to be in the root of your WordPress folder.
    3) Your webserver does not have the right (even with 766) to write to the backup directory you have setup. In this case, you will either have to try a 777 or ask your system admin to make some changes.
    If these do not solve the issue, please email me outside this thread and I will try to help you out as much as I can.

    Well…for some reason, I went back, tried to 777 the folder in order to try it out. The 777 didn’t “stick” (I assume that my provider doesn’t allow a 777 folder in the html area, for good reason). BUT, when I checked, the folder was 766 again, and it worked.
    No idea what was going on, but it’s working now. Completely excellent hack! Thanks so much for helping as well…great stuff. Makes me happy I picked WordPress to use for my blogging efforts.

    Well, your latest version of the WP backup hack seems to work just fine on my W2K system. I am not going to try the restore unless I have to 😉 Berry simple, berry easy – thanks!

    I’ve found a small problem with 1.1. Very small actually. The link to view your site after you do a restore points to the wp-admin/ directory. Other than that, it works great!

    By the way, where does WP store all posts?

    WP stores everything in your database.

    Just installed the backup11 – worked a treat first time 🙂
    Thanks LL !

    I’ve just installed the script from the zip file wp_backup.zip, and got it to work once I assigned permissions of chmod 777 (chmod 766 resulted in no backup file being created).
    When I look at the resulting SQL file, there are lots of drop and create tables, but no inserts other than into the wp_users table, so it looks like it is backing up the structure of the tables, but not the data contained therein.
    I am using WordPress 1.02. Any suggestions?
    Andy.

Viewing 15 replies - 31 through 45 (of 77 total)
  • The topic ‘WP Backup/Restore new version’ is closed to new replies.