Answered

Rich Text Control not not rendering in Custom Page

(3) Share

Report

Posted on by PatrickMichaelK

I have a Custom Page in a Model Driven Power app where I have used the standard Rich Text control.

Everything looks fine from the custom page canvas designer when editing the custom page and when previewing but when I open the custom page in the model driven app the rich text control does not display properly.

It looks like some style sheet or something is missing.

The toolbar in the control is not styled at all and appears like this in the custom page:

Is anyone else having this issue lately?
I have had the custom page working properly for a couple months but the issue started a couple days ago and I have no idea what to try to fix it.

I have tried toggling visibility of the control with a variable but that didn't help.

I've tried removing the control entirely from the custom page and try re-adding it in to see if the control had become corrupted in some way but this also didn't help.

Anyone else having this issue or have any ideas on what to try?

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (0)

VishalJhaveri 1,167 Moderator on at

Like (1)

Report
Copy link

Link copied!

No idea on this one.

Was this reply helpful? Yes No
CU10091013-0 2 on at

Like (1)

Report
Copy link

Link copied!

Did you fix it ?

Was this reply helpful? Yes No
bsobolewski 5 on at

Like (1)

Report
Copy link

Link copied!

I have same error and this message in Chrome console.

ckeditor.js:370 [CKEDITOR]: The license key is missing or invalid.
If you suddenly started to see this message, this may mean you accidentally updated CKEditor 4 to the LTS version (4.23.0 and above). This version of the editor is under commercial terms and requires acquiring an "Extended Support Model" contract - https://ckeditor.com/ckeditor-4-support/
For more information about this error go to https://ckeditor.com/docs/ckeditor4/latest/guide/dev_errors.html#invalid-lts-license-key

Was this reply helpful? Yes No
AtteP 3 on at

Like (2)

Report
Copy link

Link copied!
This seems to be caused by some mismatch between the new model-driven apps look for the rich text -field and the rich text editor -control used in the custom pages. In my case I had a model-driven app form with a rich text -field and a ribbon button to open the custom page with a rich text editor. If I have the modern look for model-driven apps turned on (the "New look" -switch on the top bar) the rich text editor in the custom page is not rendered correctly and I get the errors below:
GET https://content.powerapps.com/resource/app/8gtj48ofer3nd/openSource/modified/ckeditor/skins/moono-lisa/editor_gecko.css?t=O17A NS_ERROR_CORRUPTED_CONTENT [CKEDITOR]: The license key is missing or invalid. If you suddenly started to see this message, this may mean you accidentally updated CKEditor 4 to the LTS version (4.23.0 and above). This version of the editor is under commercial terms and requires acquiring an "Extended Support Model" contract - https://ckeditor.com/ckeditor-4-support/ For more information about this error go to https://ckeditor.com/docs/ckeditor4/latest/guide/dev_errors.html#invalid-lts-license-key ckeditor.js:370:145

If I turn of the the new look or hide the rich text -field from the model-driven app form, the rich text editor on the custom page renders normally.

Was this reply helpful? Yes No
Suggested answer

MM-16101356-0 17 Season of Giving Solutions 2025 on at

Like (4)

Report
Copy link

Link copied!

Thanks to AtteP, I took a deep dive into a solution for this. A lot of the PCF components are garbage, so we looked into forcing the old look, but found a setting in the model-driven app designer settings for disabling the modern Rich Text Editor. This resolved the issues in my custom pages while Microsoft fixes the problem.

Was this reply helpful? Yes No