Free public support 

Free public support is available on the #ext-sf_event_mgt TYPO3 Slack Channel.

Please also check the FAQ section of this documentation. New articles are added on a regular basis.

Paid Services and Support 

I also offer the following paid services:

• Personal support by email, phone, remote session or on site
• Installation and configuration for the extension
• Integrating new feature to the main extension (sponsors can be named - see Say thanks)
• Priority Bug fixes
• Developing extensions, that extend sf_event_mgt with unique features/requirements

Please contact me by email and ask for prices.

Thanks from me to: 

• Georg Ringer for his extension "news", from where I adapted some concepts and code I use in this extension
• Alexander Kellner for his extension "powermail", from where I adapted some concepts and code I use in this extension
• Thies Kracht who developed the CSV export
• Phat Hoang and Oleksandr Bachynskyi from Pixelant AB for their ideas and contributions
• Phat Hoang from Pixelant AB for the reCAPTCHA implementation
• Jean-François Sillen from Wikafi S.P.R.L for sponsoring the sys_category refactoring
• Jean-François Sillen from Wikafi S.P.R.L for sponsoring the price option feature
• W52 MarketingKommunikation GmbH for sponsoring the waitlist, user registrations frontend plugin and email attachments
• New Communication GmbH & Co. KG for sponsoring and ideas
• Tymoteusz Motylewski for implementing event speakers and other contributions
• Gerd Müller from Vogt-Schild Druck AG for sponsoring organisator filtering
• Alexander Grein from Mediaessenz for implementing the default storage Pid feature
• Bernhard Sirlinger for adding the automatic RealURL config
• Marc Bastian Heinrichs for adding Cache Tags in list and detail view and for implementing the checkPidOfEventRecord setting
• Rune Piper for several code cleanups and Pull Requests
• Haisam Zehrawi from SeminarPool GmbH for sponsoring refactoring in the CSV export
• Stefano Kowalke for several Pull Requests
• Manuel Munz for adding additional registration fields
• Christoph Lehmann for several Pull Requests
• Christoph Lehmann from networkteam GmbH for sponsoring the backport of user generated content in custom notifications.
• Der PARITÄTISCHE Wohlfahrtsverband Hamburg e.V. for sponsoring the GDPR clean command
• mediaconcept GmbH for sponsoring the metadata feature for events

General 

The general tab is used to add general information about the event like a title, start- and enddate and a description.

Additional 

The additional tab contains additional fields for the event like price, location, organiser, link and program/schedule.

Relations 

The relations tab contains fields which holds relations locations, organisators and related events.

Media 

The media tab contains fields which holds media-data for the event.

Categories 

You can assign one or multiple categories to an event.

Registration Options 

For each event, it is possible to enable registration and to limit the amount of free places, so only a limited amount of people can participate to the event. It is also possible to allow the user to create multiple registrations at once, if the field "Max. simultaneous registrations per user" is set to a value greater than 1.

Registrations 

Contains all registrations for the event. Only visible, when registration is enabled.

Metadata 

Contains fields related to meta tags

General 

The general tab contains personal data about the participant, who registered to the event

Additional 

The additional tab contains additional data about the registration

Registration field values 

The registration fields tab contains all submitted registration field values.

Payment 

The payment tab contains information about payment of the registration

Available actions 

The backend module contains 5 actions in the upper left.

• The first 4 actions creates new items (event, location, organisator, speaker)
• The last action does the same as the cronjob, it hides/removes expired registrations

CSV export 

With the backend module, you can export a list of participants for events, which are enabled with the registration option. If the list of fields exported does'nt fit your needs, you can adjust the fields in the module TypoScript settings as described in the configuration section of this extension.

Sending custom notification 

For events which are enabled with the registration option, you can also send custom email notification to the participants of the event. Press the "+" icon to get to the view, where you can select the custom notification template.

If you want to create a custom notification, you just need to add some TypoScript and a Fluid template for the new custom notification. Please refer to the manual in the administration section of this extension.

Tab settings 

Tab additional 

Tab template 

Tab notification 

Tab category menu 

Settings 

Nearly all important settings can be made through the plugin, which override the settings made with TypoScript. All plugin settings can also be configured with TypoScript (use plugin.tx_sfeventmgt.settings. with the keys shown below).

plugin.tx_sfeventmgt 

module.tx_sfeventmgt 

Property:	Data type:	Description:	Default:
settings.csvExport.fields	String	Comma seperated list of fields to include in CSV export. Please note, that you must write the property names of the fields to export (e.g. firstname, lastname, dateOfBirth, event.title) In order to export the values of registration fields, use "registration_fields" as fieldname. Note, that it is only possible to export all registrations fields at once.	uid, gender, firstname, lastname, title, company, email, address, zip, city, country, registration_fields
settings.csvExport.showFlashMessageForInsufficientAccessRights	Boolean	If switched on, a warning message is shown in the backend module, when a backend user does not have read/write access rights to the temp-folder of the default storage.	true
settings.csvExport.fieldDelimiter	String	Comma seperated list delimiter	,
settings.csvExport.fieldQuoteCharacter	String	Comma seperated list quote character	"
settings.csvExport.prependBOM	Boolean	Prepend UTF-8 BOM to export. Switch this setting on, of you have problems when opening the exported CSV file with Microsoft Excel	false
settings.list.itemsPerPage	Integer	Number of items to show per page in backend module	10
settings.search.dateFormat	String	Date format for search fields in backend module	d.m.Y H:i
settings.search.fields	String	Fields to be included in a query from the backend module	title, teaser
settings.notification.senderEmail	String	E-mail address for emails sent to user	Empty
settings.notification.senderName	String	Sender name for emails sent to user	Empty
settings.notification.senderSignature	String	Signature shown in emails sent to user	Empty
settings.notification.customNotifications.{templatename}	String	Name of custom notification template. Custom notifications can be sent to all registered participants of an event in the administration module. Example for default custom notification Each custom notification must include a title, a template and a subject Please refer to the default custom notitication for setup example.	thanksForParticipation
settings.enabledActions.notify	Boolean	If set to "1", the Notify-Action / Icon is shown for events with registration enabled.	1 (true)
settings.enabledActions.export	Boolean	If set to "1", the Export-Action / Icon is shown for events with registration enabled.	1 (true)

Plugin: Events and event-registration 

Plugin: Events and event-registration - FE user registrations 

Event 

The Event-Object has the following special getters

PrefillViewHelper 

This viewhelper prefills fields in the registration form with values from fe_users.

prefillFields {
  firstname = first_name
  lastname = last_name
  customfields = custom_field_feuser
}

Uri.PageViewhelper 

This viewhelper does exactly the same as f:uri.page, but this viewhelper builds frontend links with buildFrontendUri(), so links to FE pages can get generated in the TYPO3 backend.

This viewhelper can be used in email templates for custom notifications, when you want to link to a given page in you TYPO3 website.

Example:

<e:uri.page pageUid="4" additionalParams="{tx_sfeventmgt_pieventdetail:{event: registration.event, action: 'detail', controller: 'Event'}}" absolute="1"/>

Uri.OnlineCalendar 

This viewhelper renders a link which will add the given event to an online calendar of either Google, Outlook, Office 365 or Yahoo.

Available types:

• google
• outlook
• office365
• yahoo

Example:

<e:uri.onlineCalendar type="google" event="{event}" />

Event.SimultaneousRegistrationsViewHelper 

This viewhelper renders an array of possible simultaneous registration for the given event. The viewhelper respects the max. amount of simultaneous registrations per user and also respects the amount of remaining participants for the event.

The index of the array returned starts with 1, so the resulting array can be used directly in the f:form.select viewhelper.

Example:

<f:form.select id="amountOfRegistrations" property="amountOfRegistrations" options="{e:event.simultaneousRegistrations(event: '{event}')}" />

Format.ICalendarDateViewHelper 

Formats the given DateTime object according to rfc5545, so it can be used in the iCalendar view

Format.ICalendarDescriptionViewHelper 

Formats the given string according to rfc5545, so it can be used in the iCalendar view

Registration.Hmac 

Must be used, when the plugin Frontend user registrations is used and it should be possible for users to cancel registrations (if configured in event). See usage in UserRegistration templates.

Registration.IsRequiredField 

Can be used to show content, if a field or registration field is configured as required. See usage in Registration template and registration field partials.

Example:

<e:registration.isRequiredField settings="{settings}" fieldname="lastname">
    <span class="event-required">*</span>
</e:registration.isRequiredField>

Validation.ErrorClass 

Can be used to show a string, when a given field or registration field has validation errors See usage in Registration template and registration field partials.

Example:

<e:validation.errorClass fieldname="email" class="my-custom-class" />

Title 

Use this viewhelper to set the page title and indexed search title on event-detail and -registration pages.

Example:

<e:title pageTitle="{event.title}" indexedDocTitle="A custom title for indexed search"/>

Category.Count 

Can be used to get the amount of events per category.

Example:

<e:category.count categoryUid="{category.uid}" />

MetaTag 

Use this viewhelper to add various meta tags related to the event. The default template for the event detail view uses this viewhelper to output the meta tags "keyword", "description" and "og:title".

Example:

<e:metaTag name="keywords" content="{event.metaKeywords}" />

Filter by category 

The following code snippet shows a list of links which restrict the category to be shown to the given category:

<f:for each="{categories}" as="category">
    <f:if condition="{overwriteDemand.category} == {category.uid}">
        <f:then>
            <f:link.action action="list" controller="Event" arguments="{overwriteDemand:{category: category}}" class="active">{category.title}</f:link.action>
        </f:then>
        <f:else>
            <f:link.action action="list" controller="Event" arguments="{overwriteDemand:{category: category}}">{category.title}</f:link.action>
        </f:else>
    </f:if>
</f:for>

As all links are generated using the f:link.action viewHelper, they are fully cached.

Filter by special location properties 

It is possible to filter events by the location city and country. Using the overwriteDemand parameter is as following:

<f:link.action action="list" controller="Event" arguments="{overwriteDemand:{locationCity: 'Hamburg'}}">Show all events in Hamburg</f:link.action>

<f:link.action action="list" controller="Event" arguments="{overwriteDemand:{locationCountry: 'Germany'}}">Show all events in Germany</f:link.action>

Filter by year, month and/or day 

It is possible to filter events by a specific year, month or day. Using the overwriteDemand parameter is as following:

<f:link.action action="list" controller="Event" arguments="{overwriteDemand:{year: '2017'}}">All events in 2017</f:link.action>

<f:link.action action="list" controller="Event" arguments="{overwriteDemand:{year: '2017', month: '10'}}">All events in october of the year 2017</f:link.action>

<f:link.action action="list" controller="Event" arguments="{overwriteDemand:{year: '2017', month: '10', day: '1'}}">All events on the 1st of october 2017</f:link.action>

The filtering also respects events, which are in between the given filter criteria. If you for example set the filter option to filter events for the 2st of october 2017, then also an event will be shown, that start at the 1st of october and ends at the 3rd of october.

Cleanup expired registrations 

Only needed if you use registrations for events

If a new participant registers to an event, the participant must confirm the registration in a given timeframe (default 1 hour from registration time). If the participant does not confirms the registration in the given timeframe, the booked place for the event should be made available again for other participants.

In order to remove/hide expired registrations, a CLI command is available to remove/hide expired registrations.

Example with --delete option:

./typo3/sysext/core/bin/typo3 sf_event_mgt:cleanup:expired --delete

Output:

It is recommended to setup a scheduler task to execute the CLI command periodically.

GDPR cleanup for registrations 

Local data privacy policies may require, that you only save personal user data when needed. In order to remove personal user data of registrations including saved registration field data for expired events, a CLI command is available.

Arguments

• days - Amount of days reduced from todays date for expired event selection.

Options

• softDelete - If set, registration will not be deleted hard, but only flagged as deleted
• ignoreEventRestriction - If set, simply all available registrations will be selected and deleted. Use with care!

Example:

./typo3/sysext/core/bin/typo3 sf_event_mgt:cleanup:gdpr 10

Output

It is recommended to setup a scheduler task to execute the CLI command periodically.

Create an own notification 

To create an own notification, you first need to create a HTML template that will be used as the notification body. The template must be located in the following path:

Templates/Notification/User/Custom/

In this example, I create the file MyNotification.html

You can use the following objects in your template:

• {registration}
• {event}
• {settings}
• {hmac}
• {reghmac}
• {customNotification}

After you created the notification template, you have to configure the new notification in the TypoScript settings of the admin module.:

module.tx_sfeventmgt {
  settings {
    notification {
      customNotifications {
        myNotification {
          title = A title for the notification
          template = MyNotification.html
          subject = A subject for the email
        }
      }
    }
  }
}

After configuring the new notification to the TypoScript settings, you can use it to notifiy participants of the event.

