legacy-knowledge-base
公開されました Jun. 30, 2025

After upgrading from DXP 7.4 u63 to quarterly Release 2024.q2.12, expanding the left panel expand the left panel is not possible and the main menu on the top right is not available due to caching issues

投稿者

Ahmed Abdin

knowledge-article-header-disclaimer-how-to

knowledge-article-header-disclaimer

legacy-article

learn-legacy-article-disclaimer-text

Issue

  • I upgraded from DXP 7.4 update 63 to 2024.q2.12. After the upgrade, when I start the instance. It is not possible to expand the left panel and the main menu on the top right is not available. When trying to do so, JS errors appear in the browser. After clearing the browser cache, everything works as expected.

Reproduction Steps:

1. Set up a DXP 7.4 update 63 (I used database MySql). Do not start it.
2. Start Chrome browser and clear cache by pressing Ctrl+Shift+Del:
a. Select “All time” for Time range.
b. Tick Cookies and Cached images.
c. Click Delete data.

3. Start DXP 7.4 update 63
4. If the instance does not open in a Chrome browser, open it manually in a tab, wait until the home page is loaded, and log in as admin.
5. Once completely logged in, close the browser tab, and shut down the server.
6. Start 2024.q2.12. If the instance is not opened in a browser, open it manually in a Chrome tab.
7. Open Dev tools (F12) and under the Network tab, make sure that the Disable Cache option is unselected.

8. Keep the Dev tool console open, and log in as admin.
Checkpoint 1 (noted by the customer): In the Network tab you can see that some JS files are served from cache (Desk Cache).

Checkpoint 2: Observe that the main menu icon on the upper right is missing.
9. Try to expand the left panel by pressing the icon beside "Home" on the upper left.

Expected Result: The panel opens with no issues.
Actual Result: Nothing happens and a JS error appears in the log.

Note: When refreshing the page (CTRL + F5), everything works as expected.

Environment

  • Liferay DXP 7.4 update 63+
  • Quarterly Release 2024.q2.12

Resolution

  • We are aware of the issue. The root cause of failure is the change to etag caching introduced in 7.4.3.84-ga84
  • To resolve the issue, you will need to remove the browser cache. If you are using a CDN, please remove the CDN cache as well.
did-this-article-resolve-your-issue

legacy-knowledge-base