Resending a massive message now takes you straight to the editor of the newly duplicated message. 📧

Previously, choosing Resend on a massive message could leave you on a broken or unexpected page because the duplicated message's ID wasn't being passed to the editor. You had to go back to the list and hunt for the copy before you could tweak recipients, subject, or content.

Why it matters: resending a campaign is now a single, uninterrupted flow — click resend, land in the editor, adjust, and send. No backtracking, no guessing which copy is the right one, and less risk of editing (or sending) the wrong message. ✅

• Resend now redirects correctly to the edit page of the cloned massive message
• The duplicated message is reliably identified, so no more dead-end redirects
• Faster follow-up sends for reminders, re-invitations, and campaign repeats 🚀

Attempting to delete the last remaining session of an activity now returns a clear, readable validation message instead of failing with a server error. 🎯

Previously, this action triggered a 500 error, leaving organizers with no explanation of what went wrong or why the session couldn't be removed. Now the platform responds with a proper 422 validation response and a human-readable message explaining that an activity must keep at least one session. ✅

Why it matters: organizers no longer hit a dead end when managing sessions — they immediately understand the rule and can adjust their agenda without contacting support or retrying the same failing action. ⏱️

• Deleting the last session of an activity now returns a proper validation error (422) instead of a server error 🚫
• The error message is displayed on the activity itself, so it renders correctly in the interface 💬
• Session management via the API behaves consistently and predictably 🔗

Opening an attendee type that no longer exists — because it was archived, belongs to another event, or the link was outdated — now takes you straight back to the attendee types list with a clear "not found" message instead of showing a server error page. 🎯

Previously, these links crashed the page, leaving you stuck with no explanation and no way forward except hitting the back button. Now the system handles the situation gracefully, so bookmarked or shared links to removed attendee types never interrupt your workflow. ✅

• Editing a missing, archived, or cross-event attendee type now redirects to the index page with a friendly not-found notice
• Viewing groups for a missing attendee type follows the same safe behavior
• Eliminates unexpected 500 errors caused by outdated or invalid attendee type links 🚀

Your event logo now renders reliably on attendee networking agendas. 🖼️ Previously, the logo could fail to load on the networking agenda page, leaving attendees with a broken image instead of your branding.

Why it matters: the networking agenda is one of the most-viewed pages during an event — attendees check it repeatedly to see who they're meeting and when. A broken logo undercuts your brand at exactly the moment attendees are paying closest attention. ✨

• Fixed the logo image on attendee networking agendas so it resolves the correct CDN URL before rendering
• Aligned the networking agenda template with the exhibitor agenda template for consistent, predictable branding across both views
• No configuration needed — existing events pick up the fix automatically 🎉

Searching for companies, contacts, or locations while assigning meeting locations now works reliably, even when names contain apostrophes or other special characters. 🔍

Previously, a company like "O'Brien Consulting" or a contact named "D'Angelo" would break the underlying search query and return a server error instead of results — forcing organizers to guess or scroll manually through long lists.

Why it matters: Business conference organizers assigning meeting locations can now trust search to just work, with no dead ends or error pages in the middle of scheduling. ✅

• Company, contact name, and location filters in the location-assign search now handle apostrophes and special characters correctly
• Eliminated the 500 error that appeared when searching for names with quotes
• Search inputs are now safely bound, making the query more robust and secure 🔒

Updating an exhibitor attendee that no longer exists now shows a clear "not found" message instead of crashing with a server error. 🙌

Previously, if an attendee had been deleted, archived, or belonged to a different event, saving changes from the exhibitor area would hit an unexpected error page — leaving exhibitors stuck with no explanation and no way forward.

Why it matters: exhibitors get an immediate, understandable message and can continue working right away, instead of losing their place and reaching out to support to figure out what went wrong. ✅

