[MGNLUI-5173] Richtexteditor is not initialized when added dynamically (multi value field, stories editor) Created: 23/Apr/18  Updated: 16/May/19  Resolved: 06/May/19

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 5.6.10, 5.7.3, 6.1

Type: Bug Priority: Neutral
Reporter: Marvin Kerkhoff Assignee: Jaroslav Simak
Resolution: Fixed Votes: 3
Labels: None
Remaining Estimate: 0d
Time Spent: 0.25d
Original Estimate: Not Specified

Attachments: PNG File CkeInitBug.png     JPEG File bug.jpg     PNG File not-supported-RichTextFieldDefinition-in-content-editor.png     PNG File qa.png    
Issue Links:
causality
duplicate
is duplicated by CONTEDIT-209 FieldSetBlock should be able to inclu... Closed
supersession
supersedes MGNLVA-4 Expose VCKEditorTextField #loadEditor... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: Support
Sprint: Features 10
Story Points: 5

 Description   

Timebox for investigation.

If you add a block with a ckeditor field defined like this:

class: info.magnolia.editor.block.stock.FieldSetBlockDefinition
label: References
fields:
  text:
    i18n: true
    images: true
    label: Text
    source: true
    tables: true
    class: info.magnolia.ui.form.field.definition.RichTextFieldDefinition

You will see that you don't get it working if you click first time on the story to edit it. You need to refresh the browser that the editor loads as expected. Sometimes it's necessary to use a defined RichtextField instead of the extend Richtextfield. You probably don't want that magnolia seperates paragraphs into differenct component.



 Comments   
Comment by Thomas Peintner [ 04/Jun/18 ]

Dear Magnolia Team,

we also have a problem with the Richtextfield within a Multivaluefield. After moving a Richtextfield it does not get initialized anymore.

Also if you remove a Richtextfield, all the other Fields below need to be reordered and do not get initalized.

Refreshing the browser initializes the Richtextfields.

Using Magnolia version 5.5.2.

Best regards,

 

Comment by Viet Nguyen [ 19/Jun/18 ]

marvink2 and tpeintner, I've changed this issue type from a bug to an improvement since we are not supporting this function on our rich text editor yet - sorry for any inconvenience:

Comment by Vyacheslav Maksimov [ 19/Jun/18 ]

I consider this improvement is very necessary for working with components in the content editor. I hope that soon this task will be solved, because info.magnolia.editor.block.stock.RichTextBlock can not be used many times in one component or combined with other fields. Thank you.

Comment by Marvin Kerkhoff [ 19/Jun/18 ]

Agree. Beside the fact that it's not possible to translate content, this is the most necessary feature for our customers. In most cases the discussions ends with these facts and people starting to use the old working page editor.

 

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