latorante

This plugin takes care of WordPress inner comments error handling, and shows comment errors above the form, instead of using the weird grey page with single line error description. All this out-of-the-box.
It also remembers what you’ve typed in. So for example, if you fill in the comment form, and send it and forget required field, it will show the error above the form, and prefills the form with values you’ve submitted so you don’t have to retype them again (which is annoying).
By default, the plugin prints the error in this markup:
<pre><code><div id="formError" class="formError" style="color:red;">
 --error-here--
</div><div class="clear clearfix"></div>
</code></pre>
So it should be quite easy for you to style it in your css file with <code>".formError"</code> or <code>"#formError"</code>, you know the drill :). The default red colour is there just in case you won’t be able to style and since it’s error, red seems appropriate.
By the way, if you’ve customised your comment form with new fields, and you’re using the <code>preprocess_comment</code> hook, with the correct WordPress way of handeling errors, which is using <code>wp_die</code> on error encounter, this plugin will play nicely with that, and display your error messsage above the form as well.

Comment Form Inline Errors

AVATTAVA

Debug Activation Errors 2.0 shows you the issues during plugins activation on WordPress plugins page: plugins.php
A developers’ plugin that allows to debug the ambiguous error message: “The plugin generated ### characters of unexpected output during activation”.
If you notice messages like “headers already sent”, problems with syndication feeds or other issues, activate Debug Activation Errors 2.0 and deactivate any suspicious plugin.
Then, activate the possible culprit again and you will see if there are any issues during its activation. You can repeat this operation as many times as you want…
Whenever you have solved the issues and to stop seeing any messages, you can deactivate our plugin, Debug Activation Errors 2.0
This plugin is not designed to operate on a Multisite install (Network Mode) and we do not guarantee any results in those conditions.
@@@@@ READ CAREFULLY @@@@@
Alongside with the use of Debug Activation Errors 2.0, you should update the file wp-config.php with the below snippet of code:
/** 
 * For developers: WordPress debugging mode. 
 * 
 * Find the line of code >> define( ‘WP_DEBUG’, false ); << and replace it with the 3 lines of code below. 
 * You must set WP_DEBUG to “true” to enable the display of notices during development. 
 * WP_DEBUG_DISPLAY should always be “false”, unless you have a very strong reason to change its value to “true”. 
 * You should have a debug.log file in WordPress, if not, you must create it and set WP_DEBUG_LOG to “true”. 
 * It is strongly recommended that plugin and theme developers use WP_DEBUG in their development environments, with caution. 
 */ 
define( ‘WP_DEBUG’, true ); 
define( ‘WP_DEBUG_DISPLAY’, false ); 
define( ‘WP_DEBUG_LOG’, true );
<h3>Support</h3>
Please, use the WordPress.org forums for community support at https://wordpress.org/support/plugin/debug-activation-errors and if you spot a bug or if you have a suggestion to improve the code functionality, you can contact us at contact@avattava.xyz

Debug Activation Errors 2.0

Debugs errors and shows you the issues during WP plugins activation.

Comment Form Inline Errors vs Debug Activation Errors 2.0