We have been asked by the community to make advanced search to work closer to what older Library catalog/search systems used to work, means to automatic update on results when you add/remove terms. To do so I will code some extra options (config options) so I can intercept the adding/removing of a term but without triggering a search. This is really not easy at all since Drupal needs to process input to be able to return exposed filters and the number of them, so probably this will have to be handled as a JS task. This implies also that only pressing the "Search" button itself will trigger a search.
At the same time there is a request to have minus (or remove) buttons for each row, instead a global one at the end.
Additionally we have been requested to allow Facet Summaries for Full text to have separate "remove" buttons per field. Also a complex task, since the fact that our exposed filter has multiple entries (text) is not visible really to Drupal. Views Filters tend to be atomic. To do so, I will have to keep track of each Sub element's id and make sure people can't trick the View into accepting un-filtered user arguments. This will be also an option, since by design we still find very useful the ability of clearing all "free text" search. This also means: removing a filter entry (means e.g the second row) will need to submit and refresh the view. We can't (or should we) act on "classic" mode for this, since Facet Summaries are their own module and we really have no control on the submit action on those.
@alliomeria please correct me if I'm reading this wrong.
DiegoPino
commented
9 months ago
What?
We have been asked by the community to make advanced search to work closer to what older Library catalog/search systems used to work, means to automatic update on results when you add/remove terms. To do so I will code some extra options (config options) so I can intercept the adding/removing of a term but without triggering a search. This is really not easy at all since Drupal needs to process input to be able to return exposed filters and the number of them, so probably this will have to be handled as a JS task. This implies also that only pressing the "Search" button itself will trigger a search.
At the same time there is a request to have
minus(or remove) buttons for each row, instead a global one at the end.Additionally we have been requested to allow Facet Summaries for Full text to have separate "remove" buttons per field. Also a complex task, since the fact that our exposed filter has multiple entries (text) is not visible really to Drupal. Views Filters tend to be atomic. To do so, I will have to keep track of each Sub element's id and make sure people can't trick the View into accepting un-filtered user arguments. This will be also an option, since by design we still find very useful the ability of clearing all "free text" search. This also means: removing a filter entry (means e.g the second row) will need to submit and refresh the view. We can't (or should we) act on "classic" mode for this, since Facet Summaries are their own module and we really have no control on the submit action on those.
@alliomeria please correct me if I'm reading this wrong.