Support

Home Forums Event Espresso Premium Payment Methods Pro 2 PaypalPro methods set up issue with email

Payment Methods Pro 2 PaypalPro methods set up issue with email

Posted: September 23, 2020 at 11:28 am


Daniel

September 23, 2020 at 11:28 am

Hi!

I just activated a second PaypalPro payment method using the PaymentMethodsPro plugin. Everything seemed to be set up correctly and I had not yet put the payment gateway on the frontend since I was just starting initial testing.

Within 1 hour of creating this new “duplicate” gateway the EE messaging system started sending multiple copies of Event Registration emails.

I do not know if these events are related, but it seems likely! How could a second payment gateway of the same type trigger multiple (already sent) Registration confirmation emails?

I should add that I disabled the warning code that was blocking me from loading PMP and MER together so that may be related, but I don’t see how because the other gateway is not active and had not been used to receive payment on any events.

Please let me know if you have any insight into why adding a second payment method might trigger a multiple resending of emails?

Thanks in advance for any insight!
D


Daniel

September 23, 2020 at 11:30 am

Also, I deactivated the second PaypalPro payment method 20 minutes ago and the email sending has stopped. It had been going on a 10 minute loop sending multiple new (duplicate) emails to both Registrant and Admin.

D


Tony

  • Support Staff

September 28, 2020 at 11:39 am

Hi Daniel,

I’m really struggling to think of any kind of connection here, the only thing I can think of that would make any kind of sense here is if the request to activate the plugin triggered a cron job to send messages and the request was cached, but even then that’s a stretch.

Was it the same batch of registration emails sent? Which emails?

If so, was it the ‘last’ batch of email that was sent from Event Espresso?


Daniel

September 28, 2020 at 11:53 am

