I'm trying to install Drupal 7.34 on a VPS (on NodeServ): I followed the guidelines in the file INSTALL.txt, and I managed to reach correctly the last page of the installation script, where I fill the database parameters and.
. the site configuration when clicked every time, returns blank page. current community. chat. Drupal Answers. Site Configuration returns blank page. showing blank page in drupal 7? Blank Page when installing Drupal 7. Today I wanted to install Drupal 7 manually from the root of a subdomain. As it turned out I hadn’t used CHMOD to modify permissions of the Drupal Core files when I’d copied them.
![Drupal 7 Install Blank Page Drupal 7 Install Blank Page](http://images.sixrevisions.com/2010/11/23-07-admin_menu_module.jpg)
- . '> This procedure is based on the Mollom 2.x module for Drupal 7. </aside> Use the procedures on this page to install and configure Mollom for. Installing Mollom for Drupal 7. Installing Mollom for Drupal 8.
- Wiki Page: Multisites Using Drupal 7. Install Drupal 7 the normal way on the first domain. you could have blank pages because drupal will search for the template in the wrong file.
- This guide covers preparing for installation. If you need hosting, consider selecting one of these web hosts. For help with Drupal terms, see the glossary page. There is also information about Drupal distributions.
- Installation problem. Posted by lgreer on December 7. (I had been deleting the install. Drupal 7 Layout and Theming Workshop | Isovera | Waltham, MA.
- Install Drupal package from the Ubuntu repositories. An adjustment to the error reporting is required for the install.php page to come up properly. Drupal 7 will only support MySQL 5.0.15 or higher.
Blank pages or "white screen of death" (WSOD)Occasionally a site user or developer will navigate to a page and suddenly the page content disappears, and it becomes blank. No content. No errors. Nothing. This happens sometimes, It could happen after updating a module, theme, or Drupal core. This is what is referred to by most members of the Drupal community as the White Screen of Death or WSOD. There are several reasons why this might occur, and therefore several possible solutions to the issue.(Note: The suggestions on this page might solve the problem even when you do not get the WSOD as it relates to an Internal Server Error.)"Invisible" Errors. If error reporting is turned off, you could be getting a fatal error but not seeing it. On a production site, it is common to have error reporting turned off.
If that is the case and PHP has hit an unrecoverable error, neither an error nor content will be displayed, therefore you end up with a completely blank page. What you can do about this is either turn on PHP error reporting so it displays a message on the page itself, or check your log files (from the server) to look for the error.
How to do both of these are explained below. Enable Error Reporting. Although it may be turned off on commercial hosts and production sites (for good reason, so that users do not see the errors), these errors are one of your best tools for troubleshooting. To enable error reporting, temporarily edit your index. PHP tag (do not edit the actual file info!) to add the following: < ? E_ALL). ini_set('display_errors', TRUE). TRUE). // $Id: index.
You will now be able to see any errors that are occurring directly on the screen. Memory problems may still not be displayed, but it's the first step in a process of elimination. If you are using a multi- site setup and only want errors to appear for one site, then check the name of the host first as in: if ($_SERVER['HTTP_HOST']==='some. E_ALL). ini_set('display_errors', TRUE). TRUE). If the problem occurs while running update. FALSE). Change the shutdown handler.
![Drupal 7 Install Blank Page Drupal 7 Install Blank Page](http://refaktorthemes.com/themeforest/haiku/haiku-mobile.png)
![Drupal 7 Install Blank Page Drupal 7 Install Blank Page](http://redcrackle.com/sites/default/files/images/20151403192845.jpg)
Another way to force errors to display is to change the shutdown handler. Add the following code (originally from http: //stackoverflow. Display Errors. // - -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -. On'). ini_set('html_errors', 0).
Error Reporting. // - -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -. Shutdown Handler. Shutdown. Handler(). Error. Handler', $error)). TRUE). register_shutdown_function('Shutdown. Handler'). // - -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -.
Error Handler. // - -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -. Error. Handler($type, $message, $file, $line). ERRORS = Array(. 0x. E_ERROR'. 0x. 00.
E_WARNING'. 0x. 00. E_PARSE'. 0x. 00. E_NOTICE'. 0x. 00.
E_CORE_ERROR'. 0x. E_CORE_WARNING'. 0x. E_COMPILE_ERROR'.
E_COMPILE_WARNING'. E_USER_ERROR'. 0x. E_USER_WARNING'. 0x.
E_USER_NOTICE'. 0x. E_STRICT'. 0x. 10.
E_RECOVERABLE_ERROR'. E_DEPRECATED'. 0x. E_USER_DEPRECATED'. ERRORS)))). $name = 'E_UNKNOWN'. Error in file \x. BB%s\x. AB at line %d: %s\n", $name, @basename($file), $line, $message))). Error. Handler").
Log Files. Your log files can be accessed a few different places. This will vary depending on your host, but it's good to know what and where they are. To access the files directly on a server running Apache, on some unix shells (you may need to alter this to suit your environment), you can type the following command: tail /var/log/apache. For nginx, depending on your .
To check that you are looking at the right file, you may wish to type the following commands to find where the log files are. Error. Log' /etc/apache.
Error. Log' /etc/apache. Otherwise, if you are still able to access your admin pages through your site, which you often can during a WSOD, check the watchdog log for errors. For example you may see the 'headers already sent' error, which relates to the whitespace error (explained in the next section). The path to your watchdog log, should you lose your admin menu is: Your results will vary in different hosting environments, but this is a good starting point. Whitespace at the End of a PHP File.
The most common code error that causes a WSOD is having additional whitespace at the end of a PHP file. To avoid this issue, it is a Drupal coding standard to not include the closing ?> on a PHP file. You may also have the 'Include Unicode Signature (BOM)' option turned on on your editor, which should be turned off. PHP4 Syntax Errors and Incompatibility.
Some versions of PHP4 gag on some function declaration syntax. Here are examples of syntax that fails: function media_mover_api_media_mover($op, $action = null, $configuration = null, & $file = array(), $running_config = null ) { .. NULL, $a. 4 = NULL) { .. This appears to be a bug in PHP4 parser that makes it not be able to handle either too many "=" clauses in a function declaration or handle "& $.." So in at least some cases, this is a de facto PHP4 incompatibility. Solution: Upgrade to PHP5. PHP Versions. If you were previously running Drupal on a server with multiple versions of PHP you may have had special code in your .
Drupal which version to use. For instance, you may have added Add. Type x- mapp- php. PHP5 was used rather than PHP4. If that is the case, remove this line in your .
Invisible Errors for Developers. If you are developing a module, you may first want to test loading your file(s) to make sure that there aren't any obvious PHP syntax errors. This happens because the include_once() or require_once() function calls simply do not always report the errors [if someone knows why and has a fix for that one, please add the info here!]. The following is the command you want to run on your system (it requires PHP console, or CLI, to be installed): $ php - l < filename>. This command will ask PHP to parse your file. If you forgot a semi- colon "; ", or a closing bracket "}" it will give you the error immediately.
Fix it, and try again on your server. Additionally, you can do check all *.
On *nix, run: $ find . Better yet, you may want to write an automated test to check for such errors.
More info about Simpletest here. Implement Hook Twice. You can also get a blank screen if you have by mistake implemented the same hook more than once. For example, accidentally implementing hook_help twice.
Output Buffering. Some modules need output buffering turned on. To do this, try adding these lines to your . On. php_value output_handler mb_output_handler. Zend Compatibility Mode.
If you get the WSOD while setting up a new server, you may have a problem with zend compatibility being on. If you check the error reporting you may see an error with "Trying to clone an uncloneable object of class mysqli." This is caused by the zend compatibility mode being On in the php. To fix this, set zend compatibility to off by editing the applicable line: ; Enable compatibility mode with Zend Engine 1 (PHP 4.
Off. More detail about zend compatibility can be found here. Clearing the Cache Table. Depending on the problem, clearing the cache table (via phpmyadmin for example) can resolve a WSOD. Restarting Web server. WSOD can be caused by web server issues. Especially if you are using apache and PHP fails with error "undefined function: drupal_bootstrap() in .. Ionic Rewriter: WIMPIf you are using Drupal on a WIMP stack and getting the WSOD on the http: //www.
Ionic Rewriter ISAPI module installed in IIS during the Drupal install. The solution in this case is to add it in after install is completed. Malformed ctools plugins.
Some malformed ctools plugins (for example custom panel layouts) can cause a WSOD. If you have any custom ctools plugins, try disabling them to see if they are the issue. PHP Memory Limits. Another common reason for the WSOD is issues with memory limit. Traditionally, this has most often been a problem showing up (or rather, not showing up) in the modules admin screen, by it giving a WSOD. This issue has pretty much been solved for that page; however, there are still instances that will occur in other modules (usually showing up during admin actions like bulk updates) where PHP memory can be exhausted.
Try the solutions here first if this issue came up when you tried to go to the module page. You may also want to try running the update. If you do not know how to run update. Next, you'll want to confirm that the change has had an effect with a phpinfo() page. If you are hosting the site and it didn't work, check that you were modifying the correct php. If your site is hosted by someone else and you failed to increase the memory limit, then your host has probably locked it down (for good reason) and you'll have to negotiate with them.
There may be a few work- arounds to try, like creating a custom php. PHP execution time limits. Another PHP setting that can lead to WSOD is max_execution_time.
Apparently, on WAMP, the default is 3. Change this setting (see other sections on this page for instructions on how to change PHP settings in php. WSOD problems. Module and Theme Related Errors.
If the error is not originating from a memory limit, or any of the above errors, the error may be coming from bad code in a module or your site's theme. Theme or module lacking.
Check if the theme needed for your site is in drupal. If you use a multisite installation, the latter is drupal. Especially if you use a sub- theme, check if both the master theme and the sub- theme are there, with the right names and read permission. The same way, modules required by your site must be present in drupal.
Non- recommended Module Versions.