Support

Home Forums Event Espresso Premium EE4 ticket logic PHP jquery

EE4 ticket logic PHP jquery

Posted: October 10, 2024 at 6:29 pm

Viewing 6 reply threads


calthoracic

October 10, 2024 at 6:29 pm

Hello,

I’ve looked but only found that ticket logic is not support/implemented. e.g. If I have 4 tickets each with limit quantity of 1 and when one is selected (qty = 1), all others (or optionally a selection of tickets) are disabled or hidden. Then if the visible one is unselected (qty = 0) all others are then enabled or visible. Can this be done with jquery or some other method?

Best,
Walt


Tony

  • Support Staff

October 10, 2024 at 6:39 pm

Hi Walt,

Yes, what you are referring to could be done with jQuery but it’s not something we have available so would need custom code.

However, as you are using a Qty of 1 on each ticket and one of your requires is for all other tickets to be disabled, you could just set the ‘Maximum number of tickets allowed per order for this event:’ within the event editor to 1.

That will change the ticket selector to show a radio button for the tickets so only 1 can be selected.

Does that work?


calthoracic

October 11, 2024 at 11:01 am

Hey Tony,

I over generalized the situation, the ‘Max number” to 1 would work; however, we have one more free ticket “Second Exhibitor Registration” (also max Qty 1) which breaks the suggested solution above.

1. Exhibitors from CTS 2024 Annual Meeting
2. NEW Exhibitor
3. Exhibitor Thursday
4. Second Exhibitor Registration (free)

Can you point me to jQuery solutions/examples, my current jQuery solutions (mostly styling) use (via wp_add_inline_script) either the ‘ticket_selector’ or ‘single_page_checkout’. I haven’t been able to find examples that use selector (Qty dropdown) change/update and what scripts to place since these trigger after the relevant pages load.

Best,
Walt


Tony

  • Support Staff

October 14, 2024 at 9:19 am

I over generalized the situation, the ‘Max number” to 1 would work; however, we have one more free ticket “Second Exhibitor Registration” (also max Qty 1) which breaks the suggested solution above.

Hmm, ok, so I wasn’t sure if you’d changed how you were running the registrations from the previous thread.

So yeah the above solution won’t work with that setup

Can you point me to jQuery solutions/examples, my current jQuery solutions (mostly styling) use (via wp_add_inline_script) either the ‘ticket_selector’ or ‘single_page_checkout’.

You’re applying styles via jQuery?

But either way, it sounds like you have examples of how to add custom JS via wp_add_inline_script using the ‘ticket_selector’ handle to ad your code specifically after the default Ticket selector JS file (which is exactly what you need to do for the above, but…

I haven’t been able to find examples that use selector (Qty dropdown) change/update and what scripts to place since these trigger after the relevant pages load.

I’m not sure I follow what you are requesting here.

Using wp_add_inline_script to add your own code when the ticket_selector script is loaded is exactly what you need to do and it sounds like you have that already, correct?

If your looking for examples of how to manipulate the ticket selector use jQuery we don’t have any official examples/solutions of doing so, there are snippets like these:

https://gist.github.com/Pebblo/aadb2c7349b5093d807974aabf60288b

This is just using standard jQuery to add a checkbox element and then on change select the ‘first’ element in the (now hidden) dropdown selector, but there’s nothing really specific about the EE elements there.

How familiar are you with using jQuery?


calthoracic

October 16, 2024 at 12:12 pm

Hello Tony,
re jQuery – I know enough to get by and stay out of trouble… thanks for the example and yes, I will review and test/implement something similar.

Previously, my on change logic did not work but now know definitively that it should exist in the ticket_selector script -> [Using wp_add_inline_script to add your own code when the ticket_selector script is loaded is exactly what you need to do and it sounds like you have that already, correct? – √ YES].

Best,
Walt


calthoracic

October 17, 2024 at 5:28 pm

Hello Tony,
Apologies for appending here but I’ve tried creating a new topic today (about 3 different time) and am not seeing it appear anywhere (i.e. Show me my support posts).

subject: Do I have to migrate Authorize.net “AIM” to Authorize.net “Accept”?

Hello,

The following message is being displayed on Event Espresso Payment Methods:
Action Required: To continue processing payments, migrate to a new payment integration soon.
The following payment integrations will be removed: PayPal Standard, PayPal Express, PayPal Smart Buttons, PayPal Pro, Braintree, Payflow Pro, Authorize.net SIM and Authorize.net AIM.

eventespresso.com/product/eea-authorizenet-accept/ page displays:
Are you currently using Event Espresso for your event registrations on your WordPress website? Event Espresso includes a payment gateway for Authorize.net AIM. Authorize.net Accept is a replacement for the Authorize.net SIM service which is being discontinued by Authorize.net.

Question:
The website EE payment methods page states that a migration is needed; however; Authorize.net Accept page states “Accept” replaces “SIM”, so do I need to replace or migrate Authorize.net “AIM”?

FAQ:
How can I set up a recurring payment, payment plan, or a subscription through Authorize.net Accept?
Recurring payments, payment plans, or subscriptions are not currently supported in the Authorize.net Accept payment gateway.

Question:
If AIM is to be migrated to Accept and I am using Automated Recurring Billing (ARB), how do i implement ARB while using Accept?

Best,
Walt

tags: EE4 Authorize.net AIM migration Accept


Tony

  • Support Staff

October 22, 2024 at 3:46 am

Hi Walt,

Seems Akismet doesn’t like you, it flags your threads as spam, had you had trouble posting on forums previously (not just here but elsewhere)?

I’ve unspammed your other posts and put them into a thread here:

https://eventespresso.com/topic/do-i-have-to-migrate-authorize-net-aim-to-authorize-net-accept/

As to not cause further confusion we’ll keep the replies regarding Auth.net AIM/Accept in that thread.

In terms of the issue relating to the ticket logic, do you need anything further here?

Viewing 6 reply threads

You must be logged in to reply to this support post. Sign In or Register for an Account

Event Espresso