Legacy Knowledge Base
Published Jun. 30, 2025

Accesibility icon not being shown in a custom admin theme

Written By

Jorge García Jiménez

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

  • We've created a custom admin-theme but when we go to Instance Settings or System settings, it doesn't show some icons, p.e: accesibility icon.

Environment

  • Liferay DXP 7.4

Resolution

  • Having the correct icons available in your theme is dependent on having the correct versions of liferay-frontend-theme-styled and liferay-frontend-theme-unstyled in your package.json. 
  • You can check the versions of those themes from Control Panel -> GoGo shell using below command:
    lb styled
  • After that, adjust those versions in your custom theme's package.json. Per example, for Liferay DXP 7.4 u86 the values are:
    "liferay-frontend-theme-styled": "6.0.67",
    "liferay-frontend-theme-unstyled": "6.0.55",
  • After adjusting the versions run the following commands
    • If you are using npm:
      npm install && npm run build
    • If you are using yarn:
      yarn && yarn deploy
  • Deploy the new built theme in your Liferay installation and check if this solve the issue.

Additional Information:

Did this article resolve your issue ?

Legacy Knowledge Base