Line Break Encoding () Not Working in Custom URL Submission

  • Resolved ezeetech21

    (@ezeetech21)


    1 month, 3 weeks ago

    Hi Support Team,

    I’m encountering an issue with redirecting users to a custom URL after form submission, where I’m passing field data like this:

    website.com/?Name=[1]&%0Aemail=[2]%0ACity=[3]%0ACountry=[4]

    Previously, the template would display as follows:

    Name: John Doe
    Email: demoemail.com
    City: City
    Country: Country

    However, after updating to the latest version of Formidable Forms, the line break encoding (%0A) is no longer working. The data is now appearing on a single line, like this:

    Name: John Doe Email demoemail.com City City Country Country

    This functionality was working correctly in earlier versions of Formidable Forms. Could you please advise on how to restore the proper line break behavior with the latest update?

    Thank you for your assistance!

    Best regards,
    Zeeshan from EZee Tech

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Njones35

    (@njones35)

    Hi @ezeetech21,

    Since you are using the Pro plugin, could you please open a ticket in our helpdesk here? We are only allowed to support the Lite plugin via WordPress forums:?https://formidableforms.com/new-topic/

    Thank you!
    Nathanael.

    Thread Starter ezeetech21

    (@ezeetech21)

    Hi Nathanael,

    Thank you for your response. However, I must clarify that the issue I raised is not related to the Pro version of your plugin. The problem pertains to the Lite version, where I’m using the built-in feature (Confirmation) to redirect users to a custom URL after form submission. The issue I encountered involves the inability to properly encode line breaks (%0A) in the URL, which should work regardless of whether I’m using the Lite or Pro version.

    It’s concerning that many issues in your WordPress forum are marked as “Resolved” by simply directing users to your Pro support. This practice not only misleads users but also gives the impression that you are avoiding addressing genuine issues within the Lite version. I was curious why all your topics are marked as resolved, and it seems this is a strategy to steer discussions away from the forums.

    This issue does not require Pro support, and I have already fixed it using information from your documentation/knowledgebase. However, I would like you to provide the answer here in the forum. I will keep this topic marked as unresolved until you do. If you choose not to respond, I will leave critical reviews highlighting how you are misleading users by redirecting them to Pro support and marking all topics as resolved. It’s important for you to address this transparently in the forum so that others facing similar challenges can benefit from the solution. I hope you reconsider your approach and provide the necessary assistance, regardless of the version being used.

    Thank you,

    Plugin Support Njones35

    (@njones35)

    Hi @ezeetech21

    I am delighted that you have already fixed this issue using information from our documentation – I suspect by using this hook? https://formidableforms.com/knowledgebase/frm_redirect_url/#kb-allow-brackets-in-redirect-url

    The WordPress moderation team are quite strict with us, and have given us stern warnings in the past about discussing Pro features here. We don’t want to upset them, so our team policy is to err on the side of caution and redirect ALL users with a Pro license to the helpdesk. You will receive faster support there, and have access to more of our team also.

    Any encouragement to open a ticket in the helpdesk is intended to be for your benefit, and the faster resolution of your issue.

    Best,
    Nathanael,

    Thread Starter ezeetech21

    (@ezeetech21)

    No, I did not fix issue with that link you sent me, because problem was not to pass brackets in URL, problem was passing line break encode %0A. i mentioned in subject but it is not showing in topic’s title. so, i fixed that with another article in your documents.
    Anyways Thanks. but here your team can’t assist.

    Plugin Support Njones35

    (@njones35)

    Hi @ezeetech21

    Thanks for the clarification. Since you have found a solution, I will mark this issue as resolved now.

    Best,
    Nathanael.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.