Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Freemarker is not executed in an editable field

Written By

Tamas Kovacs

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

  • When Freemarker code is added to an editable field fragment's HTML section, the Freemarker code is not (always) executed on the published fragment.

Environment

  • Liferay DXP 7.4

Resolution

  • It is not possible to execute Freemarker inside editable fields, it is a limitation.
  • One workaround to get Freemarker to execute inside an editable field is to create an information template and map it to the editable field. In the information template, the desired logic can be executed using Freemarker and having all the content fields available.

Additional Information

  • It is caused because the content inside the editable fields is their default value. So only executes the Freemarker one time at the moment to persist it, and after this, use this value.
    It causes the default value to be calculated using the existing locale to render it when the fragment is added to the content, and this value will be used as default when there is no mapping.
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?