404 error for fragments images after updating site friendlyUrl
Written By
Jamilly Macedo
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
- When we change the site friendly URL, fragment images stop working and 404 errors were found in the browser console.
- Steps to Reproduce:
-
- Set up Liferay DXP 7.4 Update 74.
- Navigate to Site Builder > Pages > Create a test page, e.g., "/test".
- Drag and drop a basic image fragment and add an image to it.
- Publish the page.
- Go to the site menu > Configuration > Site Settings > Site Configuration > Site URL.
- Change the site friendly URL, for example: from "guest" to "guest-test".
- Refresh the page "/test".
-
Actual Behavior: Fragment images stop working and 404 errors were found in the browser console.

Resolution
- This issue is currently a limitation of the product. As workaround, use "Mapping" instead of "Source Selection" in Image Fragment.
- When configuring an image fragment, instead of selecting an image using "Direct Selection", "Mapping" can be used instead, choosing "File URL" as the field. This way the URL is not stored in the FragmentEntryLink editableValues, and the image will be displayed correctly also after changing the site friendly URL.
Did this article resolve your issue ?