Legacy Knowledge Base
Published Sep. 10, 2025

Paginator Elements Are Not Translated to the Site's Language

Written By

Cristina Rodriguez

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 using a paginator component on a site, the links to the different pages (e.g., "Page 1", "Page 2") are displayed in English.
  • These labels do not get translated even when the site's language is set to a different language, such as Spanish.

Environment

  • Liferay DXP 7.4
  • 2023.Q4+

Resolution

This is the expected behavior. By design, the language key for the paginator, page-x, must be translated manually. There are two methods to add the required translations:

  1. Language Override Tool (Recommended)
    • This tool is available in Liferay DXP 7.4 U4+ and is the recommended approach.
    • Navigate to the Control Panel → Configuration → Language Overrides.
    • Add a new override for the key page-x for each language you need. For example, for Spanish, the value would be Página {0}.
  2. Resource Bundle Module (Alternative)
    • You can create a custom module that provides a resource bundle to override the global language properties.
    • This method is useful for automating the deployment of translations across different environments, as the translations will be included in the deployed module.

Additional Information

 

Did this article resolve your issue ?

Legacy Knowledge Base