Web content templates: Make Document Library URL relativeWeb content templates: Make Document Library URL relativehttps://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&threadId=1226246112026-04-04T02:31:04Z2026-04-04T02:31:04ZRE: Web content templates: Make Document Library URL relativeJamie Sammonshttps://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=1226634782024-05-20T16:15:09Z2024-05-20T16:15:08Z<p>Feature Request Created: https://liferay.atlassian.net/browse/LPD-26324</p>Jamie Sammons2024-05-20T16:15:08ZWeb content templates: Make Document Library URL relativeTobias Barthhttps://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=1226246102024-05-16T03:38:26Z2024-05-13T08:03:35Z<p>Hi,</p>
<p>our customer is using Liferay DXP 2023.q4.4 and has an ftl template,
which renders an image using component.documentUpload.getData()</p>
<p>They we found out that the "getData()" method is served by
Java method com.liferay.portlet.documentlibrary.util.getPreviewURL</p>
<p>The generated URL is absolute, that means it starts with https://domain.com/ </p>
<p>The issue is now, that, if caching is enabled for the web content
template, the URL will be cached with full domain name. Since the
Liferay instance serves two domains - one for internal use within the
customer's network, allowing access to the Liferay admin UI, and one
for access from the public internet - wrong URL names are being
delivered. This way, the html that is delivered to public users
contains URLs that point into the internal network, and cannot be resolved.</p>
<p>In order to fix this situation and keep caching enabled, I am asking
you to:</p>
<p>
<strong>Please make it possible to easily retrieve relative URLs for
document library assets from within .ftl templates</strong>
</p>
<p>As an alternative (which is not preferred by the customer), I could
imagine that adding the requested host name to the cache key would do
the job.</p>
<p>Best,</p>
<p>Tobias</p>Tobias Barth2024-05-13T08:03:35Z