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'..

Comments

dww’s picture

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.

colan’s picture

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.

dww’s picture

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.

colan’s picture

Title: Trimmed version of post configurabe on a per node-type base » Trimmed version of post configurable on a per node-type basis
coreb’s picture

Version: x.y.z » 6.x-dev

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

pasqualle’s picture

dww’s picture

Status: Closed (duplicate) » Active

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

pasqualle’s picture

Title: Trimmed version of post configurable on a per node-type basis » Teaser limits per content types
Version: 6.x-dev » 7.x-dev
BioALIEN’s picture

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

dave reid’s picture

crutch’s picture

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.

jody lynn’s picture

Status: Active » Closed (duplicate)

This is now in HEAD

nicks’s picture

In case people are wondering - teaserbytype is a Drupal 6 module to do this.

donquixote’s picture

Status: Closed (duplicate) » Needs review

We have a duplication loop :/
Can someone post a link to the correct issue, or can we mark one of them as "fixed" ? (and the others stay "duplicate")

It's not a big deal, but a bit confusing to click around trying to spot the original.
Thanks.

thedavidmeister’s picture

Issue summary: View changes
Status: Needs review » Fixed

There's no patch here, so there's nothing to review.

The paths mentioned in the issue summary no longer exist.

Limiting the length of a teaser (teaser field or field summary) would now be set somehow when defining how to render individual fields and so would have to do with the Render/Field API rather than the node system.

I think this ticket is no longer relevant to D7+ so I'm marking it as Fixed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.