Skip Navigation

[Resolved] Customizing the CRED form top error message

This thread is resolved. Here is a description of the problem and solution.

Problem:

The problem here is that the user wanted to remove the custom field names from the field error messages in our Toolset Forms.

Solution:

Unfortunately this isn't possible because the fields are bound messages.

This support ticket is created 3 years, 1 month ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Our next available supporter will start replying to tickets in about 1.20 hours from now. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

This topic contains 2 replies, has 2 voices.

Last updated by Saul Baizman 3 years, 1 month ago.

Assisted by: Shane.

Author
Posts
#2207563
screenshot 2021-10-27 at 18.21.23.png

Hi there,

I was wondering if it were possible to customize the CRED post form top error messages. I'm using the cred_form_validate hook to validate form fields in a custom manner and assign custom error messages. The error messages always display in this format:

Custom field name: custom error message.

I'd like to remove "Custom field name:" from the error message. Is that possible? The attached screenshot shows the error message currently, and I've underlined in red what I'd like to remove.

Thank you!

Saul

#2208271

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Saul,

Thank you for getting in touch.

Unfortunately no you're not able to do this. The field name is bound to the error message.

Thanks,
Shane

#2208423

OK, thank you, Shane!