The widget always pre-selects first value in vocabulary when it is required field [#1949624]

Comment #1

PlayfulWolf CreditAttribution: PlayfulWolf commented 21 March 2013 at 22:48

Ok, 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

Log in or register to post comments

Comment #2

PlayfulWolf CreditAttribution: PlayfulWolf commented 22 March 2013 at 10:26

Priority:

Major

» Normal

changing priority to more appropriate

Log in or register to post comments

Comment #3

surtr CreditAttribution: surtr commented 9 April 2013 at 04:51

+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.

Log in or register to post comments

Comment #4

stBorchert

he/him

German

CreditAttribution: stBorchert commented 30 April 2013 at 13:41

Status:

Active

» Needs review

I have committed some changes so the widget behaves more like the original term reference widget.

Log in or register to post comments

Comment #5

PlayfulWolf CreditAttribution: PlayfulWolf commented 20 May 2013 at 19:30

Status:

Needs review

» Reviewed & tested by the community

everything works on dev version

Log in or register to post comments

Comment #6

stBorchert

he/him

German

CreditAttribution: stBorchert commented 21 May 2013 at 06:03

Status:

Reviewed & tested by the community

» Fixed

Good to hear. "Fixed" then ...

Log in or register to post comments

Comment #7

4 June 2013 at 06:10

Status:

Fixed

» Closed (fixed)

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

Log in or register to post comments

Comment #8

oenie CreditAttribution: oenie commented 5 July 2013 at 09:44

Status:

Closed (fixed)

» Needs work

This all seems to work fine as a field, but the same issue still stands when being used as a filter in views

Log in or register to post comments

Comment #9

oenie CreditAttribution: oenie commented 5 July 2013 at 11:19

Issue tags:

+#1949624

After more checking, it seems this has been reintroduced by #1945446: Support entityreference field type.

Log in or register to post comments

Comment #10

oenie CreditAttribution: oenie commented 5 July 2013 at 11:20

Removed tag

Log in or register to post comments

Comment #11

svouthi CreditAttribution: svouthi commented 15 August 2013 at 00:53

I 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! :)

Log in or register to post comments

Comment #12

svouthi CreditAttribution: svouthi commented 15 August 2013 at 02:39

Thank 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.