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.

"Website" fields requires http:// - Why??

  1. The Special 'website' field requires the user to enter http://. This makes no sense. Can't the system just add it on for them if it's required on the backend for some reason?

    This form field has a lot of issues:

    1) If you put in http:// as the default text and they have no web site, they get an error unless they manually remove it.
    2) If they have a web site, even though the form shows a faint http:// in the field, it gets erased as soon as the user starts typing. One would think since it's required it would remain there and the user's text would proceed it.
    3) There is no way to turn of validation for this field to eliminate these issues or allow the user to enter 'None'.
    4) The Validation Message override does not work. It just says "Enter a URL" as the error even if a custom message is know, to tell them they have to enter http:// or remove the one thats there. (Avoiding adding as a descr to keep things clean)
    5) Yes, using a regular text field is an alternative, but I'd love for the Gravity Folks to get the website field fixed up.

    Thanks guys.

    Posted 5 years ago on Wednesday June 19, 2013 | Permalink
  2. Richard Vav

    The url type input the Gravity Forms developers are using is implemented as per the W3C HTML5 standard, it is the browser that requires the http:// to be entered by the user for it to pass validation, the faint http:// that disappears when the user starts typing in the input is called a placeholder and again that is how HTML5 placeholders work. If you want the http:// to remain in place I would recommend you go to the Gravity Forms general settings page and switch 'Output HTML5' to 'No'.


    Posted 5 years ago on Wednesday June 19, 2013 | Permalink
  3. Phil

    This thread includes an option for automatically adding a protocol (e.g., http:// ) if the user omits it. One disadvantage of the approach is that it instructs the browser to not validate any of the fields for the form, leaving all validation up to the Gravity Forms. An advantage, however, is that the approach leaves HTML5 on, which may conveniently bring up custom keyboards on mobile devices.

    Posted 4 years ago on Saturday July 6, 2013 | Permalink

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