Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When creating the content widget is pre-selected with "FirstTerm", but should be when it is a required field.
It still should preselect , because now user may forget that he needs to select it consciously
Comments
Comment #1
PlayfulWolf CreditAttribution: PlayfulWolf commentedOk, clarification: it is "First term" selected, but has to be "none", because in many occasions users will miss that and first term will go by default
Comment #2
PlayfulWolf CreditAttribution: PlayfulWolf commentedchanging priority to more appropriate
Comment #3
surtr CreditAttribution: surtr commented+1
Behavior I'm seeing described differently for devs' benefit:
Using an exposed SHS filter in a view, when marking the filter as "required", the SHS widget shows up with the first taxonomy term selected but does not show the second dropdown with the first term's children. Must select another value for the second dropdown to populate.
Comment #4
stBorchertI have committed some changes so the widget behaves more like the original term reference widget.
Comment #5
PlayfulWolf CreditAttribution: PlayfulWolf commentedeverything works on dev version
Comment #6
stBorchertGood to hear. "Fixed" then ...
Comment #8
oenie CreditAttribution: oenie commentedThis all seems to work fine as a field, but the same issue still stands when being used as a filter in views
Comment #9
oenie CreditAttribution: oenie commentedAfter more checking, it seems this has been reintroduced by #1945446: Support entityreference field type.
Comment #10
oenie CreditAttribution: oenie commentedRemoved tag
Comment #11
svouthi CreditAttribution: svouthi commentedI am using SHS widgets as required exposed filters in two views. One of these is three levels deep, and all three fields prepopulate. Oddly, the first and second fields autoselect the second terms of their levels while the third field preselects the first term. I tried clearing all my caches in case a past selection wasn't being ignored, but this still occurs reliably. The SHS widget in my other view preselects the first term as others have mentioned. Another difference is that the first view, with all three levels prepopulated, displays the results for that selection, whereas the second view with one level prepopulated shows no results.
It would be great to see the same selection behavior as in 7.x-1.6, as I am using SHS as a menu to show only content which is relevant to the user (rather than everything at once.) I installed 7.x-1.x-dev so that I would be able to use JS callback handler module, and I love the fast action, but now my site is broken! :)
Comment #12
svouthi CreditAttribution: svouthi commentedThank you for the commits, stBorchert. I applied them and initially all my fields were prepopulating yet. However, after removing my SHS exposed filters in my views and then adding them again, they function normally. Thanks again.
Comment #13
stBorchertFrom the last comment I would guess this is fixed ...
Comment #15
YesCT CreditAttribution: YesCT commentedRemoving tag. See guideline: Do NOT use tags for adding random keywords or duplicating any other fields.