email={inputs.email} incompatible with plus addressing

  • Resolved bügelfrei

    (@alexanderbailey)


    2 weeks, 5 days ago

    I’m using a pair of forms on a site for newsletter signup (form #1, collects email address only) and subscriber profile info (form #2, optional). Form #1 passes the subscriber’s email address using Fluent Forms’ redirect query string functionality with the setting email={inputs.email}.

    Form #2 then pre-enters the email address in an email field using {get.email}. For the sake of clean UI, I hide the email field on Form #2 with the custom class “hidden”.

    It all works perfectly until a subscriber uses plus addressing (supported by Gmail, Outlook 365, and Dreamhost mailboxes, and probably many more). For example, we get the following redirect URL: https://staging.nextmetropolis.com/complete-your-profile/?email=example+test@example.com

    Although the redirect query string above is what we want it to be, the + symbol gets replaced by a blank space in the email field on Form #2. When the user clicks the form’s submit button, it fails. The user should see a tool tip with explaining the problem (“A part followed by ‘@’ should not contain the symbol ‘ ‘”), but if you have hidden the email field, the user sees nothing but a form which seems to be a dead end.

    In the staging site example linked to above, I have removed the “hidden” class from the email field for the sake of illustration.

    Obvious options for me are:
    1. Don’t worry about people who make use of plus addressing, or
    2. Don’t hide the otherwise redundant email field in the second form.

    But it would be great if the sanitizing process behind {get.email} would leave the + symbol intact.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Syed Numan

    (@annuman)

    2 weeks, 5 days ago

    Hello @alexanderbailey,

    Thank you for reporting this and for sharing the detailed example.

    We have acknowledged the issue, and our development team has confirmed that this will be addressed from the plugin side.

    As a temporary workaround, you may use the following snippet. It ensures that plus-addressed email values are preserved correctly when passed through the redirect query string.

    Please add the snippet using the Code Snippets plugin or your child theme’s functions.php file. Also, replace 1 with the ID of your first form if needed.

    https://gist.github.com/annuman97/94713380b6838f1435d20b2809e4799d

    Thank you

    Thread Starter bügelfrei

    (@alexanderbailey)

    2 weeks, 4 days ago

    Awesome, @annuman! Thank you!

    I tested the workaround successfully.

    Heads up anyone following in my footsteps to implement the workaround: When testing, don’t start from the Form #2 URL with the “+”; instead enter the plus-addressed email in Form #1. The fix works by encoding the “+” in the query string as “%2B”.

    Plugin Support Rahul Das

    (@testerrahul)

    2 weeks, 4 days ago

    Hello there,

    Glad to hear that the workaround worked for you! Also, I appreciated your suggestion following this. I hope it will be helpful for others.

    Thank you

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.