The Rich Text Editor is an Appian component plug-in that is available on the Appian App Market. This doc provides guidance if you have trouble installing or using the plug-in. For information on how to use the Rich Text Editor in your Appian apps, see the End-User Rich Text Editor Component.
Component plug-ins, including the Rich Text Editor, only work in Appian 19.1 and later.
There are two key steps to successfully using any component plug-in. Please review and confirm you have successfully handled the following two items before reaching out for support:
A properly configured dynamic content URL is required to use any and all component plug-ins. Follow the instructions here to configure your dynamic content URL: Configure Your Static and Dynamic Content URLs.
To test if your dynamic content URL is working, make sure it is accessible from your computer. One way is to use the ping command from your computer (replacing your.dynamic-content-url.com with your dynamic content url):
$: ping <your.dynamic-content-url.com> PING cloud_us-east-1_glb_1.appiancloud.com (34.235.62.31) 56(84) bytes of data. 64 bytes from ec2-34-235-62-31.compute-1.amazonaws.com (34.235.62.31): icmp_seq=1 ttl=240 time=17.6 ms 64 bytes from ec2-34-235-62-31.compute-1.amazonaws.com (34.235.62.31): icmp_seq=2 ttl=240 time=17.8 ms 64 bytes from ec2-34-235-62-31.compute-1.amazonaws.com (34.235.62.31): icmp_seq=3 ttl=240 time=20.8 ms 64 bytes from ec2-34-235-62-31.compute-1.amazonaws.com (34.235.62.31): icmp_seq=4 ttl=240 time=23.4 ms 64 bytes from ec2-34-235-62-31.compute-1.amazonaws.com (34.235.62.31): icmp_seq=5 ttl=240 time=19.5 ms --- cloud_us-east-1_glb_1.appiancloud.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4007ms rtt min/avg/max/mdev = 17.632/19.832/23.368/2.120 ms
Note: the content for the Rich Text Editor (and any component plug-in) is loaded by your computer's browser, not the server, so it's important that your browser be able to connect to the dynamic content URL. It is not sufficient if only the server can connect to the dynamic content URL.
Your plug-in should appear in the list of deployed plug-ins.
If you don't see your plug-in listed after 60 seconds, review the output of your application server log, tomcat-stdOut.log in <APPIAN_HOME>/logs (by default, it may be different in your system). You should see a message confirming that the plug-in has been successfully installed:
Successfully installed Component Plug-in 'Rich Text Editor'
If you see an error, use the log message to help resolve the problem and redeploy the plug-in.
If you add the component to your SAIL but do not see any output, do the following:
Check the dynamic content URL is serving the component plug-in. In your browser, go to https://your.dynamic-content-url.com/suite/rest/a/content/latest/webcontent/richTextField/index.html (replace your.dynamic-content-url.com with your actual dynamic content URL).
You will see a UI similar to this:
Note: this is not a working version of the Rich Text Editor plug-in, but it proves that the plug-in files are accessible through your dynamic content URL.
If you get an error page, then your plug-in was not successfully installed. If you get an error saying "This site can’t be reached", then your dynamic content URL is not set up correctly.
If you're able to load the plugin index.html but still do not see any output from the Rich Text Editor, do the following:
Example of the Chrome Network tab for a page that includes 4 instances of the Rich Text Editor Plugin
Example of the Firefox Network tab for a page that includes 4 instances of the Rich Text Editor Plugin
If the Rich Text Editor displays an interface similar to the image below, this means that your browser was able to load the index.html from your dynamic content URL but was not able to execute Javascript from your dynamic content URL.
Check your Network Developer Tools to look for any requests for "compiled.js" made to the domain of your dynamic content URL. If the Status of those requests does not equal 200, work with your system administrator to resolve the error.