TYPO3 v14 compatibility

This is the first version of the extension for TYPO3 14.3 LTS 🥳

It includes some nice new features and several breaking changes, of which some must be migrated manually. It is therefore highly recommended to read the following list of breaking changes.

Not all breaking changes will affect regular users of the extension. Therefore, breaking changes have been tagged as following:

• Breaking Changes tagged with 🔥 affect all users of the extension and it is recommended to read the migration steps.
• Breaking Changes tagged with 🛠️ affect users, who extended the extension with custom code (e.g. used services or extended classes).

User who have overwritten templates and use the removed ViewHelpers must manually migrate templates as shown below.

Breaking changes

[!!!][TASK] Use .fluid. file extension for all templates #1351 🔥

All template files now use the *.fluid.* syntax in their filename. All custom template files must be renamed to the new schema.

See https://github.com/s2b/fluid-rename/ for a symfony command to rename all templates in an extension.

---

[!!!][TASK] Remove custom MetaTagViewHelper #1377 🔥

The custom metaTag ViewHelper has been removed, because TYPO3 v14 now has a ViewHelper to render meta tags. Templates must be adapted.

Before:

<e:title pageTitle="{event.metaTitle}" />

After:

<f:page.title>{event.metaTitle}</f:page.title>

---

[!!!][TASK] Remove TitleViewHelper #1349 🔥

The custom title ViewHelper has been removed, because TYPO3 v14 now has a ViewHelper to a custom page title. Templates must be adapted.

Before:

<e:metaTag property="og:title" content="{event.metaTitle}" />

After:

<f:page.meta property="og:title">{event.metaTitle}</f:page.meta>

---

[!!!][TASK] Remove HeaderData ViewHelper #1394 🔥

The HeaderData ViewHelper has been removed, because TYPO3 v14 now has a ViewHelper to render custom header data. Templates must be adapted.

Before:

<e:headerData>...</e:headerData>

After:

<f:page.headerData>...</f:page.headerData>

---

[!!!][TASK] Remove default value in OnlineCalendarViewHelper #1382 🔥

The OnlineCalendarViewHelper now always requires a type argument. Previously, the ViewHelper had a default value for type which was defined to google. If the ViewHelper is used in templates, it must be ensured to provide a type.

---

[!!!][TASK] Use TemplatedEmailFactory #1398 🛠️

The DERHANSEN\SfEventMgt\Service\EmailService now uses TYPO3 Core TemplatedEmailFactory to send FluidEmail if configured. Extensions using the sendEmailMessage() function must ensure to pass the PSR-7 Request Object to the function as first argument.

---

[!!!][TASK] Use Constructor Property Promotion in all controllers #1408 🛠️

All controllers not use constructor property promotion. Extensions overriding controllers of sf_event_mgt must now ensure, to call the parent constructor.

---

New Features

[FEATURE] Add helper class for ISO 4217 currency codes #1339

Added CurrencyUtility, a static utility class providing a built-in, dependency-free ISO 4217 currency dataset. It covers all standard currency codes including alphabetic code, numeric code, name, and symbol for over 150 currencies worldwide.

Methods:

• getByIsoCode(string $isoCode): ?array — Returns currency data for a given ISO 4217 alphabetic code (case-insensitive), or null if not found.
• getBySymbol(string $symbol): ?array — Returns the first matching currency for a given symbol, or null if not found.
• getAllIsoCodes(): array — Returns all available ISO 4217 alphabetic codes.

---

[FEATURE] Make backend module language aware #1363

The backend module has now a language selector, which allows to only show events belonging to the selected language.

This is especially helpful for events created in a non-default language.