|
mpurse
|
February 3, 2014 at 6:59 am
We often have to move attendees to different workshops and have found your tool for this to be very helpful.
However, we always send ‘reminders’ out to each attendee before the event using email templates and short code EVENT DATE.
We have noticed that attendees that were moved to a new date receive reminders with the old (original) date in the email. This is proving to be quite disastrous.
Any fix for this please?
|
|
Sidney Harrell
|
February 3, 2014 at 1:29 pm
Can you confirm that you are on the latest version of the reassignment tool, 1.1.b? I thought I put in a fix for this in the last update.
|
|
mpurse
|
February 5, 2014 at 2:43 pm
Yes, am on 1.1b.
|
|
mpurse
|
February 7, 2014 at 4:51 am
Any news on this one? It’s caused quite a bit of chaos this week as we had quite a few people move to a new course. 🙁
Thanks.
|
|
Sidney Harrell
|
February 7, 2014 at 4:42 pm
Are you using the attendee move function or the attendee clone (copy) function?
|
|
mpurse
|
February 8, 2014 at 4:44 pm
Move. Should we be cloning instead?
|
|
Sidney Harrell
|
February 10, 2014 at 11:04 am
I’ve tried reproducing the problem, and I’m not able to get it to fail. Here are the steps I took:
created 2 events with different start dates.
signed up an attendee for the first event.
moved the attendee to the second event.
sent an email / invoice reminder with the [start_date] shortcode in it.
when I look at the email, it has the start date of the second event on it.
Can you outline what steps you take to see the error? When you look at the attendee record in the admin, is the event date correct at the top where it says ‘Registered For:’?
|
|
mpurse
|
February 10, 2014 at 3:38 pm
Hi Sidney,
I just tried it and it worked fine too. Is there perhaps a known issue relating to this when customers sign up for more than one event?
I might have it narrowed down to multiple booking people only.
Thanks, M
|
|
Sidney Harrell
|
February 11, 2014 at 3:09 pm
I know it was an issue with the last version of the attendee mover. I think I added the fix for it in the version where the attendee cloner was added. It’s possible there’s an edge case where it still happens, so if you can figure out what steps it takes to reproduce it, please let us know.
|
