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.

Notification to User doesn't recognize {user:user_email} variable

Gravity Support Forums » Plugin Support » Gravity Forms

  1. 61pixels
    Member

    I have a field in my form that is using the default value {user:user_email} to have the users email added to the form.

    I then have on my notifications setting for it to email the user, although it doesn't seem to recognize that there is in fact an email field. I get the following message "Your form does not have any email field. Sending notifications to users require that the form has at least one email field."

    The emails do seem to work still for some people, but there have been a few reports from users that they never receive the emails, so I'm wondering if it has something to do with this?

    Posted 13 years ago on Monday November 21, 2011 | Permalink

  2. Carl Hancock
    Administrator

    The {user:user_email} returns the email of the user who is logged in when they submit the form. If the user isn't logged into your site, then this merge tag isn't going to return a result. It's not something you generally use as the Send To for your email notifications.

    Usually what you use in the Send To for the email notifications is an Email field on your form. When you configure the Send To for the User Notification you can either enter a hardcoded value, a merge tag or select an Email field on your form. 99% of the time people select an Email field on their form. The User Notification is then sent to that email address.

    If you are using the {user:user_email} merge tag... it's probably only working part of the time because it's only going to work for users that submit the form while logged into your site.

    Posted 13 years ago on Monday November 21, 2011 | Permalink

  3. 61pixels
    Member

    Hi Carl, I guess I should have specified, ALL users are logged in when submitting the form. The form is on a page that is not accessible unless a user is logged in, hence why I went with the variable as opposed to the user having to type in their email address.

    Posted 13 years ago on Monday November 21, 2011 | Permalink

  4. Carl Hancock
    Administrator

    Here is what I suggest trying...

    - Edit the form
    - Add a new Email field to your form
    - Edit this new Email field
    - Give it a Field Label of "User Email"
    - Select the Advanced Tab
    - In the Default Value select the User's Email merge tag to insert {user:user_email} in the default value
    - Select Admin Only in the Visibility option
    - Save your form

    Once you make this change to the form then edit your User Notification and configure it to use that Email field to send the email to.

    Now you'll be able to view the entries for the forms that the user didn't receive the notification for and make sure that the Entry has their email in that field. By simply using the merge tag directly in the user notification it makes it difficult to track to make sure it was populated correctly. If you implement it using the steps above, then it still uses the user's email as the value... but also stores it as a field value so you can see if it was populated or not.

    If it is populated, and the user didn't receive the email then it is likely an email reliability issue with your server or an issue on the users end.

    Posted 13 years ago on Monday November 21, 2011 | Permalink

  5. 61pixels
    Member

    Thanks Carl, that is actually how it is already set up. It's an actual field. The data is always stored correctly as well as I can see the email address in the form submission itself.

    It is quite possible that it is an email on the user end or the server, I just thought I'd toss it out here to see if there was something I am missing.

    One thing I did notice, was that the last user who reported the problem, their email address had a dot in it, aka: name.lastname@something.com is it possible the . could cause the issue? I doubt it, but figured I'd toss that out there.

    Thanks again.

    Posted 13 years ago on Monday November 21, 2011 | Permalink

  6. Carl Hancock
    Administrator

    The dot shouldn't cause a problem. The issue is going to be email reliability from your server, or an issue on their end, or a combination of the two. I would suggest reading this post by Joost de Valk on email reliability:

    http://yoast.com/email-reliability/

    Posted 13 years ago on Monday November 21, 2011 | Permalink

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