|
Michael
|
November 6, 2014 at 2:37 pm
Hi. If I as an EE admin register and apply a payment (invoice) for someone from the dashboard, then change the Primary Registrant’s email address, then click Resend Registration (on any of the various screens it is available on), the message does not send.
I’m using Mandrill and can see that the message is not attempted. All other messages work as expected. EE does, however, say “the message was sent” in a popup after the button is pressed.
Can you reproduce this, or does it work for you?
The only other thing that doesn’t work for me is I cannot change the number of Events to display in the admin panel via screen options. If I choose 20, it reverts to 10. I only mention because I’ve wondered if this is because of the WPEngine heartbeat API setting, a source of wackiness, as documented here: https://eventespresso.com/topic/ee4-new-install-cannot-create-new-ticket-change-register-now-payment-method/
|
|
Lorenzo Orlando Caum
|
November 6, 2014 at 3:25 pm
Hi, you maybe seeing some caching happening with the WP dashboard. Try setting the toggle again via Screen Options and then clear your cache through the WP Engine menu.
You are using 4.4.4, correct?
—
Lorenzo
|
|
Michael
|
November 6, 2014 at 3:30 pm
Good idea, but unfortunately that’s not it in either case.
No, I’m still on 4.4.3
|
|
Lorenzo Orlando Caum
|
November 6, 2014 at 3:46 pm
Hi,
Can you update to the current release?
—
Lorenzo
|
|
Michael
|
November 6, 2014 at 3:51 pm
I plan to, but do you know if this feature was previously broken? Does it work for you on any version? Does any kind of resend work for you? Thanks
Upgrading will take me some time that I don’t have right now because I’ve modified plugin files.
|
|
Michael
|
November 6, 2014 at 4:35 pm
Lorenzo, I just did a quick test in my staging environment. Resending does not work on 4.4.4 either.
Resending of any kind doesn’t work–it doesn’t matter if you change the email address or register them from the admin panel–this applies to regular registrations too.
I have verified mail flow on 4.4.3 and 4.4.4, and only the emails that are generated at registration send, never resends.
We plan to rely on this feature to send out Reminder Emails until we create a better solution.
|
|
Lorenzo Orlando Caum
|
November 6, 2014 at 9:34 pm
Hi,
Could you go to Event Espresso –> Messages –> Settings and deactivate each message type and then drag them back to the left site to reactivate them?
—
Lorenzo
|
|
Michael
|
November 7, 2014 at 4:16 am
That didn’t work.
|
|
Lorenzo Orlando Caum
|
November 7, 2014 at 6:09 pm
Hi,
We have tested this with the current version of Event Espresso 4.4.4 on two sites on different WP Engine servers and it did work as expected.
Have you tried testing on defaults to rule out a conflict somewhere? Try installing the Email Log or Check Email plugin and then send out a couple reminders. It should log each attempt.
Also, you mentioned that you edited the core. I would temporarily rename the Event Espresso folder and move a fresh copy of the current version into place and re-test.
—
Lorenzo
|
|
Michael
|
November 7, 2014 at 6:58 pm
I’m terribly sorry: the problem was that the Registrant email had to be enabled. I previously disabled Registrant context by leaving To: blank.
I was only attempting to send to the Primary Registrant, which is the only context I had enabled, because I only collect reg info from primary. I was only sending to Primary Registrants, so it didn’t occur to me that they would be receiving the Registrant email on Resends.
Sorry to waste your time. Thank you for testing.
|
|
Lorenzo Orlando Caum
|
November 7, 2014 at 7:48 pm
Thanks for letting us know. I had not thought of that as a possible cause.
Enjoy your weekend
—
Lorenzo
|
|
Michael
|
November 10, 2014 at 7:04 am
Lorenzo, we had to enable the Registrant email context in order to make the Resend button work. A side-effect of this is that the Primary Registrant gets multiple copies of the Event Registration email when Primary Info is used for all tickets in an order.
How can we prevent sending duplicate emails to the Primary, but still enable the Registrant context so that Resends work?
Thanks
|
|
Tony
|
November 10, 2014 at 7:12 am
Hi Michael,
Which message template is this? Registration Approved?
Can you explain the steps you are taking and how you expecting the registration to work please?
It sounds like you are approving the invoice registrations, then re-sending, is that correct?
|
|
Michael
|
November 10, 2014 at 7:26 am
Hi Tony,
We have enabled the registration questions for the Primary only, so that info is used for all other registrations in an order. Because of this, I had disabled the Registrant context, so that the Primary Registrant would only receive one email.
Last week I discovered that the Resend button uses the Registrant context–even on the Primary Registrant record: if Registrant context is disabled, by leaving To: blank, the Resend button won’t work on the Primary Registrant.
So I re-enabled the Registrant context, which allowed us to use the Resend button, but the unwanted side-effect of this is that the Primary Registrant receives multiple emails per registration (the primary and each registrant’s) at the time of registration. We would like to eliminate this duplication so that Primary only receives one Registration Approved.
The Resend Registration button is important for us, because we want to use it to send a reminder email on the day of the event to each purchaser (Primary.) However, we hope to eventually automate these reminder emails rather than manually clicking Resend for each Primary Registrant in each Event occurring Today.
|
|
Tony
|
November 10, 2014 at 7:57 am
Can you tell me the Default Registration Status both within Events -> Settings.
By default it would be Pending Payment – http://take.ms/YVtKr
This can also be changed within the Event Editor for each event.
The reason I ask is each message template has their own contexts, by default a Registration that selects Invoice, would have a registration status of Pending Payment.
The Pending Payment message type, does not allow you to enable the ‘Registrant’ context.
So do you currently have the default registration status set to Approved, or are you manually approving the invoice registrations, setting them to Approved (or possibly another status)?
|
|
Michael
|
November 10, 2014 at 8:05 am
It is set to the default, Pending Payment. This creates the following behavior: if payment is successful, Primary gets Payment Received, Registration Confirmation x number of tickets sold (one for primary, one for each ‘registrant’.) If unsuccessful, they get Registration-payment pending and Payment Declined.
We don’t allow Invoice, only paypal-credit card and paypal.
When I say I enabled the Registrant context, I mean on the Registration Confirmation message type.
|
|
Tony
|
November 10, 2014 at 1:01 pm
So I re-enabled the Registrant context, which allowed us to use the Resend button, but the unwanted side-effect of this is that the Primary Registrant receives multiple emails per registration (the primary and each registrant’s) at the time of registration. We would like to eliminate this duplication so that Primary only receives one Registration Approved.
I did some investigating into this issue and realised that is not the expected behaviour.
When you collect only Primary Registrant information, and select multiple tickets, only a Single registration Approved email should be sent as EE identifies that the registration is a single user using the same details.
When testing this, are you using the same email address to register with that is registered as the EVENT_AUTHOR? This would be the email address of the user account that created the event.
How many emails are you receiving?
The Primary registrant context does seem to fail when used in the way you have described, I have added a ticket for some developer feedback on this.
|
|
Michael
|
November 10, 2014 at 1:30 pm
OK, I see the problem. It’s my fault again. The Registrant context email should be sent To: [recipient_email]. I’m sure that was the default but I lost the default setting when I changed things. [recipient_email] will work when Resending registration to the Primary Registrant.
Only if Registrant context is set To: [Primary-reg-email], then the Primary will receive duplicates. If Registrant is set to [recipient_email], then the system will hold duplicates as you said.
So this all works as expected. The ticket you created might backfire on me, because a side effect of this ‘failure’ is that in my use case I am essentially gaining a message type: Since Registrant context is sent on Resends, I can now customize the Registrant context to read as a Reminder. This is what we use Resend for! So now my Event Registration Primary email can include ticket information, and my Event Registration Registrant email can be customized to read as a Reminder email, AND it will send to the Primary on Resends. This is ideal for us, though I realize this thread might result in a change to this behavior.
We might hire a developer to program an automation of these reminder emails, but I will also mention this here as a feature request. Thanks for reading and testing.
|
|
Tony
|
November 11, 2014 at 2:11 pm
Hi Michael,
I have been discussing this with our developers and found that this is actually by design, to quote the developer:
the ‘Resend’ feature only uses the registrant context because it specifically uses registration ID’s for generating the messages (which is what the registrant context emails are for).
So if each registration resends based on the single registrant context for that specific registration, each of those registrations, does not have a PRIMARY_REGISTRANT_EMAIL.
So for the time being this will remain as is although we have added a ticket to add some documentation to help explain this, and possibly include another ‘Resend’ button to be used specifically for the Primary Registrant. These are currently feature request for a future version of Event Espresso and will be discussed further internally.
I’m glad you are now back up and running and all is working as expected, if you have any further questions just let us know.
|
|
Michael
|
November 11, 2014 at 3:14 pm
Hi Tony, thanks for clearing that up.
One last thing before you close this thread: Clicking Resend re-loads the Registrations page. Is it possible to change this behavior so that the user remains on the current page? This would allow us to click Resend on multiple users from the same screen. Instead, as it is now, we must locate the Registrant, click Resend, then locate the next Registrant.
This is the behavior from both the EE-Event-Registrations and the EE-Registrations-sort-list-by-date view. In both cases, pressing Resend redirects to EE-Registrations-unsorted.
It would be best if we could go to the Event-Registrations view, and click on each Primary Registrant Resend button without navigating back to Event-Registrations each time.
Just trying to be clear. Thanks
|
|
Tony
|
November 12, 2014 at 4:48 am
We have an open ticket to make the tables contextual and do as you are describing, but currently it has not been implemented, I will add your vote to that ticket.
However, just to check, is this when using the Resend Registration icon under actions which then reset the filters? For example – http://take.ms/X5hhu
If so I can suggest a work around for the time being, rather than using that icon click on the registrant, hit the ‘Resend Registration’ button and use the browsers back button. That will bring you back to your filtered list.
It sounds like you are doing this already and I agree it could be useful to add the Resend Registration option within the Bulk options, allowing you to select multiple registrations with the ticket boxes, then select that option.
I’ll create a feature request ticket for this, however I can’t comment on if or when that will be included currently.
|
|
Tony
|
November 12, 2014 at 5:05 am
Hi Michael,
I realised this can be done currently, although it is not obvious.
If you select the registrations you want to resend the registration to within the list using the checkbox, like this – http://take.ms/TgLhv
Then within the ‘Bulk Options’ you can select the current registration status and notify, so if the registrations are approved, select ‘Approve and Notify Registrations’ then click apply – http://take.ms/16C36
What that will do is go through each of the selected Registrations, set the status to approved and send the Registration Approved message.
One thing to note is this work around does set the registration status before sending, so when using this you want to only select registrations with the same status. For example if you select 1 Approved & 1 Pending Payment registration and use this (expecting 1 to receive Reg Approved and the other Pending payment), both of those registrations will then be approved and both will receive the Reg Approved message.
Does that make sense?
It is still a work around and so I have left the ticket created above open for discussion, but hopefully it should help with your use case.
|
|
Michael
|
November 12, 2014 at 7:08 am
Tony, this is great. Thanks a lot for your thoroughness and help in thinking this through! You wouldn’t believe how much better our workflow is now that we’re using EE.
|
|
Josh
|
November 12, 2014 at 6:44 pm
Hi Michael,
We appreciate your comment about how EE has improved your workflow. Thanks.
|
