Hello, I've been updating my site from Drupal 5.7 to 6.2.

I made sure to upgrade to the latest CCK version for 5.x (5.x-1.7) before going through the update process. Then I downloaded the latest recommended version of CCK for 6.x which is, at the time of this writing, 6.x-1.0-alpha.

My problem occurs when I run update.php to update the database. At the "Select Update" stage I get a warning message relating to the fieldgroup module included with CCK:

"fieldgroup module can not be updated. Its schema version is 1. Updates up to and including 4 have been removed in this release. In order to update fieldgroup module, you will first need to upgrade to the last version in which these updates were available."

I'm starting to wonder if this is a bug in the fieldgroup module code, since I got no such warnings when I updated to the latest 5.x version for CCK. Is there something I can alter (maybe in fieldgroup.install) so that my fieldgroup module will update properly?

Thanks a lot,
Sally

Comments

spcalpo’s picture

spcalpo commented

Oh, and I forgot to mention... I don't think I've ever actually *used* the fieldgroup module before, or I may have activated it once several months ago but never actually used it for anything, and deactivated it some time before the updating to 6.2.

Not sure if this could contribute to the problem, but thought I'd say it just in case.

karens’s picture

karens commented
Category: bug » task

This is because the update from 5.x to 6.x requires that you get current in 5.x before the update. You must have activated fieldgroup before since it has a version number.

We've deleted some of the old upgrades from the modules since lots of them have some very old very crufty code from the earliest versions of CCK that were really messy. Fieldgroup is a special case, though. The missing updates are not so messy and it's probably not used as often and probably more likely to be turned on and off as you have done, so maybe I should add the missing updates back in for the fieldgroup module to avoid situations like this.

dropcube’s picture

dropcube commented
Version: 6.x-1.0-alpha » 6.x-1.x-dev
karens’s picture

karens commented
Status: Active » Fixed

I went ahead and added the updates back into the fieldgroup module since this is probably a likely scenario.

dries’s picture

dries commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.