Bug #81014
closedckeditor removes <span>-tags inside <li>
0%
Description
demo-source:
<ul class="unstyled ul-app ul-check">
<li><span class="icon-check"></span> demo1</li>
<li><span class="icon-check"></span> demo2</li>
</ul>
The spans with icon-check get removed.
I've also already searched for solutions. Some target using allowedContent - but our "extraAllowedContent"-setting should already allow quite some things. Even filling the spans with something does not seem to protect them from being removed.
When editing a record with a RTE-field containing the above mentioned HTML it gets loaded fine in the frame - but gets removed by ckeditor upon loading. switching to the source-view (without saving) does not show those spans anymore. Saving then proves the spans are also removed in the frontend.
Switching to the source-view and saving it's possible to add the above mentioned HTML - but opening the record and saving it again removes the spans.
Updated by Simon Ouellet over 7 years ago
try this yaml config
editor: config: allowedContent : true extraAllowedContent : "span[!style]" disallowedContent: "span[style]" format_tags: p;h1;h2;h3;h4;h5;h6;div contentsCss: "path/to/rte.css" processing: HTMLparser_db: tags: span: allowedAttribs: class fixAttrib: style: unset : true
Updated by Mona Muzaffar over 7 years ago
- Status changed from New to Needs Feedback
Updated by Matthias Krappitz over 7 years ago
Had the same issue, tested this and it works. So +1 for closing this issue.
Updated by Stefan Neufeind over 7 years ago
- Status changed from Needs Feedback to Closed
I couldn't yet retest this on the setup where I originally needed it. But let's close it for now, as per the other comments - okay.
Updated by Sybille Peters almost 7 years ago
Is the proposed yaml really a good solution? Setting allowedContent to true will completely disable the filtering, which is not really recommended for security reasons (https://docs.ckeditor.com/ckeditor4/latest/api/CKEDITOR_config.html).