PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Problem with a submission: How to customize the text?

  1. adrien
    Member

    Hi (again),

    Here I'm almost done with the killer form I have built with the plugin. The only thing I want to fix is the text a user get when there is an error in a form she submitted :

    There was a problem with your submission. Errors have been highlighted below.

    Any chance I can customize it?

    Thanks,

    - Adrien O'Leary

    Posted 9 years ago on Tuesday January 12, 2010 | Permalink
  2. Hello Adrien,

    Right now it is possible to customize the validation message on a field but I do not believe it is possible to change the primary validation error message that you referenced above. This is a localized string so that it can be translated when the plugin is translated.

    I will check to see if there is a hook that can be leveraged to change this programatically. We can look into making it customizable in a future release.

    Posted 9 years ago on Tuesday January 12, 2010 | Permalink
  3. Is there an update on this issue?

    Thank you.

    Posted 9 years ago on Thursday January 28, 2010 | Permalink
  4. I have added a hook for the validation message that will allow you to change it. But that will only go out on 1.3.9. Probably a couple of weeks away.

    Meanwhile, you can use jQuery to change the message.
    Note: This snippet requires that the jQuery library is already loaded in your theme to function properly.

    Also, you will need to replace 21 (in #gform_21) with your actual form id

    <script type="text/javascript">
    
                jQuery(document).ready(
                    function() {
                        jQuery("#gform_21 .validation_error").html("My new validation message");
                    }
                );
            </script>
    Posted 9 years ago on Thursday January 28, 2010 | Permalink

This topic has been resolved and has been closed to new replies.