Problem/Motivation

When having no arguments set up for the block, it still passes them to search api autocomplete.
This results in an error displayed to the end user "Illegal choice Changed in Sort on element."

Steps to reproduce

You need a search api view. Set the form in a block and do not add any arguments.
Have the search view sort on more than 1 field. For example: Relevance and Changed

Proposed resolution

We need to check if we have any arguments added to the block config, before passing them to search api autocomplete.

Remaining tasks

None.

User interface changes

None.

API changes

None.

Data model changes

None.

CommentFileSizeAuthor
#2 3196796-illegal_choice-2.patch1.24 KBtim-diels

Comments

tim-diels created an issue. See original summary.

tim-diels’s picture

Status: Active » Needs review
StatusFileSize
new1.24 KB

  • Antonnavi committed 6229f14 on 8.x-1.x authored by tim-diels
    Issue #3196796 by tim-diels: Illegal choice Changed in Sort on element
    
antonnavi’s picture

Status: Needs review » Fixed

Hello Tim Diels,

Your changes were committed to the module DEV branch.
Thank you for help!

Status: Fixed » Closed (fixed)

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