Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Web Content Templates Using Liferay Taglibs Should Not Be Cached to Avoid Incorrect Display of Web Contents

Written By

Christopher Lui

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.

Web Content Templates allow the use of Liferay Taglibs for creating common front-end UI components in your web content. Please note that by default, Templates are cached to improve its performance, meaning that Taglibs may not function correctly if included in the Template's script.

Resolution

This is a known limitation, and the implementation of LPS-94656 makes this clear in the Template's help text. If you are using Taglibs within a Template, please make sure that the Cacheable checkbox is unchecked.

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?