[wp-hackers] User folders for themes, plug-ins
andy at yellowswordfish.com
Thu Jan 18 16:29:50 GMT 2007
Didn't I come across a new constant defined in 2.1 named PLUGINDIR ?
Which I recall is set to 'wp-content/plugins'
On 04:05 PM | Thu 18 Jan 07, at 04:05 PM | 18 Jan 07, Jamie Holly
>>>> [Mark] ...plugins may be accessing things more directly, counting
>>>> on wp-content to be the place where that stuff exists.
>>> [Charles] Ah, gotcha. Maybe we can give plug-in developers a
>> or two to help
>>> them avoid path assumptions.
>> In the current development version of WP source code, in
>> functions.php, there are functions called get_theme_root() etc. So,
>> the functions already exist, to some extent. The question is whether
>> people use them or not (probably they don't too much, and that
>> to the WP source code too).
>> It doesn't appear there are similar functions for plugins, but I am
>> not sure.
> Most plugins I see seem to rely upon:
> $pluginpath = ABSPATH . 'wp-content/plugins/';
> $pluginurl = get_settings('siteurl').'/wp-content/plugins/*';
> Since this change would most likely affect a large number of
> plugins (and
> possibly themes), hopefully a decision can be made on implementing
> it in the
> near future, that way word can get out to all developers to update
> sources to utilize the new directory structure.
> After that is done, then wp-content/plugins can be utilized more for
> Wordpress default plugins (ie: Akismet). The other option then (as
> much as I
> hate rekindling this old fire) is possible moving TinyMCE to a plugin
> included in that directory that is activated by default. Actually
> there may
> be other features that could be moved to the default plugins
> which are core features not used by everyone (Links directory comes to
> mind). This would make Wordpress much more "modular" IMHO.
> Jamie Holly
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers