Move teasers to contrib [#745614]

On all of the many Drupal sites I've created, if the teaser feature shows up, it causes problems. Even time it shows up, I bang my head against the wall re-figuring out how to eliminate it.

I did some Google searches on teasers and usability, and I suspect teasers are either 1. a niche feature or 2. an outdated feature from the dial up days. Either show me the entire article or show me a headline. I don't want a teaser.

Does #372743: Body and teaser as fields allows me to definitively ditch teasers on sites? I've waded through it, and it's not clear.

If not, should I make a new feature request (or task) for this enhancement? Should teasers be moved out of core?

Comments

Comment #1

yched commented 18 March 2010 at 09:51

Category:

support

» feature

Right now you have to remove the 'body' field and create another text field (like in D6)

Ideally I think you should be able to use a 'simple textarea, no summary input' widget on the 'body' field, but that would require a patch to make the text_textarea widget work on fields of type text_with_summary.

In a related note, I just noticed that text_textarea_with_summary widgets have a summary_rows setting, but it's not configurable in text_field_widget_settings_form().

Comment #2

yched commented 18 March 2010 at 09:53

Patch welcome, I my time online is really scarce currently :-/.

Comment #3

aren cambre commented 19 March 2010 at 00:42

Title:

Move body summaries to contrib

» Move teasers to contrib

I'm going to be bold and say we should move teasers out of core. I have yet to need it, so for me it's just code bloat and pointless database complexity.

Also, even if I needed to display a blurb below an article to entice hits, I need a hand-crafted summary, not an split point in the middle of an article.

Comment #4

naheemsays commented 18 March 2010 at 16:19

Title:	Can I now disable teasers entirely?	» Move teasers to contrib
Version:	7.x-dev	» 8.x-dev

The teaser can do both (be a part of the main body or be something separate) and it also stops excessively long articles filling up for instance node listings.

I would think this is a core feature of a cms - not everything that you personally do not use should be removed from core. IMO.