Legacy Knowledge Base
Published Jul. 2, 2025

How to identify the version of Clay under DXP?

Written By

József Géczi

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

  • As a developer, I would like to identify the exact version of Clay on the specific DXP version (and patch level) which is currently running.

Environment

  • DXP 7.1

Resolution

  • Please go to Control Panel -> System Settings -> Javascript Loader and enable the option Explain module resolutions.

  • When this option is set, reload the page and search in browser console for package frontend-taglib-clay where logs are shown, for example:

    "frontend-taglib-clay$clay-button@2.20.2/lib/ClayButton", "frontend-taglib-clay$clay-alert@2.20.2/lib/ClayAlertBase.soy", "frontend-taglib-clay$clay-alert@2.20.2/lib/ClayAlertBase"

    This also tells the version number itself. In the example above it is actually 2.20.2 - this is the one Liferay is providing in Clay taglibs under DXP 7.1.

  • That means, in case Clay taglibs are applied, that one is the Clay version which is available for use. 

  • Please note: There is no available option present out-of-the-box in liferay-clay taglibs to set which Clay version to be used, on demand.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base