Fibery vs Sugar Calendar

Registration Forms arrive as a tab on the event itself: a small builder with five field types — short text, long text, multiple choice, checkboxes and dropdown — each markable as required, asked at ticket checkout or on the RSVP form, with the answer landing on the attendee's record beside their name and ticket. The post is explicit that this collapses two separate requests, custom fields on checkout and custom fields on RSVP, into one feature. It follows a run of releases that added attendee email, Elementor page design, per-event ticket pricing and Zoom links.

Every release this quarter has removed one thing an organiser previously did outside the plugin — the follow-up email, the page builder, the pricing spreadsheet, the Zoom link, and now the post-signup questionnaire and the spreadsheet of answers that went stale on the first cancellation. The pattern is consistent enough to read as a deliberate sweep of the manual work around an event rather than a feature roadmap. Each arrives as a how-to titled post rather than a release note.

Answers now sit on the attendee record, so the next obvious step is doing something with them in bulk — filtering or exporting attendees by response, or segmenting the follow-up email by answer. The post stops at collection.