Selecting the recipients of custom notifications 

If you want to send a custom notification only to a selected group of recipients (e.g. those who actually have paid for the event), you can use the "constraints" setting to limit the recipients.:

module.tx_sfeventmgt {
  settings {
    notification {
      customNotifications {
        myNotification {
          title = A title for the notification
          template = MyNotification.html
          subject = A subject for the email
          constraints {
            paid.equals = 1
          }
        }
      }
    }
  }
}

Using the example above, only those participants will receive an email where the field "paid" equals with "1".

You can use the following conditions

• equals
• lessThan
• lessThanOrEqual
• greaterThan
• greaterThanOrEqual

You may also combine the conditions like shown below:

module.tx_sfeventmgt {
  settings {
    notification {
      customNotifications {
        myNotification {
          title = A title for the notification
          template = MyNotification.html
          subject = A subject for the email
          constraints {
            paid.equals = 1
            confirmed.equals = 1
          }
        }
      }
    }
  }
}

Note, that combined conditions are always combined with a logical AND statement, so custom notifications with the example settings from above will be sent to all participants, who have paid and confirmed to the event.

Also note, that the usage of conditions like shown above are rudimentary and does not cover all scenarios.

Configuring email attachments 

Attachments must be configured in TypoScript and it is possible to add attachments globally to all emails of a specific type or individual per event. Due to readability, the default TypoScript setup does not include an example configuration for email attachments.

plugin.tx_sfeventmgt {
  settings {
    notification {
      registrationNew {
        attachments {
          user {
            fromFiles {
              1 = fileadmin/terms-and-conditions.pdf
            }
            fromEventProperty {
              1 = files
              2 = image
            }
            fromRegistrationProperty {
              1 = registrationFiles
            }
          }
          admin {
            fromFiles =
            fromEventProperty =
            fromRegistrationProperty =
          }
        }
      }
    }
  }
}

Properties for attachment configuration 

Example for new event registrations: 

plugin.tx_sfeventmgt {
  settings {
    notification {
      registrationNew {
        attachments {
          user {
            iCalFile = 1
          }
        }
      }
    }
  }
}

In the example above, emails for new user registrations will include an iCal file for the event.

RSS feed by TypoScript (recommended) 

One way to generate the RSS feed is to use TypoScript. Add to following TypoScript to your site and adopt it to your needs:

pageEventRSS = PAGE
pageEventRSS {
  typeNum = {$plugin.tx_sfeventmgt.rss.channel.typeNum}
  config {
    disableAllHeaderCode = 1
    xhtml_cleaning = none
    admPanel = 0
    debug = 0
    disablePrefixComment = 1
    metaCharset = utf-8
    additionalHeaders.10.header = Content-Type:application/rss+xml;charset=utf-8
    absRefPrefix = {$plugin.tx_sfeventmgt.rss.channel.link}
  }
  10 < tt_content.list.20.sfeventmgt_pieventlist
  10 {
    settings < plugin.tx_sfeventmgt.settings
    settings {
      detailPid = 4
      storagePage = 3
      list {
        format = xml
      }
    }
  }
}

This example will show all events which are saved on the page with uid 3. The detail view page is the one with uid 4.

The RSS feed itself can be found with the link /?type=9918.

RSS feeds by using a plugin 

If you want to use the sf_event_mgt plugin to configure the settings of your RSS feed, then just configure the event plugin as if you are creating a list view (set startin point, categories, detail page, ...)

Next, add a new TypoScript template to the page and insert the following TypoScript to the setup section

page = PAGE
page.10 < styles.content.get

config {
   disableAllHeaderCode = 1
   xhtml_cleaning = none
   admPanel = 0

   metaCharset = utf-8
   additionalHeaders = Content-Type:application/rss+xml;charset=utf-8
   additionalHeaders.10.header = Content-Type:application/rss+xml;charset=utf-8
   disablePrefixComment = 1
}

# set the format
plugin.tx_sfeventmgt.settings.list.format = xml

# delete content wrap
tt_content.stdWrap >
tt_content.stdWrap.editPanel = 0

Important If the sf_event_mgt plugin is located in different column than default (0), then you extend the TypoScript as following:

page.10.select.where = colPos=1

plugin.tx_sfeventmgt {
    rss.channel {
        title = Feed title
        description =
        link = http://domain.tld/
        language = en-gb
        copyright = TYPO3 Event management and registration
        category =
        generator = TYPO3 EXT:sf_event_mgt
    }
}

<e:headerData>
    <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="{f:uri.page(additionalParams:{type:9918})}" />
</n:headerData>

Configuration 

The configuration is (hopefully) self explaining.

The spam check can be enabled or disabled using Typoscript.:

plugin.tx_sfeventmgt.settings.registration {
  spamCheck {
    enabled = 1
    maxSpamScore = 10
    checks {
      honeypot {
        enabled = 0
        name = Honeypot field check
        class = DERHANSEN\SfEventMgt\SpamChecks\HoneypotSpamCheck
        increaseScore = 10
          configuration {
            renderAsHiddenField = 0
          }
        }
    }
  }
}

To enable the spam check, plugin.tx_sfeventmgt.settings.registration.spamCheck.enabled = 1 must be set. Next, each spam check must be activated and configured to your needs.

The honeypot spam check 

This check adds a field (either invisible input field or a hidden form field) to the registration form. If the field is filled out, it is very likely that the form submission is spam. Therefore you should configure a high increaseScore , so the spam check as a whole already is considered as failed when this check fails.

Example template:

<f:if condition="{spamSettings.checks.honeypot.configuration.renderAsHiddenField} == 1">
  <f:then>
      <f:form.hidden property="hp{event.uid}" additionalAttributes="{autocomplete: 'hp{event.uid}'}" />
  </f:then>
  <f:else>
      <f:form.textfield property="hp{event.uid}" additionalAttributes="{autocomplete: 'hp{event.uid}', aria-hidden: 'true'}" tabindex="-1" style="display:none !important" />
  </f:else>
</f:if>

If this spam check is configured and the field is not submitted (missing in POST parameters), the check is also considered as failed.

The link spam check 

This check counts the amount of links in all submitted form fields. If the configured maxAmountOfLinks is exceeded, the check is considered failed.

The challenge/response spam check 

This check adds a hidden input field to the registration form. The check expect a specific value to be submitted in the hidden input field. If this value is not present, the check is considered failed.

The spam check has the following configuration options:

