Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Mandrill Gravity Forms Bug | Event Espresso - Staging Server

Support

Home › Forums › Pre-Releases › Mandrill Gravity Forms Bug

Mandrill Gravity Forms Bug

Posted: May 14, 2013 at 10:42 am

Viewing 1 reply thread


Bryce Jacobson

May 14, 2013 at 10:42 am

I just wanted to make note of a bug that I came across with EE Email Transactions. In versions 1.1 of that plugin when I included an email address in the BCC field under notifications in Gravity Forms those emails wouldn’t get sent and sometimes the form would fail to submit.

I updated to version 1.2.1 of EE Email Transactions and that seemed to fix the issue. I didn’t see a change log for that version so I’m not sure what you changed but it works if anyone else is having a similar issue.


Darren Ethier

May 14, 2013 at 10:53 am

Thanks for reporting Bryce,  yes that bug was fixed in 1.2.1 of the EE Email Transactions.  Sorry for not keeping the changelog up to date for the release but its not a primary product so we do better documentation “when we get around to it” :)

We are planning on releasing EE Email Transactions to wordpress.org sometime in the next few weeks.  When we release there we’ll update the changelog on each update there.
Viewing 1 reply thread

The support post ‘Mandrill Gravity Forms Bug’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Home to preview versions of next-generation Event Espresso products.

Status: closed

Updated by Darren Ethier 11 years, 8 months ago ago

Topic Tags

Tagged: ,

Notifications

This topic is: resolved
Event Espresso - Staging Server