[MGNLUI-5907] RichTextField configuration file error: magnoliaFileBrowser not found 404 Created: 29/May/20  Updated: 27/Jul/20  Resolved: 19/Jun/20

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.1
Fix Version/s: 6.2.2

Type: Bug Priority: Neutral
Reporter: Jonathan Ayala Assignee: Federico Grilli
Resolution: Fixed Votes: 1
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: 1h 31m
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2020-05-29 at 12.16.00.png     File config-magnolia-patched.js    
Issue Links:
Problem/Incident
Relates
relates to MGNLUI-4072 Configuration properties not working ... Closed
relates to MGNLUI-5912 RichTextField - contentsCss in config... Closed
relates to MGNLUI-6087 CKeditor colors, alignment, fonts and... Closed
causality
duplicate
is duplicated by MGNLUI-5908 Integration to magnoliaFileBrowser do... Closed
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:
Epic Link: Support
Sprint: Maintenance 10, Maintenance 11, Maintenance 12
Story Points: 3

 Description   

When using magnolia configuration file by setting configJsFile property to /.resources/ckeditor/config-magnolia.js, file browser plugin is not found and CKEditor is not loaded.

Steps to reproduce:

  1. Open Text and Image dialog definition in resources app /travel-demo/dialogs/components/textImage.yaml
  2. Add configJsFile property to rich text field with value /.resources/ckeditor/config-magnolia.js
  3. Clear browser cache log out-in Admincentral and add a text and image component in one test page in pages app.
  4. Open the browser debugger to see the error

    There was a similar issue MGNLDAM-759, but now it seems that those changes are still present in code.


 Comments   
Comment by Jonathan Ayala [ 29/May/20 ]

As a workaround I've come up with this patched magnolia-config file: config-magnolia-patched.js

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