Backend add Booking

[Anonymous]

Hi Franky,

would it be possible when an admin creates a booking for a person manually to have the choice to pick a person that already exists?

Maybe a way to achieve it would be from the page /admin.php?page=eme-people where from the drop down field the admin could choose an action to make a booking for a person.

Another way could be if you click on the persons reservations you are redirected to the page /admin.php?page=eme-registration-seats&search=8 (I think 8 is the specific person I was looking at) on that page the booking option is already there so you simply could chose the new event and click on add booking while having the person checked below to copy the persons details.

Well these are just the ways where I can see such a dialog being happen, but of course the functionality or feasibility is different 🙂 and you have to say if it is possible…

Cheers and thanks for considering!

JK

[Franky]

Although the “moving” feature request is probably not going to happen, this one is interesting.
I could add an autocomplete feature (like for chosing a location when creating an event), which would add a person ID to the POST.
To make it secure: no autocomplete in the frontend, and ignore the person ID when not doing a booking via the backend.

[Anonymous]

Hi Franky,

any kind of help would be appreciated 🙂

But I fear it may be only limited to the very few items that you store along with a person and not the entries (formfields) that the person has filled out once for the event of the series right?

Cheers
JK

[Franky]

indeed 🙂
But it is done, along with security improvements 🙂
Autocomplete is based on the name.

[Anonymous]

Is there a way to enhance the information to include the postal address or even more?

[Franky]

The next version will have:
– last name
– first name
– address1
– address2
– city
– state
– zip
– country
info per person, with corresponding placeholders in the forms: #_LASTNAME, #_FIRSTNAME, …

[Anonymous]

Hi Franky,

these are awesome news, with that you have a full set of information, phone and email will stay as well right?

Excellent!

Thanks again for a mind-blowing plugin!
Cheers
JK

[Franky]

Yes of course, email and phone info stay as well.
If you are interested in testing it, feel free to download the trunk already.

[Anonymous]

Hello Franky!

I do have the trunk in place now on my development site. And I like to update my forms to reflect the new options. As you mentioned you have now implemented the new placeholders, do you already had the time to update the documentation reflecting the new placeholders?

[Anonymous]

#_NAME is now #_LASTNAME right?

Does #_RESPNAME equals #_NAME?

Maybe it is an idea to have a placeholder that is combining first and last name? So #_NAME or #_RESPNAME would reflect this? Which would also be handy for those who do have a lot of user and forms in place and don’t want to work and update the users and forms?

Maybe it can be conditional? If #_FIRSTNAME / #_LASTNAME is not empty and #_NAME (#_RESPNAME) is empty then auto populate the #_FIRSTNAME & #_LASTNAME to it?

[Franky]

The doc will be updated once the version is released, otherwise people with the current version will have wrong info. For now it us only in the changelog.
For backwards compatibility (wordpress allows first and last name to be empty in a profile ), #_NAME equals #_LASTNAME. People not updating the forms don’t need to change anything, it should all still work.
#_RESPLASTNAME and such are for the rsvp mails and booking placeholders, #_ATTENDLASTNAME and such for attendance placeholders.

[Author]

Posts