• Resolved strika

    (@strika)


    Hello,
    i just want to create a multiple-seat booking form and wanna use the dynamic field option for a form with multiple persons fields.
    i know its possible with normal seats. There i can use the “#_seats” value but is there a value for multipleseats too?

    i tryed to add the categories in the field but this does not work like “#_SEATS{1}+#_SEATS{2}”
    So my questition is: Is there a value which counts the seats for multiple-seats?

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Author Franky

    (@liedekef)

    You can use #_SEATS{1} as a condition, or #_SEATS{2}.
    By default the condition fields are only allowed for fields you use in the booking form. If you want the form to react on both #_SEATS{1} and #_SEATS{2} while you want your condition to be on #_SEATS, you should activate the option “Dynamic data check on every field”

    Thread Starter strika

    (@strika)

    In my booking form i have both #_SEATS{1} and #_SEATS{2} but no #_SEATS.
    i know i could do add another field #_SEATS where the user have to choose the number of tickets but this doesnt help when i cannot compare the sum of #_SEATS{1} and #_SEATS{2} with #_SEATS.

    When i now aktivate “Dynamic data check on every field” and chose “#_SEATS” as my field for dynamic-field this not work. This will not add the template with additional fields.

    Do “#_SEATS” really sum the inputs of #_SEATS{1} and #_SEATS{2}?

    • This reply was modified 4 years, 6 months ago by strika.
    Plugin Author Franky

    (@liedekef)

    Hum … I’ll check on #_SEATS for multiseat bookings, but for your conditions: you can define 2 conditions: one for #_SEATS{1} and an identical one for #_SEATS{2}. Does that not solve the issue?

    Thread Starter strika

    (@strika)

    hm.. yes i had the same idea, but when i create 2 conditions one for #_SEATS{1} and the other for #_SEATS{2} than i have a problem with the emailadress. Where do i go with it? Because i cannot put the emailadress inside the template (error message pops up). I know i could setup the condition so good that there would not be a case for a person can buy a ticket without emailadress, but the tool think maybe there is. Do you know what i mean?

    Thats the reason why i have always at the beginning of my booking form one field for lastname, firstname and the emailadress.

    • This reply was modified 4 years, 6 months ago by strika.
    Plugin Author Franky

    (@liedekef)

    #_SEATS works as expected, however in the dynamic conditions check there’s a logic error preventing it from working there (I check if a person is linked to the booking before replacing placeholders, but during the dynamic data condition check I create a “fake” booking but no person is linked to it, so it failed there 🙂 )
    The next version will have this corrected.

    • This reply was modified 4 years, 6 months ago by Franky.
    Thread Starter strika

    (@strika)

    so i have to wait for the fix? or is there anything else i could do?

    Plugin Author Franky

    (@liedekef)

    You could download the dev-version if you want to continue quickly, otherwise you’ll have to wait for the next version.

    Thread Starter strika

    (@strika)

    do you know when the next version comes?

    and in the new version i have to use the “#_SEATS” for my condition?

    • This reply was modified 4 years, 6 months ago by strika.
    Plugin Author Franky

    (@liedekef)

    The answer to the big “when” question is the same as for all open source projects: when it is ready, it will be released 🙂
    You don’t *have* to use #_SEATS, but you’ll be able to. You can still use #_SEATS{1} and #_SEATS{2} .
    Concerning your text about “emailaddress”: I don’t understand at all what you mean there. The email address is a required field and can not be a dynamically added field, so you should always use #_EMAIL. Maybe you should explain your use-case here?

    Thread Starter strika

    (@strika)

    okay i will try to explain what i need and which fields i use:

    this are the fields i use in my main booking form:
    – #_FIELD{Ticketanzahl}
    – #_seat{1}, #_seat{2}
    – #REQ_FIRSTNAME
    – #REQ_LASTNAME
    – #REQ_EMAIL
    – #REQ_ADDRESS1
    – #REQ_ZIP
    – #REQ_STATE
    – #REQ_FIELD{ermäßigt}[radio button] (i tryed to use the EME discount option but this doesnt worked for me. so i use this workaround and set up a new field where i reduce the price by 2 €, but this is another Problem. I looked for more information how to use it in the documentation but cannot find the right one to fix the problem.)
    – #_DYNAMICDATA
    – #_DYNAMICPRICE
    – #_FIELD{Stornierungsbedingungen}
    – #_RECAPTCHA
    – #_SUBMIT

    my second template form i wanna use for the case that a person wanna buy 2 or more tickets:
    – #REQ_FIELD{P2_LASTNAME}
    – #REQ_FIELD{P2_FIRSTNAME}
    – #REQ_FIELD{P2_MAIL}
    – #REQ_FIELD{P2_Straße}
    – #REQ_FIELD{P2_Postleitzahl}
    – #REQ_FIELD{P2_Stadt}
    – #REQ_FIELD{ermäßigt}[radio button]

    What do i need: The trigger i have to use, should be the sum of #_seat{1} and #_seat{2}.

    Example: a person choose 1x category 1, 1x category 2. The person wanna buy 2 tickets at the end. For him/her and one other person.
    The form should show me 1x the mail booking form + 1x the second template inside.

    When i use 2 conditions: this does not work correctly because the dynamic-field doesnt know the value of the other cathegory so there are some cases where i dont get the right number of the second template.

    This is why i create anoher field called “Ticketanzahl” (#_FIELD{Ticketanzahl}) where the User have manually choose how much tickets he wanna to buy at all. BUT There are some fail cases where user can buy tickets without giving me all names of the persons.

    Another idea was to remove the first person details like (name,adresse,email,…) at the main booking form but this is not allowed.

    • This reply was modified 4 years, 6 months ago by strika.
    • This reply was modified 4 years, 6 months ago by strika.
    Plugin Author Franky

    (@liedekef)

    Ok, in that case #_SEATS is indeed a value you could check for, but then you’ll need to wait for the next release or use the development version.

    Thread Starter strika

    (@strika)

    Hey Franky,
    the fix with #_SEATS works really well. thank you!!

    1. now im haveing some issues with the discount. and the multiprice multiseat event.
    What i need would be something like this:
    Seats 200||100
    Price 20||15|||20||15
    means 2 price categorys for seats of 200 and 2 price categorys for seats of 100.
    i know i could create 2 events and this would work but the customer have to book 2 times than when he wanna buy 2 tickes 1 of each seat category. Thats not so user-friendly.

    2. I tryed to customize the discount (code) with your function my_eme_discount_function($booking) php example. That works really well and i asked me what kind of variables i could use inside the “$booking”. And is there a variable to get the value of each category of #_SEATS{1} and #_SEATS{2} [#_SEATS{xx}].

    3. Is it possible to show in the booking form the correct totalprice (total – discount)? actually im using #_DYNAMICPRICE. i just can see the correct total price after the submit when the payment page loads and i can select paypal but not inside the booking form.

    4. function my_eme_discount_function($booking) is just triggered when discount is used right? so is there another function i could override and add some logigs which is triggered by submit button or earlyer when the user do changes in the bookingform.
    The idea was to do some calculations an fill some hidden fields in the background. This wouldnt be necessary when 1. would work.

    You do really great work with this plugin. EME is really powerfull and you can do many thinks and i love it to customize alot and this works well. i know its hard to do some good documentation but sometimes i would like to get some more informations of it.

    Just a question to the doku:
    do im right that the documentation isnt correct here (https://www.e-dynamics.be/wordpress/registration-form-formatting/):
    #_SEATS{xx} (**)
    the ** mean this can only be used in the “list entry” template right? but its not possible for me. Just works fine for me in the header (footer not tested).

    Plugin Author Franky

    (@liedekef)

    Please open a new thread for questions unrelated to the initial question/subject of the thread.

Viewing 13 replies - 1 through 13 (of 13 total)

The topic ‘dynamic field value for multiple seats’ is closed to new replies.