Closed (won't fix)
Project:
Views (for Drupal 7)
Version:
6.x-3.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
24 Jul 2009 at 20:50 UTC
Updated:
25 Dec 2009 at 08:58 UTC
With views and panels being used extensively across a site some sites may end up with 20-40+ views with a few displays on each as well as 20+ panels on a site. It would be very useful on the views admin edit page to show the panels (and possibly other entities) that are using the view or it's displays.
That way a user could visit a view edit page, go to a display, and see the list of panels or panel pages that use that view. It would help prevent editing views settings in cases where the same view display is used in a lot of locations. :-)
Comments
Comment #1
dawehnerThats definitive kind of sensefull.
I'm wondering whether this should be provided by panels or views, because panels know which stuff is used.
Comment #2
jvieille commentedThat is a must to have requirement.
I have many views in one site I don't remember at all where they are used, but I know half of them are obsolete.
I would have to carrefully look at each Views CCK field and menu entry to check what is in used and deduct what is obsolete or redundant.
The reason for such an elementary feature being not available might be some difficulty to scan the views references in the database?
In the meantime, a "disable" option could help to put on hold guessed obsolete view before deletion
Comment #3
merlinofchaos commentedI don't think there's really any way to do this, particularly if you're using Panels or CCK or something. External modules use Views in ways that Views cannot detect.
Comment #4
jvieille commentedThis is what I guessed.
Would it be difficult to have a "disable" option that would allow to put aside the views that don't seem to be used?
This way, one can place on hold these views for a given observation time instead of deleting them and having to redo everything if the view proved later to be used?
Thanks
Comment #5
merlinofchaos commentedAdding a disable feature to views in the database is something I would like to do. It will probably happen during hte conversion of Views to getting rid of its own custom code for exports and using CTools export.inc instead.
Comment #6
jvieille commentedGreat!
Merry Christmas