Release 97 delivers a range of stability improvements, feature enhancements, and important fixes across memberships, checkout flow, ticket printing, event management, and tracking. Below is an overview of the key changes included in this release.
IP Address–Based Purchase Restrictions
A new setting has been introduced to help protect against automated bot activity during high-demand sales.
This feature allows you to define how many shopping carts or orders can be created from a single IP address within a one-hour window.
Once the limit is reached, additional purchases from that IP will be blocked until the hour resets.
If the field is left blank, no restriction is applied.
Note: Enhanced IP based purchase protection applies only to online sales
Example:
- If the limit is set to 5, the system checks how many carts/orders were created from that IP between 9:00 AM and 10:00 AM when a customer tries to create a cart at 10:00 AM.
- If 5 already exist, the new cart will be blocked.
- If fewer than 5, the action will be allowed.
“Is Force Login” Enhancement for On-Sales
A new option has been introduced to support enhanced customer login requirements:
When set to “Recommended”:
- A login popup appears across the site.
- Customers may close the popup (using the ‘Skip this step’ button) and continue as guests if they wish.
When set to “Enforce”:
- A login popup appears across the site and cannot be closed.
- Customers must log in or register to continue.
Excluded pages:
Registration, Login, Reset Password, and E-Invoice (for Malaysian clients only).
When Recommended
When Enforced
Membership Lapse Handling Improvements
Previously, memberships with a null lapse date caused an issue where the “Renew Now” button did not correctly switch to “Buy Now” after expiry.
This release resolves the issue so no manual data adjustments will be required going forward.
Status Update Fix for Archived Events
When events were marked as Archived, the operator name and modified date were not updating.
This has now been corrected so the system accurately reflects who performed the action and when.
StripePay Flickering Issue Resolved
Stripe recommended technical updates to address flickering within the payment section when the payment amount changed (e.g., applying/removing vouchers, promo codes, or modifying tickets).
With this release:
- The payment area will grey out during recalculation rather than disappearing and reloading.
- This improves stability and gives users clearer feedback while prices update.
Pixel Tracking Fix for Masked URLs
Pixel tracking was not functioning correctly when using masked URLs.
This update resolves the issue and includes improvements to event-level pixel tracking.
Printed Ticket – General Order Note Fix
Printed tickets were incorrectly showing a placeholder tag when no General.OrderNote was present.
This has now been corrected, and tickets will only display the field when an actual note exists.