challengeResponse {
  enabled = 0
  name = Challenge/Response check (JavaScript required) using ROT13 encryption/obfuscation
  class = DERHANSEN\SfEventMgt\SpamChecks\ChallengeResponseSpamCheck
  increaseScore = 10
  configuration {
    prefix = SfEventMgt
    postfix = TYPO3
  }
}

The spam check calculates a challenge consisting of the configured pre- and postfix and a hmac which includes the uid of the event. This challenge is added as data-attribute to the hidden form field.

The check expects the challenge to be returned ROT13 encrypted/encoded. There is a plain vanilla JS script in Resources/Public/JavaScript/cr-spamcheck.js that does the job for you, if you use the included partial for the spam checks of the extension.

Creating a custom spam check 

It is also possible to create custom spam checks. To do so, just add an own configuration array to the checks array and implement your check as a class that extends \DERHANSEN\SfEventMgt\SpamChecks\AbstractSpamCheck

Please refer to the existing spam checks in the extension for details.

Configuration 

Both hCaptcha and Google reCAPTCHA require API credentials, so the captcha can be check against an API. The API credentials must be added as TypoScript constants (see example below).

TypoScript Constants:

plugin.tx_sfeventmgt {
  settings {
    registration {
      captcha {
        enabled = 0
        type = hCaptcha
        hCaptcha {
          publicKey =
          privateKey =
        }
        reCaptcha {
          siteKey =
          secretKey =
        }
      }
    }
  }
}

TypoScript Setup:

plugin.tx_sfeventmgt {
  settings {
    registration {
      requiredFields = captcha
    }
  }
}

In order to use one of the captcha services, the following must be fullfilled:

• Obtain API keys for either hCaptcha or Google reCAPTCHA service
• Enable the captcha check in TypoScript constant plugin.tx_sfeventmgt.settings.registration.captcha.enabled = 1
• Set the type of captcha service you use in TypoScript constant plugin.tx_sfeventmgt.settings.registration.captcha.type = 1
• Add the API credentials to TypoScript constants in the associated section for the captcha service

How does the waitlist move up process work? 

The default automatic move up process is active, when the following conditions are met for the event:

• "Enable cancellation" is activated
• "Enable waitlist" is activated
• "Automatic waitlist move up" is activated

As soon as the event is fully booked, new registration will be added to the waitlist of the event. When a registered user cancels the registration, registrations will move up from the waitlist.

Note, that the following conditions decide, if a registration will move up:

• The registration must be confirmed
• The registration must have a valid date in the field "Registration date"
• The registration with the earliest "Registration date" will move up first

As soon as a registration moved up from the waitlist, the user will recieve an email, that the registration moved up.

Things to keep in mind when using the default move up process 

• The default move up process does not execute, when registrations are removed from the event because the confirmation dealine exceeded
• When the simultaneous registration process is used, registrations are treated seperately by the default move up process. This can result in, that the main registration will be moved up, but additonal may not.
• When the simultaneous registration process is used, the dependency to the main registration will automatically be removed. This is recommended, since the cancellation of the main registration will result in the cancellation of all "connected" registrations. The TypoScript setting settings.waitlist.moveUp.keepMainRegistrationDependency can be used to keep the dependency to the main registration.
• When the simultaneous registration process is used, moved up registrations will automatically be enabled for notification.
• If a payment process is activated for the event, the AfterRegistrationMovedFromWaitlist event must manuelly be implemented in order to send an email with payment information (e.g. payment link) to the user who moved up.

Customizing the move up process 

If the default move up process does not fulfill your needs, you can use the PSR-14 event WaitlistMoveUpEvent to create a custom move up logic. Please refer to the code of the default move up process to see how a custom logic can be implemented.

If you implement a custom move up logic and to not want the default move up process to be executed, make sure so set $processDefaultMoveUp to false in your event listener.

Event Controller 

• ModifyListViewVariablesEvent
• ModifyCalendarViewVariablesEvent
• ModifyDetailViewVariablesEvent
• ModifyRegistrationViewVariablesEvent
• ModifyCreateDependingRegistrationsEvent
• ModifyConfirmRegistrationViewVariablesEvent
• ModifyCancelRegistrationViewVariablesEvent
• ModifySearchViewVariablesEvent
• AfterRegistrationSavedEvent
• AfterRegistrationConfirmedEvent
• AfterRegistrationCancelledEvent
• EventPidCheckFailedEvent
• WaitlistMoveUpEvent
• ProcessRedirectToPaymentEvent
• ProcessCancelDependingRegistrationsEvent

Payment Controller 

• ProcessPaymentInitializeEvent
• ModifyPaymentRedirectResponseEvent
• ProcessPaymentSuccessEvent
• ProcessPaymentFailureEvent
• ProcessPaymentCancelEvent
• ProcessPaymentNotifyEvent
• ProceedWithPaymentActionEvent

Administration Controller 

• InitAdministrationModuleTemplateEvent

Event Repository 

• ModifyEventQueryConstraintsEvent

Notification Service 

• ModifyUserMessageSenderEvent
• ModifyUserMessageAttachmentsEvent
• AfterUserMessageSentEvent
• AfterAdminMessageSentEvent
• ModifyCustomNotificationLogEvent

Registration Service 

• AfterRegistrationMovedFromWaitlist

General workflow 

Depending on the selected payment method, the user is redirected to the payment providers payment page.

As a reference, please check this demo extension: https://github.com/derhansen/sf_event_mgt_payment_demo

1. Blank extension 

First of all you need a blank TYPO3 extension with at least an ext_emconf.php and an ext_localconf.php file.

2. Registration of payment method 

Add the following content to the file ext_localconf.php:

// Register payment provider
$GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['sf_event_mgt']['paymentMethods']['mypaymentmethod'] = [
    'class' => 'DERHANSEN\\SfEventMgtMypaymentmethod\\Payment\\Mypaymentmethod',
    'extkey' => 'sf_event_mgt_mypaymentmethod'
];

3. Implement Event Listeners 

Depending on the requirements of the payment method, you should implement an Event Listener for available PSR-14 Events. You should at least implement handling of redirect, success, failure and cancel actions.

The code below shows how to implement your payment method to the redirectAction PSR-14 Event of sf_event_mgt:

// Configuration/Services.yaml
services:
  Vendor\Extension\EventListener\YourListener:
    tags:
      - name: event.listener
        identifier: 'yourListener'
        event: DERHANSEN\SfEventMgt\Event\ProcessPaymentInitializeEvent

After you registered your event listener, you can add code for your Event Listener to initialize the payment:

<?php
namespace Vendor\Extension\EventListener;

use DERHANSEN\SfEventMgt\Event\ModifyDetailViewVariablesEvent;

class YourListener
{
    public function __invoke(ModifyDetailViewVariablesEvent $modifyDetailViewVariablesEvent): void {
       // Implement your code (e.g. add variables)
       $variables = $modifyDetailViewVariablesEvent->getVariables();
       $variables['newVariable'] = 'Just testing';
       $modifyDetailViewVariablesEvent->setVariables($variables);
    }
}

The setters in all events allow you to control the behavior of the payment process in the main extension.

4. Add payment class 

Please refer to the class AbstractPayment in sf_event_mgt for possible settings. You payment class must extend AbstractPayment and you should override/set the local $enable properties in order to enable the actions in sf_event_mgt

Please also refer to the PaymentController in sf_event_mgt to see all available PSR-14 Events.

In this example I create the class DERHANSENSfEventMgtMypaymentmethodPaymentMypaymentmethod and add the following method.:

/**
 * Adds required HTML (for redirection) to the given values-array
 *
 * @param array $values
 * @param bool $updateRegistration
 * @param \DERHANSEN\SfEventMgt\Domain\Model\Registration $registration
 * @param ActionController $pObj
 * @return void
 */
public function renderRedirectView(&$values, &$updateRegistration, $registration, $pObj)
{
    $pluginSettings = $this->getPluginSettings();

    /** @var \TYPO3\CMS\Fluid\View\StandaloneView $view */
    $view = $this->objectManager->get('TYPO3\\CMS\\Fluid\\View\\StandaloneView');
    $view->setFormat('html');
    $view->setLayoutRootPaths($pluginSettings['view']['layoutRootPaths']);
    $view->setPartialRootPaths($pluginSettings['view']['partialRootPaths']);
    $view->setTemplateRootPaths($pluginSettings['view']['templateRootPaths']);

    // @todo - e.g. call payment providers API to initialize payment
    //
    // Make sure to multiply the price with the given amount of depending registrations
    //
    // Depending on the payment provider you may receive a redirection URL or a token
    // which can be passed to the standalone view.

    $view->assignMultiple([
        'settings' => $pluginSettings['settings'],
    ]);
    $values['html'] = $view->render();
}

Replace the @todo section with your own code. The returned view should include some text and at least the link for the redirection. In order process automatic redirection, the view could include a JavaScript redirect to the payment providers payment page.

5. Implement methods 

