Yes, I’ve asked for issues to be reported here, so that you can get answers from the larger community of WordPress users and developers at WordPress Answers. Regarding the issue, other user also reported it, and it is due to the webhost using PHP 4. Line 10 of CatListDisplayer.php declares a private attribute. PHP 4 … Read more
Check out the source of dead_db() which powers the message. You’ll see that you can create a file db-error.php in your WP content directory (which by default is /wp-content/) and it’ll load that instead!
WordPress theme templates are not meant to be executed directly. They are loaded by WordPress core (after appropriate environment had been set up) according to Template Hierarchy.
it sounds like even though its a fresh install of WP 3.1.2 that you are also using an existing theme that is using a deprecated function (you havent said so but im presuming), if so paste this into your themes functions.php file (if your theme doesnt have one just create one and save it in … Read more
Simply use the @ operator in front of a function to suppress an error message/notice/whatever. Fun as it is: Even the image_resize() function uses it for chmod. 🙂
A white screen of death is typically a fatal PHP error, most of the time due to a syntax error. This often sends no errors to the browser. Some things you can do: Turn on PHP error_log in your php.ini file and set the error_reporting levels. http://php.net/manual/en/errorfunc.configuration.php Error info: http://www.php.net/manual/en/errorfunc.constants.php Alternatively or in combination you … Read more
if ( is_wp_error($term_id) ) { // oops WP_Error obj returned, so the term existed prior // echo $term_id->get_error_message(); } See if that works for you.
Those constants do different things. The WP_DISABLE_FATAL_ERROR_HANDLER constant is for disabling the new fatal error recovery feature introduced in WordPress 5.2. This new feature ensures that fatal errors from plugins don’t lock you out of your site, and that front-end users get some kind of “technical difficulties” message, rather than a white screen. The WP_DEBUG … Read more
There’s not one if you didn’t set one up. The codex has a good example of how to do this. <?php @ini_set(‘log_errors’,’On’); @ini_set(‘display_errors’,’Off’); @ini_set(‘error_log’,’/home/example.com/logs/php_error.log’); /** * This will log all errors notices and warnings to a file called debug.log in * wp-content (if Apache does not have write permission, you may need to create * … Read more
It could be that a plugin which blocks I.P addresses or Countries is causing this. Otherwise it maybe a setting in a security plugin has caused this. Seems the message is a custom one. Otherwise it could be something coded into a .htaccess file.