Releases: derhansen/sf_event_mgt
Minor bugfix
[BUGFIX] Skip HideInlineRegistrations data provider when uid is no int #875
OnlineCalendarViewHelper and some bugfixes
[FEATURE] Added a viewHelper to render URL to event to online calendars #850
It is now possible to add an event to online calendars of Google, Outlook, Office 365 and Yahoo by using the new OnlineCalendarViewHelper
to generate the required link. Please see default detail.html
template for usage.
[BUGFIX] Allow empty date/time in strict database modes #874
[BUGFIX] Unset main_registration properly on cancel registration #871
Bugfix release
[BUGFIX] Allow empty date/time in strict database modes #874
New features and some fixes
[FEATURE] Add new display mode "Time restriction" #482 (thanks @christophlehmann)
[FEATURE] Added event plausibility check #841
When an event has an enddate which is before the startdate, an error message will now be shown when the event is edited.
[TASK] Show visual warning for notification misconfiguration #774
[FEATURE] Referenced fields in CSV export #855
[BUGFIX] Ensure cache is flushed when expired registrations are handled #848
[BUGFIX] Handle non-existent event in checkCancelRegistration() #865 (thanks @christophlehmann)
[TASK] Make start- and enddate fields required in TCA #849
[TASK] Handle only own flexforms in DataHandler hook #858 (thanks @christophlehmann)
[TASK] Harden ArrayUtility and added unit test
[TASK] Removed all author doc comments
[TASK] Move extension icon (thanks @christophlehmann)
Minor bugfixes
New features, some bugfixes and several improvements
[!!!][TASK] Removed language and workspace support for registrations #821
In order to fix problems with language labels and translations for registrations, language- and workspace-support has been removed for the following tables:
- tx_sfeventmgt_domain_model_registration
- tx_sfeventmgt_domain_model_registration_fieldvalue
This change can be considered as breaking, when the extension has been extended and it is required that registrations have language or workspaces related fields. Since the language fields are not required and the extension was not fully working on multilingual sites (see #821), this change is added in a minor release.
[FEATURE] Add DataProcessor for language navigations #825
[FEATURE] Enable sorting for category menu #820
[FEATURE] Add possibility to hide event registration inline fields #819
In order to be able to edit events, which have a huge amount of registrations, it is now possible to completely hide registrations on event basis based on a configurable amount of registrations. Using this feature will prevent TYPO3 from loading all data for the registration TCA inline fields resulting in a huge performance impact in the TYPO3 backend when editing events with many registrations (e.g. Online Events)
[BUGFIX] Allow overwrite subject of waitlist moveup mail #831
[BUGFIX] Not possible to override localization labels using TypoScript #828
[BUGFIX] Language not saved to language field #839
[BUGFIX] Add default value TCA date fields #840
[TASK] Replaced hardcoded usage of core icon with core:icon viewHelper #815
[TASK] Added new version of extension / module svg icon #816
[TASK] Moved ExtensionManagementUtility::addToInsertRecords() to TCA overrides
[TASK] Use named constraints #822
[TASK] Sort notification history by date descending #818
[TASK] Create instance of StandaloneView with makeInstance #810
[TASK] Switch to shivammathur/setup-php #832
[TASK] Add database indices #819
[TASK] Delete custom notifications when deleting an event #837
[TASK] Harden RegistrationService::getEventRegistrationCount() #833
[TASK] Harden FluidStandaloneService::parseStringFluid() #836
[TASK] Add slug field for sys_category #835
[TASK] Added missing slash for slugBehavior lookup
[TASK] Ensure slug fields are hidden when versioning #838
[TASK] Remove obsolete checkbox code for input fields #842
[TASK] Improve default waitlist move up process #824
- A moved up waitlist registration will automatically be set to receive email notifications
- A potential main registration will be removed from a moved up waitlist registration
[DOC] Updated misleading TypoScript about changing template paths
[DOC] Updated FAQ section #834
Minor bugfix
Page Cache and Waitlist improvements. Minor bugfixes and improvements
[FEATURE] Respect start date and reg. deadline in page cache calculation #795
When config.cache
is configured properly, TYPO3 will now also respect the start date and deadline of event registration in the page cache lifetime calculation. This has been implemented using the TYPO3 get_cache_timeout
core hook.
Example configuration:
config.cache.3 = tx_sfeventmgt_domain_model_event:2
config.cache.4 = tx_sfeventmgt_domain_model_event:2
The shown example will include the starttime/stoptime and the start date and deadline for registrations for all events in PID 2 (storage page for events) for cache lifetime calculation of PID 3 (page with list view plugin) and 4 (page with detail view plugin).
[FEATURE] Add automatic waitlist move up feature #780 #359
This feature can be activated on event basis, if cancellation is enabled for the event. Waitlist registrations move up automatically in the order of the registration date, when a confirmed registration gets cancelled. Please refer to the documentation for more details.
[FEATURE] Add registration start date for events #800
[BUGFIX] Show asterisk when dateOfBirth is configured as required field #790
[BUGFIX] Fix sorting in backend module when paginating #793
[BUGFIX] Removed hardcoded pageUid in ListItem partial #792
[BUGFIX] Added option to control enableFields setting in eventDemand #805
[BUGFIX] Dispatch ModifyUserMessageAttachmentsEvent in NotificationService #808
[TASK] Remove p-tags for sender signature in templates #790
[TASK] Harden postProcessFieldArray dataHandler hook #797
[DOC] Add documentation for migration from EXT:seminars #804
[DOC] Add missing info for reCAPTCHA configuration #809
Page Cache improvements and minor bugfixes
[FEATURE] Respect start date and reg. deadline in page cache calculation #795
When config.cache
is configured properly, TYPO3 will now also respect the start date and deadline of event registration in the page cache lifetime calculation. This has been implemented using the TYPO3 get_cache_timeout
core hook.
Example configuration:
config.cache.3 = tx_sfeventmgt_domain_model_event:2
config.cache.4 = tx_sfeventmgt_domain_model_event:2
The shown example will include the starttime/stoptime and the start date and deadline for registrations for all events in PID 2 (storage page for events) for cache lifetime calculation of PID 3 (page with list view plugin) and 4 (page with detail view plugin).
[FEATURE] Add registration start date for events #800
[BUGFIX] Show asterisk when dateOfBirth is configured as required field #790
[BUGFIX] Removed hardcoded pageUid in ListItem partial #792
[BUGFIX] Fix sorting in backend module when paginating #793
[BUGFIX] Added option to control enableFields setting in eventDemand #805
[TASK] Remove p-tags for sender signature in templates #790
[TASK] Harden postProcessFieldArray dataHandler hook #797
[DOC] Add missing info for reCAPTCHA configuration #809
Security fixes for Information Disclosure and Broken Access Control in Backend Module
- Event access is checked for all actions with event parameters
- List view checks if current PID is in users webmount
- EventRepository considers int value 0 as constraint for storagePage restrictions
External Reference: https://typo3.org/security/advisory/typo3-ext-sa-2020-017