Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Problem/Motivation
Views is now in core, it is confusing for views settings to be under structure/views/settings. A user with no prior views experience should expect views settings to be located in configuration.
Proposed resolution
Re-evaluate the views settings pages and put the settings into the core settings/configuration pages as they should be now that view is in core.
Remaining tasks
discuss
plan
execute
User interface changes
This will remove the settings page from the familiar structure/views/settings route and place the settings in line with the rest of drupal core.
API changes
none.
Comments
Comment #1
nod_That makes sense to me.
Comment #2
tim.plunkettHmm, it seems odd to have the two halves of the Views UI split across two sections. It might be more correct from an Information Architecture point-of-view, but does that really make it more usable?
Comment #3
frobI am bring it up here because I was using trying out building views of config things. I wanted to see the queries that where being generated and so I went to the views settings pages, exactly where I expect them to be. However, if I wasn't experienced with Drupal that isn't where I would expect them to be because no other thing in structure has a settings page or anything resembling a settings page.
For example, here are the settings options:
Basic
LIVE PREVIEW SETTINGS
Advanced
CACHING
Disable views data caching
Views caches data about tables, modules and views available, to increase performance.
By checking this box, Views will skip this cache and always rebuild this data when needed.
This can have a serious performance impact on your site.
Clear View Cache ButtonDEBUGGING
Add Views signature to all SQL queries
All Views-generated queries will include the name of the views and display 'view-name:display-name' as a string at the end of the SELECT clause. This makes identifying Views queries in database server logs simpler, but should only be used when troubleshooting.
I would expect Caching to be in performance along with the other cache settings (unless this is completely rethought now that block caching has become more independent.
The rest should probably be taken over to its own page in the config/development section.
It just feels like views is a bolted on piece of non-core that is there and doesn't with the usability of the rest of D8.
Comment #4
frobComment #5
frobComment #6
frobClarified the title