WordPress.org

31. Nick Momrik
    Member
    Posted 9 years ago #
    

    No hurry....just suggestions. :-) Keep up the good work!

32. griffey
    Member
    Posted 9 years ago #
    

    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

33. Laughinglizard
    Member
    Posted 9 years ago #
    

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

34. Dzz
    Member
    Posted 9 years ago #
    

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

35. martin_hoegh
    Member
    Posted 9 years ago #
    

    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 :-)

36. griffey
    Member
    Posted 9 years ago #
    

    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

37. griffey
    Member
    Posted 9 years ago #
    

    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.

38. Laughinglizard
    Member
    Posted 9 years ago #
    

    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.

39. griffey
    Member
    Posted 9 years ago #
    

    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.

40. Beel
    Member
    Posted 9 years ago #
    

    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!

41. dhcalva
    Member
    Posted 9 years ago #
    

    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!

42. AntonIvlev
    Member
    Posted 9 years ago #
    

    By the way, where does WP store all posts?

43. Nick Momrik
    Member
    Posted 9 years ago #
    

    WP stores everything in your database.

44. Mark (podz)
    Support Maven
    Posted 9 years ago #
    

    Just installed the backup11 - worked a treat first time :)
    Thanks LL !

45. Tygger
    Member
    Posted 9 years ago #
    

    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.

46. Tygger
    Member
    Posted 9 years ago #
    

    *bump*

47. Laughinglizard
    Member
    Posted 9 years ago #
    

    Sorry for the late reply. This backup was written for the 1.0.1 and 1.0.2 versions and the backups that I have performed with this script contain the data.
    Did you download the updated version from
    http://dinki.mine.nu/word/b2-img/wp_backup11.zip ?

48. Tygger
    Member
    Posted 9 years ago #
    

    Thank you for your help guys. I downloaded the wp_backup11.zip and it now works a treat.
    Andy.

49. Tygger
    Member
    Posted 9 years ago #
    

    New question: In order to get it to work, I needed to set the chmod file attributes of the backup folder to 777. Are there security implications for my site because of this?
    Thanks,
    Andy.

50. Tygger
    Member
    Posted 9 years ago #
    

    Beel,
    I've removed the backup files from the server. Could you elaborate on your response please, as I'm not sure what you mean by create a password file. I'm not an expert on unix servers/.htaccess files etc.
    I really appreciate your help.
    Andy.

51. Beel
    Member
    Posted 9 years ago #
    

    http://httpd.apache.org/docs/howto/auth.html#basic
    For now, a less secure measure would be to drop an index file in the directory and then someone would need to "guess" the sql file name in order to view it.

52. prara
    Member
    Posted 9 years ago #
    

    Or restrict access through .htaccess

53. Stephan
    Member
    Posted 9 years ago #
    

    Does this still work with wp 1.2?

54. Beel
    Member
    Posted 9 years ago #
    

    yep

55. prara
    Member
    Posted 9 years ago #
    

    but I think that menu.txt doesn't work anymore you have to edit the menu.php

56. Daisyhead
    Member
    Posted 8 years ago #
    

    I have implemented this updated version and nothing happens when I try to create a backup. No file is created. Any ideas on what could be causing this?
    Thanks,
    Daisyhead

57. Beel
    Member
    Posted 8 years ago #
    

    Hmm, I redownloaded the updated version and backuprestore.php is different than the one I am using. I am on a Windows/Apache setup so I don't know if that will make a difference to you. Does your version of backuprestore have the function make_sql($table)?

58. Geof
    Member
    Posted 8 years ago #
    

    I was just wondering if there was any advantage to using this plugin rather than doing a full cPanel backup every which I currently do.

59. Anonymous
    Unregistered
    Posted 8 years ago #
    

    I actually got it to work finally. I had to change my permissions. Thanks! And I'd like to know the advantage of this backup vs the Cpanel backup as well.
    -Daisyhead

60. Beel
    Member
    Posted 8 years ago #
    

    Backup is backup. As I mentioned before I just kept this hack to test as I also backup using phpmyadmin. For some I guess it is a matter of convenience but I visit phpmyadmin often so it is six of one, half a dozen of the other for me.

Topic Closed

This topic has been closed to new replies.