Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Asset Publisher widget configuration saves by itself

Written By

Solyom Nagy-Györkös

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 Asset Publisher widget configuration saves itself when changing the Asset Selection

Environment

  • Liferay Portal EE 6.2
  • Liferay DXP 7.0+

Resolution

  •  This is the expected behavior of the Asset Publisher widget for the following sections:
    • Asset Selection Tab:
      • Asset Selection; Source/Scope (Dynamic selection)
      • Scope (Manual Selection)
      • Asset Entries selection (Manual Selection)
      • Sort Asset Entries selection (Manual Selection)

Additional Information

  • How to go back to the prior saved setup when cancelling no longer has any effect?

When configuring an Asset Selection "type" and hit the Save button, Liferay will save the configuration itself, as well. This means, if selecting a different Asset Selection "type", and would like to still use the previous configuration, simply selecting the "type" in question and Liferay will return the saved configuration for all the sections (e.g.: Scope, Source, Filter, Custom User Attributes, Ordering).

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