Control whether PHP technical faults are visible to public visitors or hidden during active site maintenance.
If PHP errors are appearing on your website, you can control whether they’re displayed to visitors through your PHP configurations. For a production website, display_errors should normally be turned off so that sensitive technical infrastructure information isn’t exposed publicly. This guide shows you how to securely manage this setting via cPanel on your 1-grid hosting account.
Before You Begin
Before changing your systemic environment paths, make sure you have the following requirements ready:
- Access to your 1-grid Customer Zone
- A web hosting account running a cPanel dashboard control panel
- Clear identification of the exact domain name you want to configure
💡 Tip: If you are actively debugging a platform conflict, turning off public display parameters does not repair the code fault. It simply prevents raw error strings from breaking your public user interface experience.
Change Your PHP Error Display Setting
1. Open Your Hosting Account
Log in to your 1-grid Customer Zone and navigate to your active environment dashboard:
Go to: Services → Hosting
Select the web hosting package associated with your target domain.
2. Open MultiPHP INI Editor
Locate your account actions panel and click the Login to cPanel shortcut link. Once the control panel initialises, navigate down to the Software section cluster and click MultiPHP INI Editor.
3. Select Your Domain
Ensure you are operating in Basic Mode. Click the dropdown menu interface to choose the specific domain name you need to manage. The platform will instantly render your active PHP runtime directives below.
4. Configure display_errors
Scroll down the alphabetically mapped directive grid to locate the display_errors setting line item. Toggle the option based on your operational requirements:
- On: PHP compilation errors, warnings, and notice strings will publish directly into your live website page layouts.
- Off: All underlying script errors are entirely masked from front-end website visitors.
⚠️ Security Best Practice: For operational live sites, always keep this directive configured to Off. Only toggle it to On temporarily inside a closed development window to pinpoint active code breaks.
5. Save Your Changes
Scroll to the absolute bottom of the editor configuration frame and click Apply. Wait for the green system confirmation alert to deploy before attempting to run testing updates on your web pages.
6. Check Your Website
Open a clean incognito or private browsing window and navigate to the affected web page routes to audit your updates. Confirm that:
- Your underlying website architecture loads normally without layout clipping.
- Your specific developer testing scripts run correctly.
What Happens Next?
Toggling display_errors strictly controls the presentation layer on the browser client side; it does not affect internal server logging mechanisms.
- Behind-The-Scenes Logging: Your background applications will continue compiling diagnostic data safely into your server folder architecture if error logging remains enabled.
- Safer Troubleshooting: This decoupling enables you to actively troubleshoot code-level faults by reading system logs via How to View PHP Error Logs while keeping your customer-facing experience professional and clean.
You’re Ready!
Your domain’s runtime PHP display configuration parameters are now fully updated inside your 1-grid hosting setup. Maintain a strict “Off” status baseline for production assets, and lean on discrete system files for your routine technical diagnostics.
Related Articles
Need Help?
If PHP error text lines continue publishing out to front-end page layouts after applying your saves, or if your site throws unexpected HTTP faults, contact us. Our support Team is ready to see how we can assist with reviewing your root runtime pathing.
To ensure our technical agents can investigate your hosting configuration environment quickly, please provide:
- Your domain name and active hosting package type
- Your active PHP version selection
- A screenshot of your current MultiPHP INI Editor settings
- A screenshot or copy of the specific error string and its active URL route
- Excerpts from your internal
error_logfolder (if available)