GrandSlambert

This plugin creates a custom post type to share information about WordPress themes and plugins you’ve developed.
<h4>Extra Details</h4>
<ul>
<li>Allows you to create sub pages and indicate which ones has the plugin documentation.</li>
<li>Provide a URL for where a person can download the plugin.</li>
<li>Add a quick link to some Frequently Asked Questions.</li>
<li>Add a quick link to the support forums.</li>
<li>Add a quick link to the plugin reviews.</li>
<li>Add a link to a donate button to allow people to donate to your plugin.</li>
</ul>

Promote My Extensions

This plugin creates a custom post type to share information about WordPress themes and plugins you've developed.

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.

Promote My Extensions vs Debug Activation Errors 2.0