Feature Request: Group Scripts & CSS by Plugin
-
Hello,
I am exploring the benefits of your plugin and wonder if I am overlooking this feature or if it would be feasible to add it?
When inspecting the list of items that can be disabled, it would be AWESOME if they were grouped by the plugin that is using them.
That would help assure that ones which are needed are not disabled due to lack of user understanding of their purpose or plugin relationship.
For example, if all the scripts and CSS, etc, related to a mapping plugin were grouped by the mapping plugins name so they could be selected all at once, that would make it very easy to deactivate the exact items without accidentally deactivating some used by other plugins. It is easy for a user to know which pages DO or DO NOT have a map on them, but it is not so easy for a user to know which various files are related only to a mapping plugin and thus may deactivate the wrong ones as a result.
Grouping by plugin or by the originator/caller of the script or css file, etc. would be AWESOME and make it very quick to add the benefits of your plugin to a site. (FYI: the Perffmatters plugin groups them as described)
Thanks for considering this feature in your future development pipeline or pointing me to in the right direction to find it if it is already incorporated.
- The topic ‘Feature Request: Group Scripts & CSS by Plugin’ is closed to new replies.