[wp-trac] [WordPress Trac] #46480: Segregating Plugins from Plugin Addons
WordPress Trac
noreply at wordpress.org
Wed Mar 13 15:30:40 UTC 2019
#46480: Segregating Plugins from Plugin Addons
-----------------------------------------------+---------------------------
Reporter: samjco | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting
| Review
Component: Plugins | Version: 5.1
Severity: normal | Keywords:
Focuses: ui, accessibility, administration |
-----------------------------------------------+---------------------------
This will allow better organization in the plugin directory of admin.
Perhaps a +/- to open up the Main Plugin to show it's add-ons. For
example:
( - ) **Advanced Custom Fields** ''(2)''
--- ACF Native field
--- ACF Table field
( +) **WooCommerce** ''(10)''
( - ) **Gravity Forms** ''(1)''
--- Gravity Froms Addon
**Hello Dolly**
This would drastically clean up/ or give "the appearance of" with the
plugins looking organized and more bearable to look at and search through.
This can be a simple addition that Plugin developer would make in their
definition of a Plugin that requires the main plugin. For example:
{{{#!php
<?php
/**
* Plugin Name: My Awesome ACF addon
* Addon Of: advanced-custom-fields // <--The repo slug of the Main plugin
*/
}}}
This can also lead to the core checking to see if the main plugin is
installed, to fire off a notification to the user: ''"Advanced Custom
Field is not installed"''
I believe this is something that should be considered and added to core
and give as a standard to plugin addon developers.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/46480>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list