Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

In DXP, it is not possible to differentiate configuration per site on embedded portlets

Written By

Alfonso Crisci

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

  • In DXP, a portlet could be embedded like below:
    <#assign preferencesMap = {"portletSetupPortletDecoratorId" : "barebone"} />

    <@liferay_portlet["runtime"]
     instanceId="1234"
     defaultPreferences=freeMarkerPortletPreferences.getPreferences(preferencesMap)
     portletProviderAction=portletProviderAction.VIEW
     portletName="my_test_portlet_web_MyTestPortletWeb"
    />
    This works, however, when setting Look and Feel or Configuration on one instance, the same settings will be replicated on the same portlet embedded on a different page

    How can the Settings and Configs be separated?

Environment

  • Liferay DXP 7.0+

Resolution longer

  • Dynamically differentiate the instanceId, for example:
    <#assign preferencesMap = {"portletSetupPortletDecoratorId" : "barebone"} />

    <@liferay_portlet["runtime"]
     instanceId="FOOTER${plid}"
     defaultPreferences=freeMarkerPortletPreferences.getPreferences(preferencesMap)
     portletProviderAction=portletProviderAction.VIEW
     portletName="my_test_portlet_web_MyTestPortletWeb"
    />

Additional Information

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?