Contextual Filters with Has Taxonomy Term ID no longer working

Created on 21 September 2018, over 6 years ago
Updated 14 December 2023, about 1 year ago

Steps to recreate;

  1. Created a new view
  2. Filtered to 1 content type
  3. Add a contextual filter "Has Taxonomy Term ID"
  4. Added validation criteria by restricting to specific vocabularies

At this point it appeared to be fine, upon reopening the contextual settings modal we discover none of the settings have been saved and the UI now appears broken.

We now have around 50 fieldsets for Access operation checks, none of which will retain the values when saving the view.

This was first discovered on a new build running 8.6. To confirm the issue we've installed 2 fresh copies of 8.6 and the problem persists.

The modal throws the following error in the JS console;

drupal.js?v=8.6.1:13 Uncaught TypeError: Cannot read property 'checked' of undefined
    at states.Dependent.compare (states.js?v=8.6.1:101)
    at states.Dependent.checkConstraints (states.js?v=8.6.1:165)
    at states.js?v=8.6.1:148
    at Array.every (<anonymous>)
    at states.Dependent.verifyConstraints (states.js?v=8.6.1:147)
    at states.Dependent.checkConstraints (states.js?v=8.6.1:168)
    at states.js?v=8.6.1:148
    at Array.every (<anonymous>)
    at states.Dependent.verifyConstraints (states.js?v=8.6.1:147)
    at states.Dependent.checkConstraints (states.js?v=8.6.1:168)

The attached images shown the initial error on screen along with a GIF demoing "Has Taxonomy Term ID" modal being scrolled after this issue appears.

πŸ› Bug report
Status

Closed: outdated

Version

9.5

Component
Views UIΒ  β†’

Last updated 21 days ago

Created by

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 bugs for the Bug Smash Initiative.

    #4 Sounds like this might have been solved by other issues.

    If this is still an issue please feel free to reopen this

Production build 0.71.5 2024