Teaser break tag <!--break--> exposed
cmgui - March 12, 2009 - 22:14
| Project: | Paging |
| Version: | 6.x-1.0-beta3 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | won't fix |
Jump to:
Description
Thank you for coming up with this wonderful and very useful module.
I installed it and it is working but there is a small problem.
The teaser break tag is not exposed when the node
is displayed in full view.
Before installing the paging module, this teaser break tag
didn't show up.
Attached here are the screen shots - teaser view (or summary view)
and full view.
Thank you.
| Attachment | Size |
|---|---|
| screen1.jpg | 20.64 KB |
| screen2.jpg | 181.83 KB |

#1
I have the same issue with 6.x-1.0-beta3 and the dev from 19th April.
#2
Same problem here with 6.x-1.0-beta3.
#3
I ran into this issue on my site also, so I did some digging. It looks it's happening b/c of a bug in the html corrector filter, not b/c of this module. From paging module version 6.x-1.0-beta3 line:
512 if (!$teaser && $node->page_count > 1 && arg(2) != 'print' && arg(2) != 'full' && $page != 'full') {513 global $pager_page_array, $pager_total;514 $pager_page_array = explode(',', $page);
515 $pager_total[$element] = $node->page_count;
516 $page = isset($pager_page_array[$element]) ? $pager_page_array[$element] : 0;
517
518 // Put the current page contents into the node body.
519 $node->content['body']['#value'] = check_markup($node->pages[$page], $node->f ormat, FALSE);
The above chunk of code is what determines what'll be displayed on the node view. Line 519 calls check_markup() and in my particular instance, I have the html corrector filter enabled for most input formats, so everything is going through the html corrector before display. I found this bug listed for the html corrector: htmlcorrector filter escapes HTML comments
I tried turning off the html corrector to see if that was the problem and sure enough, the comments were not displayed once the text wasn't filtered by html corrector.
I'd guess that this issue can probably be closed as "won't fix" but I'll leave that decision up to the module maintainers in case I'm missing something.
#4
That status was confusing. The patch that fixes this in core is #222926: htmlcorrector filter escapes HTML comments