Allow Plugins and themes to come from user definable dirs

[mdawaffe]

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.

[ryan]

LANGDIR too

[rob1n]

Once 2.2 is released, I'm on this.

[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

OR

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

[foolswisdom]

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

[ryan]

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

[darkdragon]

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.

[darkdragon]

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.

[lloydbudd]

Closing as wontfix for now.