Step 4 already showed how to implement one action. Feel free to implement other required actions (at least success, failure and cancel to your need.

Each PSR-14 Event enables you to update the given registration. Just set the properties of the $registration object and set $updateRegistration to true.

It is also possible to remove a registrations, if payment failed or was cancelled. Please see the corresponding PSr-14 Events for possible options.

6. cHash in generated links 

All links created in PaymentController will automatically have a cHash added by TYPO3. This should be ok for most scenarios, but sometimes the payment provider will append GET parameters to links (e.g. successUrl or failureUrl), which then leads to the situation, that the TYPO3 cHash check fails.

Since all Payment actions are uncached and the registration GET parameter is checked using a HMAC, the cHash can manually be removed from generated URLs by implementing the ProcessPaymentInitializeEvent PSR-14 event.

7. Security conciderations 

Make sure that your rendered Fluid standlone views do not contain sensitive data or possibilities for Cross Site Scripting (XSS) (values['html'] is rendered with f:render.raw).

The event detail page shows a 404 error 

This problem can occur in TYPO3 versions greater than 9.5.17 or 10.4.2 when the TYPO3 website has multiple sites that use a shared folder for events. If this is the case, you must configure unique slug handling in the extension settings slugBehaviour.

Why do you not include a nice CSS stylesheet? 

Because you normally customize templates/stylesheets to your needs. Therefore the extension just comes with a rudementary CSS stylesheet available in EXT:Resources/Public/Css/events_default.css which must be included manually like shown below:

page.includeCSS {
        events = EXT:sf_event_mgt/Resources/Public/Css/events_default.css
}

Is it possible to extend events/registrations with own fields? 

Yes, since version 3.0 of the extension, you can add additional Registration field on event basis.

You can also extend sf_event_mgt with own fields (e.g. new fields for Event). I have created a demo extension, which shows how to add new fields to the event and registration domain model.

Demo Extension: https://github.com/derhansen/sf_event_mgt_extend_demo

The extension contains a short manual (README.md) how to add your own fields to existing domain models.

How do I export registered participants to a CSV file? 

Please use the CSV export action as described in Backend module section.

How do I create a custom email notification? 

A detailed description can be found in the Custom notifications section.

Can I add the HMAC or an appended HMAC of the registration UID to emails? 

Yes, you can use the following objects in you email templates

• {hmac} = HMAC of uid
• {reghmac} = appended uid+HMAC

Is it possible to filter by categories in the listview 

Yes, filtering of events by a category is possible if you pass the category to the overwriteDemand setting of the listview.:

<f:link.action action="list" controller="Event" arguments="{overwriteDemand:{category: category}}">{category.title}</f:link.action>

This only works, if you create links with f:link.action as shown above. If you want to display the categories in a select-box, then I suggest you create a CSS only select box (e.g. UL menu)

When does {event.registrationPossible} return TRUE 

For each event, the attribute registrationPossible returns TRUE or FALSE, if registration for the event is possible. TRUE is returned, when all conditions below are fulfilled:

• Registration option is activated for the event
• Max participants is not reached (if max. participants > 0) or max participants is not reached and waitlist is enabled
• Date set at registration deadline is not reached
• Startdate of event is not reached
• Startdate of registration is reached (if set)

Why does the extension not support recurring events? 

The user registration is one of the main features of the extension and it requires, that every event is unique in order to save registrations for a particular event. This makes it impossible to only have one event record, that has multiple recurrences.

Since there is no smart way to add recurring events to the extension without making it more complex and harder to maintain, this feature will not make it into the extension.

How can I disable double opt in for event registration? 

You can enable autoConfirmation for new registrations as described in the TypoScript reference section. With autoConfirmation enabled, new registrations will automatically be confirmed and the user will not receive a confirmation email.

How does the simultaneous registration process work? 

If the field "Max. simultaneous registrations per user" is set to a value greater than 1 for the given event, a user is able to create multiple registrations at once. If the user in the registration view chooses to create more than one registration, there will be created the given amount of registrations in the backend for the user. All fields (e.g. firstname, lastname, email) will contain the same values.

The first registration saved is the "main registration", and all other registrations saved later will depend on the "main registration". All "dependent registrations" will automatically get the option "No email notifications" set to true, so custom notifications are only sent to the email address of the "main registration".

If automatic confirmation is turned off (default), the user has to confirm the registration by clicking a link in the confirmation email. When the user confirms the registration, all "dependent registrations" of the "main registration will automatically also be confirmed.

How can I set a default currency? 

You can set default values for many fields in TYPO3 by using TCAdefaults. To set a default value for the currency field, add the following to the Page TSConfig, which sets € as the default currency for new records:

TCAdefaults {
  tx_sfeventmgt_domain_model_event.currency = €
}

How to make the field "Accept terms and conditions" mandatory 

The field "Accept terms and conditions" is part of the registration domain model, but it is not required during registration. To make the field required, add the field to the list of required field like shown below:

plugin.tx_sfeventmgt {
  settings {
    registration {
      requiredFields = accepttc
    }
  }
}

How do I add my own custom translations 

You can override all language files with your own translations/labels. As an example, the following code overrides/extends the locallang_db.xlf and the locallang.xlf

Add this example code to a ext_localconf.php file (e.g. in a site package extension).:

$GLOBALS['TYPO3_CONF_VARS']['SYS']['locallangXMLOverride']['de']['EXT:sf_event_mgt/Resources/Private/Language/locallang_db.xlf'][] = 'EXT:your_ext/Resources/Private/Language/de.custom_locallang_db.xlf';
$GLOBALS['TYPO3_CONF_VARS']['SYS']['locallangXMLOverride']['de']['EXT:sf_event_mgt/Resources/Private/Language/locallang.xlf'][] = 'EXT:your_ext/Resources/Private/Language/de.custom_locallang.xlf';

How can I use the overwriteDemand feature for the search view 

It is also possible to use the overwriteDemand feature for the search view in order to limit the events that the search result includes. If you for example wish to limit the search to a special category, you must pass the category UID as shown below (the value field contains the category UID).:

<f:form.textfield name="overwriteDemand[category]" value="1"/>

How can I add pagination to the listview? 

Since version 6.0 of the extension, the list view uses the TYPO3 pagination API to provide necessary objects required.:

<f:for each="{pagination.paginator.paginatedItems}" as="event" iteration="iterator">
    <f:render partial="Event/ListItem" arguments="{_all}"/>
</f:for>

How can I add pagination to the searchview? 

Native pagination is not supported for the searchview, since besides GET parameters also POST parameters need to be considered in order to render the pagination. Although it technically would be possible to implement this feature, it will not be includes in the extension as it is a suboptimal solution (search word as dynamic GET parameter). If you need a paginated search for events, it is recommended to use a search extension (e.g. ext:ke_search or ext:solr).

How does the payment process work 

For each event with registration enabled, you can also enable payment. If payment is enabled, you can output available payment methods for the event in the registration form. When a user registers for an event, he can select a payment method.

The extension comes with 2 default payment methods debit and transfer. Both payment methods do not include any further payment processing.

It is possible to extend the extension with own payment methods that include further payment processing (e.g. by an external payment provider).

For more information on how to add custom payment methods, see Payment section

The default payment methods are missing 

Open the extension settings in the extension manager and press the "Save" button.

Configured price options do not show up in frontend 

Make sure that the date for the price option is valid. Also make sure, that you use {event.currentPrice} in your Fluid template to output the current price.

How can I use the iCalDownload action in the Listview? 

With the following Fluid snippet, you can use the iCalDownload in the listview:

<f:link.action action="icalDownload" arguments="{event : event}" pageUid="{settings.detailPid}"><f:translate key="event.icalDownload" /></f:link.action>

Note, that you have to set the pageUid to a page with the detail view plugin.

Why does the next/previous month links not work for the calendar view? 

The next/previous links use the overwriteDemand feature, which by default is disabled. Make sure you have unchecked the Disable overwrite demand setting in the plugin.

The category filter for the list view does not work 

The filtering also uses the overwriteDemand feature, which by default is disabled. Make sure you have unchecked the Disable overwrite demand setting in the plugin and also ensure that the category mode is not equal to Ignore category selection.

How do I show the event title as page title on the detail page? 

Either use the TYPO3 PageTitle API or you can use the title-ViewHelper of this extension.

How do I set the indexed search title for an event? 

Use the title-ViewHelper of this extension.

The Payment Plugin throws exception about missing default controller 

The page with the Payment Plugin shows the following error:

The default controller for extension "SfEventMgt" and plugin "Pipayment" can not be determined. Please check for TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin() in your ext_localconf.php

Please delete the content element with the Payment Plugin and create a blank content element of type "Plugin" and next directly select the Payment Plugin from the plugins select box.

If the plugin originally was a plugin with Flexform settings and switchableControllerActions, those settings will remain in the database field pi_flexform and lead to the described error.

How can I move registrations on the waitlist automativally up, if a registered user cancels a registration? 

Since version 5.2.0 there is a simple and default waitlist move up process. Please refer to the documentation section about the Default waitlist move up process for further information.

If the default move up process does not fulfill your needs, you can use the PSR-14 Event WaitlistMoveUpEvent to implement your own move up logic.

Event registrations get confirmed by search engines 

Under certain conditions with extensions that create sitemaps it may happen, that a confirmation link of a registration email gets added to the sitemap and afterwards visited by a search engine crawler. This behavior has at least been seen when the extension metaseo has been used to create a sitemap.

In order to avoid the registration link from being added to the sitemap, the page with the registration plugin needs to be excluded from the sitemap, i.e. use "Exclude from sitemap" in the page settings or by other means (e.g. blacklist in EXT:metaseo).

Use https://github.com/derhansen/sf_event_mgt/issues/597 for further details/discussion.

Displaying events using the "Insert Record" content element 

If you display events using the "Insert Record" content element, you may want to use a different layout to display the event detail view. For this purpose, you can use {settings.detail.isShortcut} in the Detail.html Fluid Template to render a different layout.

How can I display JSON-LD data for events? 

If you want to to display JSON-LD data for events in the event detail view, you can add an own partial including the JSON-LD data you need. Since requirements of data in JSON-LD may vary per project, sf_event_mgt does not ship with a partial or ViewHelper to create such data.

Example Partial Code (will work until Fluid < 3.0):

<script type="application/ld+json">
   <f:format.raw>{</f:format.raw>
     "@context": "https://schema.org/",
     "@type": "Event",
     "name": "{event.title}",
     "startDate": "<f:format.date format="Y-m-d">{event.startdate}</f:format.date>",
     "location": <f:format.raw>{</f:format.raw>
       "@type": "Place",
       "name": "{event.location.title}",
       "address": <f:format.raw>{</f:format.raw>
         "@type": "PostalAddress",
         "streetAddress": "{event.location.address}",
         "addressLocality": "{event.location.city}",
         "postalCode": "{event.location.zip}",
         "addressCountry": "{event.location.country}"
         <f:format.raw>}</f:format.raw>
         <f:format.raw>}</f:format.raw>,
     "image": [
       <f:if condition="{event.image}">
       "<f:uri.image image="{event.image.0}" absolute="true"/>"
       </f:if>
      ],
     "description": "<f:format.raw>{event.description}</f:format.raw>",
     "endDate": "<f:format.date format="Y-m-d">{event.enddate}</f:format.date>",
     "offers": <f:format.raw>{</f:format.raw>
       "@type": "Offer",
       "url": "<f:uri.action action="registration" absolute="true" arguments="{event : event}" pageUid="{settings.registrationPid}"></f:uri.action>",
       "price": "{event.currentPrice}",
       "priceCurrency": "{event.currency}",
       "availability": "https://schema.org/InStock",
     <f:format.raw>}</f:format.raw>,
       "performer": <f:format.raw>{</f:format.raw>
         "@type": "PerformingGroup",
         "name": "{event.organisator.name}"
     <f:format.raw>}</f:format.raw>
  <f:format.raw>}</f:format.raw>
</script>

Note: When using Fluid, always make sure to escape variables properly.

As an alternative, you could create an own ViewHelper which generates the required JSON-LD data.

Images for categories are not shown in the frontend? 

Categories in TYPO3 backend do not have an image by default. The TYPO3 extension ext:news by Georg Ringer adds additional fields (e.g. an image-field) to the category domain model.

If you want ext:sf_event_mgt to use the category domain model of ext:news, the category domain model of ext:sf_event_mgt needs to be overridden as shown below:

Add this to an extension (e.g. your sitepackage) in ext_localconf.php:

GeneralUtility::makeInstance(\TYPO3\CMS\Extbase\Object\Container\Container::class)
    ->registerImplementation(
        \DERHANSEN\SfEventMgt\Domain\Model\Category::class,
        \GeorgRinger\News\Domain\Model\Category::class
    );

After adding this snippet and clearing the cache, all categories in events do now use the category domain model of ext:news

Why is a registration link shown even if the registration dealine expired? 

Make sure that you configured the page cache settings as described in Page Cache Configuration

Editing events is very slow having a huge amount of registrations. Can this be fixed? 

Short answer: No, not really. For TCA inline fields, TYPO3 will load all data before opening the records in the backend. So having an event with 1500 registrations will actually load all registrations before showing the edit form for the event in the TYPO3 backend. Note, that just disabling the field "registration" by TCA will not work, since TYPO3 will load the data anyway.

In order to make it at least possible to edit the event data, the extension makes it possible to hide all registration inline fields and prevent TYPO3 from loading all data when a configurable limit of registrations is reached per event.

Please refer to section Extension settings for available options.

How can I show and browse the event calendar by weeks? 

The calendar view is able to show events by week or by month. The default template contains the markup for the month view including links to browse to the previous and next month.

In order to show events by week, it is recommended to create a new template layout for the calendar view and next to use the fluid variable {weekConfig} to show events for the current week and to create previous and next week links. The default template includes an example, which is surrounded by <f:comment>

6.0.0 

This version contains several breaking changes. Make sure, you read the release notes with instructions at https://github.com/derhansen/sf_event_mgt/releases/tag/6.0.0

It is at least required to execute the "Migrate plugins and settings" update wizard and to apply database migrations.

Note, that manual changes (at least to existing templates) is required. For further information please refer to the change log.

5.1.0 

This version contains a breaking change which might affect users who either extended the notification module with custom code (e.g. by xclass) or who use NotificationService::sendUserMessage() in own code.

Make sure, you read the release notes with instructions at https://github.com/derhansen/sf_event_mgt/releases/tag/5.1.0

5.0.0 

This version contains several breaking changes. Make sure, you read the release notes with instructions at https://github.com/derhansen/sf_event_mgt/releases/tag/5.0.0

4.1.0 

This version contains a breaking change which requires adoption in Fluid Templates, which is important for TYPO3 websites using multiple languages.

Make sure, you read the release notes with instructions at https://github.com/derhansen/sf_event_mgt/releases/tag/4.1.0

4.0.0 

This version contains several breaking changes. Make sure, you read the release notes with instructions at https://github.com/derhansen/sf_event_mgt/releases/tag/4.0.0

3.0.0 

2.0.0 

Flexform restructuring 

Due to restructuring of the Flexform settings of the event plugin, it is required to run the update script of the extension, so existing Flexform settings (e.g. listPid, detailPid, ...) will be migrated to the new structure. Please use the update script in the extension manager to process the migration as shown below.

Please click on the update-icon to start the category migration.

plugin.tx_sfeventmgt.settings {
  eventDetails {
    imageWidth = 200
    imageHeight =
  }
}

plugin.tx_sfeventmgt.settings {
  detail {
    imageWidth = 200
    imageHeight =
  }
}

1.5.0 

The removal of the local category system requires the execution of a migration script, so existing categories will get migrated to sys_category entries. Please use the update script in the extension manager to process the migration as shown below.

Please click on the update-icon to start the category migration.

1.2.0 

Due to the new cancellation-option for registrations, you need update all plugins, which are configured to display "Registration" in the "What to display" section. Just open the plugin for edit and select "Registration" in the "What to display"-selectbox.

What's included? 

• Events
• Registrations
• Categories
• Locations (multiple => single)
• Organizers (multiple => single)
• Speaker

We also migrated event types and target groups. The sql queries are basically the same like the category queries. You will need two more category fields in tx_sfeventmgt_domain_model_event for them.

SQL queries 

We are starting with a fresh install of sf_event_mgt so we can use ids mostly 1 to 1.

/* Organizers */
INSERT INTO tx_sfeventmgt_domain_model_organisator (uid,pid,name,email,email_signature)
SELECT
    uid,
    pid,
    title,
    email,
    email_footer,
FROM
    tx_seminars_organizers
WHERE
    deleted = 0;

/* Locations */
INSERT INTO tx_sfeventmgt_domain_model_location (uid,pid,title,address,city,description)
SELECT
    uid,
    pid,
    title,
    address,
    city,
    directions
FROM
    tx_seminars_sites
WHERE
    deleted = 0;

/* Speakers */
INSERT INTO tx_sfeventmgt_domain_model_speaker (uid,pid,name,description)
SELECT
    uid,
    pid,
    title,
    description
FROM
    tx_seminars_speakers
WHERE
    deleted = 0;

/* Description of speakers */
UPDATE tx_sfeventmgt_domain_model_speaker
SET
    description = (
        SELECT
            CONCAT(
                IF (organization!='', CONCAT(organization, '<br>'), ''),
                IF (homepage!='', CONCAT('<a href="', homepage,'">', homepage, '</a><br>'), ''),
                IF (email !='', CONCAT('<a href="mailto:', email, '">', email, '</a><br>'), ''),
                description
            )
        FROM
            tx_seminars_speakers
        WHERE
            tx_sfeventmgt_domain_model_speaker.uid = tx_seminars_speakers.uid
    );

/* Events */
INSERT INTO tx_sfeventmgt_domain_model_event (
    uid,
    pid,
    hidden,
    title,
    teaser,
    description,
    startdate,
    enddate,
    registration_deadline,
    cancel_deadline,
    enable_cancel,
    location,
    room,
    speaker,
    price,
    enable_registration,
    unique_email_check,
    max_participants,
    registration,
    enable_autoconfirm,
    enable_waitlist,
    notify_organisator
)
SELECT
    uid,
    pid,
    hidden,
    title,
    teaser,
    CONCAT(
        IF (
            subtitle!='',
            CONCAT(
                '<h2>',
                subtitle,
                '</h2>'
            ),
            ''
        ),
        description,
        additional_information
    ),
    begin_date,
    end_date,
    deadline_registration,
    deadline_unregistration,
    1, /* Enable cancellation */
    place,
    room,
    speakers,
    price_regular,
    needs_registration,
    IF(
        allows_multiple_registrations = 1,
        '0',
        '1'
    ),
    attendees_max,
    registrations,
    1, /* auto confirm registration */
    queue_size,
    1 /* notify organisator on new registration */
FROM tx_seminars_seminars
WHERE
    deleted = 0 AND
    (end_date = 0 OR end_date >= UNIX_TIMESTAMP()); /* filter out past events */

/* Events <=> Locations */
UPDATE tx_sfeventmgt_domain_model_event
    SET location = (
        SELECT
            uid_foreign
        FROM
            tx_seminars_seminars_place_mm
        WHERE
            tx_sfeventmgt_domain_model_event.uid = tx_seminars_seminars_place_mm.uid_local
        LIMIT 1 /* seminars has multiple locations, this extension has only a single location */
    );

/* Events <=> Speaker */
INSERT INTO tx_sfeventmgt_event_speaker_mm (uid_local,uid_foreign,sorting)
SELECT
    uid_local,
    uid_foreign,
    sorting
FROM tx_seminars_seminars_speakers_mm
WHERE
    uid_local IN (SELECT uid FROM tx_sfeventmgt_domain_model_event);

/* Events <=> Organizers */
UPDATE tx_sfeventmgt_domain_model_event
    SET organisator = (
        SELECT
            uid
        FROM tx_seminars_organizers
        LEFT JOIN tx_seminars_seminars_organizers_mm
            ON
                tx_seminars_seminars_organizers_mm.uid_foreign = tx_seminars_organizers.uid
        WHERE
            tx_seminars_seminars_organizers_mm.uid_local = tx_sfeventmgt_domain_model_event.uid AND
            tx_seminars_organizers.deleted = 0
        ORDER BY
            sorting ASC
        LIMIT 1 /* seminars has multiple organizers, this extension only a single organizer */
    );

/* Categories */
INSERT INTO sys_category (uid,pid,title,parent)
SELECT
    uid + 10000, /* bigger than your highest category uid */
    pid,
    title,
    823  /* Parent category for our event categories */
FROM
     tx_seminars_categories
WHERE
     deleted = 0;

/* Events <=> Categories */
INSERT INTO sys_category_record_mm (uid_local,uid_foreign,tablenames,fieldname)
SELECT
    uid_foreign + 10000,
    uid_local,
    'tx_sfeventmgt_domain_model_event',
    'category'
FROM tx_seminars_seminars_categories_mm
WHERE
    tx_seminars_seminars_categories_mm.uid_local IN (SELECT uid FROM tx_sfeventmgt_domain_model_event);

/* Registrations */
INSERT INTO tx_sfeventmgt_domain_model_registration (
    uid,
    pid,
    hidden,
    tstamp,
    crdate,
    fe_user,
    `event`,
    waitlist,
    notes,
    firstname,
    lastname,
    email,
    confirmed,
    amount_of_registrations
)
SELECT
    uid,
    pid, /* Your need to make sure registrations the same pid as event records (Inline relation) */
    hidden,
    tstamp,
    crdate,
    `user`,
    seminar,
    registration_queue,
    CONCAT(
        IF (attendees_names!='', CONCAT('Weitere Namen:\n',attendees_names,'\n\n'), ''),
        IF (interests!='', CONCAT('Interessen:\n',interests,'\n\n'), ''),
        IF (expectations!='', CONCAT('Erwartungen:\n',expectations,'\n\n'), ''),
        IF (background_knowledge!='', CONCAT('Vorkenntnisse:\n',background_knowledge,'\n\n'), ''),
        IF (known_from!='', CONCAT('Wie haben Sie von dieser Veranstaltung erfahren?\n',known_from,'\n\n'), ''),
        IF (notes!='', CONCAT('Sonstiges:\n',notes,'\n\n'), '')
    ),
    fe_users.first_name,
    fe_users.last_name,
    fe_users.email,
    1,
    seats
FROM tx_seminars_attendances
LEFT JOIN fe_users
    ON fe_users.uid=tx_seminars_attendances.user
LEFT JOIN tx_seminars_seminars ON
    tx_seminars_seminars.uid = tx_seminars_attendances.seminar
WHERE
    tx_seminars_attendances.deleted = 0 AND
    tx_seminars_seminars.deleted = 0 AND
    tx_seminars_attendances.seminar IN (
        SELECT
            uid
        FROM
            tx_sfeventmgt_domain_model_event
    );