Almost one year has past since I put together this small post. Moving these days from D6 to 7 is certainly safer and less nerve wrecking though I never think i will be a cakewalk.
I still have a few more complex sites running D6. Knowing these sites, I know they are complex and a strait forward upgrade will prob. not work. For one of these do I actually think that moving only the content users are a quicker and safer way of doing the upgrade.
- Do a minimum install of D7
- Build needed content types and config.
- Recreate the theme in D7 or port existing. Perhaps depend on how much preprocessing and other custom stuff you got.
- Use http://drupal.org/project/feeds to copy content, taxonomy and users.
Some of these D6 sites got a lot of custom stuff in the theme for the user profile pages. The old D6 core profile module was never very flexible. So all of this prob. should be recreated in a more standard way by using profile2 and contex/page-manager. There are also issues with GEO data if your D6 site contain these type of functionality, though upgrading GEO data created with the location module have worked just fine on a few sites.
thanks man. i had basically no problems with core updates. the fun began with migration of cck and some other small modules errors in update hooks. finally i ended up doing manual work with the cck part. especially with list fields that got the wrong keys in the db (after cck migrate).
ashok, i would use xdebug to stop at these lines and analyze the arrays.
Almost one year has past since I put together this small post. Moving these days from D6 to 7 is certainly safer and less nerve wrecking though I never think i will be a cakewalk.
I still have a few more complex sites running D6. Knowing these sites, I know they are complex and a strait forward upgrade will prob. not work. For one of these do I actually think that moving only the content users are a quicker and safer way of doing the upgrade.
- Do a minimum install of D7
- Build needed content types and config.
- Recreate the theme in D7 or port existing. Perhaps depend on how much preprocessing and other custom stuff you got.
- Use http://drupal.org/project/feeds to copy content, taxonomy and users.
Some of these D6 sites got a lot of custom stuff in the theme for the user profile pages. The old D6 core profile module was never very flexible. So all of this prob. should be recreated in a more standard way by using profile2 and contex/page-manager. There are also issues with GEO data if your D6 site contain these type of functionality, though upgrading GEO data created with the location module have worked just fine on a few sites.
--
Stein
thanks man. i had basically no problems with core updates. the fun began with migration of cck and some other small modules errors in update hooks. finally i ended up doing manual work with the cck part. especially with list fields that got the wrong keys in the db (after cck migrate).
ashok, i would use xdebug to stop at these lines and analyze the arrays.
I'm also looking for D7 solution.
Drupal7 for a solution?