Hello,

I'm in. I've got too the message
Theme (field_theme) is an inactive Content Taxonomy Fields field that uses a Hierarchical Select widget.
I try desactive and reactive.
I update manualy the database.
But, nothing to do. I can not use my v5.x ckk conten taxonomy widget.
# ALTER TABLE {content_field_theme} CHANGE `field_theme_value` `field_theme_value` INT DEFAULT NULL
# ALTER TABLE {content_field_theme} ALTER COLUMN field_theme_value DROP DEFAULT
# UPDATE {content_field_theme} SET field_theme_value = NULL WHERE field_theme_value = 0
For informacion, when i updage i've got, for example this message :
But the table wich is coresponding is empty.

Any idea of what i can do ? Thanks in advance.
JD

Comments

jdotti’s picture

jdotti commented

Hello,

I'm on V6.x version. I try create manually the field, it is working and look in mysql table got the same datas than the oldest.
Other informacion, the manually create one doesn't take the taxo thems which exist...

Any idea ?

Thanks
JD

plan9’s picture

plan9 commented

Hi

I had the same issue. The solution for me was as follows:

Before upgrading to 6.x - in your D5 install go to: admin/content/types and edit your content type field that uses the Hierarchical select widget. Click 'change basic information' and change the widget to 'select list'.

Perform the upgrade using instructions found here: http://drupal.org/node/340073 also note the cck advice here: http://drupal.org/node/822352

When you have got all of your contributed modules enabled in the 6.x install go back to admin/content/types and edit your content type field - changing the widget back to Hierarchical select.

You should find your field is now accessible.

I hope this works for you.

G

manoloka’s picture

manoloka commented

I did something that worked using Plan9 suggestion

Instead of going back to the old Drupal5 installation, I went to the database, found the content_node_field_instance table and change the instance for my widget from content_taxonomy_hs to content_taxonomy_select.

Then I unistalled and reinstalled the related content taxonomy modules ... and boila, it's working.