[MGNLUI-3150] Make sure CKEditor magnolialink plugin can be used with custom config.js Created: 15/Sep/14  Updated: 05/Dec/14  Resolved: 30/Sep/14

Status: Closed
Project: Magnolia UI
Component/s: forms
Affects Version/s: 5.3.3
Fix Version/s: 5.3.4

Type: Improvement Priority: Major
Reporter: Mikaël Geljić Assignee: Mikaël Geljić
Resolution: Fixed Votes: 1
Labels: ckeditor, support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLDAM-512 Make sure CKEditor filebrowser plugin... Closed
causality
duplicate
duplicates MGNLUI-2727 Rich-text field - when using custom c... Closed
supersession
supersedes MGNLUI-2810 Review configuration options in the C... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Release notes required:
Yes

 Description   

We basically need to register the server-side plugins for it to work properly.
Currently it's only done if we use the definition properties, not for custom JS config.

Additionally, we may provide a starter config.js that uses the same Magnolia config as the server-side Config object that is built from the definition.



 Comments   
Comment by Mikaël Geljić [ 15/Sep/14 ]

In order to try out the starter config JS, try to configure the configJsFile to one of the following:

  • /.resources/ckeditor/config-default.js
  • /.resources/ckeditor/config-magnolia.js
    This will then be reflected in docu as soon as ticket goes through. Tentatively setting release notes required not to forget

Side note: we will also give an update on why everything else in definition is ignored when using custom JS (re: loading order; overridability).

Comment by Mikaël Geljić [ 16/Sep/14 ]

Registration of additional plugins on the client-side is actually not working quite yet. basically extraPlugins set on the server-side override whatever's in the custom JS (just like any other config property).

Comment by Mikaël Geljić [ 30/Sep/14 ]

Re-resolving, see latest commit https://git.magnolia-cms.com/gitweb/?p=magnolia_ui.git;a=commit;h=928cfaadab9fdf7fcad6b31b35cff3d147fe5740

Basically if you go the custom JS way, you should have control over the config.extraPlugins setting. This means you're in charge of adding the magnolialink and magnoliaFileBrowser ones here. Default config-magnolia.js was adapted to reflect that.

Renamed so-called "server plugins" in MagnoliaRichTextFieldConfig to "external plugins" — that's how the client-side treats them in the CKEditor world.

Generated at Mon Feb 12 09:03:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.