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.
Recent comments
well @herb I cannot believe it, but the webform module was there in modules on the disc, but missing in the listed modules, so I delete the module folder, and downloaded it again. Then...
My Webform Worksheets have disappeared
The only thing I can think of is to make sure Webform module is enabled and that the content type that needs to contain the webforms has Webform enabled for it. Edit the content type and make...
My Webform Worksheets have disappeared
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists