- This topic has 2 replies, 2 voices, and was last updated 5 years, 6 months ago by .
Viewing 3 posts - 1 through 3 (of 3 total)
Viewing 3 posts - 1 through 3 (of 3 total)
- The forum ‘Generic’ is closed to new topics and replies.
Events Made Easy › Forums › Generic › BOOKINGFIELD{creation_date} versus BOOKINGFIELD{modif_date}
Hi I’m using [eme_if tag="#ESC_BOOKINGFIELD{creation_date}" value="#ESC_BOOKINGFIELD{modif_date}"] to customise the response in the case if a booker wants to register an “only participating” event.
In the case that a booker already registered before, this works fine
But in the case it’s a new booker, it can happen that the creation_date is different from the modif_date with 1 second. And then he’s considered to have booked already
Settings :
Allow only 1 booking per person (combo email/lastname/firstname) : yes
Only take attendance (0 or 1 seat) for this event : yes
Max number of seats to book : 1
Min number of seats to book : 0
What can i do as workaround for this problem ?
Thanx in advance
Those placeholders only relate to the current made booking, not a previous one. I can’t see any way those will help you decide if someone already registered.
You have the conditional #_IS_REGISTERED (works if the user is logged in) and the #_ADDBOOKINGFORM_IF_NOT_REGISTERED.
To change the return text if you don’t require people to be logged in, you currently would need to use the eme hooks.
Implemented a filter. It works
Thx