In the update from 7.x-3.13 to 7.x-3.14, the code represented in the attached patch was removed (the patch adds it back in again). I haven't been able to find a justification for the removal of this specific filter type. We have code which depended on this behavior: Views stored in the DB as filtered with type "Term names converted to Term IDs separated by , or +" were now showing up as filtered by the default "Term ID", and now we can't filter on boolean AND/OR combinations of taxonomy terms at all. Is it safe to restore this behavior by applying the patch, or is there a good reason for disabling this feature?
Comment | File | Size | Author |
---|---|---|---|
converts.patch | 1.93 KB | aliddell | |
Comments
Comment #2
aliddell CreditAttribution: aliddell commentedPlease disregard -- this patch represents an undocumented alteration made to the code by a former maintainer of our site.
Comment #3
aliddell CreditAttribution: aliddell commentedComment #4
aliddell CreditAttribution: aliddell commented