Opened 2 years ago
Last modified 12 days ago
#16953 assigned enhancement
Allow symlinked plugins — at Version 2
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | Future Release |
| Component: | Plugins | Version: | |
| Severity: | normal | Keywords: | has-patch dev-feedback |
| Cc: | yincrash, paulschreiber@…, boonebgorges@…, djpaul@…, coenjacobs@…, lkraav, simon@…, junk@…, juzzin, mitcho@…, kenn@…, hertzog@…, kwisatz, info@…, kawauso, synapticism, markus.magnuson@…, cklosowski@…, mike@…, imtiedup@…, johnbeales@…, beaver6813, jason@…, david@…, cor@…, JeromeC, francesco.laffi@…, rodrigosprimo@…, andyadamscp@…, andkrup, tollmanz@… |
Description (last modified by scribu)
There are many scenarios where one would like to have a plugin's folder symlinked to another location.
A couple of these scenarios are described in #13550.
The reason this is not currently possible is because plugin_basename() doesn't know how to handle symlinks.
The most simple and most flexible solution is to make the plugin basename filterable, leaving individual devs to handle symlinks, depending on their environment.
Change History (4)
comment:1
scribu
— 2 years ago
- Keywords has-patch added
- Owner set to scribu
- Status changed from new to accepted
Test files coming up.
Note: See
TracTickets for help on using
tickets.
'pre_plugin_basename' filter