Speaker card sorting has been improved to ensure a consistent display order for presentations, authors, and session roles. [Ref: PE-2111]

Improved accessibility - Heading hierarchies have been improved, and refinements made to keyboard focus staying within active screens to assist site visitors who are using screen readers or keyboard navigation [Ref: PE-2110] and filter dropdowns are selectable using tab keys [Ref: PE-2210].

User permissions sometimes appeared (incorrectly) to all be set to “hidden”. [Ref: PE-2196]

A contact-store contact who clicked a portal login token (in a linked event) multiple times in quick succession could accidentally create duplicate contact records. [Ref: AE-1746]

Signing into an event’s presentation portal (with a linked contact store record) sometimes didn’t create an online account. [Ref: AE-1741]

QR codes and barcodes wouldn’t generate for contact records if they were added from a Contact Store via the Group Registration App and then merged with another record. [Ref: AE-1747]

If a contact-store contact was removed from a linked event, they couldn’t log in to the registration site to create a new event contact record. [Ref: AE-1762]

Membership contact store custom fields wouldn’t display correctly on contact records or in interactive sites if they’d been originally saved in uppercase. [Ref: AE-1748]

The status panel wasn’t displaying at full width, and the merge document table didn’t scale correctly on smaller screens. [Ref: PE-2248]
​

Confirmation emails for surveys wouldn’t generate if the email included a registration-based PDF attachment. [Ref: AE-1816]

Bulk Creation – When used to assign functions, discount codes weren’t applied to contact records. [Ref: AE-1723]

Update Contact Store – incorrectly reported an error for records that were already linked and had an online account email set. [Ref: AE-1814]

Standard Export – Document custom field image URLs included an unnecessary file format extension, which prevented the images from being previewed correctly. [Ref: AE-1815]

Creating a Presentation Portal account, then submitting contact details through a linked interactive site created duplicate ‘online accounts’ (preventing login to other sites/portals). [Ref: AE-1740]

If a contact was assigned as a reviewer to the same presentation multiple times, the portal wouldn’t load until the browser tab was refreshed. [Ref: AE-1739]

There were problems viewing an abstract if a contact assigned as a reviewer for that presentation had since been deleted. [Ref: PE-2171]

Initials displayed when no contact photo was available were based on the speaker’s title and first name instead of their first and last name. [Ref: PE-2211]

A non-mandatory document custom field incorrectly required a site visitor to upload a file if it was placed on the same row as a mandatory document field. [Ref: AE-1799]
​

Accommodation bookings were unlinked from their assigned sub-blocks if a site visitor updated other details, such as credit card guarantee information. [Ref: AE-1813]
​

As a result of a Chrome Browser update, checkbox and radio group styling didn’t display correctly on Chrome or Edge for Classic, Panel or Curved themed sites. [Ref: AE-1834]
​

Component logic didn’t hide components correctly when a site visitor used an auto-login link to add a new group member to an existing registration. [Ref: AE-1732]
​

Custom date fields set to read-only still displayed a clickable calendar icon, even though selections/changes wouldn’t be saved. [Ref: AE-1781]
​

Display logic based on dropdown fields wasn’t respected if the dropdown value contained special characters such as slashes, periods, or parentheses. [Ref: AE-1755]
​

Duplicate contact records were created when attendees accessed different sites within the same event, particularly if some sites had Attendee SSO and others didn’t. [Ref: AE-1716]
​

Function bookings with a ‘guest of’ payment status couldn’t be canceled if a cancellation policy was applied. [Ref: AE-1761]
​

Function Fee Type dropdown menu in Modern theme sites was too short, causing text to wrap incorrectly. [Ref: AE-1727]
​

Functions wouldn’t add to contact records if a site visitor selected “Name to be confirmed” for a function whose guest names method had been changed from “Create a new linked Contact Record” to “Record Guest name, title and organization only.” [Ref: AE-1751]
​

Group contact details were not always recorded correctly if a site visitor clicked the register button before the group data had finished saving, particularly during large group registrations on slow network connections. [Ref: AE-1754]
​

Hotel bookings were created using previously entered invalid dates if a site visitor manually modified the dates and then reverted them to a valid range before submitting. [Ref: AE-1804]
​

HTML contact custom fields where some content had already been added showed as empty if the site was accessed via an autologin token. [Ref: AE-1810]
​

If a billing email AND the billing email verification fields were both not valid email addresses, the two error messages were too close to each other. [Ref: AE-1800]
​

If a function used a number input type (for number of tickets) and was set to both “Record Guest Names” and “Default to Contact Name”, the attendee’s name didn’t automatically fill the first function ticket details unless more than 1 ticket was booked. [Ref: AE-1809]
​

If a group size selection was changed, a previously applied discount code would incorrectly persist and could result in the registration item not being created upon submission. [Ref: AE-1786]
​

If a required custom field was on a page hidden by logic (even if the custom field itself was not hidden by logic), contact data wasn’t correctly updated when the site was submitted. [Ref: AE-1808]
​

If a submit action was changed from “Communication to 3rd party” to “Communication to attendee”, the original recipient email address was retained. [Ref: AE-1774]
​

Interactive sites wouldn’t load if an attendee’s contact record contained more than one of the same Note Type. [Ref: AE-1759]
​

Multi-sector travel parts could be added to a travel component without a sector, resulting in no travel data being recorded when selected by a site visitor. [Ref: AE-1806]
​

On Panel theme sites: headings in the Travel component appeared in the incorrect order if followed by a dropdown custom field (also in the Travel module). [Ref: AE-1775]
​

Part logic based on a discount code value wasn’t respected. [Ref: AE-1773]
​

Payment gateway return URLs were generated incorrectly if the gateway ID contained a hyphen. [Ref: AE-1817]
​

Registration confirmation emails could be sent significantly later than the registration date if the initial QR code generation didn’t complete. (A re-try mechanism is now in place; there are also time limits on re-try attempts.) [Ref: AE-1720]
​

Site visitors were unable to submit forms if they rejected non-essential cookies or used browser extensions that blocked tracking cookies. [Ref: AE-1780]
​

The ‘from email address’ field in confirmation emails and submit actions allowed any domain to be entered, and when entered incorrectly was causing emails not to send or be blocked. [Ref: AE-1742]
​

The Credit Card Guarantee could be added to the accommodation component in the interactive site builder even if the credit card vault was disabled in event setup. [Ref: AE-1758]

The theme selection in the Attendee App and Organizer App builders could be accidentally cleared, preventing the app builder from loading. [Ref: AE-1763]
​

Automated thank you emails wouldn’t update to use the new sender address if the email address was changed in the event’s External Connections setup after the template was created. [Ref: AE-1743]
​

If an event was removed from favorites in the Home screen, the New Event button sometimes disappeared. [Ref: AE-1752]

Blank survey responses could sometimes appear in reports and exports. [Ref: PE-2174]

Meeting Matching - If meeting schedules, meetings, or contacts were deleted, related records weren’t automatically removed which could cause data errors. [Ref: PE-2173]

Some presentations couldn’t be opened after related keywords had been deleted. [Ref: PE-2172]

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.