Multiselect: Empty terms are still active

Anonymous

#134083

Thank you Trevor!

Ross Moderator

#135326

This reply has been marked as private.

Anonymous

#135352

Dear Ross, thanks for checking. I understand what you mean.
The categories should be dominant for this job.

The best way I see is to kill all entries of the multibox before Ajax submit.
However, all shared tags are also deleted. :/

$(".sf-input-select").val('').trigger("chosen:updated");

Cheers!
Kai

Ross Moderator

#135970

Hi Kai

I’ve been thinking, and there may be a slightly cleaner way to do this.

Why not, when a user clicks a category (which is before the submit & ajax is processed), clear the values of the other field and do the chosen trigger then? Rather than to do it after the submit event, and submitting again a second time?

Something along the lines of (untested):

$('.sf-field-taxonomy-download_cat input').on('change', function(){
    $(".sf-field-taxonomy-download_tag .sf-input-select").val('').trigger("chosen:updated");
});

Then S&F will carry out its submit processes, and should in theory perform the search with the values you want.

Hope that helps

Thanks

[Author]

Posts