Support » Plugin: Snapshot Backup » [Plugin: Snapshot Backup] Upgrade to 2.0 and new installation of 2.0 error

  • Snapshot 2.0 installs and activates without any problems but when I go to any of the admin options I get the following errors:

    Warning: include(/path/wp-content/plugins/snapshot-backup/includes/snapshot-functions.php) [function.include]: failed to open stream: No such file or directory in /path/wp-content/plugins/snapshot-backup/snapshot-backup.php on line 215

    Warning: include() [function.include]: Failed opening ‘/path/wp-content/plugins/snapshot-backup/includes/snapshot-functions.php’ for inclusion (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /path/wp-content/plugins/snapshot-backup/snapshot-backup.php on line 215

    Fatal error: Call to undefined function snapshot_header() in /path/wp-content/plugins/snapshot-backup/snapshot-backup.php on line 216

    Earlier version of Snapshot was working fine for me.

    Please help.

    Thank you.

Viewing 12 replies - 16 through 27 (of 27 total)
  • Hello Jay,

    The errors are gone with the update. Thanks!

    I see the following errors under Manage Snapshots which I think are “normal” since I did not setup FTP:

    Warning: ftp_connect() [function.ftp-connect]: php_network_getaddresses: getaddrinfo failed: Name or service not known in /path/wp-content/plugins/snapshot-backup/includes/check-repo.php on line 18

    Warning: ftp_login() expects parameter 1 to be resource, boolean given in /path/wp-content/plugins/snapshot-backup/includes/check-repo.php on line 21

    Warning: ftp_nlist() expects parameter 1 to be resource, boolean given in /path/wp-content/plugins/snapshot-backup/includes/check-repo.php on line 24

    Warning: Invalid argument supplied for foreach() in /path/wp-content/plugins/snapshot-backup/includes/check-repo.php on line 31

    This section helps you keep track of your backups.
    I’ll add more functions here in future versions of the Plugin.

    Warning: ftp_close() expects parameter 1 to be resource, boolean given in /path/wp-content/plugins/snapshot-backup/includes/check-repo.php on line 44

    BTW, when will you release an upgrade with restore option?

    robinwyatt – with resources your host means CPU, memory, swap file usage. i.e. server resources. If they keep complaining about your site, your next option would be to get a VPS, semi-dedicated, or dedicated server. Though cost would be a factor.

    Plugin Author Jay Versluis



    yes those errors are another mystery to me… They were in the previous version too and again don’t show up on my server. Did you say the backups are created fine?

    I’m afraid I can’t give you a timing on when the restore option will be available, but it’ll most likely be a standalone script rather than an integration. I’ll see what works. Restore is easy when you’re restoring to the same domain and server, but it can get hairy when you want to restore onto a different domain or into a subdirectory – however those would be super cool options. Imagine you have pre-built websites you can roll out to clients at the touch of a button?



    I think what Hostpapa are concerned about is not bandwidth but as Anjaan said CPU power and overall responsiveness of their server. When Snapshot creates a backup it hogs the server resources a bit – and I’m sure that’s what they’ve picked up. Shared hosting is a very sensitive environments.

    The good news is that I’ve found a solution which will slow the process down so it takes longer, but doesn’t hog the resources. I’ll test it and will let you know – it’ll be a feature in 2.1 which I may release early next week.

    This is great news, many thanks! (Oddly, 2.0.2 is still not showing as an available upgrade for me.)

    Plugin Author Jay Versluis



    try a manual delete and restore. It’s definitely on the system:

    Hello Jay, yes the backups are created fine without any errors with 2.0.2 🙂

    Looking forward to the restore options…that would be so cool!!!

    Thanks for the quick turnaround.


    I got 2.0.2 now, thanks.

    Meanwhile, Hostpapa – who I used to love – are driving me nuts. Here’s their latest e-mail to me:


    We noticed that you are using your account to store data not related to your site in

    * /home/robinwya/robinwyatt-org-snapshot-20110715-709.tar
    * /home/robinwya/robinwyatt-org-snapshot-20110715-909.tar

    This is considered Data Warehousing and is a violation of our Terms of Service ( While we do provide unlimited disk space with our hosting package, that space must be used for data that is essential to the operation of your website.

    Please remove the data as soon as possible to avoid having your account suspended.

    HostPapa Systems Administration Department

    Of course, this is automated. But do you think that if I changed something in the path so that it reads ‘site-backup’, it would be more acceptable to them?


    Ok, forget my reply. They already responded:


    Storage of backup files is prohibited as per our Terms of Service.

    “o) Data Warehousing: The servers provided by HostPapa are intended for web services use only. Any use of our servers for file storage, data warehousing, back-up data storage, or any form of data file storage or management is prohibited. HostPapa servers are intended for web enabled services and hosting.”

    We recommend that you download and remove backup files in 24 hours after generating them.

    Plugin Author Jay Versluis


    Ah, now it all makes sense:

    It’s not the plugin they don’t like, they don’t want you to store .TAR files anywhere in your webspace. That’s very cheeky – like you say – unlimited is unlimited where I come from.

    You can always sign up with one of my FTP packages – they’re optimised for speed and backup, no penalties attached, usable immediately:

    I get:

    Warning: ftp_nlist() [function.ftp-nlist]: listen() failed: Permission denied (13) in / on line 24
    Warning: Invalid argument supplied for foreach() in / on line 31

    with version 2.0.2, and I’ve dropped and reinstalled the plug-in.

    That’s just in the Manage Snapshots UI though, not everywhere.

    Plugin Author Jay Versluis


    Some hosts don’t allow PHP to execute FTP and shell commands – probably due to security restrictions. Your host seems to be one of them.

    It basically means that the plugin can’t do what it needs to in order to work properly.

Viewing 12 replies - 16 through 27 (of 27 total)
  • The topic ‘[Plugin: Snapshot Backup] Upgrade to 2.0 and new installation of 2.0 error’ is closed to new replies.