[MGNLUI-6324] CKEditor does not find custom configJsFile Created: 15/Oct/20  Updated: 27/Jan/21  Resolved: 18/Jan/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.3
Fix Version/s: 6.2.6

Type: Bug Priority: Major
Reporter: Monica Damborenea Assignee: Oanh Thai Hoang
Resolution: Cannot Reproduce Votes: 0
Labels: maintenance
Remaining Estimate: 0d
Time Spent: 7h 20m
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2021-01-14 at 13.44.43.png     PNG File Screen Shot 2021-01-14 at 13.55.13.png     PNG File Screenshot 2021-01-15 at 17.53.45.png     File ppconfig.js    
Issue Links:
Problem/Incident
Relates
relation
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Maintenance 40
Story Points: 2

 Description   

When using a custom configFile, the CKEditor does not find it and uses a fallback CKEditor

Steps to reproduce:

  • Rich text definition with a custom configFile:
    form:
      properties:
        richText:
          label: Text editor
          $type: richTextField
          height: 500
          tables: true
          source: true
          configJsFile: /.resources/ckeditor/ppconfig.js
    

When opening the richTextField with CKEditor, a warning is thrown:

15-Oct-2020 16:09:03.517 WARNING [http-nio-8080-exec-3] com.vaadin.server.communication.PublishedFileHandler.handleRequest vaadin-save-plugin.js published by info.magnolia.ui.vaadin.ckeditor.MagnoliaCKEditorTextField not found. Verify that the file info/magnolia/ui/vaadin/ckeditor/vaadin-save-plugin.js is available on the classpath.

The opened CKEditor is not the one we were trying to use, but a fallback CKEditor.

Even when using a simple richText field with no custom configFile, we get the warning but the Magnolia CKEditor is used.
This is the definition I used:

form:
  properties:
    text:
      label: Text editor
      $type: richTextField
      height: 500
      tables: true
      source: true

Outcome:
Issue wasn't reproducible, however, a glitch was found in the legacy pages app where drop down menus in a custom config would be hidden behind Vaadin's modal dialog. This has been fixed in the scope of this ticket.


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