WordPress 4.7 – files quarantined on upgrade – AutoRestore Automation

[AITpro Admin]

Files are not automatically backed up in some cases during the WP upgrade to 4.7 and files will be quarantined in some cases, which will cause a website to crash.  We are analyzing what has changed in WP 4.7 that breaks AutoRestore Automation. We will also be posting the best and quickest solution to get websites back up from this problem ASAP.

Important Note: If you have BPS Pro 12.8 or higher versions of BPS Pro installed click this link for quickier and easier steps to fix quarantined files problems: https://forum.ait-pro.com/forums/topic/website-not-loading-after-wordpress-upgrade-or-theme-upgrade-500-error-files-quarantined/. BPS Pro 12.8+ versions automatically deactivate/turn ARQ Off when the /bulletproof-security/ plugin folder is renamed instead of having to use the BPS Pro XTF Form Tools to deactivate/turn ARQ Off.

NEWEST UPDATE:  The problem is occurring due to a latency Server API response/time issue and AutoRestore Automation on some websites.   Most websites upgrading to WP 4.7 are not experiencing this problem.  ARQ Automation is based on time/response time.  We have created new FailSafe code in BPS Pro 12.5 that will prevent this problem from occurring.  BPS Pro release date:  12-13-2016.

UPDATE: Something very strange is occurring. On some testing and Live websites the WordPress 4.7 and AutoRestore Automation are working correctly and on other websites AutoRestore Automation is not working correctly. On some websites a prompt to update the WordPress database is occurring during the WordPress upgrade and on other websites that is not happening. The only logical conclusion we can make at this point is there are several different WP 4.7 packaged versions/delivery packages for upgrade and some are doing things differently than others. Another possibility could be some sort of Browser Caching problem. There appears to be a very quick Query String “switchover” occurring during the upgrade that we have never noticed before. This could also be some sort of timing or resource issue. Lots of questions and possibilities so far and no definite answers. Pending additional research.

Safe method to upgrade to WordPress 4.7:
1. Turn Off AutoRestore.
2. Upgrade to WordPress to 4.7.
3. Re-run the BPS Pro Pre-Installation Wizard and Setup Wizard.

Steps to get your website back up:

Use these steps below to get your website back up or you can do a file restore from a backup that you made prior to upgrading to WordPress 4.7. Note: If you choose to do a file restore then use the “Safe method to upgrade to WordPress 4.7” steps listed above.

1. Use FTP and go to the Quarantine folder: /wp-content/bps-backup/quarantine
2. Download any/all folders the you find in the /quarantine/ folder to your computer.
Note: If you see a /root-files/ folder in the /quarantine/ folder, open it and check to see if there are any files in the /root-files/ folder. If there are not any files in the /root-files/ folder then do NOT download it to your computer. If you do see files in the /root-files/ folder then download the /root-files/ folder to your computer.
3. Go to the BPS Pro plugin folder: /wp-content/plugins/bulletproof-security/ and rename the /bulletproof-security/ plugin folder to /_bulletproof-security/
4. Upload the folders that you downloaded from the /quarantine/ folder to your computer to your website and choose “yes” to overwrite folders/files. If you downloaded the /root-files/ folder in Step #2 then open it on your computer and upload any/all files to your website root folder (the same folder where the wp-config.php file is).
Example: Upload the /wp-includes/ to your website and overwrite your current existing /wp-includes/ folder on your website.
5. At this point your website will be back up and working normally.
6. Download the BPS Pro xternal.php XTF file to your computer: /wp-content/plugins/bulletproof-security/admin/xternal/xternal.php
7. Upload the xternal.php file to your website root folder (the same folder where the wp-config.php file is).
8. Delete your Root htaccess file (the same folder where you just copied the xternal.php file to).
9. Open your wp-config.php file to get your WordPress Database Username and Password (the same folder where you just copied the xternal.php file to).
10. Go to the Xternal Tools page in your Browser: http://www.example.com/xternal.php.
11. Enter your DB Username and Password from your wp-config.php file to view/access/unlock the BPS Pro Xternal Tools Form.
12. Choose the Turn Off|Deactivate AutoRestore|Quarantine (ARQ) XTF Form option and click the “Submit Xternal Tools Form” button to turn Off AutoRestore.
13. Click the Lock Xternal Tools Form button after you are done using the XTF Form to lock the XTF Form.
14. Delete the xternal.php file that you uploaded to your website root folder.
15. Rename the /_bulletproof-security/ plugin folder back to /bulletproof-security/.
16. Log into your website and reinstall the WordPress 4.7 upgrade.
17. Go to the BPS Pro Setup Wizard and run the Pre-Installation Wizard and Setup Wizard.
18. Go to the BPS Pro Quarantine page and delete all WP files in Quarantine.