• Attendee updates now gracefully handle deleted, archived, or out-of-event records
• Users are redirected with a friendly not-found alert instead of seeing a 500 error
• Fewer dead ends and support tickets during busy event days 🎯

Keyword search inside mail lists now returns results reliably instead of failing with a server error. 🔍

Previously, search terms weren't being passed correctly to the database query, which left the keyword placeholder unresolved in the underlying full-text search and caused the request to fail outright. Any attempt to filter a mail list by keyword ended in a 500 error, forcing you to scroll through contacts manually.

Why it matters: finding the right recipients in large mail lists is often the first step before sending a campaign — this fix removes a hard blocker and saves you from manually combing through thousands of records. 📬

• Mail list keyword search now correctly binds search terms to the query
• No more server errors when filtering contacts by keyword
• Search behavior is covered by additional automated tests to prevent regressions ✅

Editing an attendee record that no longer exists — or that belongs to a different event — now returns a clean, predictable permission response instead of an unexpected server error. 🛠️

Why it matters: Stale browser tabs, bookmarked links, and duplicated event workflows are everyday realities for busy organizers. Instead of hitting a confusing error page, your team now gets a clear signal and can keep working without interrupting registration management. ✅

• Access is now validated before the attendee record is read, preventing crashes on missing or cross-event attendee IDs 🔒
• Attempts to update an attendee that isn't available in the current event context return a proper access-denied response 🚫
• Added automated test coverage to keep this behavior stable in future releases 🧪

Every Wompi payment status is now confirmed directly with Wompi rather than trusted from the incoming notification. Eventtia takes only the transaction ID from the notification, then reads the authoritative status from Wompi before updating the payment record.

Why it matters: a forged or tampered notification can no longer mark an order as paid, so your registration and ticket revenue is protected from fraudulent approvals — and the payment statuses you see in Eventtia always match what Wompi actually processed. 🔒

• Payment status is read directly from Wompi as the single source of truth
• Reference, amount and currency reported by Wompi are checked against the stored payment before any update is applied
• Transactions that can't be verified are no longer approved
• No configuration changes required — the safer verification applies automatically to all Wompi payments

Bulk emails with recipient conditions now keep delivering even when one recipient record fails, so a single problematic contact can no longer interrupt an entire send.

Previously, an error on one guest, list member, or exhibitor could abort the whole delivery, leaving part of your audience without the message and no clear indication of what went wrong. Each recipient is now processed independently, so the rest of your campaign goes out as planned. 📬

• Recipient failures are now isolated in the guests, contact list, and exhibitors sends, the same way they already were for attendees
• Corrected an inverted failure counter in the exhibitors send, so delivery reports now show accurate sent and failed totals
• Delivery errors are now recorded so our team can spot and resolve issues faster

Why it matters: Your communications reach the maximum possible audience on the first attempt, and the numbers you see in your delivery summary reflect what actually happened.

Attendee birthdates and event dates now display and save correctly, so the information you see in attendee records matches what was actually submitted.

Date handling issues could previously cause birthdates to be stored or shown incorrectly and event dates to appear in an inconsistent format, which made attendee data harder to trust when filtering, exporting, or reporting.

• Corrected the birthdate field on attendee records so values are captured and displayed as entered
• Standardized event date formatting for consistent presentation across attendee data

Why it matters: Clean, reliable date data means fewer manual corrections, more accurate segmentation by age or event timing, and exports you can hand off with confidence. 📅

We fixed an issue in our reCAPTCHA verification service that could cause validation requests to fail unexpectedly, occasionally blocking legitimate attendees from completing a registration or contact form.

Why it matters: reCAPTCHA is the first line of defense against bot submissions and junk registrations. When verification fails, you either lose real registrations or let spam through — both cost you time cleaning up your attendee list. This fix makes sure the check runs correctly every time, so your forms stay open to real people and closed to bots. 🛡️

• Corrected how verification requests are sent to Google's reCAPTCHA service
• Improved handling of the verification response so form submissions are validated consistently
• No action required on your end — the fix applies automatically to all forms already using reCAPTCHA

Action required if you have integrations reading attendee data. The API v2 attendee endpoints now require a valid user token. Calls made without one will no longer return data.

Attendee information retrieved through the API is now accessible only with a valid user token, closing a gap that could expose participant data to unauthenticated requests.

Why it matters: attendee records contain personal details such as names, emails, and registration data. Enforcing authentication ensures only authorized integrations can read them, helping you stay aligned with your organization's privacy and data-protection commitments. 🔒

For your developers:

• The API v2 attendees list endpoint now requires a valid user token
• The API v2 attendees search-by endpoint now requires a valid user token
• Requests without valid credentials are rejected instead of returning attendee data

If you run scripts or integrations against these endpoints, update them to send a valid user token before this release reaches your events.

Event descriptions in listings and template previews now render as clean plain text instead of exposing raw HTML tags.

Previously, descriptions written with rich text formatting could leak markup such as <p> or into the event item view, making listings look broken and unprofessional to attendees browsing your events. Descriptions are now properly sanitized before display.

• HTML tags no longer appear in event descriptions shown in event cards and lists
• Event template previews render descriptions correctly, matching what attendees will see
• No action required — the fix applies automatically to existing events and templates

Why it matters: your event listings stay polished and trustworthy without organizers having to strip formatting by hand. ✨

Searching for attendees to add to a session no longer fails when the session isn't restricted to specific attendee types. The attendee list now loads reliably, every time. 🎯

Why it matters: organizers building agendas often create sessions open to all attendee types. Previously, those sessions returned an error instead of a searchable attendee list, forcing you to reconfigure the session just to register someone. Now registration flows continue uninterrupted, saving time during high-pressure, on-site check-in and last-minute agenda changes.

• Fixed the error that appeared when searching attendees for a session with no attendee-type restrictions
• Those sessions now return the full list of eligible attendees

Brazilian Portuguese (pt-BR) attendee messages now read naturally, with correct grammar and gender agreement across form labels and validation errors. 🇧🇷

Why it matters: awkward or incorrect wording makes attendees hesitate at the exact moment you need them to complete registration. Accurate, native-sounding error messages tell people precisely what to fix, reducing form abandonment and support requests from your Brazilian audience.

• Corrected the translation of the Country field for attendees.
• Fixed grammatical agreement in the Country and City validation message, which now correctly reads "devem ser preenchidos" for this compound field.
• Adjusted feminine/masculine agreement in attendee field messages so wording matches each field name.
• Updated global pt-BR wording for consistency across the platform.

No action is required on your side — the improved translations apply automatically to any event or registration form displayed in Brazilian Portuguese.

Attendees can now include emoji in their survey responses without the submission failing. Previously, replies containing emoji were rejected outright, which meant lost feedback and confused respondents. 🎉

Why it matters: survey feedback is only useful if it actually reaches you. Emoji are a natural part of how people express sentiment, and blocking them silently cost you responses you never knew were missing.

• Survey answers now accept emoji, symbols, and a wider range of non-Latin scripts
• Website survey replies containing emoji save correctly instead of failing
• Existing survey answers are unaffected — no action needed on your side

Custom buttons in the email editor now render with the correct width and stay properly contained within their content box — so what you see in the editor is what your attendees receive in their inbox.

Why it matters: misaligned or stretched call-to-action buttons make campaign emails look unpolished and can hurt click-through rates. This fix removes the need to manually tweak layouts or re-send corrected communications.

• Custom buttons respect their configured width instead of overflowing or collapsing
• Button content stays correctly aligned inside its container across email templates
• Editor preview now matches the final rendered email more closely

Attendee names are no longer auto-formatted, so they appear in the attendee list and in Excel exports exactly as they were registered.

Automatic capitalization rules were altering names that don't follow standard patterns — surnames with apostrophes (O'Brien), prefixes (McDonald, van der Berg), or intentional lowercase spellings were being rewritten. Removing that formatting layer means every attendee sees their name written correctly on your lists, reports, and any downstream document built from them. ✍️

What changed:

• The attendee index now shows first and last names as originally submitted, with no automatic capitalization applied.
• Excel exports of attendees preserve the same original spelling, keeping your reports consistent with your registration data.
• Names containing apostrophes, mixed casing, or special characters are no longer modified.

No action is required on your side — existing attendee records will simply display their original values from now on.

Event descriptions in calendar invites (.ics files) no longer display raw HTML tags when opened in Apple Calendar on iPhone, iPad, or Mac. Attendees now see clean, readable event details exactly as you wrote them.

Why it matters: The calendar invite is often the last thing an attendee sees before your event starts. When it arrives full of <p> and tags, key logistics like the venue address, dress code, or join link get buried in markup — and your event looks unpolished before anyone walks in the door. 📱

What changed under the hood:

• Event descriptions are now sanitized before being written into the .ics file, stripping HTML markup while preserving the intended line breaks and paragraph spacing.
• Applies to all attendee calendar invites generated by Eventtia, so no action is required on your side — existing events benefit automatically.
• Rich text formatting entered in the event description editor is converted into plain-text equivalents that every calendar client renders correctly, not just Apple's.

When you duplicate an event, its pre-event and post-event notifications now carry over with their scheduling intact — no more rebuilding your reminder sequence from scratch on every clone.

Why it matters: teams that run recurring or multi-city events rely on cloning as their starting point. Losing notification timings meant re-entering every reminder by hand, and a missed one meant attendees never got their confirmation or follow-up. This fix removes that manual step and the risk that comes with it. 🔁

• Notification schedule dates are now correctly recalculated when an event is duplicated, staying aligned with the new event's dates
• Pre-event and post-event notifications are included in the clone instead of being dropped
• Added safeguards on the event record to prevent invalid or missing event references from breaking the duplication process

We resolved an issue with CORS (Cross-Origin Resource Sharing) handling that could cause certain requests from external domains, including embedded website builder content, to be blocked or behave unexpectedly.

Why it matters: this fix ensures that integrations, embedded widgets, and third-party origins load reliably without unexpected browser errors, saving time troubleshooting and providing a smoother experience for both organizers and attendees.

Enabling the password gate on your event website now automatically clears any active visitor session cookies, ensuring the protection takes effect immediately for everyone.

Why it matters: Previously, visitors who had already accessed your site could bypass a newly enabled password gate thanks to their existing session. This fix closes that gap, giving organizers confidence that turning on password protection instantly secures the site for all users — no manual cache clearing or waiting required.

We've resolved an issue affecting the attendee leads API response, ensuring your team gets accurate and complete lead information every time.

This fix means fewer surprises when pulling lead data through integrations or exports — helping sales and event staff follow up on the right contacts without missing a beat.

The platform now remembers your preferred language through a dedicated cookie, so you no longer need to reset it every time you log in or switch pages.

Why it matters: Multilingual teams and international users save time and avoid friction by having their chosen language persist reliably across the entire platform. Combined with a new language switcher directly in the navbar, changing languages is now a one-click action that stays applied wherever you go.

• New cookie-based language preference that persists across sessions
• Added a language switcher directly in the private navbar for quick access
• Hardened cookie handling with additional security safeguards

Events with all-free tickets now display correctly in the Google Events feed, ensuring your events appear with the right pricing information across Google's discovery surfaces.

Why it matters: Incorrect ticket price structures could prevent your free events from being properly indexed or displayed on Google, reducing visibility and attendance. This fix ensures accurate representation so potential attendees see the right information the first time.

We fixed a validation issue that could prevent notifications scheduled for after a workshop from being set up correctly.

This means organizers can now confidently schedule follow-up communications tied to workshop timing, without running into unexpected validation errors that delay attendee outreach.

Dates and times on the attendees list now display correctly according to your event's timezone, so you always see the right information at a glance.

This fix eliminates confusion caused by mismatched timestamps, helping organizers make quicker, more reliable decisions when reviewing attendee activity across different regions.

Filtering workshop sessions by day now returns the correct results, so attendees see exactly what's happening on the date they've selected.

This fix removes a source of confusion during event browsing and registration — no more missing sessions or unexpected entries when navigating multi-day workshop agendas. Attendees can plan their schedule with confidence, and organizers spend less time answering questions about session availability.

We've resolved an issue with the PayU webhook that could cause payment confirmations to be processed incorrectly.

Why it matters: attendees and organizers can now trust that PayU transactions are properly recorded in Eventtia without manual reconciliation, reducing support overhead and ensuring accurate payment tracking across your events.

Fixed an issue where certain file extensions weren't being recognized correctly during upload, causing valid files to be rejected.

Why it matters: this ensures the file types you rely on every day — from PDFs to images to spreadsheets — are accepted consistently, removing a small but annoying source of friction when preparing event materials.

Registration limits based on date and time now respect the exact moment you specify, down to the hour and minute, instead of rounding to the day.

Why it matters: If you set a registration deadline for a specific time, attendees will no longer slip through after that exact cutoff. This gives organizers precise control over when registration windows open and close, preventing last-minute sign-ups that exceed your planned capacity or schedule.

Deleting sponsor categories now works reliably, with clearer feedback and proper handling of associated sponsors.

Why it matters: cleaning up unused categories used to cause confusion when sponsors were still attached. The flow is now predictable, so organizers can keep their sponsor structure tidy without unexpected errors.

Attendees registered through a coupon that allows multiple attendees can no longer be deleted individually, preventing broken group registrations and orphaned records.

Why it matters: Deleting a single attendee from a multi-attendee coupon could leave the registration in an inconsistent state, causing confusion for organizers and billing discrepancies. This safeguard ensures group registrations stay intact and accurate.

Disabling the 'edit admin only' restriction on attendee custom fields now saves correctly. Previously, switching this setting to false was silently ignored, leaving the field locked to admin-only edits despite the change.

Why it matters: Event organizers can now reliably open custom fields for attendee editing without having to work around a setting that wouldn't stick — fewer support tickets, less confusion, and accurate form permissions from the first save.

Event assets now load consistently through the updated CDN routing, ensuring images and files appear reliably for every attendee.

Why it matters: This fix prevents broken asset links and missing media on event pages, reducing support tickets and ensuring a polished experience for your attendees from the moment they land on your event.

Cancellation emails and pre/post-event notifications now reach the right attendees at the right time, closing gaps where some messages were missed or sent incorrectly.

Why it matters: attendee communications are critical touchpoints around your event. This fix ensures cancellations are properly acknowledged and reminders land as expected, reducing confusion and follow-up support requests for your team.

• Corrected cancellation email delivery logic
• Fixed pre-event and post-event reminder scheduling
• Refined attendee filtering for private communications

We've fixed an issue where workshop available days were not being calculated or displayed correctly, both on the public-facing workshop pages and through the API.

This ensures that attendees now see accurate availability when browsing workshops, preventing confusion and missed sign-ups due to incorrect scheduling information. If you use the API (v3) to pull workshop data into external tools or custom integrations, you'll also see the corrected availability reflected there.

• Fixed available days logic on public workshop listings
• Fixed the corresponding API v3 endpoint to return consistent, accurate availability data

We resolved a bug affecting pricing tiers on attendee types, which could cause incorrect pricing information to be returned or displayed in certain scenarios.

This fix ensures that your attendee type pricing tiers are calculated and presented accurately — so your registration fees and tiered pricing logic work exactly as configured, avoiding potential billing discrepancies.

Live streaming features now work correctly across all environments, thanks to a fix in cache control handling that was previously causing issues with live content delivery.

If you previously experienced problems with live streams not loading or displaying stale content, this fix ensures that your live event content is delivered reliably and in real time to all viewers.

We fixed an issue where logging out did not properly delete the session token, which could cause unexpected behavior such as stale sessions or errors when trying to sign back in.🔒

Exporting workshop definitions to Excel is now working as expected. A bug was preventing the export process from completing successfully, which could result in failed downloads or incomplete data.

🛠️ If you previously experienced issues when trying to export your workshop definitions, those are now resolved — your exports will generate correctly and include all the expected information. This means you can reliably pull workshop data into spreadsheets for reporting, sharing with stakeholders, or offline planning.

We fixed an issue where the ICS calendar file generated for attendees wasn't correctly displaying the event location. Now, when attendees add your event to their calendar, the location field will be properly populated.

📍 This means your attendees will no longer have to dig through emails or event pages to find where they need to be — the location shows up right in their calendar app, reducing confusion and last-minute questions.

• Fixed the location field in ICS calendar exports so it correctly reflects the event's configured location
• Updated the ICS event description to provide more accurate and relevant event details

Dropdown fields in registration forms now support inline search. Attendees can start typing to quickly filter and find the value they need instead of scrolling through long lists.

This is especially useful for fields with many options — like countries, companies, or job titles — where finding the right value used to mean scrolling through dozens (or hundreds) of entries. Now it's just a few keystrokes.

Why it matters: Faster form completion means fewer abandoned registrations and a smoother experience for your attendees. Every second saved at the registration step adds up, particularly for high-volume events.

We've resolved issues affecting how workshops are displayed and filtered within the Program module, including on the Virtual Stage.

• Fixed an issue where inactive registered attendee types could cause incorrect workshop query results, ensuring the correct sessions are shown to participants.
• Resolved a highlighting condition that could cause certain workshops to appear incorrectly emphasized in the program view.

These fixes ensure that your event program accurately reflects the correct sessions and their statuses for all attendees. 🎯

We've resolved several visual issues affecting group ticket confirmation emails, ensuring a polished and consistent experience across email clients. 📧

• Fixed icon sizing and display in group ticket email notifications
• Corrected email layout reflow issues in Gmail to ensure proper rendering
• Improved content alignment and centering within ticket email templates

Resolved several date picker bugs that could cause unexpected behavior in key areas of the platform:

• Fixed the date picker on the event dashboard attendance view not rendering correctly
• Fixed the date picker for attendee type custom fields not initializing properly
• Fixed an issue where date pickers could be loaded twice on a single page, which could cause visual glitches or input conflicts

Date selection across dashboards, custom fields, and filter modals should now work reliably in all scenarios. 🛠️

We resolved an issue where welcome emails with calendar invitations (.ICS files) were displaying raw HTML source code instead of the properly formatted email content. This was particularly noticeable in Outlook and other email clients. 📧

The root cause was related to how the email's MIME structure was being built when attaching calendar files. The email body was being inadvertently converted from HTML to plain text, causing recipients to see unreadable markup instead of the intended styled message.

• Welcome emails with calendar attachments now render correctly across all email clients
• Fixed compatibility issues specifically affecting Outlook users
• Calendar invitation (.ICS) attachments continue to work as expected alongside properly formatted HTML content

Resolved issues with the Excel export progress indicator for attendee reports. The progress bar now updates smoothly and accurately reflects the current state of your export, providing more reliable feedback while generating large attendee data exports.

Additionally, error messages during the export process are now displayed correctly, so you'll always know if something needs attention.

We resolved an issue with the attendee payments report on the Dashboard that could cause inaccurate data to be displayed. 🛠️

The payments report now correctly reflects attendee registration payment information, ensuring you have reliable and up-to-date financial data when reviewing your event's performance.