WordPress Designpraxis Forum » BackUpWordPress Issues

several errors using the plugin

(7 posts)
  • Started 4 years ago by joecr
  • Latest reply from rol
  • This topic is not a support question

  1. Recalculate Used disk space

    Warning: Invalid argument supplied for foreach() in /home/user/public_html/blog/wp-content/plugins/backupwordpress/bkpwp-classes/manage_backups.php on line 985

    BackUp WordPress Now

    Warning: Invalid argument supplied for foreach() in /home/user/public_html/blog/wp-content/plugins/backupwordpress/bkpwp-classes/manage_backups.php on line 985
    Archive unknown
    Notice: Archive unknown in /home/user/public_html/blog/wp-content/plugins/backupwordpress/PEAR.php on line 896
    Archive unknown

    PHP information for http://blog.v2joecr.com

    max_execution_time: 30
    max_input_time: 60
    file_uploads: 1
    upload_max_filesize: 2M
    post_max_size: 8M
    register_globals:
    safe_mode:
    allow_url_fopen: 1
    eaccelerator.enable:

    Other information:

    PHP Server API: cgi-fcgi
    WordPress Version: 2.3.1
    WordPress Blog URI: http://blog.v2joecr.com
    WordPress Installation URI: http://blog.v2joecr.com
    WordPress Theme: /wp-content/themes/ocadia
    WordPress Permalink Structure: /%year%/%monthnum%/%day%/%postname%/
    WordPress wp-content directory is writable
    WordPress uses Gzip Compression
    WP-Cache is running on this installation of WordPress
    GD library is installed
    PHP Version: 5.1.6
    MySQL Version: 5.0.37-standard-log
    Browser used: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.8) Gecko/20071008 Firefox/2.0.0.8

    Schedule: manually
    WordPress Version: 2.3.1
    BackUpWordPress Version: 0.4.3
    ## November 1, 2007 21:06:37: BackUpWordPress starting at November 1, 2007 21:06:37
    ## November 1, 2007 21:06:37: BackUpWordPress using Preset

    Obviously Windows XP with Firefox 2.0.0.8

    Posted 4 years ago #
  2. joecr, there is a workaround for that issue posted here in german: http://wpforum.designpraxis.at/topic/error-invalid-argument-supplied-for-foreach-?replies=2#post-322.
    The Problem is line 982 in manage_backups.php
    if(empty($user)) { $user = "admin"; }

    If you did rename your default admin account for security reasons, you'll have to set that "admin" to whatever you named your account.

    I'll fix that issue in the next version that will come today or tomorrow.

    Posted 4 years ago #
  3. I upgraded to 0.4.4 but it still had the same error so I changed the admin the actual admin account on my blog. I now can do a SQL backup & a Manual full backup. I scheduled a weekly full backup but I don't see that it either happened or that it is trying to run it. Oh BTW if you install WordPress with Fantastico you can have it during install set the admin user name to something other then admin.

    Posted 4 years ago #
  4. joecr, thanks for the report! I am working on the plugin and hope to be able to release a stable version soon.

    Posted 4 years ago #
  5. I noticed another issue. I went with the default schedules & it is doing the SQL only backup several times a day. Here is a sample. All I did was turn them on both SQL only & the full. I'm not sure how it will deal with DST as that ends Sunday at 2 AM my time.

    • November 3, 2007 18:23 ~ sql - scheduled
    • November 3, 2007 16:15 ~ sql - scheduled
    • November 3, 2007 16:15 ~ sql - scheduled
    • November 2, 2007 16:27 ~ sql - scheduled
    • November 2, 2007 11:09 ~ full - manually
    • November 2, 2007 11:06 ~ sql - scheduled
    Posted 4 years ago #
  6. A new problem has started. Even though I disabled the extension after disabling the scheduled backup it is still doing the scheduled backup. I'm now running BackUpWordPress 0.4.5, which according to WordPress 2.3.1 is the current version.

    One other thing I noticed is in at least one of the error message you have deactivate spelled wrong as "deaktivate". A minor issue I know, but the first one is annoying.

    Posted 4 years ago #
  7. joecr, thanks again for reporting. I did notice the issue as well, but haven't been able to solve it yet. I't being solved with 0.4.6, I promise.

    Posted 4 years ago #

RSS feed for this topic

Reply

You must log in to post.