Legacy Knowledge Base
Published Jul. 2, 2025

In Liferay DXP 7.1, flags taglib uses scope of module that spawns flags window instead of Flags module

Written By

Justin Mann

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

  • In Liferay 7.0, you can change the reasons and keys for that are displayed in the Flags portlet, and the flags for other portlets will change as well (e.g. Message Board). However, in Liferay 7.1, the flags taglib was re-written so that instead of using the scope of the Flags module, the flags taglib will use the scope of whatever module spawned the modal window for flags. This means that changes to the reasons and keys for the Flags portlet will not be changed in other portlets.

Environment

  • Liferay 7.0
  • Liferay 7.1

Resolution

  • To resolve this, you can add the custom keys to the global language properties file. You can find more details about overriding global language keys in our developer tutorials, found in the link below.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base