Fixing WordPress After Update : Fix For White Page

Fixing WordPress After Update Video Guide practically shows you all the possible ways to fix your WordPress website in case you are facing the White Page issue. Practically there is nothing to write, all has been literally said for fixing WordPress after update. Here are the reference URLs used in the video plus the transcript of the video.

 

Fixing WordPress After Update : The Reference URLs

 

Two tutorials are most important. The first one is the required knowledge on how to properly update WordPress so that you will not need these painful ways for fixing WordPress after update and the second one is for the database repair part – Repairing WordPress Database.

 

Fixing WordPress After Update : Transcript

 

For those who do not understand English Language or having issue to understand the saying (English pathetically has various accents). Obviously, not everything has been said in real.

 

 
Are you having this kind of issue ? Is your problem is that, after upgrading WordPress from Dashboard, you are basically getting a white webpage. It is not that my Internet connection is slow. First we need a good FTP or SFTP software like Filezilla. Or if you love WinSCP like me, you can use WinSCP. WinSCP is most robust SFTP software but there is no official version. This WinSCP is running using emulation.

I will describe trouble shooting stepwise. If first or nth step solves your issue, there is absolutely no need to do all the things we have shown here. This is an extreme example of Whitepage syndrome after upgrading WordPress. So this the root folder of this WordPress installation. And here are three folders of WordPress – wp-content, wp-admin and wp-includes.

Depending upon the installation, you will have a PHP error log file. We can detect which factor is throughing the error. This is PHP error log file. In my case, practically there is no known solution to fix it. Second way is to add a dot to rename the plugin folders to deactivate them. And deactivating all themes except the default one using the same adding a dot to rename method.

When you will remove the dot by renaming they can be activated through WordPress Backend. So, first we need to clean the cache, cookies forcefully to make sure that, we are not getting a webpage from the cache. For my case, that method to deactivate plugin has not worked at all. I am trying to delete older cache of WordPress as another try. Definitely I can rename it. Adding a dot normally will make the folders. It can happen, for using a relative path, somehow any theme’s javascript is creating the issue. It is always better have a plugin which renders WordPress to a static HTML website. I copied one index.html file locally and opened it on browser.

I tested the Javascripts by debugging. From my experience, I understood the problem is really difficult to solve. So first I deactivated .htaccess file and checked if it is the reason for my pain. Then I tried to update and upgrade steps of WordPress. But both failed. So I have to check whether Apache2.2 is running or not. Any image or text or HTML shouldd run fine if Apache is loading rightly. But there is some issue with php of WordPress. As I am using Rackspace Cloud managed account, I know the PHP is running fine. So I started to freshly install wordpress on root folder. I moved all the files and folders to a easily recognisable named folder. Now we need to get the solution for this pain from our website. We will repair the database in easy steps. We have described this method to move WordPress from any location to any location. Now what I did is, I followed my own tutorial ! Thats funny. The process is to delete the new WordPress installation’s few important tables and import the same tables from my old WordPress installation’s database. I could have use MYSQL replication feature as well. I could opened each table as text and copy the text and execute as sql queries. Whatever the method is, I basically replaced few important tables. The result I got is – my whole website not only back, it is having a fresh new WordPress database.