This has happened to me twice now on 8.x. I am editing a view and leave the Views UI window open for quite a while. To my surprise, when I come back later the view has been deleted entirely and is no longer on the list. There are no watchdog entries to indicate this happened

Side issue in this case: To make matters more annoying, from my backup, I can't get Config to export a suitable view snippet that can be easily imported to the dev instance. It complains about weird things like modules being required that are not actually required for the view at all, but I think related to the UUID or some other aspect of the config system.

The correct behavior would be to make a confirmation page have to be approved before any view is removed entirely. I looked around the issue queues and could not find any issues corresponding to this. The workaround would be to paste an exported views config object from a backup. Somewhat related #2416109: Validate configuration dependencies before importing configuration

Comments

HongPong created an issue. See original summary.

cilefen’s picture

Whew. This makes no sense. Could you leave your browser's console open to the network tab and see if anything was posted if it happens again?

davidhernandez’s picture

Are you editing an existing view or creating a new one?

dawehner’s picture

This sounds a bit like an accidental removal when a field got removed, which was part of the view somehow. This could look like a related issue.
On a normal case we actually save the view already (unlike in D7) when the view got created the first time.

HongPong’s picture

Sure I'll try to watch for this to happen again, maybe bait it into happening on a test server. I know for a fact that I didn't delete the view (also this was an edit of an existing view, not an unsaved new view). Maybe related: my workstation has something wrong with its power supply and shut off upon sleep a few times lately. I think yesterday, the view UI was open, the computer shut off, I rebooted and restored my browser sessions. It also happened one previous time. Unlike D7 it seems like they are a little more slippery - I never had a view delete unexpectedly on D7 or D6.

I'd suggest also adding an option to log ( https://www.drupal.org/node/2595985 ) the deletion of views. If someone wants to clue me into how I could pull that off in a patch, might take a shot at it.

Version: 8.1.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Branches prior to 8.8.x are not supported, and Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

quietone’s picture

Status: Active » Postponed (maintainer needs more info)
Issue tags: -views +Bug Smash Initiative, +Needs steps to reproduce

Anyone else experienced this problem?

This needs complete steps to reproduce the issue (starting from "Install Drupal core") to move forward with this issue. Adding tag.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Status: Postponed (maintainer needs more info) » Closed (outdated)

It has been over a year and there has been no response and no further comments that anyone is having this problem.

Therefore, closing as outdated. If this is incorrect reopen the issue, by setting the status to 'Active', and add a comment explaining what still needs to be done.

Thanks!