|
Kyle Rollins
|
December 22, 2014 at 2:12 pm
Hello 😀
I am looking for help to send a payee (vs a registrant) the transaction details in an email. I’m trying to think of a clever way to do this with the existing infrastructure so I can go live quickly. Its a last minute snag the client sees as essential because they are leaving EventBrite for EE4 and they cannot imagine their attendees getting payment info because of the way they run corporate events.
Basically – the person booking the events is an admin person booking events for staff. The office / admin person is the payee (and will never attend) and they will register 10 or more people for one event. The new multiple registrations feature is amazing for this except for one piece…the first / primary registrant is treated as the payee.
We are using paypal pro, so when we get to the 2nd step / payment page, the office admin person changes the details carried fwd from the primary registrant to their details, submits and voila – payment goes thru.
While I’d love to see a box which says something like ‘If the payee is NOT an attendee tick this box and enter payee details:’ I think there is a quick alternative – create a shortcode for payee email and any other related details.
I have looked thru the shortcodes for such a payee related shortcode, but all I can find is primary registrant shortcodes. If I had shortcodes for the details captured in the step 2 / payment confirmation page, I could insert those into the existing emails which are going to the primary registrant and I’d be sorted… Any thoughts? Am I missing something??
Has anyone else had a similar issue and found a solution or suitable workaround?
Thanks,
Kyle
|
|
Sidney Harrell
|
December 29, 2014 at 10:46 am
It’s not a quick, last minute fix, but both the Single Page Check-Out module and the gateway system have been rewritten in the upstream 4.6 branch. So it’s something to take into consideration before digging to deeply into the current version. The SPCO was rewritten to be more modular in it’s composition, to allow the registration steps to be reordered, for example. And the gateway system was a major rewrite to allow things like partial payments, having gateways as add-ons, etc.
For a quick and dirty solution to your current problem, though, I would do it in jQuery. Write a little script to check for the right html, and on a hit insert your html for the button or checkbox you want, with a listener on it, so that when it’s clicked it wipes out the pre-populated values from the CC form.
|
|
Kyle Rollins
|
January 13, 2015 at 9:30 pm
OK – does anyone else have this issue? It seems to be quite a regular need. In my research I have seen old posts referring to this issue and am wondering if I’m alone or if anyone has tackled this…
|
|
Lorenzo Orlando Caum
|
January 15, 2015 at 10:42 am
Hi Kyle, I asked a team member to follow up with you on this. You should receive an email soon.
Thanks
—
Lorenzo
|
