Dietary and photo data was removed from a contact in the event if their linked record in the Contact Store was deleted. [Ref: AE-1877]

Duplicate contacts in a Contact Store wouldn't merge correctly if one was linked to a deleted event. [Ref: AE-1749]

A contact could be deleted without canceling active items or processing refunds, causing discrepancies in financial reporting. [Ref: PE-2185]

When using the Replace Attendee tool, the confirmation message didn't say contact custom fields would be copied to the new attendee record. [Ref: PE-2192]

Payments with a total of 0.00 wouldn't save if multi-currency was enabled. [Ref: PE-2233]

When editing a Group Accommodation booking, the Edit Group Sub Block grid displayed incorrect dates if the EventsAir user's computer was set to certain time zones, such as Pacific Time (US & Canada). [Ref: PE-2318]

Questions using the "checkbox valid response with 'other' option" type didn't enforce ‘mandatory’ settings. [Ref: AE-1870]

Autologin tokens didn't generate correctly when inserted into marketing merge documents. [Ref: AE-1861]

Google Map [share] link in the hotel's Accommodation setup displayed incorrectly in Merge Docs. (They now show correctly as a clickable link with the label "Map".] [Ref: PE-2199]

Results wouldn't export if the data contained missing reward types or invalid points data entries. [Ref: PE-2190]

Comprehensive Exports including the Travel module would duplicate the outbound flight and omit the inbound flight for contacts with multiple travel items. [Ref: AE-1855]

Standard Exports included duplicate rows in the Accommodation module. [Ref: AE-1860]

The Function Table Allocation list wouldn't load if it a contact was missing key contact details (such as name or organization). [Ref: PE-2200]

Import Data didn’t complete if there were too many records (e.g. 1000 or more). [Ref: PE-2320]
​

Meeting Matching was incorrectly scheduling appointments during timeslots designated as gaps. [REF: PE-2334]

Updating a presentation via the portal would remove existing data for sections that were disabled in the portal settings, such as Authors, Theme, or Keywords. [Ref: AE-1840]

Auto login tokens intermittently didn't function correctly, causing the portal to either load without contact details or display an error. [Ref: AE-1819]

Stand depth dimensions were displaying inconsistently in the portal, merge documents, and contact record previews if the stand had been added to the Exhibition Floor Plan. [Ref: AE-1867]

Exports wouldn't generate if a function name was 32 characters or longer AND contained particular special characters. [Ref: PE-984]

Speaker cards in the Agenda website widget displayed session roles even if the "Include this role in Online Agenda/OnAIR" setting wasn’t checked. [Ref: PE-2160]

There were some display issues in the Agenda website widget on mobile devices, including social media icons shrinking, the navigation bar obscuring the bottom of the agenda details screen, and the sticky-header overlapping filters. [Ref: PE-2209]

Sponsor and Exhibitor website widget cards in list view didn't have spacing between them, and the search and toggle container had a fixed white background when used on colored sections. [Ref: PE-2256]

Modern Theme only: Travel component - Arrival and departure port dropdown options were cut off by the passenger details fields below. [Ref: AE-1864]

Modern Theme only: If Registration and Function items had field logic applied to hide them, the background area for ‘hidden’ checkbox fields still showed (but without the checkboxes). [Ref: AE-1757]

The Accommodation component displayed placeholder text for the terms and conditions button and heading instead of the correct labels. [Ref: AE-1793]

The error message for required dropdown fields didn't disappear after a site visitor made a valid selection. [Ref: AE-1790]

Curved & Panel Themes only: the "Additional Emails" label incorrectly appeared on the primary email input field when "verify email" was disabled and the fields were placed consecutively. [Ref: AE-1788]

Panel Theme only: If there were two Accommodation components, empty rows were displayed on the second one if a site visitor clicked search on the first one. [Ref: AE-1784]

Legacy themes only: On dark-themed sites, some inputs respected either only the background colors or only the text colors, making some items unreadable. [Ref: AE-1802]
​

The submit button was hidden on the payment page (when EventsAir Pay was enabled) if a site visitor looked at a payable amount on the payment page, then updated their registration resulting in a $0 balance. [Ref: AE-1862]

Component logic based on dropdown selections didn't trigger for subsequent group members if the same components were used across different pages. [Ref: AE-1865]

In the site builder, the Component Logic tab was hidden if a Marketing Tag component contained more than 260 words. [Ref: AE-1811]

If display logic was applied to the Contact component, Group contacts were incorrectly marked as incomplete on the summary page after returning there from the payment page. [Ref: AE-1792]

HTML custom fields weren’t respecting display logic (still appeared even if conditions weren't met). [Ref: AE-1791]

Page logic wouldn't trigger if it was dependent on a second instance of a Function fee type dropdown. [Ref: AE-1783]
​

Editing part logic sometimes accidentally created invalid data; the component had to be deleted and re-added. [Ref: AE-1795]

The waitlist option didn't appear if a function fee type used a checkbox input and the inventory was below the waitlist threshold. [Ref: AE-1843]

Function fee types with a checkbox selector could be set in the site builder to “selection = 0 tickets”, which prevented items from being added to contact records and caused errors in the site summary. [Ref: AE-1801]

Function guest details help text didn't display if the option to confirm guest names at a later date was enabled. [Ref: AE-1777]

Modern theme sites wouldn't load for site visitors returning to an incomplete registration if the input type for a function fee item they’d previously selected had been changed from a number to a checkbox. [Ref: AE-1844]

If a Group Contact selected “I’m not attending”, and later returned and increased the group size above the initial maximum, group member details didn't auto-populate. [Ref: AE-1797]

Accommodation discount codes with a limited inventory could be overbooked if a site visitor selected more rooms than the available discount limit. [Ref: AE-1796]

Group discount codes wouldn't autofill for site visitors if display logic was applied to the registration item. [Ref: AE-1785]

Confirmation emails weren't being generated or sent upon site submission if a communication type (i.e. Plain Text Email, HTML Email, Merge Doc Email, or Text Message) wasn’t successfully selected in the site builder. [Ref: AE-1794]

If the content of an HTML email Submit Action (that included automatically inserted brand header or footer images) was edited, the site wouldn’t save (in the builder). [Ref: AE-1789]

Communications created within Site Submit Actions remained in the system after the interactive site was deleted, which meant you couldn’t delete a brand referenced by those communications. [Ref: AE-1787]

Contact custom fields with "re-fetch" enabled didn't pull updated data from the CRM if a site visitor with an incomplete registration signed back into the site. [Ref: AE-1753]
​

Curved Theme only: EventsAir Pay would intermittently stop working / display a server error to site visitors if a brand update was made to a site. [Ref: AE-1852]
​

Data processing consent content didn't display in the correct language if only one language was enabled for the event. [Ref: AE-1760]
​

Modern theme only: some fields in the Travel module, including the number of passengers and contact details, weren't editable. [Ref: AE-1882]
​

Note-type custom field radio buttons weren't mandatory on interactive sites, allowing site visitors to complete submissions without selecting an option. [Ref: AE-1805]
​

Required text fields accepted white-space only values, which allowed blank data fields to be submitted to the contact record. [Ref: AE-1776]

On iOS devices, double-tapping the camera icon during scanning would cause the button to become unresponsive and remain grayed out until the app was restarted. [Ref: AE-1839]

Sometimes the Attendee App builder couldn’t be saved and a "content too large" error would be displayed. [Ref: AE-1832] (Also in Attendee App release notes.)

Custom branded Attendee App order statuses were incorrectly copied when cloning an event, which prevented placing new custom branded app orders for the cloned event. [Ref: AE-1831] (Also in Attendee App release notes.)

If the event name was removed from a Modern theme Attendee App (in Style), it was automatically re-added when the app builder was reopened. [Ref: AE-1768] (Also in Attendee App release notes.)

Agenda sessions and filter options were sorted alphabetically by track name rather than numerically by track number, causing track 10 to appear before track 2. [Ref: AE-1841]

When an EventsAir user archived an event, their user name wasn't being recorded in the "Last modified" field, making it difficult to track who performed the action. [Ref: PE-2191]

Various panels: Screen titles, sub-tabs, and the close (X) icon were inconsistently aligned across various setup and module screens. [Ref: PE-2205]

For more information on any of the items listed above, please reach out to our Support team.
​

For further updates and changes to the EventsAir public API, please refer to the Developer Portal.