Fixes present in Fix Packs affecting themes are not directly applied to my custom theme
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
- Part of the fixes included in a given Fix Pack can be located within the base themes Unstyled or Styled.
- Just applying that Fix Pack might not make those changes appear in the custom themes which inherits from those base theme.
Resolution
- Regenerate the theme with the latest released base theme version.
- Example:
- A custom theme based on the Unstyled theme has a dependency in the package.json file to liferay-frontend-theme-unstyled: 4.0.17
- A new Fix Pack with changes in the Unstyled theme's portal_normal.ftl file is installed.
- These new changes within liferay-frontend-theme-unstyled has been published under version 4.0.37 so the dependency in package.json file should be updated to that version and the custom theme should be regenerated and redeployed after that.
Did this article resolve your issue ?