I wanted to have the entire About page I created displayed as a sticky content of the front page. I added <!--break--> to the bottom of the text but left the filtered HTML text format untouched and only the X number of words were displayed. So I changed it to Full HTML and the full page was displayed. I moved it back to Filtered HTML and only the X number of words were displayed. When previewing the changed text the help message at the top of the form mentions <!--break--> but doesn't say anything about the text format. So either the "Filtered HTML" text format is incorrectly removing <!--break--> or the help text needs updated to suggest using "Full HTML".

Comments

shp’s picture

Title: <!--break--> removed in Filtered HTML text format » <!--break--> removed when "Limit allowed HTML tags" filter is enabled
Component: node system » filter.module

+ Subscribing for this bug.

The reason is not the entire "Filtered HTML" format, but the "Limit allowed HTML tags" filter. It uses the filter_xss(), which removes all the HTML comments.

I've found the solution: adding <!--> to the "Allowed HTML tags" list. But note, that this skips all the other HTML-comments!

stolzenhain’s picture

I had a hard time finding any documentation on this while battling with the wysiwyg editor configuration – maybe a simple note on the text format page should be included.
For the exotic usecase of having more comments one wouldn't want to show up in the output, one could still build an extra filter removing any comment but the <!--break--> one.

Version: 7.12 » 7.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

rocketeerbkw’s picture

Issue summary: View changes
Status: Active » Closed (duplicate)
Related issues: +#881006: Regression: 'break' tag doesn't work with Filtered HTML

Closing as duplicate of #881006: Regression: 'break' tag doesn't work with Filtered HTML. There's a workaround in comment #118.