Level 3

RTE in AEM 6.4 touchUI

Forum|Forum|6 years ago
September 26, 2019
2 replies
4805 views

Hi,

Rich Text Editor in touchUI dialog is not working for us even in out of the box text component.

We are getting this error in the console whenever we try out of the box text component or our custom component.

richtext.min.5-42--0.js:1148 Uncaught TypeError: a.rte.ui.cui.DefaultFullScreenAdapter is not a constructor

at c.initializeEditorKernel (richtext.min.5-42--0.js:1148)

at c.startEditing (richtext.min.5-42--0.js:1160)

at c.start (richtext.min.5-42--0.js:1161)

at c (richtext.min.5-42--0.js:812)

at Object.success (richtext.min.5-42--0.js:812)

at k (jquery.min.js:99)

at Object.fireWith [as resolveWith] (jquery.min.js:100)

at d (jquery.min.js:190)

at XMLHttpRequest.b (jquery.min.js:202)

Any idea?

Thanks & Regards,

Rachna

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

H

Hamid1350

Adobe Employee

Ref: We are getting this error in the console whenever we try out of the box text component

Can you be more specific:

1. What are you doing when you get the error ? Steps that leads to the error

2. What version of the product ?

U

user05162

Adobe Employee

I just tried this on my side and OOTB text component works without any issues on AEM 6.4

Can you try to remove the custom code and test if you still see the same issue?

Another way to test is to point the "sling:resourceSuperType" to "core/wcm/components/text/v2/text"

R

rachnamehtaAuthor

Level 3

I am just adding a point, It seems you are using core component in 6.0

That could be the reason because I can"t see any version of core component which is fully compatible with 6.0

aem -core-wcm-components/VERSIONS.md at master · adobe/aem-core-wcm-components · GitHub

You may try with foundation Text components.

/libs/foundation/components/text

Hi Arun,

Thank you for your reply. We are not using core components, we managed to fix it by using extraClientlibs="cq.authoring.dialog.rte.coralui2" in touchUI dialog. RTE is now showing up but it didn't show "paraformat" options as we were using sling:resourceSuperType and loading RTE from xml file, we had to copy all the RTE options and add uiSettings node to the dialog xml file in order for us to have completely working RTE in touchUI dialog. Classic UI dialog still loads them from generic xml.

TouchUI dialog had to have all them copied to dialog xml file. If anyone knows how to generalise options so that both classic UI and touchUI dialogs load RTE from common xml file, that would great. I saw one of the related post Custom RTE not working with aem page template/property

Thanks,

Rachna