<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial,helvetica,sans-serif;font-size:10pt">Just to let people know, you won't be able to jump directly from CCK 4.7 to CCK 6.x, so if you use CCK you'll have to upgrade to 5.x first, anyway.<br><br>Both the 4.7 to 5.x and the 5.x to 6.x upgrades involved lots of complex database manipulation, and we had also been supporting upgrades from some very old and completely different database schemas from the early versions of CCK, so getting updates that would work reliably in every situation was becoming impossible. It was taking more time to write and debug the updates than any other part of the code. I finally bit the bullet and cut out the old update code in the D6 version.<br><br>I know that won't be popular, but if we're doing the same in core, at least it's consistent. And I suspect other contrib module authors would welcome a chance to cut out their
old update code, so maybe other modules will require an intermediate upgrade to D5 before going to D6.<br><br>Karen<br><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"><br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Michelle Cox <mcox@charter.net><br>To: development@drupal.org<br>Sent: Tuesday, December 4, 2007 10:19:14 AM<br>Subject: Re: [development] important reminder: do not use API functions inupdate code<br><br>
<br>I'm one of those hoping I can take a site from 4.7 straight to 6
without <br>having to go through 5 first. But my feeling is, if it works, great,
but <br>don't hold back progress or anything just to make it possible. If
keeping <br>the 2 version jump option is causing problems then I'll deal with
having to <br>do one version at a time.<br><br>Michelle<br><br><br><br><br></div><br></div></div></body></html>