Opened 13 years ago

Closed 11 years ago

#1136 closed bug (invalid)

replace category module with taxonomies and views

Reported by: wkornewald Owned by: haiku-web
Priority: normal Milestone: Website R2 (Drupal 5)
Component: Website/CMS Version:
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

The category module is buggy, adds an unnecessary dependency, and doesn't really add any functionality beyond what taxonomy and views could do that we'd need. Of course, before doing this step we'd have to do a full analysis of the affected pages and how we're going to replace each of them. Maybe the taxonomies are too visible (and need to be hidden with an extra module).

Change History (7)

comment:1 by gavin, 12 years ago

Owner: changed from wkornewald to gavin

comment:2 by nielx, 12 years ago

Owner: changed from gavin to haiku-web
Version: R1 development

Reassign to generic owner.

comment:3 by nielx, 12 years ago

Is this task still relevant? Maybe the 4.x version was buggy, but the module is still developed. Could someone enlighten me why this change would be beneficial?

comment:4 by koki, 12 years ago

The category module (http://drupal.org/project/category) is still buggy, and its development has not been very active. Although it is working OK in our current setup, it would be safer and wise (maybe even necessary?) to replace it when upgrading to Drupal 5.x. Might be tricky though.

in reply to:  4 comment:5 by wkornewald, 12 years ago

Replying to koki:

The category module (http://drupal.org/project/category) is still buggy, and its development has not been very active. Although it is working OK in our current setup, it would be safer and wise (maybe even necessary?) to replace it when upgrading to Drupal 5.x. Might be tricky though.

You mean Drupal 6. You're running crusty old technology. Hopefully it won't fall apart too soon. ;)

comment:6 by koki, 12 years ago

Hi Waldemar. Good to hear from you. :)

You mean Drupal 6.

No, I said and meant Drupal 5. I don't know what whoever takes up this task will end up doing, but the initial plan as we talked it with Gavin was to migrate to Drupal 5 first, as Drupal 6 is still missing some modules that we need (including some important ones like Views and CCK).

You're running crusty old technology. Hopefully it won't fall apart too soon.

I see no reason why it should fall apart. And new does not necessarily mean better: as of lately, our crusty old Drupal 4.x has for the most part had less problems than Trac, which is supposed to be state of the art technology, right? :P

Anyway, as far as I am concerned, you guys feel free to fix/improve/enhance/whatever the website. :)

comment:7 by nielx, 11 years ago

Resolution: invalid
Status: newclosed

This is no longer a goal of the project for now, perhaps with the migration to Drupal 6, but the module suffices for now.

Note: See TracTickets for help on using tickets.