“WP-Admin Dashboard Display Error” How to fix it?

“WP-Admin Dashboard Display Error” How to fix it?

In today`s post, we take a look to fix “WP-Admin Dashboard Display Error”. If you found that your WordPress website dashboard is looking strange and things are not loading properly or everything inside admin is not working or displaying, You should follow this step by step guide to solve the error.

Why you are getting this Error?

This error relates to “CSS” When your admin CSS will not load properly you will encounter this error. Most of the time you get this error after upgrading your WordPress website or installing/updating any Plugin. If you recently updated WordPress, then most likely it`s not updated properly and your wp-admin or wp-includes folder files are corrupt now.

Luckily, we’ve come up with 7 simple solutions to fix your site`s Wp-Admin Dashboard Display Error. So let’s just fix it, shall we?

Solution 1: Firewall or a Proxy Connection

You should check your internet connection, if your internet connection is behind a proxy or firewall you will encounter this error. Sometimes Proxy connection or firewall block CSS files to load and this is the reason you see the dashboard without usual formatting.

If you check and found any Proxy or Firewall enabled, you should disable it. To Disable a Proxy or Firewall in Windows operating system you can check this guide: How To Disable Proxy Firewall. After disabling Proxy or Firewall you should try to delete cookies and cache, to open menus to clear cache, cookies, or history you can press Ctrl-Shift-Delete (Windows) or Command-Shift-Delete (Mac).

Now you can check your site admin if everything fixed now.

Solution 2: Switch to Twenty Eleven Theme

You can switch your theme to Twenty Eleven which is a default WordPress theme, by theme switching you can remove any Theme Specific problem which prevent to load CSS files properly. Change your theme and check if this solve your problem.

Solution 3: Reset Plugin Folder by FTP

If you have installed any admin specific plugin to manage Admin Menu or Custom Admin Theme you should deactivate those plugins and check if this fix the error. If this does not work you should try to reset plugin folder by FTP, Below are steps to reset the Plugin Folder…

  • You can connect via any FTP client to access all your WordPress directory files.
  • After connecting with server, now navigate to wp-contents directory.
  • Find “plugins” folder and rename this folder to “plugins-reset”.
Reset plugin folder via FTP

Reset plugin folder via FTP

  • Create a new folder “plugins” under same directory wp-contents.

Now refresh the WordPress wp-admin page and check if this solve the error. If you found everything working properly, then it is one of the plugins that is generating the error.

To fix this you should go back to FTP and delete the newly created “plugin” folder and change the “plugin-reset” folder back to “plugins”. Now when you navigate to plugin menu under wp-admin dashboard you may find all plugins disabled, activate your plugins one by one to find out the plugin which is not compatible. Once you get the plugin which is causing this error deactivate and delete it.

Solution 4: Re-upload wp-includes and wp-admin Folders via FTP

First thing we recommend before starting this solution to make a backup of your WordPress website. After making a backup you should download the matching version of files from WordPress Release Archive.

After downloading WordPress zip to your desktop and extracting the zip archive, you should connect to your website using your FTP client.  Once connected with your site you can see all directories inside FTP, now navigate and select folders “wp-includes” and “wp-admin” from your desktop to replace old folders in FTP directory.

Re-upload wp-includes and wp-admin Folders via FTP

Re-upload wp-includes and wp-admin Folders via FTP

Once your FTP client start uploading files from your computer to server it will show a pop up and ask that “Target File already Exist”, Select Overwrite and check the box always use this action to upload all files properly.

Select Overwrite in Filezilla Upload

Select Overwrite in Filezilla Upload

Once you have uploaded all files, simply go to WordPress admin area and refresh the page, you may find everything working now.

Solution 5: Increase PHP Memory

Connect with your site through any FTP client and download wp-config.php file which is located in the root WordPress directory, now try adding the code which is given below to your wp-config.php file and save the file.

define('WP_MEMORY_LIMIT', '64M');
Increase PHP Memory Limit in WordPress

Increase PHP Memory Limit in WordPress

Now, we just increased the memory limit to 64M. If you are unable to change memory limit you should contact your host to increase the memory limit by php.ini file.

If you have access to your plugin area you can also, download this free Memory Bump plugin to increase memory of your WordPress site.

Solution 6: Use CONCATENATE SCRIPTS

You can connect via FTP client and open the directory wp-admin, now search for the file “load-styles.php” and download it to your PC. Make a backup of this file and open the file with notepad or notepad++, now search and find this line in load-styles.php file

error_reporting(0);

…Replace this line to this…

error_reporting( E_ALL | E_STRICT );

Now upload and overwrite “load-styles.php” file in ftp, and then simply refresh your WordPress admin screen few times and you can see the CSS styles come back to Normal.

You can also add the code given below to your “wp-config.php” file with FTP and it will do the same thing.

define( ‘CONCATENATE_SCRIPTS’, false );
define( ‘SCRIPT_DEBUG’, true );

Solution 7: Fix any possible blank space in your wp-config file.

With Help of your FTP client you can download “wp-config.php” from Website directory, Now you can open and review this file in Notepad or Notepad++ to check the ending lines of the file.

Compare this…

    <?php
    // ** MySQL settings ** //
    define('DB_NAME', 'putyourdbnamehere');    // The name of the database
    define('DB_USER', 'usernamehere');     // Your MySQL username
    define('DB_PASSWORD', 'yourpasswordhere'); // ...and password
    define('DB_HOST', 'localhost');    // 99% chance you won't need to change this value
    define('DB_CHARSET', 'utf8');
    define('DB_COLLATE', '');
     
    // Change each KEY to a different unique phrase.  You won't have to remember the phrases later,
    // so make them long and complicated.  You can visit http://api.wordpress.org/secret-key/1.1/
    // to get keys generated for you, or just make something up.  Each key should have a different phrase.
    define('AUTH_KEY', 'put your unique phrase here'); // Change this to a unique phrase.
    define('SECURE_AUTH_KEY', 'put your unique phrase here'); // Change this to a unique phrase.
    define('LOGGED_IN_KEY', 'put your unique phrase here'); // Change this to a unique phrase.
     
    // You can have multiple installations in one database if you give each a unique prefix
    $table_prefix  = 'wp_';   // Only numbers, letters, and underscores please!
     
    // Change this to localize WordPress.  A corresponding MO file for the
    // chosen language must be installed to wp-content/languages.
    // For example, install de.mo to wp-content/languages and set WPLANG to 'de'
    // to enable German language support.
    define ('WPLANG', '');
     
    /* That's all, stop editing! Happy blogging. */
     
    if ( !defined('ABSPATH') )
    define('ABSPATH', dirname(__FILE__) . '/');
    require_once(ABSPATH . 'wp-settings.php');
    ?>

and this…

    <?php
    // ** MySQL settings ** //
    define('DB_NAME', 'putyourdbnamehere');    // The name of the database
    define('DB_USER', 'usernamehere');     // Your MySQL username
    define('DB_PASSWORD', 'yourpasswordhere'); // ...and password
    define('DB_HOST', 'localhost');    // 99% chance you won't need to change this value
    define('DB_CHARSET', 'utf8');
    define('DB_COLLATE', '');
     
    // Change each KEY to a different unique phrase.  You won't have to remember the phrases later,
    // so make them long and complicated.  You can visit http://api.wordpress.org/secret-key/1.1/
    // to get keys generated for you, or just make something up.  Each key should have a different phrase.
    define('AUTH_KEY', 'put your unique phrase here'); // Change this to a unique phrase.
    define('SECURE_AUTH_KEY', 'put your unique phrase here'); // Change this to a unique phrase.
    define('LOGGED_IN_KEY', 'put your unique phrase here'); // Change this to a unique phrase.
     
    // You can have multiple installations in one database if you give each a unique prefix
    $table_prefix  = 'wp_';   // Only numbers, letters, and underscores please!
     
    // Change this to localize WordPress.  A corresponding MO file for the
    // chosen language must be installed to wp-content/languages.
    // For example, install de.mo to wp-content/languages and set WPLANG to 'de'
    // to enable German language support.
    define ('WPLANG', '');
     
    /* That's all, stop editing! Happy blogging. */
     
    if ( !defined('ABSPATH') )
    define('ABSPATH', dirname(__FILE__) . '/');
    require_once(ABSPATH . 'wp-settings.php');
    ?>
    .

It should always show the closing tag like this “?>” at the end of codes,  if you found anything after this ending line you must delete it. Sometimes an extra blank line or dot after the closing tag cause the whole error.

I hope this has been a helpful guide to fix “WP-Admin Dashboard Display Error”. If nothing works or if any of the above solutions fixed this problem for you, then share your thoughts in comments?