Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Hi,
Using content_taxonomy to insert field with CCK for content type via Hierarchical Select causes the following error. Eventhough it is initially saved, but later the selection cannot be retrieved from from select menu. However, normal taxonomy assign to a content type assignment works fine.
warning: Illegal offset type in C:\wamp\www\drupal\sites\all\modules\content_taxonomy\content_taxonomy_options.module on line 159.
Comments
Comment #1
wim leersSigh. I guess this really is caused somehow by the Hierarchical Select module, then.
I will need screenshots of your Hierarchical Select settings, but also screenshots of *all* the content_taxonomy settings, because I personally can't reproduce this.
Or if your site is live, send me the login details and give me FTP access.
Comment #2
najibx commentedIt's all good now.
While preparing a demo to you, I found out a clear answer (but not really a solution though).
Here's the scenario, if if the vocab setting, you select this vocab allow multiples values, in taxonomy_fields, it also allow "Data settings" for the taxonomy which sometime can overrides the original setting. In earlier case, my data setting is not match with the original vocab setting. Once I set both the same (allow multiple values), the problem is gone.
I suspect this more taxonomy field issue than Hierarchical Select.
Thanks for your kind attention and sorry for troubling you :-)
Comment #3
wim leersAhah! Thank you VERY much. Several people have reported this issue, and I was unable to duplicate it. Now I have a place to redirect them too :)
Would you also be so kind to make a new issue for this in the content_taxonomy issue queue? This could obviously be improved in content_taxonomy's UI.
Comment #4
najibx commentedOK, I posted it there. Conflict if "Data settings" not the same with Vocab setting
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.