-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deleting a view #1325
Comments
@Graham-72 Is this what you need? |
.Yes thanks. I was in a muddle because I cloned an admin view and then found no delete option. |
Ah, thanks @Graham-72! That's a tough bug to find! I bet when we clone an a default view provided by a module, we don't update it's "storage" value in the config file to indicate it's a user-created view, so it still thinks it's a default, module-provided view. If you use the "Revert" option, does it delete the view? Internally, Revert and Delete use the same form, but Revert copies in a default version of the view from whatever module provided it. |
Yes, it does delete it. Although from the on-screen comments "Reverting the view Clone of Admin Content will restore it to the original settings provided by the "node" module." and "The view Clone of Admin Content has been reverted to its defaults." one might expect, after editing a clone, to revert to the unmodified clone. I have just discovered how useful it is to be able to clone and then adapt an admin view in order to show pre-selected types of content, also both published and all unpublished rather than just 'own unpublished'. I'm happy! |
That's the whole point of Administration Views in core, a.k.a. #151 😉 |
Respect! |
How do I delete a view that I have created but no longer need? Is there a menu option somewhere or should I just delete the configuration file from the active config files?
The text was updated successfully, but these errors were encountered: