Views using an InOperator filter cannot be saved if one of the ValueOptions doesn't exist anymore

Created on 8 September 2017, over 7 years ago
Updated 14 December 2023, over 1 year ago

Problem/Motivation

When editing a view with an InOperator filter, it cannot be saved if the ValueOption being filtered on doesn't exist anymore.

Proposed resolution

Prevent options from being removed or update the view when they are removed.

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component
ViewsΒ  β†’

Last updated about 9 hours ago

Created by

πŸ‡¬πŸ‡§United Kingdom timmillwood 🏴󠁧󠁒󠁷󠁬󠁳󠁿 Wales, UK

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡³πŸ‡±Netherlands Lendude Amsterdam

    Going through old issues for the Bug Smash Initiative.

    Now you get a fairly clear message: "No valid values found on filter: Content: Something." on the Views UI and the View stop displaying results until you fix it.

    We could add a config dependency to this field, but as always, the problem then becomes, what is the correct action to take? Just stop filtering on that value? That might lead to a information disclosure. If this was the only value filtered on, it's not doing anything, should we remove it?

    So, I think, what happens here is right, make the user fix the View and don't show anything until they do.

    Other thoughts?

  • Status changed to Closed: works as designed 7 months ago
  • πŸ‡¦πŸ‡ΊAustralia acbramley

    Agree with #15

    Please feel free to reopen with other ideas if appropriate.

Production build 0.71.5 2024