2. 2
About me
Frans Saris
developer @beech.it
TYPO3 core/extension dev
slack: minifranske
twitter: @franssaris
github: fsaris & frans-beech-it
Beech.it
first TYPO3 partner worldwide
website: www.beech.it
github: github.com/beechit/
3. 3
Why the switch to CKEditor?
● We don’t have to fully maintain it our self
● Superb browser support
● Complying with the latest web accessibility
standards
● Inline editing features
● Advanced Content Filter
4. 4
Big changes
● Presets in YAML
● No automatic migration of existing configs
● <p> are now saved in database!
● No <typolink> anymore
5. 5
Why YAML?
● CKEditor uses plain javascript for
configuration
● typoscript for BE config is confusing for
newcomers
● A new structure (new start)
separate “processing” and Editor-related configuration
● Allows options to be extend
but no conditions or unsetting values
6. 6
Presets
● Defines editor appearance
● Defines what tags and styles are
● Defines what plugin’s to load
● Defines database processing `RTE.proc`
10. 10
Add your own preset
// Register or own text-element config
$GLOBALS['TYPO3_CONF_VARS']['RTE']['Presets']['text-element']
= 'EXT:config_examples/Configuration/RTE/TextElement.yaml';
ext_localconf.php
23. 23
Override default preset
// Set your own default RTE config
$GLOBALS['TYPO3_CONF_VARS']['RTE']['Presets']['default']
= 'EXT:config_examples/Configuration/RTE/Default.yaml';
ext_localconf.php
24. 24
Advanced Content Filter
● Only tags/classes/styles that are configured are
kept
● Filters content during editing and paste
● Enabled by default
● Makes `processing` config most of the times
obsolete “RTE.proc”
http://sdk.ckeditor.com/samples/acf.html
26. 26
But I don’t want to switch!
● Deprecated in TYPO3 8 LTS
● Moved to FriendsOfTYPO3/rtehtmlarea for 9
https://github.com/FriendsOfTYPO3/rtehtmlarea