Closed (fixed)
Project:
Views (for Drupal 7)
Version:
6.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
27 May 2009 at 12:41 UTC
Updated:
2 Jan 2014 at 19:06 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dawehnerwhat should this view do?
should the view override node/% or should it be a example for filtering by story/page nodetype?
Comment #2
merlinofchaos commentedYou might see SimpleViews for this, though I agree that more default views, in general, are not a bad idea. They can start off disabled very easily so they aren't too intrusive, and provide wonderful examples. Patches (or even exports of good views that work with just Drupal core) are welcome!
Comment #3
iantresman commented"should the view override node/% or should it be a example for filtering by story/page nodetype?"
Yes, I would include one of each. As merlinofchaos says, they are disable by default, and aren't intrusive. Hence a good starting point.
Comment #4
merlinofchaos commentedViews cannot be used to override node/% -- don't try it. The results are not what people want or expect.
Comment #5
iantresman commentedThis is the first time I've heard of this... and I did get odd results. Could a warning be displayed if anyone tries this? And/or describes what does happen of someone tries to override node/%
Update: 3 Aug 2010: See also my post and thread "Views: Overriding a node layout" for alternative workarounds.
Comment #6
merlinofchaos commentedIn theory the fact that Views generates lists of content and node/% is a single piece of content I would think would give people pause. I'd rather simply document it than actually throw up a warning, because there's any NUMBER of pages that would be unhealthy to override and node/% is just the one people try the most often.
Comment #7
dawehnerHere is a analyze patch for this.
Comment #8
merlinofchaos commentedCommitted to all branches.