After Installing The Theme
If you upload the theme and then activate it, but see nothing but a white screen, please read the following information.
This is more common than you might think, and it can be frustrating to sort out.
First, it is important to understand what the white screen, often referred to as the “white screen of death,” actually means. Simply put, there is an error that you can’t see. The reason you can’t see it is because, WordPress is not displaying the error that is causing the problem. When attempting to diagnose a white screen condition, consider what you did before the condition occurred:
Did you install an upgraded version of WordPress, and did you check to see if the white screen occurred before you installed and activated your theme?
Did you install any plugins prior to installing the theme?
There are several causes for this condition. We will be addressing the ones most likely to occur — Plugins, Theme, and Other Causes.
1. Plugins – No matter how hard developers try, it is impossible to write plugins that will work and play well together with every theme. The same is true in reverse. If you experience the white screen after activating the theme, the problem could be a plugin that is in conflict with the theme. Try the following:
If you can access the admin area of your site, but get the white screen on the front end, login to your admin section and deactivate all plugins. After doing so, check your front end page again. If you can see it, you have a plugin conflict. Now, start activating each plugin one by one. When you see the white screen again on the front end pages, you will know that the last plugin you activated is the likely culprit. Deactivate it and continue checking all remaining plugins one by one to make sure there are no others.
If you are getting the white screen on the front end and the back end admin area, then you will need to access your site via an FTP client. A little known trick is to change the name of your/wp-content/plugins folder to something else temporarily like “plugins.bak.” This will make WordPress ignore your plugins. Then check to see if this resolves the problem. If it does, log into your admin section and then change your plugin.bak folder back to plugins . Then deactivate all of your plugins via your admin page.
2. Theme – The most likely issue associated with a theme being the cause of a white screen condition is when the upload of the theme did not complete the transfer of all files, the transfer resulted in corrupted theme files, or you have PHP configuration memory limits set too low. Try this:
If you can access your admin area disable all plugins as described above, change the theme to one of the WordPress default themes. Check to see if this resolves the problem. If it does, try reinstalling the theme by completely removing the old copy in /wp-content/themes/ and installing a fresh copy. I recommend using FTP to do this because you less likely to run into errors than when you use the HTTP WordPress theme installer. Activate the replacement theme and see if the white screen condition returns.
If you cannot access your admin area, use an FTP client to access your site. Disable your plugins by following step #2 in the plugins instructions above, and delete the theme entirely. This will force WordPress to use the default WordPress theme. See if the problem persists. If it does, then the problem is likely in your WordPress installation. If the problem does not occur, then install a fresh copy of the theme via FTP, activate it and see if the problem reappears.
You may also be suffering from a web server configuration that is set with PHP memory limits too low. If this is the case, it can cause the white screen condition as well. Check with your web hosting service and ask them to increase your PHP memory_limit to at least 64 megabytes. 128 megabytes is recommended.
3. Other Causes I am providing a list of possible other causes of the white screen condition here because they too can cause this error:
Blank space in functions.php – This is easy to do if you’ve been modifying the file. A good way to check is to replace it with the unchanged version of the file and see if the site works.
Blank line in wp-config.php – a blank line at the start of this file can bring on the White Death. Check for extra spaces at the end as well.
File Permissions – Make sure all the directories are set with permission of 755 and the other files 644. This should not happen because the server should inherit the permissions of the files that get uploaded to the server. But we have seen occurrences where, for example, unpacking a ZIP archive using CPANEL and other interface tools botched permissions.
Multiple Plugins – When you’re reactivating your plugins, the first one you find that causes the problem may not be the only one. Sometimes it's a combination of two or more. So you may think you have the problem solved, but it may still exist and come back in the future.
Check your error logs. A good amount of the time, server logs will show *exactly* what php function is causing the issue, and where.
Run a PHP validate on the code prior to saving. It will catch a lot of simple mistakes.
If you just installed WordPress, a WordPress plugin, or a theme for your site and out of nowhere your site returns a 500 Internal Server Error, please read the information below.
If you have been surfing the web for any length of time you have probably encountered a 500 internal server error. These errors are not confined to WordPress. They are generic errors that report very little on what the actual cause is. First, don’t panic. Lot’s of people have been confronted with these errors, and they can be fixed. In fact, I fix them all the time.
There are five major reasons why these errors occur in WordPress:
- Incorrect web server configuration
- Incorrect folder/file permissions
- Corrupt files or files that contain errors in code
- PHP memory limits set too low
- Conflicting third party plugins
1. Incorrect web server configuration – If your web server (whether it be Apache or IIS) is configured with incorrect directives, they can cause 500 errors to occur. The problem is that web hosting support will often blame the error on software you have installed without even checking to see what is contained in their error logs. Just know that after you have checked the following remaining causes, and they fail to resolve the issue, you will need to (sometimes forcefully) get your web host to help diagnose and fix the problem.
2. Incorrect file permissions – With very few exceptions, file permission for WordPress, plugins, and themes need to be set at 755 for folders, and 644 for files. You may think that setting permissions more loosely, like 777, will relieve the problem, but you would be wrong. Setting permissions either too strict or too loose often cause this and other errors.
3. Corrupt files or files that contain errors in code – – Usually improper/errors in file transfers to the web server cause corruption to occur. It may look like the file is sitting there just fine, but something in the process caused the file to be unusable by the server. For example, if you uploaded a text file in binary language instead of ascii it will render the file unreadable by the web server. Coding errors can also create this error, whether that be in WordPress, a plugin, or a theme.
Often, the only way to resolve an error in WordPress core is to reinstall WordPress.
- If it is plugin related, deactivating all plugins will relieve the error.
- If it is theme related, deleting and reinstalling the theme will often take care of the problem.
By far the most common 500 error produced by a file is related to the WordPress .htaccess file. The .htaccess file is primarily designed to be used with custom permalink structures. But it is also used by some third party plugins, and for overriding certain server configuration directives if allowed. If it contains errors, it can return the dreaded 500 internal server error. The .htaccess file is located in the root folder of your WordPress installation (not the theme).
- log into your site via FTP (Filezilla, etc.)
- download a copy of your .htaccess file, rename the copy e.g. “.htaccess-backup”
- delete the .htaccess file residing on your Web server
- create a new blank file called “.htaccess” on your PC/laptop/Mac
- upload this new file to your Web server in the same place as the original .htaccess (which you deleted)
- navigate to your WordPress admin URL, e.g. http://www.yoursite.com/wordpress/wp-admin, and you should now be able to log in!
- finally, once logged in, navigate to the Permalinks settings page in the admin console and do nothing further. Simply going to the settings page should enable WordPress to write the correct .htaccess declarations itself.
- max_execution_time 1200
- memory_limit 128M
- post_max_size 32M
- upload_max_filesize 32M
You should now be able to nagivate to www.yoursite.com or http://www.yoursite.com/wordpress (depending on whether WordPress is running your entire site or just a blog etc.) and all should be well once more.
4. PHP memory limits set too low, There two ways to solve this problem.
You can either get your web host to increase your PHP limits. You can upload your theme via an FTP client. We offer a video tutorial located in the Video section of the forum that explains how to use FTP to install your theme.
5. Conflicting Third Party Plugins Should Be Deactivated
If you can access the admin area of your site, login to your admin section and deactivate all plugins. After doing so, check your front end page again. If it loads without error, you have a plugin conflict. Now, start activating each plugin one by one. When you see the 500 error again on the front end pages, you will know that the last plugin you activated is the likely culprit. Deactivate it and continue checking all remaining plugins one by one to make sure there are no others.
If you are getting the 500 error on the front end and the back end admin area, then you will need to access your site via an FTP client. A little known trick is to change the name of your/wp-content/pluginsfolder to something else temporarily like “plugins.bak.” This will make WordPress ignore your plugins. Then check to see if this resolves the problem. If it does, log into your admin section and then change your plugin.bak folder back to plugins . Then deactivate all of your plugins via your admin page.
Recommended PHP configuration limits are as follows:
You can verify your PHP configuration limits by installing a simple plugin found here. If you still cannot resolve the 500 error, talk with your web hosting support.
If the import stalls and fails to respond after a few minutes, or it fails with a simple error message like “Import failed,” You are suffering from PHP configuration limits that are set too low to complete the process. You should contact your web host and ask them to increase those limits to a minimum as follows:
max_execution_time 3600 max_input_time 3600 memory_limit 256M post_max_size 64M upload_max_filesize 64M max_input_vars 3000
You can verify your PHP configuration limits by installing a simple plugin found here. And you can also check your PHP error logs to see the exact error being returned.
Also if possible update your PHP version to 5.5
After doing this you can reset your database using the WordPress Database Reset Plugin and try to re-import the demo data ( WARNING : Reset the database will make you lost all the data of your current wordpress )
If you still have problem your web host may uses process watching software that prevents bulk processing on their web servers. If you have problem please submit a ticket and we will help you to import the demo.
If you are installing your theme from the WordPress theme installer, but get a message that says "Are you sure you want to do this?", most likely your web server is configure with low PHP settings that only allow a certain size ZIP file to be uploaded via WP admin.
Most hosting companies configureure their servers to only have the maximum file upload size limit at 8-10 MB, some are less. The Alibaba theme ZIP is currently about 34 MB in size which is due to the included plugins and all the demo content. So if you get this error, your web server is rejecting the upload due to the overall size of the Alibaba.zip file. WordPress is unfortunately giving you a rather ambiguous message in response. This is not a theme issue or bug.
There two ways to solve this problem. You can get your web host to increase your PHP limits so a larger zip file is allowed to be uploaded. They will know which limits to set if you explain the issue. You can upload your theme via FTP. View our video tutorial in the Video section of the forum to learn how to install your theme via FTP. It is very easy and efficient.
Recommended PHP configureuration limits are as follows: max_execution_time 60 memory_limit 128M post_max_size 48M upload_max_filesize 48M