Blank or Partially Rendered Pages

From WHMCS Documentation

If at any time you encounter a blank or partially rendered page in your WHMCS installation, this indicates a fatal PHP error is occurring which stops the execution from being able to continue. This page covers the most common causes of these problems, how to identify them and methods for resolution.

The display of error information is disabled by default. The Error Management documentation provides in-depth information regarding the default error behaviors and optional settings of WHMCS.

Enabling Display Errors while your installation is accessible to end users may lead to potential security risks due to the information within the error message details. If you enable Display Errors for debugging purposes, don't forget to turn it off again!

Getting Error Information

The WHMCS Error_Management system includes many useful options. The Display Errors option allows you to view additional information about critical errors.

When Should You Enable Display Errors

The Display Errors option provides additional information when you experience a critical error that results in one of the following issues:

  • Friendly "Oops!" pages
  • Entirely blank pages
  • Partially rendered pages

In most cases, use the Log Errors and SQL Debug Mode options first. These options will usually capture the same information that the Display Errors option renders. In the event that these options are not viable or do not yield any information, Display Errors is a good alternative.

The Display Errors option is very helpful. However, it will show your error information to anyone who is encountering the same error condition. Avoid showing errors to visitors or non-privileged staff whenever possible.

Typical Causes

Some of the most common causes of "Oops!", partial, or empty page rendering include:

  • Missing or corrupted files or incomplete uploads.
  • The server doesn't meet the minimum system requirements.
  • PHP, Apache or ionCube Loader®-related errors.
  • Incompatible hooks or addons.
  • Syntax errors in custom modules, hooks, or templates.

Enabling Error Reporting

Enabling From The Admin Area

If the admin area still allows you to navigate to General Settings, follow the steps below to enable error display. Then, retry the steps that previously led to the blank or partially rendered page. The system will display additional error information.

  1. Navigate to Configuration () > System Settings > General Settings > Other or, prior to WHMCS 8.0, Setup > General Settings > Other.
  2. Select the Display Errors checkbox at the bottom of the page.
  3. Click Save Changes.

Remember to disable Display Errors when you are finished troubleshooting. Leaving error display enabled can be a security concern.

Enabling From Your Configuration File

If the error is severe enough, you may not be able to log in to the admin area. In those situations, there is a manual configuration file flag option that you can add to the configuration.php file in the WHMCS root directory to enable error reporting.

Add the lines to the end of the configuration.php file. This will be immediately before the closing PHP tag (?>) if your configuration.php file has one. If it doesn't, this will be after the last line in the file.

$display_errors = true;

After adding the lines and saving and uploading the file, retry the steps that previously led to the blank or partially rendered page. The system will display additional error information.

Remember to disable Display Errors when you are finished troubleshooting. Leaving error display enabled can be a security concern.

Disabling Error Reporting

Disabling from the admin area

If you enabled error reporting via the admin area, make sure to follow the steps below after you finish troubleshooting:

  1. Navigate to Configuration () > System Settings > General Settings > Other or, prior to WHMCS 8.0, Setup > General Settings > Other.
  2. Deselect the Display Errors checkbox at the bottom of the page.
  3. Click Save Changes.

Disabling from the configuration.php file

If you enabled error reporting via the configuration.php file, make sure to remove the following line from the configuration.php file after you finish troubleshooting.

$display_errors = true;

Sometimes, you may also see the following lines in configuration.php file:

$display_errors = E_NOTICE;
$display_errors = E_ALL;

As a precaution, remove any lines starting with $display_errors from the configuration.php file.

PHP Warnings and Notices

If the Display Error options are disabled and you're still seeing warning messages, it indicates the Error Reporting level in your server's PHP configuration is too high. This is a PHP configuration level issue. Shared hosting or reseller users may require the assistance of the hosting provider.

If you have sufficient access and have configured your server to use WHM for administration, follow these steps:

  1. In WHM, navigate to Software >> MultiPHP INI Editor.
  2. Click the Editor Mode tab.
  3. Select your PHP version from the Select a PHP version menu.
  4. Scroll down to the error_reporting setting.
  5. Change the value to the following string:
E_ALL & ~E_WARNING & ~E_USER_WARNING & ~E_NOTICE & ~E_USER_NOTICE & ~E_STRICT & ~E_DEPRECATED & ~E_USER_DEPRECATED

Further Troubleshooting Steps

Client Area Only

If the admin area is loading correctly and only the client area is blank this suggests the template folder missing or the /templates_c folder invalid path/not writeable.

To resolve this:

  • Re-select the template at Configuration () > System Settings > General Settings or, prior to WHMCS 8.0, Setup > General Settings. Then, click Save Changes.
  • Ensure the templates_c has the appropriate permissions and ownership values so it's writeable by the script (usually CHMOD 755, but in some environments CHMOD 777 may be required).
  • If the /templates_c directory has been moved to a custom location ensure the path is correct in the configuration.php file. Your server admin/hosting provider will be able to confirm this.

Admin Login Page Only

The admin login page does not involve templates, so seeing a blank page here suggests a problem with the Ioncube configuration on your server. You can download the Ioncube Loader Wizard from http://www.ioncube.com/loaders.php and upload to your whmcs directory, then visit it in your browser. Your server admin/hosting provider will need to resolve any errors it identifies.

If it reports Ioncube is installed correctly please ensure display_errors is enabled in the server's PHP configuration as this may be suppressing out error messages WHMCS is trying to output with the display_errors line in the configuration.php file detailed above.

Problematic custom widgets may also cause a blank page. Try removing any non-standard files from the /modules/widgets directory.

Oops! or Blank Pages Elsewhere

If blank pages are occurring on all pages, please try all the above steps, particularly enabling display_errors. If none of the above resolves the issue review any custom files in the following locations and ensure there are no blank spaces or carriage returns outside the <?php and ?> tags:

  • /configuration.php
  • /includes/hooks/
  • /modules/admin/
  • /modules/addons/
  • /modules/registrars/
  • /modules/servers/
  • /modules/widgets/
  • /lang/
  • /lang/overrides/
  • /admin/lang/
  • /admin/lang/overrides/

It may be necessary to remove any custom files from these locations temporarily, if doing so resolves the issue then you can add them back one-by-one until the problem re-occurs, you can then contact the vendor of the offending file for a fix.

If none of the steps on this page fix the problem then please contact our support team for assistance. In your support ticket please include the attempts you have made to resolve the issue, instructions to reproduce the blank page and FTP/SFTP access.