Gravity Support Forums Topic: Broken URL in Notification Email

Gravity Support Forums Topic: Broken URL in Notification Email https://legacy.forums.gravityhelp.com/topic/broken-url-in-notification-email Gravity Support Forums Topic: Broken URL in Notification Email en-US Sun, 19 Apr 2026 19:58:00 +0000 http://bbpress.org/?v=1.0.1 <![CDATA[Search]]> q https://legacy.forums.gravityhelp.com/search.php Dana Cobb on "Broken URL in Notification Email" https://legacy.forums.gravityhelp.com/topic/broken-url-in-notification-email#post-60668 Tue, 29 May 2012 16:26:46 +0000 Dana Cobb 60668@https://legacy.forums.gravityhelp.com/ I am closing this forum topic because we are working with you through the Priority Support ticket system. Chrischmi on "Broken URL in Notification Email" https://legacy.forums.gravityhelp.com/topic/broken-url-in-notification-email#post-60512 Mon, 28 May 2012 08:10:53 +0000 Chrischmi 60512@https://legacy.forums.gravityhelp.com/ We have a form, which sends a notification. the notification includes a long URL as <a href="...." rel="nofollow"> tag, containing all form fields as parameters. The URL is used to enter the form data to a shop system. Example: We build the following URL inside the notification configuration: <a href="https://shop.company.com/?product=123&name=Carl&phone=+49" rel="nofollow">https://shop.company.com/?product=123&name=Carl&phone=+49</a> 221 123456&company=xyz But the URL in the received email is: <a href="https://shop.company.com/?product=123&name=Carl&phone=#43;49" rel="nofollow">https://shop.company.com/?product=123&name=Carl&phone=#43;49</a> 221 123456&company=xyz We do have some problems with the URL: 1) The phone number will be coded by Gravity Forms to "#43;49 221 123456" (with decimal char code), in an URL it would be needed as "%2B49 221 123456" (with hex code). 2) All ampersands will be coded as & instead of delivering the & inside the href-part of the </a><a> tag. 3) Our real URLs are very long, because of the number of fields. All URLs have a Line Break somewhere between 1000 and 1100 characters. The line break happens inside field names or values and is not provided in the notification configuration. Please advice a solution or workaround.</a>