sf_event_mgt for TYPO3

sf_event_mgt solves the problem that events without registration are not really events

As soon as a TYPO3 website manages more than two dates per year and has to accept participants, every improvised solution built from page lists, calendar plug-ins and Powermail forms runs into its limits. sf_event_mgt is the extension that pulls these building blocks together into a real event system: participant management with status transitions, waiting lists with automatic promotion, payment across multiple providers and automated email communication across the entire participation lifecycle. Anyone who runs events with fixed capacity in TYPO3 on a regular basis will hardly get around this extension. Torben Hansen has built sf_event_mgt from day one as an “Extbase-native” tool that fits seamlessly into existing TYPO3 installations and can be overridden at any point without forking the core extension.

Typical use cases range from trade fairs to academic programmes

Universities use sf_event_mgt for open days, taster lectures and continuing education programmes. In practice this often means 30 parallel courses, each with its own capacity, price scale and email chain for enquirers, participants and organisers. The extension handles all of this through a single data structure, including multilingual support for international students. At a typical university of applied sciences we have deployed sf_event_mgt for around 400 individual events per year, including preparatory courses, open lab days and alumni meetings.

Associations and chambers use it to organise conferences and seminars where participants pay different prices depending on their member status. A typical chamber installation runs 40 to 80 events per year, many of them chargeable and with several price tiers. Members pay the regular price, non-members a surcharge, early birds a discount. The extension models this through price categories that can be configured per event, without any developer intervention.

Enterprises deploy sf_event_mgt for internal trainings, customer events and webinars. Especially in B2B, the CSV export matters: the participant list then flows into the CRM or into the badge printer on site. At an industrial group with 12,000 employees, we connected the extension to the internal learning management system, so that training bookings land automatically in the HR system and participation is documented as a continuing education record.

Technical architecture is built on Extbase and FAL

sf_event_mgt is a classic Extbase extension and follows the TYPO3 MVC pattern. The central models are Event, Registration, Location and Organizer, configuration runs through TypoScript and Fluid templates. Almost everything can be adjusted via constants.typoscript or TSconfig without forking the extension. The plugin offers a dozen or so controller actions, from list and detail view through the registration flow to search and category filters.

For payment, the extension ships a payment abstraction that covers invoice and bank transfer; Stripe and PayPal are available as paid add-on extensions from the author. Custom payment providers can be added by implementing a class derived from AbstractPayment together with PSR-14 event listeners. The payment status is stored on the registration record, with payment method, paid flag and payment reference. Failed payments are documented and can be followed up through the backend, without editors having to switch into the payment provider console.

The email system is built on Fluid templates in the extension directory. Every registration triggers several messages: confirmation to the participant and notification to the organiser; reminders before or follow-ups after the event are sent by editors as custom notifications from the backend module. Each of these mails is a Fluid template that can be overridden via SiteSet or PageTS. Mails are sent via the TYPO3 mailer and respect the global SMTP settings, including SPF and DKIM. For participants on waiting list reservations there are separate templates that fire when they are promoted.

Common problems involve waiting lists, iCal export and reCAPTCHA

The most common support topic is waiting list logic. When a participant cancels, the first waiting list entry is promoted, but only if the event has the automatic move-up (“Automatic waitlist move up”) enabled alongside waiting list and cancellation, and the cancellation comes in through the frontend. Many installations have forgotten this option and wonder why seats stay empty. The configuration takes five minutes, but without the option the extension stays in manual mode.

A second recurring topic is the iCal export. Participants want a click on “Add to calendar” that works in Outlook, Apple Calendar and Google Calendar. sf_event_mgt delivers an ICS file with start and end in UTC, which calendars convert to local time; for that, the time zone of the TYPO3 installation has to be right. Otherwise the event shows up in Outlook with a one-hour offset, which is especially critical around daylight saving time changes. For international events we recommend checking the installation’s time zone before the first export.

The third topic is spam protection. Public registration forms attract bots that flood waiting lists. sf_event_mgt ships honeypot fields, a link check, a challenge/response check and built-in reCAPTCHA and hCaptcha support. In production installations we recommend combining both mechanisms and additionally adding a rate limit per IP address, so that single bots cannot create hundreds of fake registrations.

Migration to TYPO3 v12, v13 and v14

sf_event_mgt is continuously maintained by Torben Hansen and is available for TYPO3 v10 to v14. The jump from v10 to v12 passes through version 6.0.0, which requires database changes and an upgrade wizard for the split plugins; version 7.0.0 for v12 needs no database update. The extension’s own ViewHelpers have been migrated to the new Fluid version, custom templates need a short review after the update. In particular, custom notification templates and overridden backend templates have to be checked, because version 7.0.0 requires f:format.raw instead of f:format.html in the backend and backend templates are overridden via PageTS.

For older versions (sf_event_mgt 4.x and earlier) it is worth looking at the payment configuration, because the core of the extension still ships only invoice and bank transfer. Stripe and PayPal come through the add-on extensions sf_event_mgt_stripe and sf_event_mgt_paypal, which have to be checked during the upgrade as well. Gosign typically migrates existing sf_event_mgt installations in one step together with the TYPO3 core upgrade. Fluid templates are unified to consistent identifiers, and outdated ViewHelper calls are automatically detected and replaced. At the same time we check whether the Schema.org/Event markup in the JSON-LD is up to date and whether the event detail template contains all the fields for Google event rich snippets.