[Jose]

I updated my site to WP 4.7, and these warnings appeared

[06-Dec-2016 20:26:59 UTC] PHP Warning:  copy(/homepages/38/d369103164/htdocs/wordpress/licencia.txt): failed to open stream: Permission denied in /homepages/38/d369103164/htdocs/wordpress/wp-admin/includes/class-wp-filesystem-direct.php on line 257
[06-Dec-2016 20:26:59 UTC] PHP Warning:  copy(/homepages/38/d369103164/htdocs/wordpress/license.txt): failed to open stream: Permission denied in /homepages/38/d369103164/htdocs/wordpress/wp-admin/includes/class-wp-filesystem-direct.php on line 257

Now all the site shows a blank page.
What can I do?

[AITpro Admin]

Yep, we are seeing some very strange inconsistent things occurring with the WordPress 4.7 upgrade.  On some sites everything is working perfectly and on other sites AutoRestore Automation is not working.  See additional research in the main forum topic, which we will be updating as we try to figure out what the hell is going on.  We will also be posting a solution/fix to get sites back up ASAP in a few minutes.

[Paul]

[Topic has been merged into this relevant Topic]
Hi Updated WordPress today but it appears AutoRestore never shut down now all files appear quaranteened and site is down?

[AITpro Admin]

@ Paul – Yep, we are aware of the problem.  See the beginning of this forum topic and the steps to fix your site.

[Paul]

Thankfully had a backup, restored and updated with ARQ off If I now go to AutoRestore|Quarantine and back up the folders with magic buttons then turn on is this ok?

[AITpro Admin]

@ Paul – Just do the safe steps below to upgrade WordPress.

Safe method to upgrade to WordPress 4.7:
1.  Turn Off AutoRestore.
2.  Upgrade to WordPress to 4.7.
3.  Re-run the BPS Pro Pre-Installation Wizard and Setup Wizard.

[Jose]

Restored and updated!

Trying to find the option for turning off the cURL Scan and re-run the pre-instalation wizard again.

[Jose]

Done! Perfect. Thanks.

[AITpro Admin]

@ Jose – Great!  Now to fix our/this BuddyPress/bbPress forum site.  We are missing BuddyPress/bbPress menus after upgrading this site to WP 4.7, which is not related to BPS Pro in anyway.  The fun never ends. 😉

[Jose]

I see. It’s the story of no ending.
Greetings.

[AITpro Admin]

@ Jose – Yep, you got that right.  We hold our breath during every Major WordPress upgrade. 😉

[AITpro Admin]

What’s interesting is I have upgraded and tested the WP 4.7 upgrade on 20 more sites and all of the upgrades were successful.  ARQ Automation worked fine and no files were quarantined.  So the only logical explanation I can think of is something like since I upgraded as soon as WP 4.7 was released and so did you and Paul then maybe the problem had to do with some sort of resource or request overload – ie 1,000,000 people upgrading to WP 4.7 at the same time caused some sort of delay or response lag that caused ARQ Automation to fail.  ARQ Automation is based on time so that is very possible.  In any case, so far no one else is reporting a problem.  So that is big relief.  And like I said I upgraded 20 sites without any problems. Whew!

[Jose]

May be waiting two or three hours since the upgrade notification would be fine, trying to avoid lots of folks updating at the same time.

[AITpro Admin]

Yeah, maybe, but this is definitely something we need to figure out so that it will not happen again.  This may not be something we can control on our end and may be a WordPress API server thing that is beyond our control.  😉

[Author]

Posts