Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
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
Hi was this issue resolved and if so how? I am having the same issue.
Thanks in advance
Hi Anyan, did you open a support case and had the issue solved?
I believe that's an issue with the component plugin framework rather than this particular plugin. Can you please open a support case about it?
Hi Team, these days our platform move upgrade to 22.3, and for this plugin, sometimes it will load fail, and find some api response 403 code, do you know the cause?
Thank you!
No component plug-ins are compatible with Portals... yet. Hopefully that will come soon.
Is the Rich Text Editor Component compatible with portals?
Yes, it will always be backwards compatible