Feature #14595
closed
rtehtmlarea does not support old rte configuration
0%
Description
as long as rtehtmlarea doesn't support all configurations of the old - and still standard - rte it will not be possible to replace the old rte just by installing rtehtmlarea and it can't be chosen as new standard rte
Editors shouldn't be confused or even notice that there is a new rte.
this affects only parts of the configuration like css classes
(issue imported from #M866)
Updated by Stanislas Rolland over 19 years ago
You can install both the classical RTE and the htmlArea RTE and they will share the same configuration.
In the case of the classical RTE, you need to define the CSS classes in the RTE configuration. In the case of the htmlArea, you need to define the CSS classes in an external stylesheet file.
But there is no conflict between the two. Once the editors are properly configured, the editors will see only the main difference: they can now edit in Mozilla/Firefox.
Updated by Ingo Renner over 19 years ago
The aim of this bugreport is the following scenario:
When having a configuration for the classic RTE and you want to migrate to rtehtmlarea you must not change anything to have rtehtmlarea behave like the classic RTE, rtehtmlarea should notice and use the old configuration.
Only this way rtehtmlarea can become the default RTE for TYPO3 one time, what I really would appreciate. So this bugnote i not a BLOCKER for rtehtmlarea itself, but a BLOCKER for rtehtmlarea becoming the default RTE.
bearbeitet am: 13.03.05 19:30
Updated by Stanislas Rolland over 19 years ago
You may need to install both RTE's anyway, because htmlArea RTE does not support IE5 and the classical RTE does not support Mozilla/Firefox/Netscape and supports no browser on Mac or Linux.
edited on: 13.03.05 20:04
Updated by Martin Kutschker about 19 years ago
I don't want to use and configure more than one RTE, so I prefer to disable the classic RTE if I install HTMLarea.
What configuration options are missing? Shall a new bug filed for everyone, making this a meta-bug for tracking the whole issue?
Updated by Stanislas Rolland about 19 years ago
I think that the only settings that rtehtmlarea does not support are related to CSS classes definitions, and are the following:
RTE.classes, classesParagraph, classesTable, classesLinks, classesTD, mainStyleOverride and inlineStyle.
These properties are currently ignored by rtehtmlarea.
Updated by Stanislas Rolland almost 19 years ago
Will be corrected in next version for ease of migration. However, note that if a change goes unnoticed, it is probably useless.