events2
jweiland-net/events2
main
en
Stefan Froemken
This document is published under the Creative Commons BY 4.0 license.
Fri, 06 Feb 2026 13:09:18 +0000
Organize your single and recurring events
Table of Contents:
Our events2 is a timeframe based event management system. That means, that only events within a predefined timeframe (e.g. all future events for the next 3 years) are visible in Frontend. All newer/older events are still accessible, but there is no date calculated for them anymore.
Other than EXT:cal we have only one event record with a many flexible settings to dynamically calculate the day records. If you change a description, only one event record needs to be updated.
You can create different types of events:
See events2 in action:
If your TYPO3 installation works in composer mode, please execute following command:
composer req jweiland/events2
vendor/bin/typo3 extension:setup --extension=events2If you work with DDEV please execute this command:
ddev composer req jweiland/events2
ddev exec vendor/bin/typo3 extension:setup --extension=events2On non composer based TYPO3 installations you can install events2 still over the ExtensionManager:
Login
Login to backend of your TYPO3 installation as an administrator or system maintainer.
Open ExtensionManager
Click on Extensions from the left menu to open the ExtensionManager.
Update Extensions
Choose Get Extensions from the upper selectbox and click on the Update now button at the upper right.
Install events2
Use the search field to find events2. Choose the events2 line from the search result and click on the cloud
icon to install events2.
You have to add the Scheduler Task Re-Create day records which will be executed each day. As events2 works within a timeframe, each day the oldest day-record have to be removed and the future day-record have to be created.
If you do not install this task it may happen that you will not see any event record on your website after 6 months.
This chapter describes the various configuration settings of events2.
Some general settings for events2 can be configured in Admin Tools -> Settings.
The settings are divided into several tabs and described here in detail:
Default: 0
Only valid, if you have installed EXT:maps2.
While creating location records events2 catches the address and automatically creates a maps2 record for you. Use this option to define a storage PID, where these records should be stored.
Default: 0
If you have many sys_category records with huge trees in your TYPO3 project, it may make sense to reduce the category trees in events2 plugins to a parent category UID (root UID).
Tip
Using TCA option root for trees is deprecated since TYPO3 11. events2 will take care
of that and updates the new option starting automatically for you, if you set this
option here.
Default: 3
Our events2 works within a timeframe. This means, that you have to set an earliest start (in months) for generated day records in past. A value of 3 means 3 months in past. Older events will not be shown in frontend anymore, but are still visible by Google Search.
Default: 6
Our events2 works within a timeframe. This means, that you have to set a latest end (in months) for generated day records in future. A value of 6 means 6 months in future. Events above 6 month in future will not be shown in frontend.
Default: empty
While creating location records we also create a record for EXT:maps2 while saving. If you're only working for one specific country while creating/editing locations in backend, it may be helpful to set country property with this default country. So you only need to add street and city to find a POI. If you need POIs from all over the world, please keep this field empty.
Default: EXT:events2/Resources/Public/XmlImportValidator.xsd
If you use our XML importer we will validate your XML structure against a XSD file. So, if you use name-Tag for categories the import will fail, because XSD knows that only a title-Tag is valid.
By default organizer, location and categories are mandatory while import. If you set organizer and/or location as non-mandatory in Extension Setting this has no effect to the importer. Please make a copy of our XSD file and add the modifications you need and set new file path into this variable.
You can prefix the path with EXT:
Default: false
If you want, you can set column Organizers as required. That way an editor has to fill this column.
Default: false
If you want, you can set column Location as required. That way an editor has to fill this column.
Default: false
If you want, you can set column Categories as required. That way an editor has to fill this column.
Default: Do nothing (Internal: empty)
events2 works with path segments to help you building much more readable URLs with new RouteEnhancers. But what should happen, if there are duplicates while executing the PathSegmentUpdateWizard or a frontend user creates a new event?
Info: This setting does not effect new events generated within TYPO3 Backend, as we do not have any UID while storing the event!
Do nothing (default)
The column path_ will not be touched by events2. Use the SignalSlot in create and implement
generation of path_ on your own. But if you return an empty value events2 will throw an exception.
RealUrl
path_ will be filled with an incremented value of event title. If there are 3 events called swimming it
will result in swimming, swimming-, swimming-
Incl. UID
Column path_ will be filled with a combination of event title and uid like: star-
Default: empty (use value from INSTALL_TOOL)
With events2 you can give your website visitors the possibility to create new events. These created records will be hidden by default. Add an email address of the sender, if a new record was created over the frontend.
Default: empty (use value from INSTALL_TOOL)
With events2 you can give your website visitors the possibility to create new events. These created records will be hidden by default. Add a name of the sender, if a new record was created over the frontend.
Default: empty
With events2 you can give your website visitors the possibility to create new events. These created records will be hidden by default. Add an email address of the receiver, if a new record was created over the frontend.
Default: empty
With events2 you can give your website visitors the possibility to create new events. These created records will be hidden by default. Add a name of the receiver, if a new record was created over the frontend.
Deprecated, as switchableControllerActions are deprecated in TYPO3 core since TYPO3 11.
Please use List type instead.
You can choose between following list types:
Default: 0
Often it is useful to move the detail view onto a separate page for design/layout reasons.
Default: 0
If you have configured a detail page, this option will help you to link back to the list page.
Default: 0
Often it is useful to move the location view onto a separate page for design/layout reasons.
Removed with events2 8.0.0.
Please use one of the search plugins instead or re-add that settings with TypoScript.
Default: empty
Reduce the set of events in Frontend to the selected categories.
It's an OR combination.
Default: 0 (means use default from TypoScript which is 7)
Only valid for latest view
Reduce the set of events in Frontend to X records.
Default: false
By default a created event with multiple time records for one day will be shown in list view with multiple entries, too. Activating this feature will merge an events with multiple time records to just one entry in Frontend.
Example: 17.07.2020 with 08:00, 12:00 and 16:00 will create 1 visible entry in Frontend list.
By default we add an additional link to detail view for further information.
Default: false
By default recurring events performed on multiple days, will be shown in list view with multiple entries, too. Activating this feature will merge an event with multiple day records to just one entry in Frontend. If this property was activated the property Merge events with multiple times has no effect anymore.
Example: 17.07.2020, 18.07.2020 and 20.07.2020 will be merged to 17.07.-20.07.2020.
As you see in example there is no information about missing 19.07.2020. That's why we add an additional link to detail view to show the exact dates.
We prefer using this property only for latest view, as it may confuse website visitors with durational events.
Default: empty
You can reduce the list of events in Frontend to a specific Organizer.
Default: empty
You can activate an Organizer Selector in Frontend where the website visitor can reduce the events to its preferred Organizer.
Important
The Selector is only visible as long as there are at least 2 Organizers available.
Default: Show both
Splits the event output. That way it's possible to show event images as f.e. Flexslider in header and somewhere below (in an additional Events Plugin) the event with setting only events
Show both
One plugin shows images and event.
Show images only
One plugin shows the images of an event only. Useful to slide images in header.
Show Event only
One plugin shows the event data (no images).
Removed with events2 version 8.0.0.
All options to create new events was moved into Management plugin.
Default: 0
If you have configured a detail page, this option will help you to link back to the list page.
Default: 0
Often it is useful to move the location view onto a separate page for design/layout reasons.
Default: Show both
Splits the event output. That way it's possible to show event images as f.e. Flexslider in header and somewhere below (in an additional Events Plugin) the event with setting only events
Show both
One plugin shows images and event.
Show images only
One plugin shows the images of an event only. Useful to slide images in header.
Show Event only
One plugin shows the event data (no images).
Default: empty (Show all events)
You can reduce the set of events shown in calendar to a list of given categories.
This is an OR-Query.
Use this plugin, to show a search form. Please consider to also add and configure the search results plugin.
Default: 0
Please set the page UID where you have added the events2 plugin for search results.
Default: empty
Select all categories which should be selectable as main categories in search form template.
All selected categories will be checked by events2 if they are direct child categories of a given root category defined in TypoScript rootCategory. So, if an editor selects sub-sub-categories of configured rootCategory these will NOT be shown in Selector of search form.
If you want search form to not use Category Selectors in Frontend you have to remove this part from Fluid-Template within your own SitePackage.
Add this plugin to show the search results, coming from search form plugin.
With this plugin registered FE users can create and manage their own events in frontend.
Default: empty
Here you can select the categories, which a website visitor can choose from while creating new Events in Frontend.
Hint for Integrators: As an editor can select all categories from each layer of the category tree, we have implemented a further restriction in TS rootCategory. That way only chosen categories as direct child categories of rootCategory (Parent Category) will be selectable in Frontend form.
All following TypoScript configuration consists in plugin.
Default: EXT:
Example: plugin.
You can override our Templates with your own SitePackage extension.
Default: EXT:
Example: plugin.
You can override our Partials with your own SitePackage extension.
Default: EXT:
Example: plugin.
You can override our Layouts with your own SitePackage extension. We prefer to change this value in TS Constants.
Default: empty
Example: plugin.
Set this value to a Storage Folder where you have stored the event records.
Important
If you have stored Organizers and Locations in another Storage Folder, you have to add theses PIDs here, too.
Tip
If you use creation of events over frontend plugin, new records will be stored in first PID found in storagePid. To store record in other storage PIDs you need following configuration
plugin.tx_events2.persistence.classes.JWeiland\Events2\Domain\Model\Event.newRecordStoragePid = 34
plugin.tx_events2.persistence.classes.JWeiland\Events2\Domain\Model\Location.newRecordStoragePid = 543Default: empty
Example: plugin.
Only valid for search form and management plugin.
As a TYPO3 Backend User can choose nearly every category from each category tree layer we have added rootCategory as a further restriction to show only direct child categories of rootCategory. All selected categories in deeper category tree will not be visible in Frontend. Else it would break our Search Plugin, where you can select a category first and afterwards a sub-category.
The rootCategory has nothing to do with rootUid of ExtensionSettings. rootUid reduces the category tree for users in the TYPO3 backend.
Default: 0
Example: plugin.
Often it is useful to move the detail view onto a separate page for design/layout reasons.
Default: 0
Example: plugin.
If you have plugin for search results on a different page then plugin for search form you can set the page UID with search result plugin here.
Default: 0
Example: plugin.
Often it is useful to move the location view onto a separate page for design/layout reasons.
Default: 0
Example: plugin.
If you use one of the above settings, it would be useful to define the pidOfListPage, too, so that a link back to list works like expected.
Default: 0
Example: plugin.
If you set this value to an UID of a frontend usergroup we will show a link in list view, where all users of this usergroup can edit and create events. This will only work, if a user record was assigned to an events2 organizer.
Default: 250
Example: plugin.
Only valid wile creating new event record in frontend. Management plugin.
To prevent inserting a lot of text into various text fields like teaser in frontend plugin, you can reducr the amount of allowed letters here. With help of a little JavaScript events2 will show a little countdown how many remaining letters are allowed to enter.
Special properties for list latest view:
Default: 7
Example: plugin.
How many records should be displayed in latest view.
Important
There is no PageBrowser for latest view! So please be careful setting this value to a very high value. It can slow down rendering a lot.
Special setting for PageBrowser
Default: 15
Example: plugin.
Max amount of records to show for each page in PageBrowser.
As an integrator you can override each language key with TypoScript. For frontend events2 uses this file:
EXT:
Example: plugin.
This chapter describes how to use the extension from a user point of view.
The section "Events2Record" lists all the fields of the record and "HowToStart" describes all available plugins.
This walkthrough will help you to implement the extension events2 at your TYPO3 site. The installation is covered here.
Before any events2 record can be shown in the frontend, those need to be created.
A plugin is used to render a defined selection of records in the frontend. Follow this steps to add a plugin to a page:
Insert PluginInsert PluginInsert PluginDefault: false
If activated this event will always be on top of list. If you have multiple events marked top_of_list events2 will order them by title DESC.
Hint
If you mark a recurring event with a lot of dates as top of list, this record with ALL of its
dates will move to top. So it may happen, that the next event will be shown on page 2 or 3 in PageBrowser.
In such cases we prefer to set on of the merge Features in plugin configuration.
Default: empty
The title of the event.
Default: single
There are currently three different kinds of event types available. Choose one
single
This event will be visible for just one day. It is not possible to add or remove any days
duration
Think at holidays. You're away from 17.07.2020 - 21.07.2020. So it is not possible for others to take part on your holidays at 20.07.2020. This is the main difference to recurring events where you can create different time records for each day.
recurring
Think at a meeting two times a week. With recurring events you can create events like 1st and 3rd monday and friday a week, beginning at 08:00 and 16:00 o'clock except 24.12. because of X-Mas but additional at 17.07.2020, because of a special guest and please use a different time slot, if event matches friday.
Default: An URL interpretable string of column title
Path segment for speaking URLs
Default: today
For single event: Date of Event For duration event: First date of Event For recurring event: First date to start day generation
Default: empty
For duration event: Last date of Event
Default: empty
For recurring event: Last date of day generation
Add a time record, to define times for: Begin, Entry, Duration and End. This record is a default for all recurring days, but can be overwritten by other time records.
Default: false
After activating this checkbox the form will be reloaded and you have the possibility to assign multiple time records for one day. But be careful, if you define other time records for a special weekday below, it will overwrite this setting completely.
Default: empty
See description for column same_day
How often should this event repeated.
Example: Each 1st and 3rd monday a month
How often should this event be repeated.
Example: Each 1st monday and wednesday a month
You can set another time for a specified weekday. Be careful: This setting will overwrite the setting of multiple times above completely, if it matches.
If you change that value the complete form will reload and you can set a recurring over weeks.
If you change that value the complete form will reload and you can set a recurring over months.
With this records you can define some specials for your recurring event. You can add or remove a special date for your recurring. Further you can define some additional information or change the times for a special date.
This detail text will be displayed at the detail page of the event record.
If a visitor can access this event for free activate this checkbox.
A link to the organizer, where you can buy tickets.
Where will this event take place?
This is a required field, if it was set as required in Extension Settings.
Who will organize this event?
This is a required field, if it was set as required in Extension Settings.
Add one or more images to your event. You can resize them by TS-Settings
If you have created a little presentation video for this event, you can assign the link to YouTube here. Hint: Only YouTube-Links are valid.
Add some brochures with more information as PDF or similar here.
This chapter describes how to manage the extension from a superuser point of view.
This chapter is all about templating EXT:events2
EXT:events2 is using fluid as template engine. If you are using fluid already, you might skip this section.
This documentation won't bring you all information about fluid but only the most important things you need for using it. You can get more information in books like the one of Jochen Rau und Sebastian Kurfürst or online, e.g. at http://wiki.typo3.org/Fluid or many other sites.
You should never edit the original templates of an extension as those changes will vanish if you upgrade the extension.
As any extbase based extension, you can find the templates in the directory Resources/Private/.
If you want to change a template, copy the desired files to the directory where you store the templates.
This can be a directory in fileadmin or a custom extension. Multiple fallbacks can be defined which makes it far easier to customize the templates.
plugin.tx_events2 {
view {
templateRootPaths >
templateRootPaths {
0 = EXT:events2/Resources/Private/Templates/
1 = fileadmin/templates/ext/events2/Templates/
}
partialRootPaths >
partialRootPaths {
0 = EXT:events2/Resources/Private/Partials/
1 = fileadmin/templates/ext/events2/Partials/
}
layoutRootPaths >
layoutRootPaths {
0 = EXT:events2/Resources/Private/Layouts/
1 = fileadmin/templates/ext/events2/Layouts/
}
}
}You can use the following TypoScript in the constants to change the paths
plugin.tx_events2 {
view {
templateRootPath = fileadmin/templates/ext/events2/Templates/
partialRootPath = fileadmin/templates/ext/events2/Partials/
layoutRootPath = fileadmin/templates/ext/events2/Layouts/
}
}ViewHelpers are used to add logic inside the view. There basic things like if/else conditions, loops and so on. The system extension fluid has the most important ViewHelpers already included.
To be able to use a ViewHelper in your template, you need to follow always the same structure which is:
<f:fo>bar</f:fo>This would call the ViewHelper fo of the namespace f which stands for fluid. If you want to use ViewHelpers from other extensions you need to add the namespace declaration at the beginning of the template. The namespace declaration for the events2 extension is:
{namespace e2=JWeiland\Events2\ViewHelpers}Now you can use a ViewHelper of events2 with a code like:
<e2:trimExplode><!-- some comment --></e2:trimExplode>If you want to know what a ViewHelper does, it is very easy to find the related PHP class by looking at the namespace and the name of the ViewHelper.
Having e.g. JWeiland\Events2\ViewHelpers and convertToJson you will find the class at events2\\Classes\ViewHelpers\\ConvertToJsonViewHelper.php.
The most of awesome thing is that you can use ViewHelpers of any extension in any other template by just adding another namespace declaration like:
{namespace something=OtherNamespace\OtherExtension\ViewHelpers}and call the ViewHelper like
<something:NameOfTheViewHelper />We have some JS in events2 to search for Sub-Categories and other various Ajax-Calls. To handle them we add some environment specific variables to template like host name, current storage PIDs and TS settings.
You can use this VH to convert an array into JSON format to have variables in a better accessible format for JavaScript.
<div class="events2calendar" data-environment="{environment->e2:convertToJson()}"></div>It searches the given link for Youtube ID and attaches the ID to the embedded Youtube Link.
Link: https://www.youtube.com/watch?v=B5gDI2h0F20 Youtube ID: B5gDI2h0F20 Embedded link: //www.youtube.com/embed/B5gDI2h0F20
<iframe width="560" height="315" src="{e2:createYoutubeUri(link: event.videoLink.link)}" frameborder="0" allowfullscreen></iframe>Ok, following scenario: You have an events2 Plugin where you have selected the categories house and tree. Further you have an event which is assigned to the categories performance, cinema and tree. Of cause this event will be shown in Frontend, because category tree matches.
BUT: If you want to show the first possible category in Frontend, it is possible that performance will be shown, which is not allowed by the Plugin.
This ViewHelper creates an intersection of both category selections which contains the allowed categories only.
<f:for each="{e2:getAllowedCategories(event: event, pluginCategories: settings.categories)}" as="category" iteration="iterator">
<f:if condition="{iterator.isFirst}">{category.title}</f:if>
</f:for>In case of recurring events you can have multiple exception types like add, remove, info and time. Each of these exceptions are related to a specific date.
With this ViewHelper you can get all exceptions for a specific date. Further you can select, if you want all exceptions or only exceptions of a specific exception type.
<f:for each="{e2:getExceptionsFromEventForSpecificDate(event: day.event, date: date, type: 'add,time,info')}" as="exception">
<em>{exception.exceptionDetails -> f:format.html(parseFuncTSPath: 'lib.parseFunc') -> f:format.nl2br()}</em>
</f:for>For each event you can create a general time record, multiple time records for same day, different time records for each weekday and you can create a different time records for a specific date as exception.
As you see it's hard to see with time record is valid, which has priority and which time record has which sorting.
With this ViewHelper you only set an event and a date (DateTime) and you will get the correct time record(s) as array.
<f:alias map="{times: '{e2:getMergedEventTimes(event: day.event, date: date)}'}">
<f:for each="{times}" as="time">
<f:render section="showDateAndTime" arguments="{day: day, date: date, time: time}" />
</f:for>
</f:alias>Instead of looping all exceptions for a specific day in Fluid Template and check if there is an exception of type remove we have created this ViewHelper. Just give it an event and a date (DateTime) and you will know, if this event was canceled for specifix date.
<strong>
{f:if(condition: '{e2:isDateMarkedAsCanceled(event: day.event, date: date)}', then: '<s>')}
{date->f:format.date(format: '%A, %d.%m.%Y')}
{f:if(condition: '{e2:isDateMarkedAsCanceled(event: day.event, date: date)}', then: '</s>')}
</strong>In earlier versions of events2 some day records are wrong because of problems with daylight saving times. In the
meantime we have solved that problem and created a repair command whose name is now rebuild.
If you expect still some problems in day generation, it may make sense to execute this command or, if you want to cleanup day table in general. If your day table is very big, it may make sense to exclude this table from SQL export/migration. On target project/server you just need to execute this command to re-build all missing day records again.
Since events2 version 8.0.0 this CLI command is also schedulable (can be configured in scheduler module).
Tip
Instead of the scheduler task Re- this command will additionally TRUNCATE the complete day table!
Important
As day table will be TRUNCATED it is possible that there are temporarily no events in frontend visible!
events2 uses the Simple from TYPO3 Core to navigate through
your records with first, previous, next and last buttons. If
you need something more complex like 1, 2 ... 56, 57, 58 ... 123, 124 you
should use another pagination library or build your own one. In the next steps
I explain you how to implement the numbered_pagination solution
of Georg Ringers.
Install numbered_
Install and activate numbered_ extension from Georg
Ringer. Please check in your SitePackage extension that
numbered_ is set as a dependency and will be loaded
before events2 and your SitePackage.
Change pagination class in TypoScript
plugin.tx_events2.settings.pageBrowser.class = GeorgRinger\NumberedPagination\NumberedPaginationChange path to events2 partials
Set constant partial to a location within your SitePackage:
plugin.tx_events2.view.partialRootPath = EXT:site_package/Resources/Private/Extensions/Events2/Partials/Create Pagination template
Create file Resources/
with example content from numbered_pagination
https://github.com/georgringer/numbered_pagination/blob/master/Resources/Private/Partials/Pagination.html
<html lang="en"
xmlns:f="http://typo3.org/ns/TYPO3/CMS/Fluid/ViewHelpers"
data-namespace-typo3-fluid="true">
<ul class="f3-widget-paginator">
<f:if condition="{pagination.previousPageNumber} && {pagination.previousPageNumber} >= {pagination.firstPageNumber}">
<li class="previous">
<a href="{f:uri.action(action:actionName, arguments:{currentPage: pagination.previousPageNumber})}" title="{f:translate(key:'pagination.previous')}">
{f:translate(key:'widget.pagination.previous', extensionName: 'fluid')}
</a>
</li>
</f:if>
<f:if condition="{pagination.hasLessPages}">
<li>…</li>
</f:if>
<f:for each="{pagination.allPageNumbers}" as="page">
<li class="{f:if(condition: '{page} == {paginator.currentPageNumber}', then:'current')}">
<a href="{f:uri.action(action:actionName, arguments:{currentPage: page})}">{page}</a>
</li>
</f:for>
<f:if condition="{pagination.hasMorePages}">
<li>…</li>
</f:if>
<f:if condition="{pagination.nextPageNumber} && {pagination.nextPageNumber} <= {pagination.lastPageNumber}">
<li class="next">
<a href="{f:uri.action(action:actionName, arguments:{currentPage: pagination.nextPageNumber})}" title="{f:translate(key:'pagination.next')}">
{f:translate(key:'widget.pagination.next', extensionName: 'fluid')}
</a>
</li>
</f:if>
</ul>
</html>Clear Cache
Needed to reload the fluid templates.
This chapter describes some best practice concepts
Events2 has a built-in mechanism that takes care of clearing the cache after manipulation of Event records.
When a list or detail view is rendered on a page, a cache tag in format tx_events2_pid_PID (where PID is
the uid of the events storage folder) is added. Each time an event record is edited, deleted or created, this
cache entry is flushed. No additional cache configuration is needed if only the Event plugins are used.
If you use other ways of displaying event records, the cache is not flushed automatically.
This can be done automatically by using this command in the PageTsConfig:
TCEMAIN.clearCacheCmd = 123,124,125The code needs to be added to the sys folder where the event records are edited. Change the example page ids to the ones which should be cleared.
In normal case you only will see something like "detail view" in title of detail page. If you want to change that title to current events title incl. its date you can make use of the new TYPO3 page-title providers (since TYPO3 9.4). Luckily events2 comes with its own provider to realize a pretty nice detail page-title for you with following TypoScript:
config.pageTitleProviders {
events2 {
provider = JWeiland\Events2\PageTitleProvider\Events2PageTitleProvider
# Please add these providers, to be safe loading events2 provider before these two.
before = record, seo
}
}If you upgrade/update EXT:events2 to a newer version, please read this section carefully!
Because of the new column def_ in tx_
you will get various duplicate event records in your list views. Please
execute the command events2: after the update to fix this issue!
settings.selectableCategoriesForNewEvents settings.new.selectableCategoriesForNewEvents . If you have defined
that setting in management plugin please execute the events2 upgrade wizard.Because of missing uniqueness while generating path segments for imported event records we had to update the constructor arguments of GeneratePathSegmentEvent. First argument has be be array of parameters we get from SlugHelper->generate and second argument is the SlugHelper itself.
We have marked the FeUser ViewHelper as deprecated. As a replacement for
access restrictions there is a new Access catching
invalid requests. You should update your own templates accordingly.
Because of an "edit" and "activate" linking problem in information mail, we
had to store the event non-hidden in database first and had to hide the event
after the mailing in a second step. Else the event slug can not be added to
route enhancer. Please make sure that your own modifications
to plugin. configuration is still
working.
There is a new Persisted available to allow generating
slugs to hidden event records. Needed for info mails.
Events2Management:
type: Extbase
extension: Events2
plugin: Management
routes:
- routePath: '/events/m/lme'
_controller: 'Management::listMyEvents'
- routePath: '/events/m/p'
_controller: 'Management::perform'
-
routePath: '/event/m/p/{event_title}'
_controller: 'Management::perform'
_arguments:
event_title: event
-
routePath: '/event/m/a/{event_title}'
_controller: 'Management::activate'
_arguments:
event_title: event
defaultController: 'Management::listMyEvents'
aspects:
event_title:
type: PersistedHiddenAliasMapper
tableName: tx_events2_domain_model_event
routeFieldName: path_segmentWe render our own template for error which results in much nicer
flash messages output. Please be prepared to override them accordingly.
This version is NOT compatible with TYPO3 10 and TYPO3 11 anymore.
We have upper case first char of all fluid sections <f:.
Please make sure to adopt that in your extending templates.
There is an UpgradeWizard to convert s in FlexForms to s, but
with each update of an events2 plugin s was written to DB again. We
have updated that page name to s in our FlexForms, now. Please execute the
UpgradeWizard again.
This version is NOT compatible with PHP versions lower than 7.4!
We have updated over 10.000 lines of code. Please click the flush cache button in installtool.
As switchable are deprecated since TYPO3 11 we have migrated them to individual plugins.
Please execute UpgradeWizard events2Move to migrate existing plugins. Please backup your project
before executing this Wizard!
With this change we have migrated all list*Actions into one listAction. Please have a look into our templates and add the missing conditions to your templates.
We have renamed EventController to ManagementController. So please rename the templates accordingly.
We have split the SearchController into SearchForm- and SearchResultController. So please rename the templates accordingly.
Fluid widget functionality was completely removed in TYPO3 11.
Instead of ICal please use link to action of our new ICalController:
<f:link.action action="download" controller="ICal" target="_blank" arguments="{dayUid: day.uid}">
{f:translate(key: 'export')}
</f:link.action>Instead of Poi in Location/Show.html please migrate to:
<f:render partial="Maps2/PoiCollection"
section="showMap"
arguments="{poiCollections: {0: location.txMaps2Uid}, override: {settings: {mapWidth: '100%', mapHeight: '300', zoom: '14'}}}" />and check, if path to EXT:maps2 partial still matches your needs:
plugin.tx_events2.view.partialRootPaths.2 = EXT:maps2/Resources/Private/Partials/We have removed the use of jquery and migrated all code to VanillaJS. So please check
page. and page. if they are matching the needs of your project.
As f:widget.paginate is deprecated and POST requests are not allowed anymore in this widget, we have migrated the f:widget.paginate widget to new TYPO3 Pagination API.
Please remove the f:widget.paginate from Templates and insert this code:
<f:render partial="Component/Pagination"
arguments="{pagination: pagination, paginator: paginator, actionName: actionName}" />Nearly all Controller Actions contains a call to the new TYPO3 EventDispatcher now. That way we have moved a lot of logic of the event controllers into EventListeners. All Extbase SignalSlot have been removed.
The Action listSearchResults was moved from event controller into day controller. Please move
your own ListSearchResults template from Event into Day folder and update controller name
in Search/Show.html:
<input type="hidden" name="tx_events2_events[controller]" value="Day" />
All deprecated methods and version_compare lines have been removed.
edit action is defined as uncached in ext_localconf.php now.
You have to remove existing Re-Generate tasks from scheduler and create them again. That's because of changed contructor arguments.
It is now possible to assign multiple organizers to an event record. That's why we have added a new MM table
and a new column organizers which has to be created by Analyze database button in Installtool. Please
execute events2 upgrade wizard to migrate all current relations into this new table. If UpgradeWizard was
executed successfully you can remove the old organizer column.
Please update following parts in your templates:
<f:if condition="{e2:feUser(field: 'tx_events2_organizer')} == {event.organizer.uid}">to
<f:if condition="{event.isCurrentUserAllowedOrganizer}">We have changed the column detail_ of event table to detail_. Please execute
UpgradeWizard to move all data into this new column. Old calls to getDetailInformations are still possible but
deprecated and removed with events2 7.0.0.
In XSD file for XML import we have changed organizer to organizers. Please update your XML file generation
or load an old XSD file in Extension Settings of Installtool. But with 7.0.0 we will not support the old
organizer property while XML import anymore.
We have changed the keys for various used hooks from incremented numbered to string based keys in ext_localconf.php. As a developer you should check, if your own implementation is still working.
We have changed some method arguments, please flush cache in InstallTool
We have changed data type of country to INT in DB. Please start compare database in INstalltool.
With events2 6.0.0 we have removed TYPO3 8 compatibility and add TYPO3 10 compatibility. We have not added any new features.
Because of incompatibility we have created a new pageTitleProvider as replacement for pageTitleUserfunc.
With this release we have implemented a better multilingual support. We are not done, but as long as DayGenerator still has problems with languages we have marked a lot of fields in translated events as readonly.
If you use events2 with one language only, there is no problem to upgrade to 5.0.0.
With version 4.1.0 we have added the path_segment for slugs in event records, but first with version 4.1.1 we have added the Updater for this field. Please visit InstallTool and execute the updater for Slugs in event records.
If you don't use the event2 API or you don't use your own XmlImporter an Update shouldn't be a problem for you.
We have modified findHiddenEntryByUid to findHiddenEntry in AbstractController. With the new argument
you can now select hidden records by any property you want.
We have added a lot of strict_types. Please check your extension code accordingly, if you have modified events2.
We have added Task object as second argument to constructor of AbstractImporter. Therefor we have removed
all arguments of importer method of XmlImporter.
Method initialize is not required by ImporterInterface and will not be called anymore. Please move initialization
process into Constructor directly.
New Feature: We have added 3 new getters to Time object:
These are very helpful as you now can format them with f:format.date() VH
With version 3.3.1 we have added a new column same_day_time to day table. It helps us to GROUP BY days with
multiple time records for one day, if mergeEventsAtSameDate is set in plugin.
Please update DB in Installtool and start scheduler task to re-generate all day records.
With version 3.2.0 we have completely rewritten DayRepository to work with Doctrine/Core QueryBuilder now. We have added functional tests to be sure to have same results as in previous versions.
We have renamed mergeEvents checkbox in FlexForm to mergeRecurringEvents. Maybe you have to reactivate that checkbox.
In previous versions we have grouped events in ListLatest view automatically for you. Now you have to manual activate mergeRecurringEvents to group them.
We have moved static TypoScript to another location. Please use update wizard in ExtensionManager to update paths.
We have removed mergeEvents option from ExtensionManager. If you have set this option please re-create your records with CLI or scheduler task.
With version 3.1.0 we have made a little but breaking change:
In earlier versions you may have done:
<f:form.textarea class="form-control addRemainingCharsCheck" id="teaser" property="teaser" rows="5" cols="50" />
This will not work anymore, as it would be very hard for integrator to place the container for remaining chars correctly. Please change this part to:
<div class="form-group row">
<div class="col-sm-4"></div>
<div class="col-sm-8">
<span class="remainingChars" data-id="teaser"></span>
</div>
</div>Use data-id to relate it to a textarea id-attribute.
In previous versions we had the problem, that an added day as exception will never be of type Day. It is of type Exception with different properties then a Day, which made us many headaches in Fluid-Templates. In GetDateTime VH we had streamlined Day and Exception records into an array which contains all needed information. You can't control and you may not understand how this array was build. With version 2.4.0 we have solved this problem and simplified Fluid template a lot. Instead of modifying the DB tables and models we have reduced some method-calls down to the DateTime representation of Day and Exception records:
So, please check your own extensions, if you make use of these methods. To solve the problem from above, we have implemented two new ViewHelpers. Please have a look into our new templates and update your own templates to the new structure:
Event property download_ can now collect more then one link. Please update DB in Installtool and clear
system caches.
Now you can create events with a recurring of one or more months.
We have removed all methods to get time records for an event from DayRelationService as we have all these methods in EventService already.
Version 2.4.0 is now TYPO3 9 compatible. We also have removed compatibility to TYPO3 6 and 7.
With version 2.3.0 we have rewritten the frontend Events2.js completely. Now it it much more readable and it prevents executing JavaScript, if it is not valid for current view. That's why we have some changes in our templates:
We have removed TypoLinkCodecService as it was only needed by our own TypoLink VH and is part of TYPO3 since TYPO3 7.*.
Organizer and Location are not required anymore by default. If you still need them required go into ExtensionManager and set them as required. This change results into some further changes to our templates:
We have moved all email settings in ExtConf to new tab "Email"
EXT maps2 is not a hard-coded dependency to events2 anymore, but we still suggest it in ext_emconf.php.
Version 2.0.0 will come with some new cols and we have removed some cols. So please be careful while comparing database with TCA definition after upgrading.
Important
Please do not delete cols in InstallTool after installing the new version! Only add the new fields, than go into Extensionmanager, select events2 and start the upgrade script. Delete the old cols in InstallTool only, if the upgrade script symbol will not appear in Extensionmanager anymore.
We have removed ShowEventDatesViewHelper, because it was sometimes too hard to change that template. So we have moved that widget into a normal ViewHelper. Please use GetEventDatesViewHelper instead, you can find an example in Partials/Event/Properties.html.
In case of our new database structure we have removed our e2:widget.paginate ViewHelper. Please update all templates to use the original f:widget.paginate ViewHelper of fluid and maybe remove the maxRecords attribute.
The labels of the show action selectbox in Plugin (switchableControllerActions) has changed. We have added the new action showByDate for DayController. So you have to open each plugin and set show action again.
After all these changes you have to re-create all day records. The easiest way to do so is: Create scheduler task of type "Create/Update Days" if not already exists. Execute that task.
We have removed our own TypoLink ViewHelper as it is not needed anymore since TYPO3 7.6. Please change all e2:link.typolink VHs of your templates into f:link.typolink.
If you translate an event into a new language, events2 will not create day records for this language. That's because
you may have changed the event_ of an event. In that case events2 can not associate a day record of
default language to day records of the translated record. As a solution we have disabled the translation feature
for day table completely.
This approach has one disadvantage:
You currently can't search for translated events in frontend search.
We build the day records while saving an event record in backend. Further we re-build them while executing
the scheduler task Re- and while executing the command events2:.
No. Currently you have to create your own export mechanism. But as we have implemented such a solution already for one of our customers you can ask us at: projects@jweiland.net
Yes. But currently only XML files are allowed. Please add Scheduler Task Import events and set a filepath
to import. Examples of XML files are available at https://github.com/jweiland-net/events2/tree/main/Tests/Functional/Fixtures/XmlImport.
We will validate the imported file against configuration in EXT:.
All errors will be logged in a Messages. in same directory of imported XML file.
In Extbase a link will be created by its Plugin Namespace like tx_events2_calendar or tx_events2_list. As we have
designed plugin Search form as its own Plugin it will only react and build links based on plugin
namespace tx_. But this is a problem. To build correct links within the search results plugin
which should be compatible with our events2 list Plugin we have to change its plugin namespace to tx_.
That's why we set the plugin namespace of search results plugin back to namespace of events2 list plugin:
plugin.tx_events2_searchresults.view.pluginNamespace = tx_events2_listWe prefer to not change that value.
If you need the image rights from the uploader for uploaded images you should install EXT:checkfaluploads and add following line into FormFields template:
<f:form.checkbox value="1" name="event[images][{index}][rights]" checked="" />In our TypeConverter we check for installed checkfaluploads and add an error message, if checkbox was not activated
If you want to delete an image, you can add following line into FormFields template:
<f:form.checkbox value="1" name="event[images][{index}][delete]" checked="" />This version adds TYPO3 13 compatibility with various improvements and modernizations.
Note: This version requires TYPO3 13 LTS and drops support for previous TYPO3 versions. If you need TYPO3 12 LTS compatibility, please use events2 version 9.x
settings.selectableCategoriesForNewEvents settings.new.selectableCategoriesForNewEvents This is just a plain upgrade without any new features