[wp-hackers] a plugin of a theme's own

[David Chait]

If it makes it conceptually easier for people, why not have a 
[theme]/plugins/ optional subfolder?  If there are files there, treat them 
as 'second pass' plugins during the plugin-load process.  I think that's the 
proper 'container' direction (aside from moving to an actual container, i.e. 
zipped format of some sort...).  And it makes more sense than some file 
named 'functions.php' in the theme folder (there's already a ton of php 
files).  People would understand a folder named 'plugins', I'd think!

-d

----- Original Message ----- 
From: "Jason Bainbridge" <jbainbridge at gmail.com>
To: <wp-hackers at lists.automattic.com>
Sent: Tuesday, September 20, 2005 10:34 AM
Subject: Re: [wp-hackers] a plugin of a theme's own


On 9/20/05, Trevor Turk <trevorturk at yahoo.com> wrote:
> I think the idea is that themes which make use of a
> lot of plugins, like k2, benefit from this because it
> makes it much easier to get things up and running the
> way the theme designer intended.
>
> Now, I understand the point that convenience features
> shouldn't always be included, but I think that the
> goal of making themes more flexible, powerful, and
> easier to install is a worthy one.

It sounds like this would be better served by a new container (for
lack of a better term) that contains both a theme and plugins, now of
course you can do that manually now but wouldn't such a container fit
better in the WP framework than mixing plugins/functions in with
themes?