Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Checking ticket options | Event Espresso - Staging Server
Hi, I have a multi-event setup, where one of these events has 2 ticket options (say A and B).
The event allows a group registration with max=2.
At the moment, it would be possible to buy 2xA and 0xB (or the other way around).
The goal is to allow only 1xA and 1xB.
I know this is not officially supported in the current version (I use 3.1.36.1.P).
However, I reckon it shouldn’t be that much difficult to hack this in. Would it be possible with some javascript added?
Could you please point me at the right files to look at and possibly give me a tip on how to achieve this?
I would put the script in the shopping_cart.php template, so you can copy it to uploads/espresso/templates and save your modification from getting overwritten on update.
You should be able to put in some jQuery to put a listener on select.price_id so that when it is changed, you can go up to the table.price_list parent, and change all of the children select.price_id to match the one that was changed. Almost like the first example here: http://api.jquery.com/change/ but with a little modification.
The support post ‘Checking ticket options’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.