WordPress Designpraxis Forum » BackUpWordPress Issues resolved

multiple warnings (log posted)

(8 posts)
  • Started 4 years ago by shootingboard
  • Latest reply from leemason

  1. shootingboard
    Member

    Looks like a nice plugin, but when I tried to do first backup I got this (after several minutes):

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

    (HUNDREDS OF THESE LINES):
    Warning: Invalid argument supplied for foreach() in /home/shooting/public_html/wp-content/plugins/backupwordpress/bkpwp-classes/options.php on line 254

    (THEN THESE LAST TWO LINES):
    Warning: copy(/home/shooting/public_html/_vti_pvt/service.pwd) [function.copy]: failed to open stream: Permission denied in /home/shooting/public_html/wp-content/plugins/backupwordpress/bkpwp-classes/manage_backups.php on line 558
    Archive unknown

    Notice: Archive unknown in /home/shooting/public_html/wp-content/plugins/backupwordpress/PEAR.php on line 896
    Archive unknown

    .....

    My phpInfo:

    max_execution_time: 0
    max_input_time: 60
    file_uploads: 1
    upload_max_filesize: 32M
    post_max_size: 16M
    register_globals: 1
    safe_mode:
    allow_url_fopen: 1
    eaccelerator.enable:

    Other information:

    PHP Server API: apache
    WordPress Version: 2.2.3
    WordPress Blog URI: http://shootingboard.net
    WordPress Installation URI: http://shootingboard.net
    WordPress Theme: /wp-content/themes/wordpress-ii-silver-2006
    WordPress Permalink Structure: /%year%/%monthnum%/%day%/%postname%/
    WordPress wp-content directory is not writable
    WordPress does not use Gzip Compression
    WP-Cache is running on this installation of WordPress
    GD library is installed
    PHP Version: 4.4.4
    MySQL Version: 4.1.22-standard
    Browser used: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en) AppleWebKit/419.3 (KHTML, like Gecko) Safari/419.3

    Posted 4 years ago #
  2. Your WordPress installation resides within your web root, where other files as well as your wordpress files are located, too. The user the webserver runs with on that machine has no permissions to read those files.
    I'll work on BackUpWordPress to have the option to automatically exclude those files from a backup task. Watch out for BackUpWordPress version 0.3.3.

    Posted 4 years ago #
  3. shootingboard
    Member

    Thanks for the prompt reply. It looks like the backup plugin worked, regardless of the error messages. I can see a backup folder in my backup directory (actually two, since I ran it twice). I can see all my "other" non-wp files have been copied in those folders -- all the files from my public_html folder. Thanks again.

    Posted 4 years ago #
  4. sk
    Member

    I got exactly the same errors. However, I figured out that in my case the problem was that I tried to run a backup with a different user than the one how installed the back-up plugin. When I use the user how installed the backup, everything works fine. Any other user gets errors like the ones mentioned above, the presets list is either empty or cannot be edited and any backup you start runs forever although you see files created in the backup-folder.

    If you use different users to manage your site, try to do the backup with the same user how installed the backup plugin.

    The problem seems to be caused by the way how the backup options are stored in the database. Everytime a different user changes one of the backup options the setting of any other user will be deleted and only the setting of the current user will remain in the database.

    Posted 4 years ago #
  5. ditto - same problem. wordpress is installed in root directory. same login user as the one who installed the plugin (only have one admin user).

    Posted 4 years ago #
  6. sk, yes, that is due to an idea I had, stroing options on a per-user basis. Right now you can grant capabilities to manage backups or download backups to a user. Use a plugin like Role Manager for this.
    The "different settings per user feature" seems to be buggy though. A workaround would be to grant permissions only to one user at the moment.

    Posted 4 years ago #
  7. leemason, same problem as shootingboard or sk?

    Posted 4 years ago #
  8. sorry, same as sk. but only have a single user w/admin settings.
    wordpress 2.2.2. installed

    Posted 4 years ago #

RSS feed for this topic

Reply

You must log in to post.