Legacy Knowledge Base
Published Jun. 30, 2025

Adding a meta tag in a web content template with a description containing a single quote could break the HTML

Written By

Jose Bodega

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

  • Create a web content with a description containing a single quote (')
  • In the content template, the description is retrieved and added as a meta tag in the head section of the page using the following code.
<@liferay_util["html-top"]>
    <meta property="og:description" content='${description}'>
</@>
  • This results in misplaced text and links at the beginning of the page.

Environment

  • Liferay DXP 7.4+

Resolution

The problem originates from custom theme template code generating meta tags where single quotes in description conflict with the quotes delimiting the content attribute.

To fix this, escape  description variable using the htmlUtil.escape() method within your custom template. For instance, modify the following custom code:

<@liferay_util["html-top"]>
    <meta property="og:description" content='${htmlUtil.escape(description)}'>
</@>

This escapes special characters, preventing HTML structure issues in meta tags.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base