Add a 'disabled' section to config changes page when removing config

Created on 2 December 2016, almost 8 years ago
Updated 27 June 2023, over 1 year ago

Follow up for πŸ› When deleting a content type field, users do not realize the related View also is deleted Fixed .

When removing config display a message or add a 'disabled' fieldset that shows any disabled config.

Currently only a message is logged but no other feedback is given to the user that a config has been disabled. Currently this is grouped under the 'updated' config. More precise feedback would probably be better.

πŸ“Œ Task
Status

Needs work

Version

11.0 πŸ”₯

Component
ConfigurationΒ  β†’

Last updated 1 day ago

Created by

πŸ‡³πŸ‡±Netherlands Lendude Amsterdam

Live updates comments and jobs are added and updated live.
  • VDC

    Related to the Views in Drupal Core initiative.

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.

  • πŸ‡ΊπŸ‡¦Ukraine vlad.dancer Kyiv

    For me, this issue might be wontfix, and we should instead focus on how to actually communicate to users what config is being updated or deleted

    @xjm oh, really? Thank you, but no, we shouldn't!

    I lost recently a day of local work while just tried to use views_natural_sort module in my views.
    The same as here https://www.drupal.org/project/better_exposed_filters/issues/2992372#com... πŸ› When module uninstall, view is deleted Active
    And don't say me that I should backup such things!

    I'm sorry but I feel myself very upset.
    I wish nobody never get into this situation.

    Why not just introduce "trash bin" concept without restoring, just to store any config deletions! Let's say "config_deleted" or "config_r__0ab2f8e96b" and so on?

  • πŸ‡ΊπŸ‡ΈUnited States pcrats33

    If you're not going to fix this.. at least put in a graphic of a thug with a crowbar breaking a computer or something severe. First timers are almost 100% not likely to get the extent that they will lose their views. In my case, I lost the built in Content view that lets me search content from the back-end administration page. Luckily my test site hasn't been changed yet, and still has the view. I'm not exactly sure how easy it will be for me to eyeball-copy/create it from two browser windows. Is there a better way to extract/import views? If the infrastructure doesn't play well with disabling views.. can you make it easy to export a view to json and import a view from json? Perhaps export all deleted views to a .json file for backup?

  • πŸ‡ΊπŸ‡ΈUnited States guymandude

    I just came across this as a very recent user to D9/10. I deleted a field from a Content Type and it broke the Views that were using it. Very annoying to say the last, but more importantly it's a recipe for disaster. I also found I cannot simply edit the broken View and remove the same field from it to fix it quickly. The old fields are not visible on the View edit page any more!

    The View was disabled which was helpful to understand what had happened, but can you not configure it such that a reference to the broken field is still visible allowing easy removable from the Views edit page?

Production build 0.71.5 2024