I just started getting some warnings both on the front and back end (using WordPress) of a site I’m working on. Error reporting is turned off using error_reporting(0); placed at the beginning of wp-config.php file. I tried to put it into the main index.php file as well, to no avail.
The warnings only started to show up today and they don’t show up on the live version of the site, which is at least 99% the same code, same database.
Here are the errors (substituted domain name for domain.com):
Warning: is_dir() [function.is-dir]: open_basedir restriction in effect. File(/) is not within the allowed path(s): (/var/www/virtual/domain.com/:/usr/share/php/) in /var/www/virtual/domain.com/htdocs/wp-includes/functions.php on line 2104
Warning: file_exists() [function.file-exists]: open_basedir restriction in effect. File(/) is not within the allowed path(s): (/var/www/virtual/domain.com/:/usr/share/php/) in /var/www/virtual/domain.com/htdocs/wp-includes/functions.php on line 2095
Warning: is_dir() [function.is-dir]: open_basedir restriction in effect. File(/) is not within the allowed path(s): (/var/www/virtual/domain.com/:/usr/share/php/) in /var/www/virtual/domain.com/htdocs/wp-includes/functions.php on line 2104
Why do I get these messages ? Shouldn’t error_reporting(0) turn off all warnings?
Try:
However, depending on your host you may not have access to dynamically change ini settings like that.
Some of the commenters don’t seem to know how WordPress sets error reporting. They say stuff like “should be done” like this, or that. But the fact is in WordPress all you have to do is go to wp-config.php and change WP_DEBUG from true to false. That will do exactly what you want.
OK, so in the end I solved the problem by directly modifying the php.ini file. This is the line:
Thanks, @halfer
In wordpress, one can turn on error reporting with just the following lines of code: