Legacy Knowledge Base
Published Sep. 10, 2025

CSS changes are not reflecting

Written By

Ankit Gupta

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

The CSS changes are not reflecting in the browser until and unless the caches are cleared.

Environment

  • Liferay 6.2

Resolution

If the CSS changes are reflecting in the theme until the browser cache is not cleared. Therefore, to reflect the changes set below properties as "false" in the portal-ext.properties.

# Set this property to true to load the theme's merged CSS files for faster
# loading for production.
#
# Set this property to false for easier debugging for development. You can
# also disable fast loading by setting the URL parameter "css_fast_load" to
# "0".
#
theme.css.fast.load=true
# Set this property to true to load the packed version of files listed in
    # the properties "javascript.barebone.files" or
    # "javascript.everything.files".
    #
    # Set this property to false for easier debugging for development. You can
    # also disable fast loading by setting the URL parameter "js_fast_load" to
    # "0".
    #
    javascript.fast.load=true

The reason for disabling the properties theme.css.fast.load and javascript.fast.load (i.e. setting them to false in portal-ext.properties) is to restrict Liferay from using cached files, so they can be deployed on runtime, otherwise, you may not be able to see the results until a restart. It may still be possible for a browser cache to interfere, however. In testing these properties, if you are still unable to make the desired changes to the files for your custom war file in runtime, it may be necessary to redeploy the war file to have the changes reflected.

Did this article resolve your issue ?

Legacy Knowledge Base