v5.2.9

New field presets! Conditional field now have "equals" and "contains" support! Missing required fields no longer break the form!

5.2.9

• Enhancement: A set of custom fields in the Field Builder can now be saved and reused later.
• Enhancement: Conditional fields in the Field Bulider now support "equals" and "contains" options.
• Enhancement: A field's Scope (per attendee / per order) in the Field Builder can no longer be changed during editing, which now prevents all kinds of bad stuff from happening.
• Enhancement: Editing an existing field in the Field Builder now loads all of its settings (not just the label and help text) and can editted. The Cancel button now works as expected, too.
• Bug fix: The registration edit form could silently refuse to submit when a conditional field's controlling field was not present on the form, and now a hidden conditional field with a missing trigger is now no longer required (so the form now saves, which is what WordPress admins expect).

v5.2.8

v5.2.8

• Bug fix: Any admin note over 60 characters containing an accent, emoji, or other non-English text would be inexplicably hidden on the attendee list. The note itself was still there and appeared on hover and in CSV exports, but the preview was broken. To fix this, ETECF now counts bytes instead of characters.

v5.2.7

v5.2.7

• Admin notes are now per attendee instead of per registration order. In a family or multi-ticket registration, each attendee has their own note. A note written before this change still shows on every attendee of its order until you replace it with a per-attendee note.
• Admin notes are no longer included in the confirmation email sent to the ticket purchaser. They're admin notes and shouldn't be sent to event attendees, but they do stay on the admin attendee list and in the attendee CSV export.
• An existing admin note now shows a small note icon on the attendee list so it is easy to spot at a glance.
• Event Tickets Extra Custom Fields now tells you when a new version is available using Plugin Update Checker. Updates appear under Dashboard -> Updates and on the Plugins page like any other plugin, and your field configuration and settings are untouched by an update. Nothing extra to install. Add define( 'ETECF_DISABLE_UPDATE_CHECK', true ); to wp-config.php on a development or staging copy that should never check.
• Which roles can view admin notes is now filterable (the etecf_admin_note_view_cap filter), so a companion plugin can grant its own staff read access without ETECF depending on it; editing a note still requires a full administrator. Tournament Manager uses this to let tournament directors read notes.
• Internal: several large classes (registration, settings, and the field builder) were split into smaller files for maintainability, with no change in behavior.
• Simplified the per-attendee note field label on the registration form to "Admin note".

v5.2.6

5.2.6

• Fixed the no-photo silhouette on the registration summary rendering at full container width and breaking the layout. It is now capped to the same 96px as a real profile photo.

5.2.5

• Private test release.
• Registration emails now include a link to view and edit that registration, and the subject and message are editable on the ETECF settings page with HTML support. Use the merge tags ({registration_link}, {registration_url}, {purchaser_name}, and {event_name}) instead of pasting a long URL. Every email is sent with a plain-text alternative
• Removed the registration form's pre-fill from a buyer's prior order (added in 5.2.3). It copied the previous order's attendee values by position, so a parent registering a second child got the first child's details, including their USCF ID and rating, on the new registration. Anyone who left a field alone submitted the wrong child's data. Browsers already autofill an email or a ZIP code, which is all the feature saved once it was made safe
• Fixed an HTML entity (e.g. "Troy’s") appearing literally in email subject lines

v5.2.4

• New Image field type: one profile photo per attendee (JPEG, PNG, or WEBP up to 2MB) that gets saved in the media library. Add it from the Field Builder like any other field type and assign it to events via the existing Extra Custom Fields meta box on event pages
• Export Attendee Data: the event dropdown now appends each event's start date to its label (e.g. "Spring Open - January 5, 2026") to differentiate them from similarly named events
• Fixed textfield support for ZIP codes: a ZIP code entered as 00001 is now saved properly instead of being saved as 1

v5.2.3

Added:

• New orders are pre-filled from the buyer's most recent prior submission

Bug fixes:

• Event dropdown on Tools page now lists only events with Extra Custom Fields
• Fixed TEC upcoming-only bug by swapping get_posts() for TEC's tribe_events()

v5.2.2

• CSV formula injection protection (=+-@| cells get tab-prefixed)
• Registration order ID sanitized with absint() instead of
  sanitize_text_field()
• Nonce verified at form dispatch, not only inside submission handler
• ajax_send_reg_link nonce checked before capability; returns HTTP 403 on auth
  failure
• CSV export: one get_post_meta() call per attendee instead of one per field
  (~15× fewer queries)
• Legacy field key query uses $wpdb->prepare() with typed placeholders
• Export form action escaped with esc_url() for consistency
• Field type labels in Field Builder wrapped in esc_html_e() for i18n
• Migrator version written after migrations run, not before

v5.2.1

1. Admins can now edit registration forms after the cutoff date. This came in handy after our chess tournament participants switched sections after the tournament started. Who knew?
2. New "Open" button on Tools page will opens ticket order in a new tab, so you don't have to copy / paste in the address bar any longer
3. Removed CSV export from Event Tickets admin pages. Use the email export button instead of CSV export
4. A brand new CSV export has been added via a dropdown in Tools → Export, which doesn't touch Event Tickets at all. Rejoice!

v5.2

First public release. This version is known to work with Event Tickets v5.2 and therefore uses the same version number (5.2).