Legacy Knowledge Base
Published Jul. 2, 2025

RenderURL doesn't work in Nested Applications Portlet

Written By

Joel Jeong

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • If you deploy a portlet within the "Nested Applications" portlet that has a <liferay-portlet:renderURL > tag in the JSP, the url that is rendered is not "recognized" by the portlet and a redirect does not occur.

    For example, if you have a portlet that will take a parameter and then redirect users to a particular page on the system based on the forwardTo parameter:

    <liferay-portlet:renderURL var="forwardToTEURL">
    <portlet:param name="forwardTo" value="TE" />
    </liferay-portlet:renderURL>

    The portlet will not work as intended when it is deployed within a "Nested Applications" Portlet, and redirect will not occur.

Environment

  • Liferay DXP 7.2

Resolution

  • The actionURL should be used instead of the renderURL to send redirects.

 

Did this article resolve your issue ?

Legacy Knowledge Base