preparing for D7

spangaroo - October 2, 2009 - 05:34

I'm somewhat of a newcomer to Drupal but have been following the latest developments very closely. After reading the slides posted at webchick.net, I'm quite interested in what it's going to take to get my current installation (6.13) compatible with D7 when it comes out.

For security reasons I always try to stay up to date. But I often find that I spend most of my time managing my Drupal installation and modules rather than creating content. Unfortunately I'm just a one-man operation so right now I'm trying to plan the best way to stay current with D7 while also making free time to contribute to website.

Modules
It seems that D7 has absorbed some of the most useful modules in the core. I know that when I first started with WordPress I went crazy with my plugins and after a SQL injection or 2 I learned my lesson.

My current D6 installation has quite a few modules that certainly add functionality, but I wouldn't consider critical. For my D7 plan, I'm hoping to rely strictly on the Core to build a feature-rich CMS that is also easy to maintain. While there are some modules that add incremental improvements to my site (i.e., Read More tweak) to follow the K.I.S.S guidelines I may leave them out.

With this in mind, do I need to start following the D7 progress of the each individual contributed module?

Should I restructure my current list of modules and figure out which ones aren't absolutely necessary?

Sorry if this issue has been posted somewhere already and thanks for any advice or tips you're able to share.

_

WorldFallz - October 2, 2009 - 15:28

With views and several other critical modules not in core for d7, I think it extremely unlikely you'll be able to recreate your site strictly with core for d7.

In any case, here's my plan of attack:

  1. list all my contribs.
  2. identify those that have been moved into core (ie cck, filefield, token, etc.).
  3. identify those I don't really need/want to bring forward.
  4. identify those that have a D7UX pledge
  5. check usage statistics for the remaining modules and identify any with less than 1000 est users.
  6. of those with less than 1000 users, evaluate the track record of the maintainer and either mark them safe, find an alternative, or decide if I have the skills necessary to maintain and/or port it.

_
Don't be a Help Vampire - read and abide the forum guidelines.
If you find my assistance useful, please pay it forward to your fellow drupalers.

I think there is no reason to

Spaiz - October 2, 2009 - 18:09

I think there is no reason to rush. Keep updated to a latest Drupal 6 version and consider moving to Drupal 7 3-4 month after it goes public. 3 - 4 months is a good term for most modules to be updated for D7.

Thank you for the tips

spangaroo - October 5, 2009 - 08:54

Thank you for the tips guys.

Right now I'm updating to 6.14 and made a few minor changes to the structure of my content via Views + Panels. With the change to D7, will these latest configurations become obsolete?

Themes
I've also refreshed my D6 theme, but wondering how much of a change is coming to the core in D7. I know some people won't upgrade due to if it ain't broke don't fix it rule, but I really dislike seeing the error messages in RED that state I need to update my core.

I'd like to stay up to date with the most recent security patches and added functionality if possible. Not sure how long it will take for some D7 themes to arrive right after the release of D7, or if it is even worth it since I'm putting a lot of time updating my D6 installation.

 
 

Drupal is a registered trademark of Dries Buytaert.