I have installed the the HS build from May 18th. I had a content_taxonomy fields which supported HS v2 and worked fine. They are not working in HS v3. HS v3 does work as a regular taxonomy.

This can be seen in the site I sent Wim with regards to #256813: Javascript makes IE freeze. If one tries to create an article, the taxonomy form works but below is the content_taxonomy field which does not work as expected.

CommentFileSizeAuthor
#2 content_taxononmy_widget.jpg6.43 KB32940stf
content_taxonomy.jpg34.09 KB32940stf

Comments

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Title: Cannot use content_taxonomy » Document upgrade path for content_taxonomy uses
Assigned: Unassigned » wim leers

Since version 3, you must no longer use the "Select" widget for Content Taxonomy fields. There is a separate "Hierarchical Select" form element now!

Also, content_taxonomy exposed filters are NOT supported. Only Taxonomy exposed filters. But that shouldn't be a problem, since you have to use "tag" or "both" in the "Save options" setting of a content_taxonomy field anyway.

This will need to be documented better to prevent similar support requests in the future.

32940stf’s picture

32940stf commented
StatusFileSize
new content_taxononmy_widget.jpg6.43 KB

Does that mean I should see a new widget if I am creating a new field or modifying my current field. I still only the original 3. See attached. (Or am I missing your point above completely and looking in the wrong place)

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

I think you have not yet enabled the corresponding module: Hierarchical Select Content Taxonomy.

32940stf’s picture

32940stf commented

That was it for the first step. Updating the documentation is a good idea. I am starting in on the testing now ;)

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Title: Document upgrade path for content_taxonomy uses » Document upgrade path
Category: support » task
Status: Active » Fixed

Documented in a new file: UPGRADE.txt. I documented the entire upgrade path, not just for content_taxonomy users.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.