CCK broken with drupal 4.7 beta 6? [#53839]

I just upgraded to beta 4.7.6, ran update.php, loaded the modules page again, but CCK doesn't seem to work anymore.

When I try to add new/edit content types/fields, I get a message telling me that everything went fine, but in fact something went wrong because the new content types/fields don't show up and the edits aren't registered. Looking into the database shows that the new additions/edits never made it into the database.

Moreover, if I try to add a new node for already created CCK content types, all the fields except the title field are missing, and the title field is now lacking its label.

What happened? Is it me who accidentally did something wrong, or is this happening to everybody and is actually a bug due to the update?

Comments

Comment #1

RayZ CreditAttribution: RayZ commented 14 March 2006 at 15:12

Title:

CCK broken with drupal beta 4.7.6?

» CCK broken with drupal 4.7 beta 6?

I am able to add a new CCK node with no problems using the latest drupal and cck cvs versions. See if you can recreate the problem with a fresh install of each and report back.

Comment #2

Permanently Undecided CreditAttribution: Permanently Undecided commented 14 March 2006 at 16:46

Thanks Ray for replying. With a fresh installation of Drupal 4.7 beta 6 and CVS CCK the problem doesn't occur and everything works smoothly. However, I tried upgrading again duplicating my site and using a database dump of my site that I did before upgrading the first time, and the problem occurs again with the second upgraded version too. Since CCK works with the fresh installation, it maybe has something to do with the upgrade itself? I have no other ideas on what might be wrong.

Comment #3

Permanently Undecided CreditAttribution: Permanently Undecided commented 15 March 2006 at 01:26

Status:

Active

» Fixed

I managed to fix this problem--I suddenly realized I'd forgotten to disable CCK before doing the upgrade.

Since I still had a copy of the non-upgraded version of my site (and the relative database dump), I was able to reinstate the old version, disable CCK from the modules page and upgrade again. This time CCK worked fine from the start.

I have no idea why disabling contributed modules before upgrading is necessary, but I realize now it is indeed good advice.