WordPress.org

Make WordPress Core

Opened 7 years ago

Closed 6 years ago

Last modified 6 years ago

#4039 closed enhancement (wontfix)

Allow Plugins and themes to come from user definable dirs

Reported by: mdawaffe Owned by:
Milestone: Priority: low
Severity: normal Version: 2.1
Component: Administration Keywords: has-patch plugin-management
Focuses: Cc:

Description

Ultimate goal: allow WP to run from completely clean svn co/export and still have custom plugins/themes/cache/uploads/etc.

Patch:

  1. PLUGINDIR -> wp_plugin_path( [$file] ). Deals with absolute or relative PLUGINDIR definitions.
  2. new PLUGINURL and wp_plugin_url( [$file] ). Constant is false by default but can be set to a full url.
  3. get_theme_root() and get_theme_root_uri() respect new contstants: THEMEDIR, THEMEURL.

Possible hangups:

  1. editing plugin and theme files. Does the recent list always work?
  2. get_themes() outputs relative paths when THEMEDIR not defined, absolute path whet THEMEDIR is defined.

Attachments (1)

4039.diff (16.2 KB) - added by mdawaffe 7 years ago.

Download all attachments as: .zip

Change History (13)

mdawaffe7 years ago

comment:1 ryan7 years ago

LANGDIR too

comment:2 rob1n7 years ago

  • Milestone changed from 2.2 to 2.3
  • Owner changed from anonymous to rob1n

Once 2.2 is released, I'm on this.

comment:3 follow-up: mdawaffe7 years ago

For 2.3, we should figure out once and for all if we want to allow alternate plugin dir, theme dir, upload dir (already possible with filter), and lang dir

OR

allow for an alternate wp-content dir and get them all with one swoop.

comment:4 in reply to: ↑ 3 foolswisdom7 years ago

Replying to mdawaffe:

For 2.3, we should figure out once and for all if we want to allow alternate plugin dir, theme dir, upload dir (already possible with filter), and lang dir

I hope so, I am one of those wordpress/ directory type and I would like just to have flat directories for plugins, themes, files etc right there

comment:5 foolswisdom7 years ago

  • Milestone changed from 2.3 to 2.4 (next)

comment:6 darkdragon6 years ago

  • Keywords plugin-management added

comment:7 rob1n6 years ago

  • Owner rob1n deleted

comment:8 ryan6 years ago

Resurrecting for 2.5 consideration. All in one swoop or per dir?

comment:9 darkdragon6 years ago

Per directory, please.

The reason for this is that it might not make sense to since the CSS in themes have to be public of have some proxy for output (not ideal).

For Plugins, I would want to totally move them out of the public web space to a directory below and map that from multiple WordPress installations, if needed.

comment:10 darkdragon6 years ago

  • Milestone changed from 2.5 to 2.6

No traction. Moving to 2.6. I don't know if Ryan is still working on this, so move back if a fix is implemented.

comment:11 lloydbudd6 years ago

  • Resolution set to wontfix
  • Status changed from new to closed

Closing as wontfix for now.

comment:12 Nazgul6 years ago

  • Milestone 2.6 deleted
Note: See TracTickets for help on using tickets.