Bug #23699
closed
wrong table-cell rendering in RTE included tables
0%
Description
with this TYPOScript-command we could reset that in table-cells the bodytext would be wrapped with a p-tag:
lib.parseFunc_RTE.externalBlocks.table.stdWrap.HTMLparser.removeTags = P
With this command in TYPO3 V4.4.4 with rtehtmlarea V2.0.5 you will get this:
<td>Zelle 1.1</p></td>
No starting p-tag but an ending p-tag!?
put this command into the setup of a template:
lib.parseFunc_RTE.externalBlocks.table.stdWrap.HTMLparser.removeTags = P
put a datarecord "text" into a page and put a table into the rte-field.
Then look into the source-code of that page.
(issue imported from #M15945)
Files
Updated by Stanislas Rolland almost 14 years ago
If what you want is to avoid having paragraphs within table cells, why not use
RTE.default.buttons.table.disableEnterParagraphs = 1
in Page TSConfig?
Updated by Stanislas Rolland almost 14 years ago
Regarding the issue, is the html correctly structured in the database?
Please upload an example html content in a .txt file that would allow to reproduce the issue.
Updated by Kurt Kunig almost 14 years ago
Anybody modified my description!?
I wrote:
<td>Zelle 1.1</p></td>
and now you read this:
<td>Zelle 1.1</td>
Nevertheless, an ending p-tag without a starting p-tag must be a mistake - or not!? ;-)
And what's about this command:
lib.parseFunc_RTE.externalBlocks.table.stdWrap.HTMLparser.removeTags = P
Doesn't it work any longer?
Updated by Kurt Kunig almost 14 years ago
with:
lib.parseFunc_RTE {
externalBlocks.table.HTMLtableCells {
default >
default.stdWrap.parseFunc =< lib.parseFunc
}
externalBlocks.table.stdWrap.HTMLparser.removeTags = p
}
only with:
lib.parseFunc_RTE {
externalBlocks.table.stdWrap.HTMLparser.removeTags = p
}
you will have the effect with the single ending p-tag.
Have a look into the attached file beginning at line 86
In the database there is NO ending p-tag!!!
Updated by Stanislas Rolland almost 14 years ago
I guess this is a duplicate of very old issue #0001318. Was just resolved in all branches from TYPO3 3.8+ !
Please confirm.
Updated by Kurt Kunig almost 14 years ago
Yes! It is the same.
But why it appears again in 4.4.4!? The versions before worked properly!
Updated by Stanislas Rolland almost 14 years ago
Apparently not. It may depend on the specific html structure.
This was fixed yesterday in all branches from TYPO3 3.8 to current trunk.
Updated by