[wp-trac] [WordPress Trac] #39151: Plugin Namespacing for Tags
WordPress Trac
noreply at wordpress.org
Wed Jan 4 08:15:34 UTC 2017
#39151: Plugin Namespacing for Tags
-----------------------------+------------------------------------------
Reporter: LewisCowles | Owner:
Type: feature request | Status: closed
Priority: normal | Milestone: Awaiting Review
Component: Plugins | Version: trunk
Severity: normal | Resolution: invalid
Keywords: | Focuses: administration, performance
-----------------------------+------------------------------------------
Changes (by LewisCowles):
* status: new => closed
* resolution: => invalid
Comment:
It was a suggestion for REST-API and plugin management via admin.
Simple logic (to me) was that although execution is deferred, many plugins
do a non-trivial amounts of processing on early hooks and even upon
`__construct`. Mitigating that would add speed to a site, and lower
resource consumption as it seems quite high.
This could benefit users across the board including the smallest shared
hosting users right up to sites with a lot of spot traffic, or high
overall traffic because there would simply be more resources to go around
by lowering how much of the resources are needed per-request.
I have since looked at the source code. I now feel this may not be
possible or practical the way this issue originally outlines.
I Still feel conditionally loading plugins is a great idea if deliberate;
but the framework for doing so probably cannot be a core concern, simply
because of the startup process (looks like plugins come in-use very early
and are included in `wp-settings.php`).
Closing.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/39151#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list