Assets created from an Asset Publisher don't keep the categories and/or tags of the filter
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
- An Asset Publisher (AP) can be configured to filter by certain categories and/or tags.
- When the Display Settings of the AP has Show Add Content Button enabled, it's possible to create new assets directly from the AP.
- In some cases, the asset created already has filled out the categories and/or tags from the AP configuration. But in other cases, it isn't.
Resolution
- The discrepancy lies on the precise configuration of the filter rules in the AP:
- If the rule is of the type Contains All, then creating a new asset from the AP will automatically add those categories and/or tags.
- If the rule is of the type Contains Any, then creating anew asset from the AP will not fill out the categorization section.
- The justification for the second situation is avoiding potential problems with content creators that may not have permissions to see all categories and/or tags used in the AP filter. They might think that only a few categories and/or tags are assigned to the created asset although there are more. This might imply having the new asset being shown in another AP that the creator did not intend to.
Did this article resolve your issue ?
