Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Fix Pack and Hotfix installation order on Liferay Portal EE

Written By

Liferay Support

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.

The order of fix pack and hotfix updates are determined by engineering in several ways. This order is hardcoded in the update.

Environment

  • Versions previous to Portal 6.2 SP11

Resolution

General Guidelines:

  1. The general order of installation is: Fix-Packs and Security Updates before Hotfix updates.
  2. Subsequent order is determined by type of component. For example, a core fix would precede an upgrade fix.
  3. Numerical suffixes do not affect load order.
  4. Do not modify the fix order by editing the update. This can cause conflicts.

Exceptions:
Certain fixes that resolve, or are dependent on other updates, may change the load order such that code conflicts do not happen. To determine if a hotfix update will override or conflicts, run the patching-tool info command.

$> ./patching-tool.sh info

[ -] [fix-name][fix-number][liferay-version] :: Currently not installed; Won't be installed: [fix-name]-[fix-number]contains the fixes included in this one
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?