- This topic has 11 replies, 3 voices, and was last updated 11 years, 7 months ago by
.
-
Posts
-
Hello!
I love this plugin. I’ve hacked out most of the signup fields as they were not necessary for our site, but one thing that would be extremely useful is to be able to have a time stamp when a person signed up for an event.
For gaming sites this is useful because first come first serve is usually how it goes. It seems the #_ID is constant and does not change for each event. If I had an #_EVENTID to say this person signed up first, second, third… that would work too.
Any help is much appreciated.
Hmmm … it’s not that simple: the attendees list shows the persons who subscribed, but one person can subscribe more than once … And subscriptions can be changed by an admin later on as well …
Indeed. If it was simple I probably could have figured it out, but I looked at the code and said this is beyond me 🙂 I appreciate the information and any workaround would be good too. I really like everything about the plug-in and this is the only feature that I am missing currently, but honestly not such a huge deal.
I will use seat limits and set up another event that holds overflow. Even then it is difficult because I cannot see order or date/time, but will work for our requirements.
Thanks again.
Well, in the trunk version I’ve added code so every booking has a date/time there. Using that date/time in the attendees list is more complicated (because of the more-than-one issue), but a real booking table can be created: a new shortcode etc … but I guess the backend is sufficient there if I just add the date of the booking to it.
is it possible in new version to add it in “Attendees list format” field?
Done in trunk: “the creation and modif date can now be shown for the bookings list (when using #_BOOKINGS) via 2 new placeholders: #_BOOKINGCREATIONDATE and #_BOOKINGMODIFDATE”
Hi Franky,
thank you, great news for me, still 2 requests:
editable date format for #_BOOKINGCREATIONDATE (i searched in options but i didn’t figure how to)?
Both date and time, for example 22/04/2013 – h. 13:00:49 are possible or will be in near future?
doing some test i noticed that if i use #_BOOKINGS something goes wrong. For the same event i have 25 attendees in list when in #_ATTENDEES, in #_BOOKINGS the respname are 27 with some duplicate…
Some chance to have subscription date and time working in #_ATTENDEES ?
The same person can book more than once, that’s the difference in attendees and bookings. So you’ll never have the subscription date in #_ATTENDEES, only in #_BOOKINGS
done, thank you Franky
- The forum ‘Bug fixed or feature request implemented’ is closed to new topics and replies.