PHP error reporting – difference between E_ALL, E_ALL & ~E_NOTICE & ~E_ALL

I’m confused about this settings. What are the differences?

Here, I’m talking about the basic idea behind php error reporting. This is a PHP function which defines how PHP report errors to server error logs. The error_reporting() function sets the error_reporting directive at runtime. PHP has many levels of errors, using this function sets that level for the duration (runtime) of your script.

Did you ever face this problem on your cPanel account? The disk space increasing inadvertently without any reasons. Mostly this occurs due to the high usage on your website error logs, php related errors causing this issue. Here we need to find a permanent solution for this issue. The high disk usage is just because of large error logs on the account.

Explanations

E_ALL : Everything

E_ALL & ~E_NOTICE : Report all errors except E_NOTICE

~E_ALL : Stop all

E_NOTICE :: This will be helpful to analyze programming related errors. Please check this for more details >> error_reporting <<

So you can change the error reporting from E_ALL to other. Cool!!

How can I change this from cPanel account?

If your server has CloudLinux and installed PHP selector you can set this settings from the cPanel itself. Please follow the steps pasted below:

1. Log into cPanel.

2. Move to “cPanel >> Software and Services >> Select PHP Version.”

3. Click on “Switch To PHP Settings.”

Select PHP Version

4. You can set/change error_reporting from there.

Select PHP Version1

If it’s not listed there, please contact your host. If the server does not support Cloud Linux and PHP selector, you can set this from the PHP configuration or by adding php.ini file.

More about Cloud Linux technology

CloudLinux is a Linux based Operating system especially used in a shared environment which isolates each user in its own light weight virtualized environemnts (LVE) which consumes predefined amount of resources allocated for each user. That is, each user will be in a caged environment.

The resource usage of any user won’t affect the stability of another users. Each user will be allocated a specific amount of resources. If a user’s PHP script utilizes the entire resources allocated to it, then it won’t affect other users. Only that particular user will face problems related to this. That particular user will get a “Resource limit reached” error while he access his website. Read more related posts from Cloud Linux

Post navigation

Arunlal A

Senior System Developer at Zeta. Linux lover. Traveller. Let's connect! Whether you're a seasoned DevOps pro or just starting your journey, I'm always eager to engage with like-minded individuals. Follow my blog for regular updates, connect on social media, and let's embark on this DevOps adventure together! Happy coding and deploying!

4 thoughts on “PHP error reporting – difference between E_ALL, E_ALL & ~E_NOTICE & ~E_ALL

  1. This error is very much common in Windows 7 and I have faced this issue for a few times and this error is mainly categorized under the Windows update error and it can easily be solved by just updating the Windows properly and reinstalling the printer.

  2. Your article has piqued my interest. This is definitely a thinker’s article with great content and interesting viewpoints. I agree in part with a lot of this content. Thank you for sharing this informational material.

  3. Thank you very much … I have one query regarding PHP.

    when running ‘php -v’ in command line, it runs into the error as as follows:

    “ea-php56” is not an EA4 SCL PHP

    . Can you guide me about this, this the apache logs:
    [Sat Apr 20 07:16:55 2019] [error] [client xxxxxxxx] \xe2\x80\x9cea-php56\xe2\x80\x9d is not an EA4 SCL PHP

  4. Delete your browser’s cookies, check the .htaccess file. If they are not sufficient to fix the error, then contact ISP or Hosting Provider or contact CMS provider.

Leave a Reply

Your email address will not be published. Required fields are marked *