Web contents and blog posts can be displayed in asset publishers even if their filters wouldn't allow them
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
- A web content (or blog post) can be displayed in any Asset Publisher, even if its configuration wouldn't allow it, by requesting a URL of the form: .../-/asset_publisher/$asset_publisher_identifier/content/$web-content-friendly-url
Resolution
- This is the expected behavior for the Asset Publisher.
- The Asset Publisher acts as a container to display assets. For web contents and blog posts there are standard URLs like the one above that allow to display any such asset given the Asset Publishers identifier and the asset's friendly URL.
- The configuration of an Asset Publisher only applies when viewing the specific page where it is located.
- This behavior allows displaying any web content in an Asset Publisher of choice if it is the default Asset Publisher of the page.
- A user trying to view the assets via this URL must still have the appropriate permissions.
- The URL can also be enlarged with /$siteId to display assets from other sites.
- Given this behavior, the configuration and filters of an Asset Publisher should not substitute the permissions framework.
- For example, if one Asset Publisher is configured to display the asset's author but another isn't, it will still be possible to see the author of those assets displayed in the second Asset Publisher by requesting them in the first one via the appropriate URL.
Did this article resolve your issue ?
