You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a follow-up task that was mentioned in #2074 (where we removed the tag default from all core views).
Now with Views in core and also with admin_views in core, I think that it would make sense to be adding:
a core tag for all views provided by core
a custom tag for all views manually added to the site
a %module name% tag for all views regardless of whether they are core/contrib/custom (we currently have a "Default (module-provided)" indication in the "Storage State" column, which is not very useful, but it would be if the module providing the view was also indicated). If not a tag, this could be a new provided-by property.
As it is now, these tags would have no value, but if we added an instant search filter at the top of the views list (#503), then it would be very useful, because as you must have also experienced yourselves, most sites end up with a few dozens of views.
Anyways, I have previously filed #1897 in which I mention the same issue. Similar/related but different problems.
The text was updated successfully, but these errors were encountered:
This would make sense. Just to say while is correct to say that nothing would change initially, this would actually be useful for Admin Bar Views Grouping
I fully support all efforts to make better use of Views tags and also improve the UI for setting them.
This is a follow-up task that was mentioned in #2074 (where we removed the tag
default
from all core views).Now with Views in core and also with admin_views in core, I think that it would make sense to be adding:
core
tag for all views provided by corecustom
tag for all views manually added to the site%module name%
tag for all views regardless of whether they are core/contrib/custom (we currently have a "Default (module-provided)" indication in the "Storage State" column, which is not very useful, but it would be if the module providing the view was also indicated). If not a tag, this could be a newprovided-by
property.As it is now, these tags would have no value, but if we added an instant search filter at the top of the views list (#503), then it would be very useful, because as you must have also experienced yourselves, most sites end up with a few dozens of views.
Anyways, I have previously filed #1897 in which I mention the same issue. Similar/related but different problems.
The text was updated successfully, but these errors were encountered: