Hindi Language Support
ManageMyTrust now supports हिन्दी as a third language, alongside English and French.
- Users can switch to Hindi using the language switcher — now live in production.
- Form labels, validation messages, help text, choice options, and key UI strings across donors, blog, email templates, and organisation settings are all available in Hindi.
Customise Your Ticket Terms & Conditions Heading
Event organisers can now set a custom heading for the Terms & Conditions section that appears on tickets. Previously this always read "Terms & Conditions". You can now change it to whatever is appropriate for your event — for example, "Participation Guidelines" or "Event Rules".
Add a Personal Message to Confirmation Emails
Each event can now carry an additional text block that is appended to every registration confirmation email sent to attendees. Use this to add a personal welcome note, event-specific instructions, or anything else you want every registrant to see after they sign up.
Sold Out Badge on Ticket Types
When a ticket type reaches capacity, it now shows a clear "Sold Out" badge on the event detail page. Attendees can immediately see which ticket types are no longer available without having to attempt checkout.
Make Address Collection Mandatory
Organisers who have enabled address collection at checkout can now make it mandatory. When the mandatory flag is on, attendees cannot complete registration without filling in their address — useful when address data is required for compliance or donation attribution.
Make PAN Card Number Mandatory
Similarly, organisers who collect PAN card details can now make the PAN card number field mandatory at checkout. The PAN card file upload remains optional — only the number is enforced. This is useful for events where donor identification under Indian tax law is required.
Date Fields Can Now Restrict Past or Future Dates
Date-type registration fields can now be configured with a date constraint:
- Past only — attendees can only enter a date in the past (useful for dates of birth, previous events attended, etc.)
- Future only — attendees can only enter a future date (useful for follow-up appointment dates, etc.)
- No restriction — the field accepts any date, as before
The constraint is enforced both on the form itself and on the server, so it cannot be bypassed.
Attendee Address Data in CSV Export
When you export event orders to CSV, the attendee's address fields are now included as columns. This makes it easier to use the export for reporting, compliance, or mailing purposes without needing to look up individual registrations.
Fixes
Ticket lookup and OTP redirecting to home page on Event Spotlight pages
If your subsite uses the Event Spotlight section (pinning a single event to a page) rather than the standard events listing, attendees who went through the ticket lookup or OTP verification flow were being redirected to the home page instead of back to the event. This is now fixed — the flow stays on the correct event page throughout.
Multi-select registration fields now display correctly
Checkbox-style (multi-select) registration fields were invisible on the Step 2 checkout form due to a styling issue. They now render correctly with proper checkbox layout and your organisation's theme colours.
Mandatory checkbox fields now enforced correctly
Checkbox registration fields marked as required were not actually being enforced — attendees could leave them unticked and still proceed. This is now fixed.
Attendee ticket PDFs now correctly gated on payment
Attendees for group bookings could previously download their ticket PDF before payment was confirmed. The payment status check now works correctly for all registration types, including those part of a group order.