Remove php error message

Remove warning messages in PHP

Solution 3: To suppress warnings while leaving all other error reporting enabled: Solution 4: If you don’t want to show warnings as well as errors use Error Reporting — PHP Manual Question: I am running a script where a url parameter is increasing by 1. On github of codesniffer project you can find PSR2 ruleset: https://github.com/squizlabs/PHP_CodeSniffer/blob/master/src/Standards/PSR2/ruleset.xml Solution 3: Because I have a large nubmer of files and probably some excludes, it seems a good idea to define my own ruleset.

Remove warning messages in PHP

I have some PHP code. When I run it, a warning message appears.

How can I remove/suppress/ignore these warning messages?

You really should fix whatever’s causing the warning, but you can control visibility of errors with error_reporting() . To skip warning messages, you could use something like:

error_reporting(E_ERROR | E_PARSE); 

You can put an @ in front of your function call to suppress all error messages.

To suppress warnings while leaving all other error reporting enabled:

error_reporting(E_ALL ^ E_WARNING); 

If you don’t want to show warnings as well as errors use

// Turn off all error reporting error_reporting(0); 

How to Remove Warning Messages in PHP, Use the @Sign Here is another simple method of removing warning messages with PHP. All you need to do is to put @ in front of the function you intend to run. Here is an example: @theFunctionHere (); How error_reporting Works In PHP, the error_reporting function allows setting the type of error reporting that the …

Ignore warning and carry on

I am running a script where a url parameter is increasing by 1. Every so often, I get the error message below and the script comes to a halt:

