By mkjones on

Hey everyone, I messed up when I upgraded to v6 from v5 becuase my CCK was so old. I got a weird "Updates up to and including 1008" error which I couldn't fix.

Turns out I never used CCK in my site, it was just on my server and enabled. SO, I was thinking I could just clear out the tables in my database so the errors would go away and I could install it in the future without worry.

Can anyone tell me which are the CCK tables so I can delete them all?

Comments

vm’s picture

vm commented

seems to me you can use the uninstall tab in adminsiter -> modules and have CCK remove it's own entries into the DB.

mkjones’s picture

mkjones commented

Do you mean by simply disableing the module? I did this and when it was re-enabled the error returned (its a database issue between versions). Prompting me to guess that the tables remain in place.

However you may be right. I will re-upload the module, re-enable, and see what I can get.

mkjones’s picture

mkjones commented

Riiiight..

I re-uploaded and and re-enabled CCK now it says:

user warning: Table 'database_db.cache_content' doesn't exist query: DELETE FROM cache_content in /home/.hizanherz/****

mkjones’s picture

mkjones commented

OK

I've sort of fixed it.

By running:

CREATE TABLE cache_content
(
cid varchar(255) NOT NULL default '',
data longblob,
expire int NOT NULL default '0',
created int NOT NULL default '0',
headers text,
PRIMARY KEY (cid),
INDEX expire (expire)
)

Which I got the info from: http://drupal.org/node/314929

The error no longer appears in my admin panel as I now have the right table in place, even if its empty.

However, when I run the update.php I STILL get the annoying:

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

Which I really can't understand.

mkjones’s picture

mkjones commented

FIXED:

The table I was after was the "system" table and the "modules/cck/content.module" record.

I initially ran this:

UPDATE `data_db`.`system` SET `schema_version` = '5999' WHERE CONVERT( `system`.`filename` USING utf8 ) = 'modules/cck/content.module' LIMIT 1 ;

Which updated the schema to the same version as the other CCK elements in the database.

Run the update, re-enabled CCK, run the update again, sorted.