after content_taxonomy installation, hierarchical_select stops working. disabling the content_taxonomy will make it work again

CommentFileSizeAuthor
#4 content_taxonomy.patch.patch1.11 KBwim leers

Comments

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

I can't reproduce this, more details please.

AmirTheSeventh’s picture

AmirTheSeventh commented

let's wait and see if others encounter the same problem or not. it might be caused by latest commits to content_taxonomy, i'll get back to this next week and post more details.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Status: Active » Postponed (maintainer needs more info)
wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Assigned: Unassigned » wim leers
Status: Postponed (maintainer needs more info) » Reviewed & tested by the community
StatusFileSize
new content_taxonomy.patch.patch1.11 KB

Confirmed. Patch attached. When a content_taxonomy field was in a fieldgroup, it was being picked up. When it wasn't in a fieldgroup, it wasn't detected, because it was looking in the wrong place (content_taxonomy has changed since the original version of hierarchical_select was written).

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Version: 5.x-1.1 » 5.x-1.2
Status: Reviewed & tested by the community » Fixed
Anonymous’s picture

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