WP_DISABLE_FATAL_ERROR_HANDLER vs WP_DEBUG ? What to use and when to use to see errors?

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

Enable errors PHP WordPress 5.2

You can disable this behaviour by setting WP_DISABLE_FATAL_ERROR_HANDLER to true: define( ‘WP_DISABLE_FATAL_ERROR_HANDLER’, true ); This will stop the “The site is experiencing technical difficulties” message from appearing, so errors will appear as they did prior to this feature being added.

Does wordpress have an error log?

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

Using $wpdb generates DB error

its a syntax error according to error message. starements like below might work for you. global $wpdb; $wpdb->show_errors(); $tableCustom = ‘join_users_defis’; $sql = “SELECT * FROM {$wpdb->postmeta}”; $requeteAffichage = $wpdb->get_row( $sql ); //or $requeteAffichage = $wpdb->get_results( $sql ); var_dump($requeteAffichage);

Customize WooCommerce Error Message

You can do this with the woocommerce_add_error filter. Add the following to your functions.php file. // alter the subscriptions error function my_woocommerce_add_error( $error ) { if( ‘The generic error message’ == $error ) { $error=”The shiny brand new error message”; } return $error; } add_filter( ‘woocommerce_add_error’, ‘my_woocommerce_add_error’ );