Warning: file_get_contents (https://example.com?id=431): failed to open stream: HTTP request failed! HTTP/1.1 429 Please retry after few minutes

$i = 1; while($file = file_get_contents('https://example.com?id='.$i)) < echo ''.$i.'
'; $i++ > 

While I know I can use error_reporting(0); to stop the warnings from appearing, my question is as follows: will the script continue running after the hidden warning?

You can, of course, disable error reporting as others have suggested. However, there are two MUCH better solutions.

First, you could use set_error_handler to create a function which converts errors into exceptions (code in Example 1 here: http://php.net/manual/en/class.errorexception.php). Then, you can simply use a try and catch to check to see if an exception has occurred, and handle it appropriately. See here: http://php.net/manual/en/internals2.opcodes.catch.php

Another solution would be to use PHP’s cURL library (http://php.net/manual/en/book.curl.php). cURL will let you check if an error has occurred when you make an HTTP request, and you can respond appropriately .

To be clear, since it seems to be OP’s only concern: both of these solutions will allow the script to continue running after an error has occurred. They also have the added benefit of allowing OP to create code that makes a predetermined programmatic response to errors rather than just blindly ignoring any and all errors with unknown results (and no indication that they even happened).

Finally, a note that’s applicable to this particular situation: HTTP 429 is «too many requests,» which makes sense given that OP is placing these requests one after another with no delay. Sleeping (http://php.net/manual/en/function.sleep.php) between HTTP requests would likely eliminate the problem entirely.

This is not something you should use in prod, but try:

error_reporting(E_ERROR | E_PARSE); 

I think it is better to check if the file is reachable before trying to read it.

Источник

How to remove warning and error messages in PHP

Error warnings for PHP are helpful during development, where you can use them for debugging. Showing the same errors and warnings in a production environment could pose a security risk as it could expose sensitive and exploitable information about the system.

Warning and error reporting in PHP are configured via the display_error error_reporting directives. display_error defines if errors are displayed at all, while error_reporting allows you to specify the type or level of errors to show.

Steps to remove error and warning messages in PHP:

$ sudo vi /etc/php/7.4/apache2/php.ini

; This directive controls whether or not and where PHP will output errors, ; notices and warnings too. Error output is very useful during development, but ; it could be very dangerous in production environments. Depending on the code ; which is triggering the error, sensitive information could potentially leak ; out of your application such as database usernames and passwords or worse. ; For production environments, we recommend logging errors rather than ; sending them to STDOUT. ; Possible Values: ; Off = Do not display any errors ; stderr = Display errors to STDERR (affects only CGI/CLI binaries!) ; On or stdout = Display errors to STDOUT ; Default Value: On ; Development Value: On ; Production Value: Off ; http://php.net/display-errors display_errors = On

Set the value to On instead to further tune the types of messages to display using error_reporting directive.

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; Error handling and logging ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; This directive informs PHP of which errors, warnings and notices you would like ; it to take action for. The recommended way of setting values for this ; directive is through the use of the error level constants and bitwise ; operators. The error level constants are below here for convenience as well as ; some common settings and their meanings. ; By default, PHP is set to take action on all errors, notices and warnings EXCEPT ; those related to E_NOTICE and E_STRICT, which together cover best practices and ; recommended coding standards in PHP. For performance reasons, this is the ; recommend error reporting setting. Your production server shouldn't be wasting ; resources complaining about best practices and coding standards. That's what ; development servers and development settings are for. ; Note: The php.ini-development file has this setting as E_ALL. This ; means it pretty much reports everything which is exactly what you want during ; development and early testing. ; ; Error Level Constants: ; E_ALL - All errors and warnings (includes E_STRICT as of PHP 5.4.0) ; E_ERROR - fatal run-time errors ; E_RECOVERABLE_ERROR - almost fatal run-time errors ; E_WARNING - run-time warnings (non-fatal errors) ; E_PARSE - compile-time parse errors ; E_NOTICE - run-time notices (these are warnings which often result ; from a bug in your code, but it's possible that it was ; intentional (e.g., using an uninitialized variable and ; relying on the fact it is automatically initialized to an ; empty string) ; E_STRICT - run-time notices, enable to have PHP suggest changes ; to your code which will ensure the best interoperability ; and forward compatibility of your code ; E_CORE_ERROR - fatal errors that occur during PHP's initial startup ; E_CORE_WARNING - warnings (non-fatal errors) that occur during PHP's ; initial startup ; E_COMPILE_ERROR - fatal compile-time errors ; E_COMPILE_WARNING - compile-time warnings (non-fatal errors) ; E_USER_ERROR - user-generated error message ; E_USER_WARNING - user-generated warning message ; E_USER_NOTICE - user-generated notice message ; E_DEPRECATED - warn about code that will not work in future versions ; of PHP ; E_USER_DEPRECATED - user-generated deprecation warnings ; ; Common Values: ; E_ALL (Show all errors, warnings and notices including coding standards.) ; E_ALL & ~E_NOTICE (Show all errors, except for notices) ; E_ALL & ~E_NOTICE & ~E_STRICT (Show all errors, except for notices and coding standards warnings.) ; E_COMPILE_ERROR|E_RECOVERABLE_ERROR|E_ERROR|E_CORE_ERROR (Show only errors) ; Default Value: E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED ; Development Value: E_ALL ; Production Value: E_ALL & ~E_DEPRECATED & ~E_STRICT ; http://php.net/error-reporting error_reporting = E_ALL

error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT

$ sudo systemctl restart apache2

Источник

How to Remove Warning and Error Messages in PHP

PHP, being a robust server-side scripting language, is widely used in web development. An essential part of the development process is handling and debugging errors, which can provide valuable insights about issues present in the code. Despite their usefulness, displaying errors directly on the webpage may lead to unprofessional user experiences and, in worst cases, can even expose sensitive information to end-users. Thus, learning how to control and remove these error and warning messages is critical.

Understand the Error Reporting Levels

Before we jump into how to remove the warning and error messages, it is important to understand the types of errors that can occur in PHP. PHP error reporting levels are:

1. E_ERROR: A fatal run-time error that can’t be recovered from. The script execution is halted.
2. E_WARNING: Run-time warning that doesn’t stop script execution.
3. E_PARSE: Compile-time parse errors.
4. E_NOTICE: Run-time notice, indicating something that might be an error.
5. E_ALL: All errors and warnings (including E_STRICT and E_DEPRECATED).

Adjusting the Error Reporting Level

You can adjust your error reporting level in PHP by using the `error_reporting()` function. By passing in different constants, you can control what kind of errors PHP should report. For instance, you might use the following line to report all errors except notices:

Источник