You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes there's a need to limit the number of tickets per transaction.
It would be ideal if Camptix allowed for a "maximum tickets per transaction" option per ticket / reservation / coupon / event.
This may not prevent someone purchasing multiple tickets in multiple transactions, but would be useful in certain circumstances.
This could be very useful for Speaker tickets / coupons, where a generic coupon/reservation is shared with speakers, with the intention of them claiming one-per-speaker, but seeing they can claim multiple leads to additional plus ones.
Other events may be special, and intended on every attendee having a singular ticket (Community Summit for example).
+1
I fully support the addition of this option. In our event we have encountered this problem, and although thanks to @dd32 we have solved it with CSS, it is not an elegant or easy option for non-programmers.
just scanning the code, I imagine there is edge cases to consider (such as the camptix_max_tickets_per_order_after_coupon_bypass filter), but does seems like a good idea - presumably it's only ever been a filter in code due to these complexities in the code.
Sometimes there's a need to limit the number of tickets per transaction.
It would be ideal if Camptix allowed for a "maximum tickets per transaction" option per ticket / reservation / coupon / event.
This may not prevent someone purchasing multiple tickets in multiple transactions, but would be useful in certain circumstances.
This could be very useful for Speaker tickets / coupons, where a generic coupon/reservation is shared with speakers, with the intention of them claiming one-per-speaker, but seeing they can claim multiple leads to additional plus ones.
Other events may be special, and intended on every attendee having a singular ticket (Community Summit for example).
This came up on Slack today:
https://wordpress.slack.com/archives/C08M59V3P/p1724266664412339
It turns out we have some code to do this, to limit it to 1 per transaction for specific sites:
wordcamp.org/public_html/wp-content/mu-plugins/camptix-tweaks/camptix-tweaks.php
Lines 997 to 1015 in dfe9fe7
See also; #740 and #1305
The text was updated successfully, but these errors were encountered: