Instead of using global JS-variables and ignoring serendipity[textarea]={$view}, this
approach actually uses the variable and therefore reinstates wysiwyg_init.tpl.
ckeditor_custom_config.js (Thx Ian!) is still respected, but the toolbar got restored to the old version. We need an easy way to remove _underline_, for example. It could be extended though.
This fixes #{107} somewhat, as serendipity_image_selector.php is useable now, but still with display errors (and without an upload widget). Probably still a good idea to copy the ML-eapproach of the normal textareas
This also works with htmlnuggets, without using spawnnugget from the core, instead wysiwyg_init.tpl gets reused in the plugin-config.
ckeditor_custom_plugin.js got emptied, the relevant code (which should only be the part that adds the plugins into the toolbar) should be integrated into wysiwyg_init.tpl).
This supports custom ckeditor plugins and a custom ckeditor config
and reads $eventData for
- normal entry form (case1) textareas,
- staticpage (case2) textareas and
- other nugget plugins (case3) textareas.
They all are build differently, therfore we needed three cases.
Please test!
Based to following commits
8e26bd9 prepare core ckeditor for custom config and plugins
44ea050 fix virtual js
40609d8 add backend_footer hook
References #72
– <button> must have an explicit type="buttons" since it falls back
to type="submit", which can have side effects
– <button> must not have a href attribute, always use data-href
Partial manual revert of 168cb146eaec3c568527bbc5dcf06b4cb6e9bda8.
Please note that this does *not* contain any changes to the UI as
discussed; those will follow later.
References #41
This includes only the icons actually used or intended to be used
in the backend. Please note that unfortunately, some class names
have changed. Also some icons have been exchanged.
