[wp-trac] [WordPress Trac] #16953: Allow symlinked plugins

[WordPress Trac]

#16953: Allow symlinked plugins
-------------------------+-----------------------------
 Reporter:  scribu       |       Owner:
     Type:  enhancement  |      Status:  assigned
 Priority:  normal       |   Milestone:  Future Release
Component:  Plugins      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |
-------------------------+-----------------------------

Comment (by kchrist):

 This is also an issue for WordPress sites deployed via Capistrano.

 Capistrano keeps previous deployments of the site so you can easily roll
 back changes. So the actual filesystem path to the site might be:

 `/home/username/web/example.com/releases/20121018101521/public`

 But it's symlinked as:

 `/home/username/web/example.com/current/public`

 The latter is the path in my web server config. The ''current'' directory
 is a symlink to the latest deployment, which is actually the datestamped
 `releases/20121018101521` directory.

 As a result, the entire site is in a symlinked directory. This isn't an
 issue for most plugins but it's come up more than once in my experience
 running a handful of sites this way.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/16953#comment:31>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software