Something is wrong with the teaser break; it is being filtered out after preview because of the < and > characters, I think. The exact problem is to be investigated.

Comments

marco’s picture

marco commented

I can't replicate: both in stories and static pages <!--break--> seems to work.
Could you provide some steps to replicate?

dries’s picture

dries commented

I think that the break-tag (<!--break-->) gets stripped out upon preview when you enable the HTML filter. Try this: enable the HTML filter, go to the forum topic submission page, enter some text with a break-tag in it and click "Preview". Is the preview correct and is the break-tag still there (so that it continues to work when you click preview again)?

marco’s picture

marco commented

ok, now I can replicate.
this needs some thought: you need to filter html comments out, or pages get mangled if you open a comment without closing it (try, it's funny!)
so perhaps we should use another break tag, something like "<teaser />"?

moshe weitzman’s picture

moshe weitzman commented

+1 for <teaser />

al’s picture

al commented

-1 for

If we fix the filter system to filter only on output, this bug will surely go away?

If you want to have an HTML teaser break, surely we should make sure we only use standard HTML? Anything else will break validation.

cnelsonakgov’s picture

cnelsonakgov commented
Title: Teaser break acting weird » Re: [drupal-devel] bug #1643 : Teaser break acting weird

Al Maw wrote:

> 20/05/2003 - 04:15 : Al Maw
> -1 for
>
> If we fix the filter system to filter only on output, this bug will
> surely go away?
>
> If you want to have an HTML teaser break, surely we should make sure we
> only use standard HTML? Anything else will break validation.
>

Remember, though, the teaser is part of what gets filtered on output.
It won't break validation cause it never (shouldn't ever) shows up. I
don't see anything wrong with using a custom tag to indicate to drupal
to mark for breaking the teaser.

dries’s picture

dries commented

As of a few minutes ago, Drupal uses "on output" filters. This bug is now fixed and I'm marking it accordingly.

al’s picture

al commented

Verified. CLOSING.