I was wondering if you know of any module or hack that would allow an editor/writer to choose *exactly* when the teaser stops? This would be a custom node by node basis, not only the system settings.

I'm having a problem with my teasers looking inconsistent as the system doesn't know, from a style point of view, the correct location to end the teaser.

Using a previous system, the editors would add the tag in the writer's post and that would create the teaser. From my experience the Read More module doesn't yet support this feature as it only moves the link out of meta section.

Just a suggestion. Thanks for all of your helpful support and contribution to Drupal.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

spangaroo’s picture

FileSize
6 KB

Well thought I'd update because I found that there's already a

"Teaser Break" function included in TinyMCE.

I attached a screenshot because it needs to be enabled under admin/settings/wysiwyg/profile then "Edit" and under Buttons and Plugins you can enable it.

It's all the way the bottom right corner I'll be using this from now on.

So with Read More link and this Teaser Break feature, it looks like editors will be able to customize beautiful teasers, no problem.

Todd Nienkerk’s picture

Title: adding a <!more> tag or <--break--> to end the teaser » Add an input filter to specify location of link using a <!--more--> tag
Version: 6.x-3.0 » 6.x-5.x-dev
Assigned: Unassigned » Todd Nienkerk

The <!--break--> tag is built into Drupal core. It's how Drupal knows to separate the teaser from the full body of the node. The "Teaser Break" button in TinyMCE is merely a way to drop that tag into the textarea.

Adding a <!--more--> tag is exactly the kind of feature I want to add in a future version of Read More, but I'll have to research the best way to implement the input filter necessary to achieve this.

Todd Nienkerk’s picture

Status: Active » Needs review

After lots of research, I've decided it's not feasible to create an input filter to manually place the link and a #more anchor. However, I have added the option to add an anchor to the link so that the user skips past the (already read) teaser content when they land on the destination page.

The changes are in the 6.x-5.x-dev branch.

Todd Nienkerk’s picture

Title: Add an input filter to specify location of link using a <!--more--> tag » Add anchor to take user directly to unread content
fletchgqc’s picture

There must be some kind of error in the code because it's eating my content.
I had this:
<h2>content</h2><p><img ..../>content....en dos años. Como su estado se mejoraba...</p>

With the "skip to unread content" option, it turns into this (in the full node view):

<h2>content</h2><p><img ..../>content....en dos años.</p>
<a name="more"></a>o su estado se mejoraba...</p>

Also, I'm not sure whether this option should be enabled by default. The advertised and principal functionality of the module is to move the read more link. My instinct would be that any other changes should be "opt-in" rather than "opt-out" (I suppose that argument goes for the nofollow option too).

I'm turning the option off now but hope this info helps you.

izmeez’s picture

I have just loaded the 6.x-5.x-dev version and this feature seems to work fine, takes user to the end of the teaser.
I didn't change any options, I just loaded the module.

Thanks,

Izzy

dddave’s picture

Status: Needs review » Needs work
FileSize
38.76 KB
24.25 KB

Whoa, this has cost me hours to debug and in the end I am kicking me for not seeing the problem earlier.

I noticed that on content previously displayed without a problem, that some text in the middle was missing. This happened in full node view and NOT in the teaser view. The Read More link is set to display inline. Attached pic 1 shows the faulty display and pic 2 shows the correct display. I finally found out that it had to do with the teaser length I had set and after that it took me only endless turning off of modules to get to this module. Doooh.

Disabling the anchor option solves this problem totally.

Todd Nienkerk’s picture

fletchgqc: I agree that this should be made opt-in instead of opt-out. The "Skip to unread content" will be disabled by default.

Further testing is obviously needed. I have added a disclaimer to the admin interface warning users that this feature is under active development.

mcurry’s picture

subscribe