hi
I am new to drupal and my client want to develope his site using drupal, but I don't know which is better to use either drupal 5 or drupal 6.

can you please give a brief note of this.

Thanks
AB

Comments

matt_harrold’s picture

Unless you're going to require a module unavailable for D6, there is no reason to stay with D5 anymore (IMHO).

The install routine for D6 is better, it has more features, less screen clutter, and themes seem easier to make.

Many new features in contributed modules seem to be developed for D6 only, probably because it is easier to write modules too (I'm guessing though .. I haven't tried making a module for D6 yet).

drupalhook’s picture

Hi,

Thank you for your suggestion.

Actually I already installed Drupal 5 and Drupal 6 in my local machine. But client's requirement is some new modules like JOBS PORTAL, PODCAST WITH RSS FEED, CAREERS, EVENT MANAGEMENT WITH CALENDAR VIEW, HTML SITEMAP..... these modules are hardly available in drupal 6 and drupal 5.

Since these are client's requirement we need to develop modules, I don't know which version gives us better compatibility and easiest way for developing a module.

Can you please help me on this way.

Thanks
AB

pkej’s picture

The release cycle of Drupal is on high octane. For example, major modules like Views, CCK and Panels were all released for D6 just this autumn, even though D6 has been on line for almost a year.

That should suggest using D5, but that's actually an argument for going with D6. The next release, D7, will render D5 obsolete. That might be a while into the future, 6 months, give or take 6 months ;)

Then the next release D8 will start its development cycle and within 12 months to 18 months make D6 obsolete.

Thus, if you start on D5 you might find that D7 is out when you're finished developing your modules, and thus moving most of the community to at least D6, just to keep up. If you start now on D6 you would at least have a couple of years until you are forced to move your development to D7 or D8.

Module development?

Off the bat I can't see a reason for developing your own modules. You might need to develop a few features, or help out on a few other modules, but in general it seems that you could to all of the above with CCK, Views and Panels + a extensions for these (like the CCK audio field for the podcasts, rss for views, etc).

Jobs portal: CCK nodes and taxonomy. Views for searching/matching. Perhaps notifications for when jobs matching skills are available.
Podcast with rss: CCK nodes with audio fields, views with rss.
Careers: A bit fuzzy, do you mean CVs? Then it is CCK, nodereference, nodereferrer, taxonomy, node profiles.
Event management: RSVP module, event manager and/or signup module. Here you could convert the existing modules from 5.x to 6.x instead of rolling your own.
Sitemap: Sitemap module

There even is a module called job search for 5.x, which needs to be ported to 6.x

I think the best would be to look at all the existing 5.x and 6.x modules, decide on which to use and update/fix them for 6.x.

Paul K Egell-Johnsen

Paul K Egell-Johnsen