Teaser limits per content types

Stefan Nagtegaal - April 7, 2005 - 12:16
Project:Drupal
Version:7.x-dev
Component:node system
Category:feature request
Priority:normal
Assigned:Unassigned
Status:active
Description

The functionality to extract a teaser of a post - aka "trimmed verion" - should be configurable on a per node-type base. This will take care of a lot of bug reports we got and feature requests in #drupal-support..
So, in short we move the option "Length of trimmed post" from 'admin/node/configure' to 'admin/node/configure/types/$node->type'..

#1

dww - August 7, 2006 - 18:28
Version:4.5.2» x.y.z

i think this would be handy. moving to the right version...

note, in the current HEAD (pre 4.8), the global settings are on admin/content/node-settings (the link is called "post settings") and we should move them to the edit page for each node type under admin/content/types ... other than the length of the teaser, the only other things on the node-settings page are # of posts on the front page and if preview should be required or not. clearly, the # of posts needs to be global, but perhaps required vs. optional preview should be per-node-type, too? if both of those moved out, it'd make node-settings a pretty dumb page, and we should find a new home for the # of posts on the front page.

#2

colan - September 22, 2006 - 20:29

What about keeping the global page as it is? administer->settings->posts can hold global settings, and administer->settings->content types can hold override settings ("Length of trimmed posts" and possibly "Preview post") for each node type.

I don't like the idea of removing these global settings. If you want to change the length of trimmed posts globally with 30 node types and there's no global setting, then you have to make the same change 30 times.

Theme settings take advantage of this global/local concept.

#3

dww - September 22, 2006 - 21:55

sure, global vs. per-type over-ride sounds fine. feel free to write a patch for it. ;) i've got no time these days for something like this, and i don't actually need it for any of the sites i deal with.

#4

colan - October 13, 2006 - 22:24
Title:Trimmed version of post configurabe on a per node-type base» Trimmed version of post configurable on a per node-type basis

#5

coreb - November 30, 2006 - 02:05
Version:x.y.z» 6.x-dev

Moving out of the "x.y.z" queue to a real queue.

#6

Pasqualle - September 16, 2008 - 02:34

#7

dww - September 16, 2008 - 06:08
Status:duplicate» active

This is the oldest issue, and should be the active. All the others are duplicate of this.

#8

Pasqualle - September 16, 2008 - 13:01
Title:Trimmed version of post configurable on a per node-type basis» Teaser limits per content types
Version:6.x-dev» 7.x-dev

#9

BioALIEN - September 16, 2008 - 19:33

My issue #122781: Configure teaser limits per content types was flagged as a duplicate of this. Subscribing here instead.

#10

Dave Reid - October 10, 2008 - 23:05

#11

crutch - February 20, 2009 - 04:11

This is something that I'm interested in. For example, if I have an image with tags, I want to set a post setting for Tag results specifically (Taxonomy [terms][vocabulary]).

The problem is that if I set the global post settings to three (3) for the front page, then when clicking/viewing a taxonomy term (tag), it is also set to that global setting and I have no way to allow more postings to show for the taxonomy/term.

Optimum config for me would be to have a post setting for the Front Page RSS feed and then a post setting for the Taxonomy (Tags) RSS feed.

 
 

Drupal is a registered trademark of Dries Buytaert.