The feature module became something of a disaster. There is a real small number of people, who have access to edit the components of http://drupal.org/features (the famous node number #2) - only super-power administrators. And due to how the module is written, even then, the admin link is only shown in the sidebar block on http://drupal.org/admin not in the page itself. The node itself is empty and the feature list is generated to that from handbook.module (a submodule to drupalorg.module) with
function handbook_nodeapi(&$node, $op = 'view', $teaser = FALSE, $page = FALSE)
{
if ($op == 'view' && $page) {
$extra = '';
switch ($node->nid) {
case 2: // Features
$extra = feature_listing();
break;
// ...
}
$node->content['body']['#value'] .= $extra;
}
}
So basically, the contents of feature_listing() is the page. There is nothing else provided by feature module, just this very limited, and structure enforced features page. There is no way to include flashy videos or images right on this page, but only to link other pages and images on the site. No wonder the information here is awfully outdated. And I mean it.
The features page starts with collaborative book as most important feature, or Open source is a feature(?!) or "an external authentication source [can be used] like Jabber, Blogger, LiveJournal or another Drupal website" - information which is highly outdated, all these models were in core but then removed from core through the years. Also, screenshots for features like versioning point to Firebird(!) browser shots of Drupal 4.3(!!) Serious! http://drupal.org/node/3927 And this page is linked prominently from our front page blurb! It is!
So we should put an end to this madness once and for all and put this page to the hands of the docs team for massaging. It is about time. Getting rid of this obscure feature module also helps the upgrade to Drupal 6.
So how to get rid of that:
1. Copy the output of feature_listing() into the node itself (I could do this).
2. Remove the three related lines from the handbook.module (I could not do this due to file permissions set on the module).
3. Disable, delete and forget feature module. (The first two again I could not do due to file permissions).
I think this is an extremely easy migration path, so there should be no reason, we don't do this as soon as possible.
Comments
Comment #1
gábor hojtsyHas "patch" (describes the short and straightforward process to go through) and is ready to be committed.
Comment #2
kika commentedHey, that's my Firebird right there! Hands off! It belongs to Drupal Museum (tm)!
On more serious note, I am glad this old cruft goes away. But make sure this stuff is properly archived, it is part of our heritage.
Comment #3
gábor hojtsykika: well, the feature module itself does not support versioning, so moving the current content to a handbook page in itself will serve history keeping better. From there, since handbook pages are forced to have revisions, history of changes will be kept. Also, the fact that we might not link to Drupal 4.3 screenshots in up-to-date feature overviews does not mean that those screenshots are actually removed. :)
Comment #4
add1sun commentedOh, please yes. +100 to getting rid of Feature module from me.
Comment #5
gábor hojtsyYay!
Got credentials, so dumped the output of feature_listing(); into node 2, updated handbook module and deployed on drupal.org. Finally topped it off by disabling the feature module and updating its page to say that it is a retired module: http://drupal.org/project/feature
Now the docs team should run with this and produce something much more useful starting either from this outdated information in horrendous markup, or something else.
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.