After migration of WordPress website I can't access the admin (white page)

I am trying to move a WordPress site from my local server to the online server.

The problem is that, after the migration, if I try to open the administration page (wp-admin) I only obtain a white page, as you can see here:

[To see links please register here]

. Everything else seems work well in the homepage:

[To see links please register here]

.

In my local web server I have the WP site into the folder: `/var/www/wordpress`. I have moved it into a **wordpress** folder that is into my root directory of my online web server.

I have also import the local database into the onlyne database using MySql and then I have use the **Search and Replace for WordPress Databases Script** to change automatically all the `http://localhost/wordpress` occurrence into the database tables with

[To see links please register here]

.

I've fought the dreaded "White Screen of Death" myself a few times. You can browse the threads at the [Wordpress Support Site](

[To see links please register here]

) to glean some suggestions, or Google it for lots and lots of people's stories and advice dealing with these. I can't recommend a single, authoritative reference for this.

In most of my cases it was caused by whitespace after a closing `?>` tag that got introduced because of changes in newline schemes between my dev and production servers, usually in a plugin.

You might also try putting Wordpress into [debug mode](

[To see links please register here]

) or adding `error_reporting(E_ALL);` to the first line of your site's `/wp-admin/admin.php` file to see if these give you any hints.

I've personally been able to avoid these (touch wood) by using the [XCloner plugin](

[To see links please register here]

) to make transfers between my Win dev machine and *nix production server.

Inside your settings for your WordPress dashboard there are two fields named "WordPress address (URL)" and "Site address (URL)". These are also known as the "Home" and the "Site URL" settings for your website. The values need to match the server you're actually running on.

**If you can't get to the admin, you can use phpmyadmin, go into your database, find the fields kin the wp_options table, and make sure they reflect your domain.**

It should be enough in most of cases.

There is an error on your site, and you need to find out what's happening.

## WordPress URLs

When migrating WordPress sites where the URL changes, you will need to tell WordPress about the new URL. WordPress stores that information in the database, so if you're comfortable with that, you could find the correct entry in the `wp_options` table in your database and update its value.

I will show some fixes for standard WordPress installs (where the site URL is the WordPress root), but you _may_ need to use different values for `home` and `siteurl` if you have a different setup.

### Fix URLs via SQL

You will need to update the relevant fields in the DB, those being the entries of `wp_options` where the `option_name` is `siteurl` or `home`. You can find these fields using phpmyadmin, mysql-workbench, or another database management tool, or you can use the following query, changing the URL to be your own.

<!-- language: lang-sql -->

UPDATE `wp_options` SET `option_value`='http://www.myurl.com' WHERE `option_name` IN ('siteurl', 'home');

### Fix URLs via `wp-config.php`
However, you can also do this via `wp-config.php`, which I find to be much more comfortable. Just open `wp-config.php` and add the lines:

<!-- language-all: lang-php -->

// Site URLS (override DB settings)
define('WP_HOME','http://www.myurl.com'); //<-- NO TRAILING /
define('WP_SITEURL','http://www.myurl.com'); //<-- NO TRAILING /

Obviously you'll need to supply your correct URL.

It's possible that this is the only error you're having, and after adding those lines to `wp-config.php`, you will be able to log in and use your site normally.

## Debugging WordPress errors

However, if you continue to experience problems, and any time you're working on developing a website, you will want to see error output. You can check your server logs for information about the errors, but you may find it more convenient for WordPress to simply display the errors in the page. To enable error display, change the following setting to `true` in `wp-config.php`.

define('WP_DEBUG', true);

Now WordPress will display any errors it encounters directly in the webpage. Be sure to change the setting to `false` for use on a production site.

## Working with `wp-config.php`

This file will be located in the root directory of your wordpress installation. To make any of the changes mentioned here, you may either edit the file directly on the server (via `ssh` for example), or download the file with an FTP client, make your changes using a text editor, and upload the file again.

It's also a good idea to keep a backup copy before making any changes in case you break something while you're working.

## References

You can read all about changing the WordPress site URL on the [docs page](

[To see links please register here]

).

Late To the party, I've experienced this recently and I managed to solve the issue. Here is what I've done.


**Step 1:** Set `WP_DEBUG` to `true` from the `wp-config.php` file

**Step 2:** I tried `domain.com/wp-login.php` instead of `domain.com/wp-admin` by this I was able to get atleast login form and some errors of `Warning: Cannot modify header information - headers already sent by `

**Step 3:** I've added `ob_start();` in `wp-login.php` file after `<?php` in first line, of course to get me in for a while.

**Step 4:** This trick worked. I've disabled all the plugins, and errors are gone.

**Step 5:** Activated all the plugins one by one to find which plugin is causing error, So that I can fix the error in particular plugin. Like there was one plugin adding style before `wp_enqueque_style` so I set it to a function and hook it properly.

There were some minor errors too like `deprecated` functions. Its up to you whether you want to correct it or use alternate plugin.

And Don't forget to remove `ob_start` from `wp_login.php` file. The core files should not be changed.

Hope this helps someone like me.

I had the same problem after migrating to a local server.
A first attempt failed because there were many hardcoded filepaths in the database.
So I tried again and took care to create the same path as on the live server and the same hostname and databasename. Now the website was good but wp-login gave a white screen.

With wp-debug I found that the problem was caused by wp-super-cache plugin that had a full filepath hardcoded in the config.php
Changing this path to the full local path did the trick.

Edit wp-content/themes/active-theme-folder/function.php and add this code just before:

<?php
define('WP_HOME','http://www.myurl.com'); //<-- NO TRAILING /
define('WP_SITEURL','http://www.myurl.com');

Add the below line into the `wp-config.php` file:

define('WP_HOME', 'http://' . $_SERVER['SERVER_NAME']);

define('WP_SITEURL', WP_HOME . '/');

In you wp-config.php file just above the line stop editing line add this line:

define('RELOCATE',true);
/* That's all, stop editing! Happy blogging. */

Then go to your login URL, refresh the page and log in.
IMPORTANT: **If you can log in, then remove the RELOCATE line before preceding any further.** Then navigate to:

Settings > General

Set your Wordpress URL and Site address to the correct locations:

WordPress Address (URL):

[To see links please register here]

Site Address (URL):

[To see links please register here]

Press "Save".

These are the steps I usually follow.

1. Upload files and database.
2. Set the correct file permissions.
4. Update the database configurations in the wp-config.php file to match the server db login.
5. Update the `wp_options` table for updating the site url and home url.
6. If everything goes well you should be able to login to the admin using the `wp-login.php` as the url.
7. The first thing next to do is to go to the permalinks and click save it will automatically update the `.htaccess` file. If there is no write permisson it will show you can copy it and edit the file via ftp.
8. Next thing you can easily update all the urls safetly with a plugin named `velvet urls` . Using it for many years. It will update all other urls in the database.

All these steps will be enough if everything goes correctly.

If you get a blank page or something you can turn on the error reporting and write the logs from the wp config file itself. You can try some of these to debug.

1. Just remove plugins from the folders one by one.
2. Remove the custom theme which you are using.

Unless you edited the core files mostly it will solve the issue. Only other chance is the version mismatch for php or mysql that is also very important thing to note while migrating. Hope this helps someone.