Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

aui_deprecated.css cannot be loaded when switching to RTL languages

Written By

Alfonso Crisci

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • When using DXP in RTL languages (e.g.: Arabic, Hebrew), customers may notice visual errors and inability of Liferay to load CSS files, like, for example, aui_deprecated.css and others:

css_not_loaded.png

With messages similar to this (Chrome):

Refused to apply style from 'http://localhost:8080/o/frontend-css-web/portal/aui_deprecated.css?t=1559257778864' because its MIME type ('') is not a supported stylesheet MIME type, and strict MIME checking is enabled.

Environment

  • Liferay DXP 7.0
  • Liferay DXP 7.1

Resolution

  • Verify if your Liferay installation is affected by LPS-82650: if it is, open a support ticket asking for a patch
  • If your Liferay DXP is not affected by LPS-82650 or you don't use theme.css.fast.load=false, javascript.fast.load=false or include-and-override=portal-developer.properties in your portal-ext.properties file, chances are that the web server in front of Liferay is not delivering the css resources correctly. In that case, the below can only be a temporary workaround:

    - Stop the server
    - Delete the content of $LIFERAY_HOME/work, $LIFERAY_HOME/osgi/state
    - Delete the App server's temporary cache (in Tomcat: $TOMCAT_HOME/work and $TOMCAT_HOME/temp)
    - Restart the server
    - Clear the browser's cache

    And, for a full solution, the web server shall be tuned correctly
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?