Skip Navigation

[Resolved] Inconsistency in CRED default validation and cred_form_validate

This support ticket is created 10 years, 4 months 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.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Tagged: 

This topic contains 2 replies, has 3 voices.

Last updated by carletto0282 9 years, 5 months ago.

Assisted by: Ana.

Author
Posts
#116227

I needed some advanced validation for my CRED form so I used the cred_form_validate hook to achieve it. However, the validation seems to be different for each of those cases. The default validation will work before the form is submitted (it displays an error tooltip above the field, i.e. This field is required).

However, when I use the cred_form_validate hook, the page refreshes and then only after that it will display the error message. Also, this error message does not look like the above tooltip. It displays a red border around my field and adds the error text above it. This breaks the user experience.

Why two different-looking types of error messages? Why not make cred_form_validate use the default validation and validate without a page refresh and display that tooltip?

#117163

Ana
Supporter

Dear Hassan,

thanks for the feedback. This is not presently possible with CRED but we are going to make some major changes in this plugin and we will consider your request.

Regards,
Ana

#228513

Hi guys + one for this feature... the actual workflow of validation is really displeasing, as Hassan already pointed out!

So please take in serious consideration a way to enhance this!
Thank you very muh

Best regards
Carlo

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.