Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By netmastan on
I've installed drupal 6.2 . So far its good until I was looking for CCK image field and imagecache... they are for drupal 5 or beta.
Shouldn't Drupal makes this a core module.. everyone at some stage will need to have these modules. As far I know version 5 modules are not compitable with version 6.2.
I don't know whether i should switch to Drupal version 5..
Regards
Comments
Welcome to my torment!
It has been a seriously long time since 6.0's release for module development to have fallen so far behind. I understand that some modules are rather complicated and need time to complete the switch with adequate testing, but it seems as though most have yet to even begin the process. With the coder module out there, it seems as though this should give people a huge head start. Maybe I'm being naive.
In any case, I've been running 6.x on my personal sites and porting modules as I need them, but on all production sites (including new development projects), I'm afraid I'm still stuck on 5.x...
BTW, ditto on CCK - seems odd that the basic functionality has not yet been absorbed into the core.
...
You should use the version that suits your needs. That's always the answer.
The complexity of upgrading modules really depends on several factors.
Has the module been obsoleted by core functional changes? Then it doesn't get updated.
Is the module fairly simple? Then it's straight forward but the maintainer may not have a need to update it, patches welcome, usually.
Did the contributor leave the community (paid work, contributed, doing something else)? Someone else will need to pick it up.
Is the module maintainer waiting on another module....... That's more complicated.
A number of modules have opted out of providing certain features due to relying on code from other modules. Views and CCK being two of those cornerstone modules. This has the benefit of grouping, standardizing and cutting down on code use. It has the disadvantage of relying on someone else. Views is now 3rd or 4th generation now and a lot has been learned so the maintainer decided on a complete rewrite to incorporate that knowledge. As a result, the crew doing CCK decided to take this opportunity as well to plan more extensively for the future as well.
Basic CCK functionality _has_ been added to core. It was added in Drupal 5. Additional content types (forums, book) module were further converted in Drupal 6 along with other fixes. Much more work was planned for by the major CCK contributor but due to a long illness and death in the family that work was not done as no one else stepped up and did it for Drupal 6.
a few misc other notes
Although they may not be the ones you want, there are more then a few updated modules for 6.
# 6.x Modules: 499
# 5.x Modules: 1,867
Known reported back through update module Drupal installations
# 6.x: 26,661 active installations
# 5.x: 15,574 active installations
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
API redesigns
Both View and CCK developers have undertaken substantial API/code redesigns as part of the 6.x update. In both cases, they have stated that a direct 5.x->6.x update would have been done long ago, but it's this more fundamental redesign that's taking longer than would otherwise be expected.
Hopefully, this work will lay a solid foundation for the future, and significant portions of both are likely to get into the 7.x core.
---
Work: BioRAFT
I think that you should look
I think that you should look and see which version has all the modules that you need to do what you want. Choose the one that does it all. Version 6 seems slow in getting modules, so version 5 might be a better choice.
Thank you guys for the
Thank you guys for the explanation.