Unable to view site after upgrading to Wordpress 4.2

[googlearchive]

Unable to view site after upgrading to Wordpress 4.2

[alfredwb]

How did you upgrade?

[jdsanford]

I upgraded locally, then redeployed.

On Sun, Jul 12, 2015 at 4:14 PM, alfredwb [email protected] wrote:

How did you upgrade?

—
Reply to this email directly or view it on GitHub
#43 (comment)
.

[alfredwb]

Thank you, +jdsanford for the response.
Upgrading: I considered two routes to manually update locally

1. take latest files from githib on this project, or
2. download latest Wordpress files, unzip and replace older files.

I imagine the first to be more reliable, but possibly with a lag when new Wordpress versions are released. I imagine the second to be better, if I knew what to copy and what to leave.
I've tried both methods unsuccessfully, so if you could give me brief guidance (or point me to some instructions), I'd be very grateful!

Alfred

[Kage1989]

I've managed to upgrade the version of Wordpress in this project to the latest version 4.4.2 by changing the entire wordpress folder. This would be easy if you're starting out fresh.

As your project grow bigger and have more themes and plugins, my guess is that you might have to follow the following steps:

1. Backup the wordpress folder (in case the update fail, you still have a rollback to fall on)
2. Update the entire wordpress folder to the latest version
3. Copy back the wp-content folder (we shouldn't be changing anything other than this wp-content folder right?)
4. Test on local to make sure it runs before deploying live. If update fails, there's still the backup from step 1. So your site should be safe if you copy back the entire wordpress folder.

Yup. Hopefully, this helps anyone else who have faced this same issue. Point to note is that the update has to be done locally and then redeployed for the update to take effect. Meaning we can't use the Update to latest Wordpress version feature on Dashboard.