Thank you for the reply! Much appreciated.
I have again added a second Payment Gateway without any email resending issues. Perhaps it is just the first time you activate a gateway – maybe a gateway of the same type? Maybe a gateway of the same name? (Not sure at what stage of payment gateway creation I updated the name.

In any case, I am moving forward with this two gateway solution.

D


Tony

  • Support Staff

September 28, 2020 at 2:24 pm

That’s what makes this really weird, none of those requests are related to messages at all. There’s nothing even remotely similar to the requests that trigger messages when you enable a payment method.

Having a payment method with the same name shouldn’t be an issue as internally they are unique.

This with your other thread with messages leads me towards some kind of caching somewhere, I just can’t think of anything else that would make sense in those situations.

Are you running any form of caching?


Daniel

September 29, 2020 at 10:37 am

Yes, as with every other WP site I have multiple types of caching. I tend not to use object or query caching, but I do have page-level caching for non-logged-in users.

There is code that relates messages to Payment Methods… I definitely saw some code that triggered messages but I couldn’t quite get my head around all the conditions which is why I sent the question.

In any case, it appears that the duplicate messages have not reappeared. But It may be caused only on the first time activating a new payment method?

D


Tony

  • Support Staff

September 29, 2020 at 12:17 pm

I tend not to use object or query caching, but I do have page-level caching for non-logged-in users.

Page caching for non-logged in users shouldn’t cause either of these.

There is code that relates messages to Payment Methods… I definitely saw some code that triggered messages but I couldn’t quite get my head around all the conditions which is why I sent the question.

Which code? Payment methods don’t directly trigger messages, they update payments, which in turn updates transactions, which updates registrations which trigger messages.

But in either case, the request for activating/enabling a payment method has nothing remotely similar to triggering messages which is what I referred to above, not the payment method itself 🙂

In any case, it appears that the duplicate messages have not reappeared. But It may be caused only on the first time activating a new payment method?

I’ve tested this a few test sites just to confirm and so far, o additional messages. Seems like a tough bug to reproduce so far, which is frustrating as there’s simply nothing to even start troubleshooting yet but I’ll see if anything some up on those sites.


Daniel

September 29, 2020 at 12:45 pm

Thank you Tony!

As I said, this issue is no longer happening and I have a second Paypal Pro Payment gateway up and running.

So, please de-prioritize this issue.

I am still testing the 1000+ repeat email sending you mentioned … but so far have not had time to really get it worked over.

You must be logged in to reply to this support post. Sign In or Register for an Account

Support forum for Event Espresso 3 and Event Espresso 4.
Documentation for EE3 and EE4
Documentation for Event Espresso 3 Documentation for Event Espresso 4

Status: publish

Updated by  Daniel 3 weeks, 6 days ago ago

Topic Tags

Notifications

This topic is:
pending
Do NOT follow this link or you will be banned from the site!
[gravityform id=80 title=false description=false ajax=false]
<div class='gf_browser_unknown gform_wrapper' id='gform_wrapper_80' ><form method='post' enctype='multipart/form-data' id='gform_80' action='/topic/payment-methods-pro-2-paypalpro-methods-set-up-issue-with-email/'> <div class='gform_body'><ul id='gform_fields_80' class='gform_fields top_label form_sublabel_below description_below'><li id='field_80_1' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_80_1' >First name<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_text'><input name='input_1' id='input_80_1' type='text' value='' class='medium' aria-required="true" aria-invalid="false" /></div></li><li id='field_80_2' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_80_2' >Email address<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_email'> <input name='input_2' id='input_80_2' type='email' value='' class='medium' aria-required="true" aria-invalid="false" /> </div></li><li id='field_80_3' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' >GDPR Agreement<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_checkbox'><ul class='gfield_checkbox' id='input_80_3'><li class='gchoice_80_3_1'> <input name='input_3.1' type='checkbox' value='I consent to have this website store my submitted information so they can respond to my inquiry.' id='choice_80_3_1' /> <label for='choice_80_3_1' id='label_80_3_1'>I consent to have this website store my submitted information so they can respond to my inquiry.</label> </li></ul></div></li><li id='field_80_4' class='gfield gform_validation_container field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_80_4' >Phone</label><div class='ginput_container'><input name='input_4' id='input_80_4' type='text' value='' autocomplete='off'/></div><div class='gfield_description' id='gfield_description_80_4'>This field is for validation purposes and should be left unchanged.</div></li> </ul></div> <div class='gform_footer top_label'> <input type='submit' id='gform_submit_button_80' class='gform_button button' value='Download Now' onclick='if(window["gf_submitting_80"]){return false;} if( !jQuery("#gform_80")[0].checkValidity || jQuery("#gform_80")[0].checkValidity()){window["gf_submitting_80"]=true;} ' onkeypress='if( event.keyCode == 13 ){ if(window["gf_submitting_80"]){return false;} if( !jQuery("#gform_80")[0].checkValidity || jQuery("#gform_80")[0].checkValidity()){window["gf_submitting_80"]=true;} jQuery("#gform_80").trigger("submit",[true]); }' /> <input type='hidden' class='gform_hidden' name='is_submit_80' value='1' /> <input type='hidden' class='gform_hidden' name='gform_submit' value='80' /> <input type='hidden' class='gform_hidden' name='gform_unique_id' value='' /> <input type='hidden' class='gform_hidden' name='state_80' value='WyJbXSIsIjBiNjdjZjkyMDUzOWUxOWY5Y2NiZjIwMzM4YjA1Mjk4Il0=' /> <input type='hidden' class='gform_hidden' name='gform_target_page_number_80' id='gform_target_page_number_80' value='0' /> <input type='hidden' class='gform_hidden' name='gform_source_page_number_80' id='gform_source_page_number_80' value='1' /> <input type='hidden' name='gform_field_values' value='' /> </div> </form> </div><script type='text/javascript'> jQuery(document).bind('gform_post_render', function(event, formId, currentPage){if(formId == 80) {} } );jQuery(document).bind('gform_post_conditional_logic', function(event, formId, fields, isInit){} );</script><script type='text/javascript'> jQuery(document).ready(function(){jQuery(document).trigger('gform_post_render', [80, 1]) } ); </script>
[i]
[i]