OverviewStarting in 24.2, the Styled Text Editor Component is available directly in the product. Consider using this in place of the plug-in moving forward. For more information, review: https://docs.appian.com/suite/help/latest/Styled_Text_Editor_Component.html
Visit https://community.appian.com/w/the-appian-playbook/1378/end-user-rich-text-editor-component for more information. If you have any problems installing or using the component, please see the https://community.appian.com/w/the-appian-playbook/1603/rich-text-editor-component-plug-in-troubleshooting-guide
Key Features & Functionality
Supported Browsers: Chrome, Firefox, Edge, SafariSupported on Mobile
The same html renders correctly on any online html editor:
Hello,I am seeing an issue where fn!richTextField() does not correctly render text if it starts and ends with paragraph tags: <p> and </p>.Here is an example of with the <p> tags. See the raw input on the top, and the input rendered by the fn!richTextField() field on the bottom: Here is an example without the <p> tags: Does the fn!richTextField() not recognize paragraph tags? Could this be added in the next version?
Hi,the plugin need some specific configuration after installation? because a message appear "System configuration missed" instead of plugin interface.Thanks.
Note that when clicking the "Post Comment" link it
Dan, we were actually able to reproduce similar a similar issue even with the latest plugin version. We caught a video. It looks like it's clearing the value while the component is still loading, so definitely a more uncommon case. Hope this helps!
Der, upgraded the component and can no longer reproduce the issue. Thanks for the help!
I'm not able to reproduce this on the latest version of the rich text editor (1.4.0). Do you have a screen record you could share, preferably from the /design interface?
Hello, I am seeing an issue using this component when another Appian element to clears out the value of the text field. Steps to reproduce:
This is leading to confusion from our end users with our use case. Is there a workaround for this issue?
Has anyone experienced any issues when a http:// url us posted in the rich text field and then clicking the url and the link being blocked?We are seeing if we have a https url, we get a "popup" of 'Visit URL'. When we click, access is blocked. However, if we copy the URL and paste in the browser, the URL accesses the site fine.