rich text editor is not working in On-premises envionment

Any reason to not use the styled text editor?

Failing UI plugins typically point to a missing split domain setup for static/dynamic content. If this is the case, the document viewer will fail as well.

Hi Stefan Helzle ,

Thanks for your response,

styled text editor working fine but we have recently installed the rich text plug in it seems not working as expected,

do we need to add any other ?

Hi suresh  ,

I previously faced the similar issue on our on-premise system while using the richTextEditor field.
Upon analyzing, I identified that we missied configuring the Dynamic Content URLs and the static URLs. 
You can refer to the documentation from Appian.

Rich text editor component troubleshooting guide

Configure your static and dynamic content urls

suresh said:

styled text editor working fine but we have recently installed the rich text plug in it seems not working

The Styled Text component is much newer and effectively replaces the Rich Text Editor plug-in, for all but a very specific set of corner cases, just FYI.