[wp-trac] [WordPress Trac] #16953: Allow symlinked plugins
WordPress Trac
noreply at wordpress.org
Mon Feb 10 22:55:26 UTC 2014
#16953: Allow symlinked plugins
----------------------------------------------+----------------------------
Reporter: scribu | Owner: rmccue
Type: enhancement | Status: assigned
Priority: normal | Milestone: Future
Component: Plugins | Release
Severity: normal | Version:
Keywords: has-patch dev-feedback 3.9-early | Resolution:
| Focuses:
----------------------------------------------+----------------------------
Comment (by nacin):
Replying to [comment:96 tollmanz]:
> I have tested 16953.9.diff and it works well for a situation where I was
bit by this "bug". My situation involves a Capistrano-like "releases"
directory that is symlinked to a web root. Within the WordPress
installation, the wp-content directory has been moved.
This isn't really Capistrano-specific, or really related at all, as
Capistrano is symlinked from the web root. At least where I have seen
this, wp-content is not typically then symlinked from elsewhere.
----
I found a few missing wp_register_plugin_realpath() calls. Specifically
around plugin sandboxing and also for mu-plugin inclusion. Network plugins
are in the normal plugins directory. mu-plugins are separate; they are
indeed supported by plugin_basename() and are represented by the
WPMU_PLUGIN_DIR directory.
Trying this out sans-filter.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/16953#comment:98>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list