Upgrade 

Update to Version 11.1.0 

Mail security scanners and link previews (e.g. Microsoft Safe Links) open the links of a mail automatically. Before this version, the activation link of the notification mail activated the event with a simple GET request. Further, every owner of an event was able to activate his own event and bypass the moderation.

The activation link opens the new action confirmActivation of the Management plugin now. It shows a summary of the event and a button, which activates the event via POST. The links are signed with a moderationToken. confirmActivation and activate are allowed with a valid moderationToken or for backend administrators only. The token signs the event UID and stays valid until the event was deleted.

Activation links of mails sent before this update do not contain a moderationToken. They are denied, unless they are opened by a backend administrator logged in into the backend.

<f:link.action pageUid="{settings.pidOfManagementPage}"
               action="confirmActivation"
               controller="Management"
               absolute="1"
               arguments="{event: event, moderationToken: moderationToken}">
    Datensatz freischalten
</f:link.action>

{namespace e2=JWeiland\Events2\ViewHelpers}

<f:variable name="event">{finisherVariableProvider.SaveEvent.insertedUids.tx_events2_domain_model_event}</f:variable>
<f:variable name="moderationToken">{e2:moderationToken(event: event)}</f:variable>

<f:link.action pageUid="{pidOfManagementPage}"
               action="confirmActivation"
               controller="Management"
               extensionName="Events2"
               pluginName="Management"
               absolute="1"
               arguments="{event: event, moderationToken: moderationToken}">
    Datensatz freischalten
</f:link.action>

-
  routePath: '/event/m/c/{event_title}'
  _controller: 'Management::confirmActivation'
  _arguments:
    event_title: event

Update to Version 11.0.0 

This version contains breaking changes. The images of the event form of the Management plugin are uploaded with the file upload handling of Extbase now. The own type converter for uploads has been removed. Please go through all steps below, if you use the Extbase based event form of the Management plugin or have extended the event model.

The form based on EXT:form (site setting events2.form.useExtForm with NewEvent.form.yaml) is not affected by this change.

<html xmlns:cfu="http://typo3.org/ns/JWeiland/Checkfaluploads/ViewHelpers"
      data-namespace-typo3-fluid="true">

<f:form.checkbox property="images.rights" id="imageRights" value="1"/>
<label for="imageRights"><cfu:imageRightsMessage/></label>

Update to Version 10.2.4 

Due to an issue in the DayRecordService, records in the day table that use enable fields, such as hidden, starttime, or endtime, were not removed when new day records were generated for a given event. As a result, the day table grows significantly with each execution of the Re-Create day records scheduler task.

After updating to version 10.2.4, please run the TYPO3 command events2:rebuild.

If you are not familiar with the CLI, you can alternatively truncate the tx_events2_domain_model_day table and then run the Re-Create day records scheduler task again.

Update to Version 10.0.0 

Because of the new column def_lang_event_uid in tx_events2_domain_model_day you will get various duplicate event records in your list views. Please execute the command events2:rebuild after the update to fix this issue!

Update to Version 9.1.9 

We have moved TypoScript setting settings.selectableCategoriesForNewEvents

into settings.new.selectableCategoriesForNewEvents. If you have defined that setting in management plugin please execute the events2 upgrade wizard.

Update to Version 9.0.8 

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.

Update to Version 9.0.4 

We have marked the FeUser ViewHelper as deprecated. As a replacement for access restrictions there is a new AccessRightsEventListener 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.tx_events.settings.overrideForm.finishers.* configuration is still working.

There is a new PersistedHiddenAliasMapper 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_segment

We render our own template for errorAction which results in much nicer flash messages output. Please be prepared to override them accordingly.

Update to Version 9.0.0 

This version is NOT compatible with TYPO3 10 and TYPO3 11 anymore.

We have upper case first char of all fluid sections <f:section name="Date">. Please make sure to adopt that in your extending templates.

Update to Version 8.3.2 

