Legacy Knowledge Base
Published Jun. 30, 2025

Portlet's title is shown instead of the web content's title

Written By

Kanchan Bisht

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

  • The web content's title is not displaying.

  • Steps to reproduce:
    Start server
    Create global web content
    Put a WCD on a page, select global scope, and display the web content in it
    Observed behavior: Portlet's title (WEB CONTENT DISPLAY (GLOBAL)) is shown instead of the web content's title
    Expected behavior: Web content's title should be displayed

Environment

  • Liferay DXP 7.4 

Resolution

  • The observed behavior is a known bug of DXP 7.4 which has been addressed by LPS-173249.

Additional Information

  • Please submit a support ticket with the patch details attached if you require a hotfix or more information on this.
  • As per our release change: Customers on 7.4 can expect customer-specific hotfixes will be made available on demand for releases that have been issued within 180 days or the last 6 Updates, whichever is greater, as determined by the date the incident was reported to Liferay.
  • Installing Fix Packs and Hotfixes on Liferay DXP will guide you to install the Fixpack or Hotfix in your environment.
Did this article resolve your issue ?

Legacy Knowledge Base