On 04 Apr 2005, at 07:20, CodeMonkeyX wrote:
OK I had an idea which should not be too complex.
I could create an admin page where the site administrator defines custom types to filter the archive. These types are defined by a combination of node types and taxonomy terms. So for example:
Type: Technology Blog => node-type = 'blog' AND term = 'technology'.
There administrator can then create pretty much any custom type they like for the archive, and the module can build the SQL on the fly without much overhead to speak of.
Just an idea right now, but I think I will play with it a bit and see how it goes.
1. Terms are already bind to node types. If I wanted a "technology blog", chances are I already have a vocabulary term that does exactly this. If not, I could achieve this using the existing taxonomy system. IMO, it is not the archive module's task to build an extra layer on top of the taxonomy module. 2. One could create new categories (groupings) which don't exist elsewhere on the site. This could be confusing. 3. There are sites with hundreds of terms. On such sites, it would be tiresome to setup additional bindings. To move this forward, I'd would look at the various taxonomy_* modules in the contributions repository, to see if there is a particular navigation scheme that is worth integrating and that works for all sites. At DrupalCon in Antwerp it was suggested that we could create something like iTunes' browser, in case you are familiar with that. If we go that route, the archive module becomes more of a "browse module" than an "archive module". Interesting stuff, -- Dries Buytaert :: http://www.buytaert.net/