Possible Duplicate:
How to prevent access to Views-only content?

Sometimes I build a content type whose data really only makes sense to display in a View. An example would be a content type called "Slide" and a View called "Slideshow". I may not want people or search engines to actually go to the node because the slideshow is displaying a series of slides, and by itself, the "Slide" is not very interesting.

So what strategies do site builders usually employee in this situation? Do they style the "Slide" node so that if someone goes there, it looks OK? Do they un-publish the "Slide" so only admins can access it, and then program the view to not filter on only published content?

  • If this question is closed as an exact duplicate, it would be nice if the system linked to the previous question. – JM01 Mar 7 '12 at 15:06

A couple strategies here...

One is the obvious one you mention: Don't publish the 'Slide' content type, so it never appears on the 'live' site.

Another is that you don't make special 'slideshow' content types. You just add fields to your normal content types that will be displayed in a slideshow display mode. Then you hide them for other display uses like Default and Teaser.

Drupal's flexibility with this type of scenario is one of its major strengths. But it also means that site editors have to remember which field does what, or which type of nodes not to publish.

|improve this answer|||||
  • What the OP called "Slideshow" is a view, not a content type. – kiamlaluno Feb 25 '12 at 21:55

Not the answer you're looking for? Browse other questions tagged or ask your own question.