There is an UpgradeWizard to convert sDEFAULT in FlexForms to sDEF, but with each update of an events2 plugin sDEFAULT was written to DB again. We have updated that page name to sDEF in our FlexForms, now. Please execute the UpgradeWizard again.

Upgrade to Version 8.0.0 

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.

<f:link.action action="download" controller="ICal" target="_blank" arguments="{dayUid: day.uid}">
  {f:translate(key: 'export')}
</f:link.action>

<f:render partial="Maps2/PoiCollection"
          section="showMap"
          arguments="{poiCollections: {0: location.txMaps2Uid}, override: {settings: {mapWidth: '100%', mapHeight: '300', zoom: '14'}}}" />

plugin.tx_events2.view.partialRootPaths.2 = EXT:maps2/Resources/Private/Partials/

Update to Version 7.1.0 

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}" />

Upgrade to Version 7.0.0 

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.

Update to Version 6.3.0 

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_informations of event table to detail_information. 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.

Update to Version 6.2.6 

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.

Update to Version 6.2.4 

We have changed some method arguments, please flush cache in InstallTool

Update to Version 6.1.1 

We have changed data type of country to INT in DB. Please start compare database in INstalltool.

Upgrade to Version 6.0.0 

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.

Upgrade to Version 5.0.0 

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.

Update to Version 4.1.1 

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.

Upgrade to Version 4.0.0 

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.

Update to Version 3.7.0 

New Feature: We have added 3 new getters to Time object:

• getTimeEntryAsDateTime
• getTimeBeginAsDateTime
• getTimeEndAsDateTime

These are very helpful as you now can format them with f:format.date() VH

Update to Version 3.3.1 

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.

Update to Version 3.2.0 

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.

Update to Version 3.1.0 

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.

Upgrade to Version 3.0.0 

• We have removed GetEventDates VH and implemented a completely new way to get future event dates.
• We have removed MicroStart VH
• We have removed MicroStop VH
• We have removed Sort VH, as sorting in VH is always a bad idea.

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:

• Renamed EventService::getSortedTimesForDay to EventService::getSortedTimesForDate * Property $day changed from type Day to DateTime
• Renamed EventService::getDifferentTimesForDay to EventService::getDifferentTimesForDate * Property $day changed from type Day to DateTime
• Renamed EventService::getTimesForDay to EventService::getTimesForDate * Property $day changed from type Day to DateTime
• Renamed EventService::getExceptionsForDay to EventService::getExceptionsForDate * Property $day changed from type Day to DateTime

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:

• New VH: GetExceptionsFromEventForSpecificDate
• New VH: IsDateMarkedAsCanceled

Event property download_links 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.

Update to Version 2.4.0 

Version 2.4.0 is now TYPO3 9 compatible. We also have removed compatibility to TYPO3 6 and 7.

Update to Version 2.3.0 

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:

• Remove all siteId variables. Please use {data.pid} instead
• Remove all jsSearchVariables. They are now all available in just jsVariables
• All jsVariables are removed from Templates and Partials and has to be in all Layout file now
• The <div> for remainingChars has been removed as it will be created dynamically with JS now
• CSS class addRemainingCharsCheck activates max chars feature for textareas automatically
• The <span> for locationStatus has been removed as it will be created dynamically with JS now
• Change CSS class powermail_input to form-control in Event/FormFields Partial
• Move records for selectboxes in search plugin from {data} to {selectorData}
• Make data with current tt_content record available in jsVariables, too.
• We have added two more Layouts. Please adjust the new path in your 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:

• Add if to render section "location" only if a location is available
• Add if to render section "googleRoute" only if a location is available
• Add if to render section "organizer" only if a organizer is available
• Add if to location to prevent rendering footer for each event in list
• Move <p>-Tag, for editing your own records in FE, inside of the if
• Add if to organizer and location in Create.html
• Add if to organizer and location in Update.html

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.

Upgrade to Version 2.0.0 

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.

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.