Includes free SSL certificate, unlimited bandwidth & fully optimised for WordPress.
Fully PCI-DSS compliant hosting, backups every 4 hours & free DDoS protection.
Unlimited bandwidth, WHM & cPanel control panel & fully white label.
Great value domain names available.
Create a professional looking website in minutes. Over 190 templates.
Speed up the delivery of your site.
Beautifully Simple. Massively Configurable. Scales from 1 VPS cloud, all the way up to a load balanced cluster.
Fully managed, high-spec dedicated servers deployed on our gigabit network, backed by our superior 24/7 UK support.
For our clients only. Open a ticket you can track and reply to.
Instantly talk to one of our support team, we're here to help.
Talk to us: 020 8050 1337 (Monday–Friday 9am – 8pm)
Business plans have access to 24/7 emergency phone support.
Search our extensive archive of guides to help you with your hosting account.
or go directly to our support site:
This article will show you how to centralise the reporting of PHP errors to a single error_log. This can make debugging a much more pleasant experience.
Define a central error_log
Most websites load a configuration file or header file before anything else. Quite often, this is called index.php and it lives in the public_html directory. Simply add the following lines of code immediately after the opening <?php tag
Simply replace [cpanel_username] with your cPanel username e.g. if your username was krystald you would add:
This will cause all errors to be recorded into error_log in your home directory.
Remember, there may be parts of your website (maybe the administration section) that don't load the index.php file in public_html, so you may have to add this directive to other initiation scripts to capture everything.