An extra "/" character is added to a link I created in an email notification

  • Profile Image
    infoclicks
    Asked on April 08, 2015 at 08:40 AM

    Hi,

    In email notification of the form submission, I wanted the URLs are clickable. So I edited it as instructed

    Screenshot: http://www.screencast.com/t/Lt5JnXeyx

    The problem is in my mailer, when I received the email notification and clicked on the link, I got error page not found

    Screenshot : http://www.screencast.com/t/cgxMwGQUaZAz

    As you see it added an etra / in front of the URL which I didn't insert.

    Any ideas?

     

    Thanks,

  • Profile Image
    raul
    Answered on April 08, 2015 at 12:27 PM

    You can add the http:// portion of the URL in your anchor tag so the addtional / is not added and then you can add a URL validation to your field in order to force your users to enter a valid URL.

    So, your users can enter the URL like in the picture below:

    And the link should work correctly.

    Hope this helps.

    Let us know if you need further assistance.

  • Profile Image
    infoclicks
    Answered on April 08, 2015 at 05:40 PM

    Thanks Raul.

    I  followed your instruction and it works however only if the user type www.domain.com or domain.com

    but if they typed http://domain.com then in the email notification clicking on it it will take you to http//domain.com with error page not found?

     

     

  • Profile Image
    EltonCris
    Answered on April 08, 2015 at 07:32 PM

    @infoclicks

    Thanks for your reply.

    In that case, restricting the value to start with "www" should prevent that error. You can use input mask feature and fill it with "www" as the default readonly value so they only have to enter their domain name without the http.

    I have also raised this to our developers. I've been known to this issue for quite a long time already. I think this was added for security reasons but I think this deserves an exemption.

    Thank you!

  • Profile Image
    liyam
    Answered on April 10, 2015 at 02:25 AM

    Hello,

    You may try it again using Raul's recommendation. It should handle even if the user enters a URL that starts with http://.

    If you have other questions, please do let us know.

    Thanks.