Support » Plugin: BackUpWordPress » Update to 3.9 broke WP (whitelist-html.php missing)

  • Hi, I just installed the update to the latest version. I’m also on the latest WP version. Now my site shows (in debug mode) this:

    Warning: require_once(/home/xxx/public_html/wp-content/plugins/backupwordpress/whitelist-html/whitelist-html.php): failed to open stream: No such file or directory in /home/xxx/public_html/wp-content/plugins/backupwordpress/classes/class-plugin.php on line 133
    Fatal error: require_once(): Failed opening required '/home/xxx/public_html/wp-content/plugins/backupwordpress/whitelist-html/whitelist-html.php' (include_path='.:/opt/cpanel/ea-php70/root/usr/share/pear') in /home/xxx/public_html/wp-content/plugins/backupwordpress/classes/class-plugin.php on line 133

    What can I do?


    • This topic was modified 5 months, 1 week ago by paddor82.
    • This topic was modified 5 months, 1 week ago by paddor82.
Viewing 15 replies - 1 through 15 (of 25 total)
  • Yep I get the same error, latest version 3.9 latest WordPress, PHP 7.1

    If you just want to get WordPress running rename the plugin folder in wp-content/plugins/ to backupwordpress.tmp or similar this will disable the plugin and temporarily remove the error.

    I think a fix from the developers is needed?

    Cheers Basil



    Same here. Updated all my plugins and got a white page on the site. Checked the error log and found:
    Failed opening required ‘/public_html/wp-content/plugins/backupwordpress/whitelist-html/whitelist-html.php

    Renamed the plugin’s directory and the site comes back up. I’ve installed a different backup plugin. I won’t work with plugins I can’t trust. The developer needs better testing before releasing updates.

    It’s official: the update trashes entire website. I’ve had to disable the program and try to go back to the previous version.

    aieeeeeeeeee same! had to deactivate it and now looking for the previous version to re-install.

    I’m a total newbie and have just had this error. Thanks so much for the heads up about renaming the folder. I did that and the site is back up and running.

    Moderator Jose Castaneda



    Just noting to all the plugin author has also been made aware here:

    @jcastaneda Good to know Jose, hopefully the author will get on it asap.

    Same issue here. Is this plugin dead in the water? What’s the best replacement? Thanks.


    Same. Over to updraft.

    Who are these bozos? Same here. Is it that hard to test a plugin “upgrade”?

    Hi I can confirm that the update to this plug in also wiped out my site. It looks to me like the plug in does not work on recent versions of WordPress.



    Luckily I tested this on my local development virtual machine website and finding that it made the site unusable before I attempted updating our production site.

    I’ve usually had good experience and trusted BackUpWordPress in the past and the release notes for 3.9 said that it only was an readme update, so I thought it was safe. Had to fix 20+ sites with this error today. I’ve now switches 20+ sites to Updraft.

    PSA, in case anyone lands here, if you have this problem just FTP into your site and rename the BackUpWordPress folder. Once site is working, probably best to give up on BackUpWordPress, disable/delete, then switch to something like Updraft that developers actually test before foisting it on us. I dislike Updraft, used it a bunch, too featured and bloated IMHO, but it works. Sigh.

    It’s also possible to just set up various server level backups and not even use a backup plugin. Sometimes, these WordPress plugins just seem to duplicate stuff that’s available in Cpanel and WHM.


Viewing 15 replies - 1 through 15 (of 25 total)
  • You must be logged in to reply to this topic.