Legacy Knowledge Base
Published Jun. 30, 2025

Customize the OOTB portlets on the Liferay SaaS platform

Written By

Madhusudan Sharma

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.
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

  • Could you please provide us with a blog to customize OOTB JSP in Liferay SaaS platform?

Environment

  • Liferay DXP 7.1
  • Liferay DXP 7.2
  • Liferay DXP 7.3
  • Liferay DXP 7.4

Resolution

  • Liferay SaaS is explicitly for preventing deploying any custom code to DXP. Therefore, it is not possible to customize the OOTB portlets in the Liferay SaaS platform.
  • However, it is possible to build your own implementations for example, if you don't like the OOTB blogs, you can create an Object to hold the blog data and custom react fragments to handle the display.
  • Additionally, an alternate approach could be to use the concept of Widget Display Templates to customize the appearance and functionality of out-of-the-box widgets, such as the Asset Publisher and Media Gallery widgets.

Additional Information

To get more insights, please find the below documentation:
Did this article resolve your issue ?

Legacy Knowledge Base