Bug #42568
closed
htmlArea RTE exitHTMLparser_db wont work in page table
0%
Description
I have extended the `pages` table with a htmlArea RTE.
I run into the problem that the B and I tags are not remapped to strong and em. I use the following Page TS Config on rootlevel:
RTE.default.proc.exitHTMLparser_db = 1
RTE.default.proc.exitHTMLparser_db.tags.b.remap = strong
RTE.default.proc.exitHTMLparser_db.tags.i.remap = em
In others tables like `tt_content` or custom extensions it works great.. So it might be some kind of a bug..
The other configurations I use works for all tables:
RTE.default.ignoreMainStyleOverride = 0
RTE.default.contentCSS = fileadmin/templates/RTE/stylesheet.css
RTE.default.showButtons = blockstylelabel, blockstyle, formatblock, textstylelabel, textstyle, bold, talic, table, tableproperties, findreplace, orderedlist, unorderedlist, rowproperties, rowinsertabove, rowinsertunder, rowdelete, rowsplit, columnproperties, columninsertbefore, columninsertafter, columndelete, columnsplit, cellproperties, cellinsertbefore, cellinsertafter, celldelete, cellsplit, cellmerge, link, unlink, outdent, indent, insertcharacter, code, undo, redo, subscript, superscript, italic, textindicator, about, chMode, removeformat, pastetoggle
RTE.default.buttons.pastetoggle.setActiveOnRteOpen = 1
#RTE.default.buttons.pastetoggle.hidden = 1
Updated by Thorsten Kahler about 12 years ago
- Status changed from New to Needs Feedback
- Assignee set to Arek van Schaijk
Hi Arek,
do other transformations etc. work properly?
Updated by Stanislas Rolland about 12 years ago
What field of table pages did you extend?
Updated by Arek van Schaijk about 12 years ago
Sorry, I made some mistakes...
"All" Rich Text Editors are showing <b> and <i> tags instead of <strong> or <em> tags in the text mode of the RTE (also after a save), so there is no difference between tables (sorry for my confusion)!
The content passed though lib.parseFunc_RTE are showing on the front-end <strong> and <em> so that looks okay..
The difference where I was talking about caused by the Format_Html viewhelper of fluid (Tx_Fluid_ViewHelpers_Format_HtmlViewHelper). It seems that this viewhelper does not take into the remap options of the RTE (so content from a rte passed trough <f:format.html> showed <b> and <i> tags in the front-end).
But now whe are talking about this... Its almost anno 2013, it should be better to have strong and em as default (isnt that possible?).
Updated by Arek van Schaijk about 12 years ago
The b element should be used as a last resort when no other element is more appropriate. In particular, headings should use the h1 to h6 elements, stress emphasis should use the em element, importance should be denoted with the strong element, and text marked or highlighted should use the mark element.
Source: http://www.w3.org/wiki/HTML/Elements/b#Example_of_bad_usage
Updated by Thorsten Kahler about 12 years ago
- Status changed from Needs Feedback to Rejected
- Assignee deleted (
Arek van Schaijk)
I close this ticket because it's just a matter of configuration.
Arek: if you prefer <strong> and <em> over <b> and <i> (for a good reason, indeed) you can exchange the buttons "bold" and "italic" with "strong" and "emphasis" in your setup. You can also start a feature request to change the example setups of EXT:rtehtmlarea, too.
Updated by Arek van Schaijk about 12 years ago
FYI
It was caused by the Extension Builder: http://forge.typo3.org/issues/42765#change-139642