When updating from 5.x-1.0 to 5.x-1.1, the new columns field_myfield_icon and field_myfield_shadow don't get added to the content_field_myfield table. After adding them manually (VARCHAR(250) NULL) things work fine.

CommentFileSizeAuthor
#3 geonames_cck.install.gz752 bytesAnonymous (not verified)

Comments

the greenman’s picture

the greenman commented

Sorry for the delay in response. Have been on holiday.

Yeah. This is irritating. To be honest, I have not yet found the correct way to add new fields to a cck table when I let CCK create the tables for me. Will work on it.

Anonymous’s picture

Anonymous (not verified) commented

No problem. Manually adding the columns worked for me and I only had one geonames_cck field.
I'll have a look at the cck update process to see if I can find a way to do this.

Anonymous’s picture

Anonymous (not verified) commented
StatusFileSize
new geonames_cck.install.gz752 bytes

Ok. I took some time to dig in to this. I couldn't find a clean cck way to do this, so I decided to write my own update function. As is applies to Geonames 5.x-1.* and it's the first update, I named it geonames_cck_update_5100.
I tested it for both cck field storage types (CONTENT_DB_STORAGE_PER_FIELD and CONTENT_DB_STORAGE_PER_CONTENT_TYPE) and it works fine on MySql. I didn't test it on pgsql.
I attached the geonames_cck.install file I created.

Gertjan