Legacy Knowledge Base
Published Jul. 2, 2025

Integrating AlloyEditor fields in AUI forms

Written By

Daniel Couso

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • CKEditor textareas are usually introduced in JSP pages by calling the taglib InputEditor:
<liferay-ui:input-editor
contents="<%= HtmlUtil.escape(title) %>"
editorName="ckeditor"
name="titleEditor"
onChangeMethod="OnChangeTitle"
placeholder="title"
required="<%= true %>"
showSource="<%= false %>"
>
  • However, changing the editor type from CKEditor to AlloyEditor by simply modifying the value of the attribute editorName from ckeditor to alloyeditor will not work.

Environment

  • DXP 7.1+

Resolution

  • The integration of an AlloyEditor using the taglib InputEditor is not as straightforward as with CKEditor.
  • Two additional elements have to be put in place:
    • An auxiliary hidden input field (Blogs Example).
    • An auxiliary piece of Javascript code which copies the Alloy Editor's content to the aforementioned auxiliary hidden input field at the time of submitting the form (Blogs Example).
Did this article resolve your issue ?

Legacy Knowledge Base