Module grouping or dependencies for 4.7.0?
since my last request for new functionality in 4.7.0 went over so well, i thought i'd try again. ;) (just kidding). seriously, this is a pain in the ass for CCK usability: http://drupal.org/node/49690 all of CCK's field types are implemented as separate modules. they currently have names like "text.module" or "date.module", etc. however, that means they show up all over the place in the admin/modules page, which makes it hard for admins to enable all the required modules for CCK. apparently, there are a couple of possible solutions: http://drupal.org/node/18447 "Simple dependency system" this one has a patch by chx waiting to be committed. http://drupal.org/node/19477 "Module Grouping by Folder in Admin/Modules" this is just in the "it'd-be-nice-if..." phase, so there's basically no hope for this one in 4.7.x. if neither of these issues gets fixed for 4.7, CCK is going to have to rename all its files (and therefore function names), to avoid user confusion, and make CCK easier to administer and use. people have mentioned a few other modules (ecommerce, etc) where this is a problem. i'd love to avoid the pain of renaming things in cvs (no one say "svn" or "bzr", or i'll scream), but we're going to have to do that before 4.7.0 really goes live if neither of these issues (or something very similar) get fixed for 4.7.0. should i give up hope and start working on renaming the CCK field modules to "cck_field_text", "cck_field_date", etc (or something)? i don't want to spend time writing a patch for core to group modules from the same subdirectory together on the admin/modules page, if there's no chance it would get committed in time for 4.7.0. please let me know. thanks, -derek
since my last request for new functionality in 4.7.0 went over so well, i thought i'd try again. ;) (just kidding).
See the following patch: http://drupal.org/node/53096 -- Morbus Iff ( keep out of reach of children ) Technical: http://www.oreillynet.com/pub/au/779 Culture: http://www.disobey.com/ and http://www.gamegrene.com/ icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus
Derek Wright wrote:
modules to "cck_field_text", "cck_field_date", etc (or something)? i don't want to spend time writing a patch for core to group modules from the same subdirectory together on the admin/modules page, if there's no chance it would get committed in time for 4.7.0. please let me know.
I have a patch for this in, but the policy has changed somewhere along the way; UI enhancements were originally considered bugs and could be fixed, but now they're features and have to wait for 4.8.
Derek Wright wrote:
modules to "cck_field_text", "cck_field_date", etc (or something)? i don't want to spend time writing a patch for core to group modules from the same subdirectory together on the admin/modules page, if there's no chance it would get committed in time for 4.7.0. please let me know.
I have a patch for this in, but the policy has changed somewhere along the way; UI enhancements were originally considered bugs and could be fixed, but now they're features and have to wait for 4.8.
Yes, this will have to wait. -- Dries Buytaert :: http://www.buytaert.net/
Derek Wright wrote:
since my last request for new functionality in 4.7.0 went over so well, i thought i'd try again. ;) (just kidding).
Please stop that. We focus on getting 4.7 out of the door.
seriously, this is a pain in the ass for CCK usability:
Which is of no concern to core. Cheers, Gerhard
On Sat, 11 Mar 2006 19:05:11 +0100 Gerhard Killesreiter wrote:
Please stop that. We focus on getting 4.7 out of the door.
sorry, i'm done. this is the first release cycle i've been a drupal community member for, so i'm learning as it unfolds. apologies to everyone for that...
Which is of no concern to core.
my confusion stemed from the fact that there seem to be 3 kinds of drupal modules: 1) things actually in core 2) modules that are nearly as important as core (for example, project.module -- there were numerous emails on this list about critical bugs in project holding up the 4.7 release, etc) 3) everything else i was under the mistaken impression that CCK was supposed to be a major part of the new 4.7 functionality, and therefore, that it belonged in group #2 -- that it was "of concern to core". i didn't ask about this feature to be a pain in anyone's ass, but because i thought that if this list was going to hunker down and throw itself at project.module's issue queue, CCK was a similarly important module, and that a small, last-minute feature could be added to ease CCK's 4.7 lifespan. a few developers that seem to be well-respected around here were working on the patch (which would have benefitted some other modules, too), so i thought i was being helpful by drawing attention to the issue. the obvious flaw in my logic is that CCK is not considered that important. now i know. ;) i didn't mean any harm, and i'm sorry i generated any heat over this. is project.module just a special case because it's in use on drupal.org? are there any other modules that belong in the nearly-as-important-as-core category? that info would help me (and probably others on this list) know where to focus energy for the rest of the time until 4.7.0 RC is out. thanks, -derek
On Tue, 2006-03-14 at 05:08 -0600, Derek Wright wrote:
is project.module just a special case because it's in use on drupal.org? are there any other modules that belong in the nearly-as-important-as-core category? that info would help me (and probably others on this list) know where to focus energy for the rest of the time until 4.7.0 RC is out.
AFAIK, it is because Drupal like to eat it's own dog food, but in order to do so, project.module must be working otherwise you can kiss Drupal's bug tracking and downloads section goodbye, rendering drupal.org very much impaired. -- brian@brianpuccio.net GPG Key ID 0xBBD2401F
Derek Wright wrote:
my confusion stemed from the fact that there seem to be 3 kinds of drupal modules:
1) things actually in core
2) modules that are nearly as important as core (for example, project.module -- there were numerous emails on this list about critical bugs in project holding up the 4.7 release, etc)
This is only true because not having project module up to date will make it impossible to update drupal.org which in turn will not allow us to test the current Drupal code base there.
is project.module just a special case because it's in use on drupal.org?
Yes.
are there any other modules that belong in the nearly-as-important-as-core category?
cvs.module, list.module, simplenews.module.
that info would help me (and probably others on this list) know where to focus energy for the rest of the time until 4.7.0 RC is out.
You can look at the issue queues for the modules mentioned above and / or core. There are a lot of pending bug related patches which need to be looked at and tested. Cheers, Gerhard
On 3/14/06, Gerhard Killesreiter <gerhard@killesreiter.de> wrote:
Derek Wright wrote:
2) modules that are nearly as important as core (for example, project.module -- there were numerous emails on this list about critical bugs in project holding up the 4.7 release, etc)
This is only true because not having project module up to date will make it impossible to update drupal.org which in turn will not allow us to test the current Drupal code base there.
is project.module just a special case because it's in use on drupal.org?
Yes.
are there any other modules that belong in the nearly-as-important-as-core category?
cvs.module, list.module, simplenews.module.
There is this list in the handbook of modules used on Drupal.org http://drupal.org/node/27367 I imagine that bugs in some of these would hold the While it may not be kept 100% up to date or the transition to 4.7 may include a plan to replace some of the modules, that list is a good indicator of modules that are important to Drupal.org. Greg
participants (7)
-
Brian Puccio -
Derek Wright -
Dries Buytaert -
Earl Miles -
Gerhard Killesreiter -
Greg Knaddison -
Morbus Iff