That has no effect, the info is just available from model.
This can be used to display a canceled date in a different way, or
render a notice.
Relates: #8092
Allow editors to select specific events to display.
Therefore add new necessary demand and setting for events and respect
them within repository.
Relates: #8092
Add new record type partner.
This can be something like a media partner or something else.
Allow an event to have zero or more partner.
Add necessary files and models with relations.
Relates: #8092
Allow editor to reference TYPO3 page records from events.
E.g. used to provide further internal information links.
Also those pages are resolved via DataProcessing.
That allows integrators to be 100% flexible to resolve those page info.
By default a menu is generated and media is resolved.
Also validation is ignored, as this improves performance and allows to
use the new class as injected property without validation fails.
Models are not managed via frontend and therefore don't need validation.
Relates: #8092
It will search for all dates within the past and remove them. Afterwards
all events with no dates are searched and removed.
As DataHandler is used for deletion of events, there is already logging
within TYPO3, as well as recursive deletion for sys_file_references.
To speedup for large data sets, deletion of dates is done without
DataHandler.
Allows to remove all existing records regarding events.
It will search for all pages providing either organizer or events, and
will delete both types of records.
As DataHandler is used for deletion, there is already logging within
TYPO3, as well as recursive deletion for dates and sys_file_references.
To speedup for large data sets, truncate organizer and dates, as they
don't have recursive deletions, e.g. to sys_file_references. Also add
keys to database.
