Fields removed from View still appear in config dependencies

Created on 17 May 2018, over 6 years ago
Updated 21 September 2024, 2 months ago

Removing a field from a view does not necessarily remove it from the config dependencies.

I removed the following fields from my view :

- field.storage.group.field_bid_closure_date
- field.storage.group.field_bid_length
- field.storage.group.field_bid_open
- field.storage.group.field_bid_start_day
- field.storage.group.field_current_bid_period
- field.storage.group.field_earliest
- field.storage.group.field_latest_bid_date

However, if I export the view the config still references them, meaning the view would be deleted if I deleted the fields:

dependencies:
  config:
    - field.storage.group.field_bid_closure_date
    - field.storage.group.field_bid_length
    - field.storage.group.field_bid_open
    - field.storage.group.field_bid_start_day
    - field.storage.group.field_current_bid_period
    - field.storage.group.field_earliest
    - field.storage.group.field_latest_bid_date
πŸ› Bug report
Status

Closed: works as designed

Version

11.0 πŸ”₯

Component
ViewsΒ  β†’

Last updated about 10 hours 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.

  • πŸ‡¦πŸ‡ΊAustralia pameeela

    As already noted, the view is no longer deleted if a referenced field is deleted, but still I am not able to reproduce this. In some quick testing, the config was updated to remove the dependency. So this still may be valid but it needs specific steps.

    Here is what I tested:

    1. Add a field to a content type field_new_field_test
    2. Add the field to a view display
    3. Check the field is listed in config as a dependency
    4. Remove the field from the view
    5. Check the config, the field is no longer listed

    Based on #6 I also tested this:

    1. Enabling default display in views settings
    2. Add the field to the default display
    3. Check the field is listed in config as a dependency
    4. Disable default display
    5. Remove field from non-default display
    6. Check the config, the field is no longer listed

    Screenshots showing before and after of config:

  • Status changed to Closed: works as designed 2 months ago
  • πŸ‡³πŸ‡ΏNew Zealand quietone

    I also was not able to reproduce this using a fresh install of Umami.

    If you are experiencing this problem on a supported version of Drupal reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue β†’ (starting from "Install Drupal core").

Production build 0.71.5 2024