Legacy Knowledge Base
Published Jun. 30, 2025

The validation message of some inputs doesn't mention the correct input name

Written By

Marcos da Silva Xavier

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

  • Fields marked as required and left empty when trying to submit a form or publish a folder display a different error message than what is expected: “This field is required”. 

Environment

  • DXP 7.4 U49+

Resolution

  • Before the release of DXP 7.4 U49, the default error message would only be "This field is required." if you did not set a custom message. However, after this update, even if you do not set a custom error message, it will display the message as this: "This [FIELD NAME] field is required."
  • This behavior was flagged as intended and was introduced by LPS-166091.
  • It was stated that the error message displayed in previous versions of DXP that came before U49 was not the right one, instead what should have been displayed was always: "This [FIELD NAME] field is required."
  • If you wish to change this behavior, the only way to do that is to customize the taglibs. The associated links can be found at the Additional Information section below.

Additional Information

 

 

Did this article resolve your issue ?

Legacy Knowledge Base