There’s only 2 general places the problem could be: One is the theme and two is the plugins. The actual problem is that there’s a deprecated function that’s being called. The header already sent message is just WordPress’s way of telling you the backend broke before it could build the frontend. I suggest you: disable … Read more
As said on https://wordpress.org/support/article/debugging-in-wordpress/#example-wp-config-php-for-debugging: (note though, the “blogging” below is now “publishing”) NOTE: You must insert this BEFORE /* That’s all, stop editing! Happy blogging. */ in the wp-config.php file. So just put it there, like this: define( ‘WP_DEBUG’, true ); /* That’s all, stop editing! Happy publishing. */ But actually, depending on the WordPress … Read more
This is probably the new Heartbeat API. It is running in intervals from 15 to 60 seconds and offers a simple way to communicate with WordPress per AJAX in the background. You can disable it in JavaScript with wp.heartbeat.stop(); and in PHP with remove_action( ‘admin_init’, ‘wp_auth_check_load’ ); (might not be enough on some pages).
What you’re looking for is the Log Deprecated Notices plugin. (Don’t run it on a production site, as it is a direct-to-database log.) What it’ll do is convert those cryptic messages that are likely to reference has_cap() or some line in functions.php, to what’s actually going on. The Debug Bar plugin is also nice. It … Read more
Yes. It is possible and you’re on the right track! 🙂 AJAX calls happen “behind the scenes” and no screen output is generated during the process no matter what you echo or print_r – that’s why you don’t see anything returned to you – instead that server response is captured by javascript and acted upon … Read more
Is this what you are looking for? add_filter(‘show_admin_bar’, ‘__return_true’); Codex Btw following code in wp-config.php could help also: define( ‘WP_DEBUG’, true ); // Or false if ( WP_DEBUG ) { define( ‘WP_DEBUG_LOG’, true ); // writes errors down in wp-content/debug.log define( ‘WP_DEBUG_DISPLAY’, true ); // shows errors on screen output, set false to on write … Read more
@Wyck was right, ( well sorta 😛 ) you can set error logs but 1) You need to enable debugging 2) ini_set(‘log_errors’, 1); or 0 for false 3) You need to set a log location via ini_set(‘error_log, $location) Once you have that set you can then if need be test if said file exists via … Read more
I use a plugin for this issue. Even if debug is set to false, it still prints error to the screen in red. It is easy and fast to create the plugin. In your plugins folder in your wordpress install, create a new file and call it anything you like, for instance, debugger-plugin.php. Open up … Read more
I gave up on using the plugin and use FirePHP straight as a mu-plugin: And firebug.php file consists of: <?php /* Plugin Name: FirePHP Version: 0.1 */ require_once( ‘FirePHPCore/FirePHP.class.php’ ); ob_start(); $firephp = FirePHP::getInstance( true ); function logit( $var, $title=”From FirePHP:” ) { global $firephp; $firephp->log( $var, $title ); } Then I call it from … Read more
You need to kill the script. Add die; after your var_dump. WordPress post submissions operate on a post/redirect/get principle. The reason you don’t see the output is that the page has been reloaded. That is, you post the form, the form gets processed, and the page is redirected back to itself but without the $_POST … Read more