Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Rating does not work on the Asset Publisher

Written By

Ahmed Abdin

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

  • I have an issue with the Asset Rating. I create web content or any asset that can be rated. I place an Asset Publisher on a page to display the content. I enable the ratings on the Asset Publisher. When I rate the displayed article, I receive a JS error, and after refreshing the page, the rating is reset.

Reproduction Steps:

  1. Start 2025.q2.2
  2. Go to Content and Data --> Web Content, and add a web content.
  3. Go to Site Builder --> Collections, create a collection, and configure it for the basic web content.
  4. Go to Site Builder --> Pages, add a page, and add to it an Asset Publisher widget.
  5. Configure the AP widget to display the content and enable the Ratings option.
  6. Go to the Page and try to rate the displayed content.

Expected Result: The rating value remains with no issue.

Actual Result: A JS error is thrown in the browser console, and after refreshing the page, the rating is reset.

Environment

  • Liferay Quarterly Release 2025.q2.2

Resolution

  • The case has been addressed and resolved by LPD-55075. If you are in 2025.q2+ releases, kindly request a hotfix. It is included in 2025.Q1.12
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?