.. You may want to use the usual include line. Uncomment and adjust the path. .. include:: ../Includes.txt ====================================== EXT: Registrations for calendar events ====================================== :Created: 2010-02-18T17:33:18 :Changed by: thomas :Changed: 2013-05-03T08:46:39 :Classification: register4cal :Keywords: forAdmins :Author: Thomas Ernst :Email: typo3@thernst.de :Info 4: :Language: en |img-1| |img-2| EXT: Registrations for calendar events - register4cal .. _EXT-Registrations-for-calendar-events: EXT: Registrations for calendar events ====================================== Extension Key: register4cal Language: en Keywords: forAdmins Copyright 2000-2010, Thomas Ernst, This document is published under the Open Content License available from http://www.opencontent.org/opl.shtml The content of this document is related to TYPO3 \- a GNU/GPL CMS/Framework available from www.typo3.org .. _Table-of-Contents: Table of Contents ----------------- `EXT: Registrations for calendar events 1 <#__RefHeading__595_932349152>`_ **`Introduction 3 <#__RefHeading__597_932349152>`_** `What does it do? 3 <#__RefHeading__2498_2124461809>`_ `Screenshots 4 <#__RefHeading__601_932349152>`_ **`Installation 7 <#__RefHeading__1581_2124461809>`_** `Prerequisites 7 <#__RefHeading__1583_2124461809>`_ `Installing the extension 7 <#__RefHeading__1585_2124461809>`_ `Add static templates 7 <#__RefHeading__1587_2124461809>`_ `Adapt TypoScript settings to your needs 7 <#__RefHeading__1589_2124461809>`_ `Recommended: Adapt settings for “calendar base” extension 7 <#__RefHeading__1591_2124461809>`_ **`Users manual 8 <#__RefHeading__1593_2124461809>`_** `Activate the registration for an event 8 <#__RefHeading__1595_2124461809>`_ `Linking Calender Event Organizers and Frontend Users/Groups 9 <#__RefHeading__1601_2124461809>`_ `User-defined fields 9 <#__RefHeading__1607_2124461809>`_ `Field sets 11 <#__RefHeading__1609_2124461809>`_ `Set storage folder for fields and fieldsets 11 <#__RefHeading__5558_1196535638>`_ `FAQ 12 <#__RefHeading__605_932349152>`_ **`Administration 13 <#__RefHeading__607_932349152>`_** `Enabling registration in event list view 13 <#__RefHeading__1617_2124461809>`_ `Enabling fields for frontend editing 14 <#__RefHeading__1619_2124461809>`_ `Telling users that they need to log in 15 <#__RefHeading__1621_2124461809>`_ `Display of users which have already registered during/after registration 16 <#__RefHeading__6536_1351994983>`_ `Vcard files with participant information 17 <#__RefHeading__6538_1351994983>`_ **`Configuration 20 <#__RefHeading__611_932349152>`_** `Reference 20 <#__RefHeading__1725_1668450124>`_ `Markers for templates 23 <#__RefHeading__2782_1815006686>`_ `Changing texts with TypoScript 24 <#__RefHeading__7183_758407849>`_ **`Known problems 26 <#__RefHeading__619_932349152>`_** **`To-Do list 27 <#__RefHeading__621_932349152>`_** **`ChangeLog 28 <#__RefHeading__623_932349152>`_** .. _Introduction: Introduction ------------ .. _What-does-it-do: What does it do? ^^^^^^^^^^^^^^^^ .. _General-overview: General overview """""""""""""""" The very popular TYPO3 extension “Calendar Base” (“cal”) provides a nice calendar, showing all types of events in several possible calendar displays. The extension “register4cal” adds a registration functionality to the calender events. Users can register and unregister for events. A maximum number of attendees can be set for events and a waitlist can be used if this number has been reached. .. _Userdefined-fields-for-registrations: Userdefined fields for registrations """""""""""""""""""""""""""""""""""" Several sets of userdefined fields can be defined and displayed in the registration form. This provides a very flexible way to obtain additional data from the attendees. Possible field types include text fields, multiline text areas as well as selection boxes. Fields are fully configurable from the TYPO3 backend and can be arranged in fieldsets. Every event can either use no fields, a configured default fieldset or an individual fieldset. Changing fields or fieldsets will not affect already stored registrations. .. _Registration-in-single-event-view-and-event-list-view: Registration in single event view and event list view """"""""""""""""""""""""""""""""""""""""""""""""""""" This extension supports the registration from the single event view as well as from the event list view. While the single event view shows the registration form below the event display, the event list view has a box attached to each event, including a checkbox to allow the user to register or unregister for the event. .. _Email-confirmation-and-notification: Email confirmation and notification """"""""""""""""""""""""""""""""""" Every change in a registration can cause a confirmation being sent to the user which registered for the event. Also, a notification can be send to the organizer(s) of the event if a registration has been changed. .. _Registration-display: Registration display """""""""""""""""""" Besides from showing registration records in the backend, this extension provides a frontend-plugin which can display registrations in two ways: - An event view, where frontend-users can see the events, they have registered for. - An participant view, where event organizers can see the users which have registered for their events .. _Foreign-user-registration: Foreign user registration """"""""""""""""""""""""" Event organizers can be enabled to register/unregister foreign users for their events. This enables the organizers to manage all attendees for their events via this extension, even if the registration has been communicated via other ways than the website. .. _Frontend-editing: Frontend editing """""""""""""""" This extensions fully supports the frontend editing features of the cal extension. It provides modified cal default templates, showing how to include the additional event fields into an additional tab of the cal frontend editing view. .. _Supporting-extensions: Supporting extensions """"""""""""""""""""" The following extensions can be used together with this extension: - rlmp\_dateselectlib: Provides a date selection for the register4cal fields when using calendar event frontend editing. - onetimeaccount: Enables users to create a temporary frontend user account to register for events. .. _Screenshots: Screenshots ^^^^^^^^^^^ |img-3| *Illustration 1: Activate registration in backend* |img-4| *Illustration 2: Settings for a userdefined field* |img-5| *Illustration 3: Single event view with registration form* |img-6| *Illustration 4: List of events for which the current frontend user has registered* |img-7| *Illustration 5: Event list view with registration box attached to event* |img-8| *Illustration 6: List of registrations shown to the organizer of an event* .. _Installation: Installation ------------ .. _Prerequisites: Prerequisites ^^^^^^^^^^^^^ Before you install this extension, be sure that the following prerequisites are fulfilled: - You are using at least PHP version 5.1.0 on your server - You have installed the Calendar Base extension “cal”, it is configured properly and working. .. _Installing-the-extension: Installing the extension ^^^^^^^^^^^^^^^^^^^^^^^^ Download the extension from the TYPO3 extension repository and install it through the typical TYPO3 extension installation process using the Extension Manager. During the installation you will be asked to perform several database changes. .. _Add-static-templates: Add static templates ^^^^^^^^^^^^^^^^^^^^ You should now add the required static templates to one of your template records. The following list shows, which templates are provided and when they should be used: .. ### BEGIN~OF~TABLE ### .. _Basic-settings-register4cal: Basic settings (register4cal) """"""""""""""""""""""""""""" .. container:: table-row Static Template Basic settings (register4cal) Usage General settings for this extension. Should be used, if you are using the current template files from this extension (e.g. for a new installation) .. _FE-Editing-register4cal: FE-Editing (register4cal) """"""""""""""""""""""""" .. container:: table-row Static Template FE-Editing (register4cal) Usage Settings for frontend-editing. Include this static template, if you are using the frontend editing feature of the Calendar Base extension. The register4cal fields need to be included in the templates, too! .. _Compatibility-to-old-templates-register4cal: Compatibility to old templates (register4cal) """"""""""""""""""""""""""""""""""""""""""""" .. container:: table-row Static Template Compatibility to old templates (register4cal) Usage General settings for this extension, fitting to the old template files used in previous versions of this extension. Use instead of “Basic settings” if you have modified template files from register4cal versions up to 0.6.2. This template should not be used for fresh installations as it might me removed in the future. .. ###### END~OF~TABLE ###### .. _Adapt-TypoScript-settings-to-your-needs: Adapt TypoScript settings to your needs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ When using the “Basic settings” static template, there is only one setting which needs to be adapted. Add :: plugin.tx_register4cal_pi1.singleEventPid = [pid] to your TypoScript template and replace [pid] with the page id, that contains the Calendar Base plugin for single event display. .. _Recommended-Adapt-settings-for-calendar-base-extension: Recommended: Adapt settings for “calendar base” extension ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ To find out, which frontend users are organizers for events, this extension expands the organizer records of the Calendar Base extension, so that frontend users can be assigned. But the Calendar Base extension also provide the possibility to assign freely typed in organizers for events. For events, which have a freely typed in organizer, this extension can not determine the matching frontend user. Therefore the organizer textfield should not be used for calender events. The Calendar Base extension provides the possibility to hide the organizer textfield. For this extension it is recommended to activate this option. If you wish to do so, log on to the TYPO3 Backend and go to “Ext. Manager” → “Loaded extension”. Click on the Frontend Plugin “Calendar Base”. In the “Enable features” section, you will find an option “Hide organizer textfield”. Activate it and click on the “Update” button. |img-9| *Illustration 7: Calendar Base setting "Hide organizer textfield"* .. _Users-manual: Users manual ------------ .. _Activate-the-registration-for-an-event: Activate the registration for an event ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ To activate the registration for an event, simply display the event in the TYPO3 Backend and go to the “Registration” tab. |img-10| *Illustration 8: Activate registration for an event* Registration sepecific fields After checking the field “Activate registration” TYPO3 asks you to save and refresh the display. Confirm this. The display will be refreshed and show more registration related fields: |img-11| *Illustration 9: Registration related fields for an event* .. ### BEGIN~OF~TABLE ### .. _Activate-registration: Activate registration """"""""""""""""""""" .. container:: table-row Field Activate registration Usage Activate or deactivate the registration for this event. For recurring events, registration is activated for all occurrences of the event. If registration is not activated, all other fields are hidden. .. _Field-set: Field set """"""""" .. container:: table-row Field Field set Usage Choose the set of user-defined fields to be shown for the registration for this event. - “Don't use any user fields” will show no user-defined fields - “Use default field set” will use the field set marked as default. If multiple field sets have the “default” option set, the first one found will be used - If you select a defined field set, this field set will be used .. _Registration-start: Registration start """""""""""""""""" .. container:: table-row Field Registration start Usage Date since when registering for this event should be possible. If you leave this field empty, users can register immediately for the event. .. _Registration-end: Registration end """""""""""""""" .. container:: table-row Field Registration end Usage Date till when registering for this event should be possible. If you leave this field empty, users can register until the start date of the event. .. _Maximum-number-of-attendees: Maximum number of attendees """"""""""""""""""""""""""" .. container:: table-row Field Maximum number of attendees Usage Maximum number of attendees, which should be able to register for this event. If you leave this field empty, registering is possible for an unlimited number of attendees. .. _Activate-waitlist: Activate waitlist """"""""""""""""" .. container:: table-row Field Activate waitlist Usage If activated, users can enlist to a waitlist, of the maximum number of attendees has been reached. If not activated, no further registrations are possible if the event is fully booked. .. ###### END~OF~TABLE ###### .. _Assigning-organizers-to-the-event: Assigning organizers to the event """"""""""""""""""""""""""""""""" Besides from the registration specific fields, the organizer setting of the event is important, if the organizer should be able to see registrations for this event in the frontend. On the Organizer tab, there are two possibilities to assign the organizer, if the Organizer Textfield has not been hidden as described in the Installation section. If you assign a Calender Event Organizer record, the fronent users, linked to that record, will be able to see the registrations for this event. Do not use the Organizer Textfield, if you wish to use this functionality. |img-12| *Illustration 10: Assigning an organizer to an event* The Calendar Base extension provides the possibility to hide the Event Organizer Textfield. It is recommended that you do this. Please refer to the description in the Installation section on how to do this. .. _Linking-Calender-Event-Organizers-and-Frontend-Users-Groups: Linking Calender Event Organizers and Frontend Users/Groups ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. _If-cal-is-configured-to-use-the-Calendar-Base-Organizer-data-model: If cal is configured to use the Calendar Base Organizer data model """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" If cal is configured to use the build in Calendar Base Organizer data model organizers are stored as separate records. In order to allow frontend users to see registrations for events for which they are the organizers, it's additionally important to link Calender Event Organizers and Frontend Users. This can be done in the Calender Event Organizer records of the Calendar Base extension. This extension adds an additional field to the record: |img-13| *Illustration 11: Link Calendar Event Organizers and Frontend Users/Groups* In this field you can select Website user and Website usergroup records and assign them to the organizer. If such an Calender Event organizer has been asigned to a Calender Event, these users can see who registered for an event and may use additional administrational functions for the event. .. _If-cal-is-configured-to-use-Frontend-Users-as-organizer-data-model: If cal is configured to use Frontend Users as organizer data model """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" In this case nothing needs to be configured. Register4cal will automatically recognize the setting and show the relevant events if the frontend user is logged on. .. _User-defined-fields: User-defined fields ^^^^^^^^^^^^^^^^^^^ User-defined fields are grouped into field sets. These field sets can be used for registrations. You can create your own fields by adding “Registration for calender events: Fields” records. User-defined fields need to be stored on the same Page/SysFolder where the events are stored.Alternatively they can be stored in the configured storage folder. The record for an user-defined field is displayed in the TYPO3 Backend as following: |img-14| *Illustration 12: User-defined field* .. ### BEGIN~OF~TABLE ### .. _Language: Language """""""" .. container:: table-row Field Language Usage Language selection. Create a record for language “Default” first. If required, fields can be translated using the normal TYPO3 record translation functionality. .. _Name: Name """" .. container:: table-row Field Name Usage Name of the field. Field names need to be unique. .. _Caption: Caption """"""" .. container:: table-row Field Caption Usage Caption of the field. This value is shown in the registration form. .. _Type: Type """" .. container:: table-row Field Type Usage Type of the field. Depending on the type, different input controls are shown in the registration form. Also, different other options will be shown in TYPO3 Backend. Possible types are: - Simple Textfield - Multiline Textfield - Selectionbox .. _Options-Selectionbox: Options(Selectionbox) """"""""""""""""""""" .. container:: table-row Field Options(Selectionbox) Usage Define the options to be shown in the selection box. Separate multiple options by “\|” .. _Default-value-all-field-types: Default value(all field types) """""""""""""""""""""""""""""" .. container:: table-row Field Default value(all field types) Usage Default value for the field .. _Width-all-field-types: Width(all field types) """""""""""""""""""""" .. container:: table-row Field Width(all field types) Usage Width of the field .. _Height-Mutliline-Textfield: Height(Mutliline Textfield) """"""""""""""""""""""""""" .. container:: table-row Field Height(Mutliline Textfield) Usage Height for multiline textfield .. _Height-Selectionbox: Height(Selectionbox) """""""""""""""""""" .. container:: table-row Field Height(Selectionbox) Usage Height for selection box. Set to 1 to display a drop down selection, Set to greater than 1 to display a selection list with the given height. .. _Field-contains-number-of-participants-Simple-Textfield: Field contains number of participants(Simple Textfield) """"""""""""""""""""""""""""""""""""""""""""""""""""""" .. container:: table-row Field Field contains number of participants(Simple Textfield) Usage Indicates, that the field contains the number of participants which should be registered with this registration. If set, the value of this field will be taken as the number of participants for a registration. If no such field is contained in a fieldset for a registration, 1 participant is being counted per registration. .. ###### END~OF~TABLE ###### .. _Field-sets: Field sets ^^^^^^^^^^ User-defined fields are grouped into field sets. These field sets can be used for registrations. You can create your own field sets by adding “Registration for calendar events: Field sets” records. Field sets need to be stored on the same Page/SysFolder where events and fields are stored. Alternatively they can be stored in the configured storage folder. Field sets can only use fields, which are stored in the same Page/SysFolder. The record for a field set is displayed in the TYP3 Backend as following: |img-15| *Illustration 13: Field set* .. ### BEGIN~OF~TABLE ### .. _Name: Name """" .. container:: table-row Field Name Usage Name of the field. Used to select field set in event record. .. _Fields: Fields """""" .. container:: table-row Field Fields Usage Select the user-defined fields to use in the fieldset here .. _Default-field-set: Default field set """"""""""""""""" .. container:: table-row Field Default field set Usage If set, this field set is being used as default fieldset. “Use default fieldset” is the default setting for the field set selection in the event record. If multiple field sets with this option set exist, this first one found will be used. .. ###### END~OF~TABLE ###### .. _Set-storage-folder-for-fields-and-fieldsets: Set storage folder for fields and fieldsets ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ User-defined fields and fieldsets will first of all be be searched in the folder, containing the event records. In case you have your event records only on a single page/sysfolder, there is nothing else to do than store the field and fieldset records on this page/sysfolder, too. If you are using multiple pages/sysfolders to store your events, you may want global fields and fieldsets for all events. In this case you can define the page id (pid) of a page/sysfolder from which fields and fieldgroups are used, too. This can be configured via the Extension Manager in the extension configuration of this extension. |img-16| *Illustration 14: Extension Configuration in Extension Manager* After changing this settings it is required to clear the cache so that the changes become effective. FAQ ^^^ .. _Even-though-I-activated-the-registration-feature-the-single-event-view-does-not-show-the-registration-form: Even though I activated the registration feature, the single event view does not show the registration form. """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" Check if you are inside the registration period. Check if a frontend user has logged on .. _The-registration-form-is-being-displayed-well-in-the-single-event-view-but-the-event-list-view-does-not-show-the-registration-possibility: The registration form is being displayed well in the single event view, but the event list view does not show the registration possibility. """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" Read the section on enabling list view registration. Some changes need to be done in the list view templates to activate registration in event list view. .. _My-user-defined-field-is-not-being-shown-in-the-registration-form: My user-defined field is not being shown in the registration form. """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" Did you include your user-defined field into a field set? Did you include it in the field set used for the registration for this event? .. _What-happens-if-I-change-a-field-or-field-set-after-it-has-been-used-for-a-registration: What happens if I change a field or field set after it has been used for a registration? """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" Nothing. Existing registrations will not be affected by changes on fields or field sets. For new registrations always the current definition of fields/field sets is being used. .. _I-need-an-additional-field-type-for-my-user-defined-fields-how-can-I-set-it: I need an additional field type for my user-defined fields, how can I set it? """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" Currently it is not possible to define additional field types (except from modifying this extensions coding). If you have a good reason to add another field type, write an email and I'll see what I can do. .. _Administration: Administration -------------- .. _Enabling-registration-in-event-list-view: Enabling registration in event list view ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ To activate the registration feature in the event list view of the Calendar Base Extension, additional markers need to be included in the Calendar Base templates. .. _Marker-for-submit-button: Marker for submit button """""""""""""""""""""""" The marker ###MODULE\_\_tx\_register4cal\_submit### inserts the submit button for the registration form. It should be added in the list template (default: EXT:cal/template/list/tmpl) in subpart “###LIST\_TEMPLATE###”. The marker can be added twice to show the button both button on top and below the event list. Please notice the double underscore in the marker name after “MODULE”. .. _Example: Example ~~~~~~~ ::

###PAGEOF### ###PAGES### ###PREVIOUS### ###NEXT###

###HEADING###

###FOUND### ###MODULE__tx_register4cal_submit###
###MODULE__tx_register4cal_submit###

###PAGEOF### ###PAGES### ###PREVIOUS### ###NEXT###

###CREATE_EVENT_LINK### .. _Marker-for-registration-box: Marker for registration box """"""""""""""""""""""""""" The marker “###MODULE\_tx\_register4cal\_listreg” (notice the doule underscore after “MODULE”) inserts the registration box for each event. It needs to be added to the event template (default: EXT:cal/template/phpicalendar\_event.tmpl, since Calendar Base 1.3.0 EXT:/cal/template/event\_model.tmpl). There are several subparts for event display to which the marker should be added: - ###TEMPLATE\_PHPICALENDAR\_EVENT\_LIST\_ODD### - ###TEMPLATE\_PHPICALENDAR\_EVENT\_LIST\_EVEN### - ###TEMPLATE\_PHPICALENDAR\_EVENT\_LIST\_ODD\_ALLDAY### - ###TEMPLATE\_PHPICALENDAR\_EVENT\_LIST\_EVEN\_ALLDAY### .. _Example: Example ~~~~~~~ ::
###IMAGE### ###TITLE###
###STARTDATE### ###ENDDATE### ###STARTTIME### ###ENDTIME###
###MODULE__tx_register4cal_listreg###
###CATEGORY_LINK###
###DESCRIPTION###
.. _Example-templates-for-Calendar-Base: Example templates for Calendar Base """"""""""""""""""""""""""""""""""" This extension contains modified templates for Calendar Base for the event list view. From version 1.4.0 on, cal contains a new set of templates, called “Standard”. The previously used templates are still contained and called “Classic”. The extension register4cal contains adapted templates for both the standard and the classic templates. These files can be found in EXT:register4cal/templates/cal\_standard and EXT:register4cal/templates/cal\_classic. With some lines of TypoScript, you can use the template files from this folder, where the required markers for registration in event list view have been added already. .. _Typoscript: Typoscript ~~~~~~~~~~ :: plugin.tx_cal_controller.view { list.listTemplate = EXT:register4cal/templates/cal_standard/list.tmpl event.eventModelTemplate = EXT:register4cal/templates/cal_standard/event_model.tmpl } .. _Enabling-fields-for-frontend-editing: Enabling fields for frontend editing ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This extension supports the Calendar Base frontend editing of events. The additional fields related to the registraion feature can be added via markers to the template files of the Calendar Base extension. In addition, some TypoScript settings are required. .. _Adding-static-template: Adding static template """""""""""""""""""""" All TypoScript settings, related to Calendar Base frontend editing have been put into the static template “FE-Editing (register4cal)”. Ensure you have included this static template to your TypoScript template(s), so that the settings will be taken into account. **IMPORTANT:** If you have other additional fields defined for Calendar Base frontend editing, you need to combine these settings manually with the settings of this extension. .. _Template-files-to-modify: Template files to modify """""""""""""""""""""""" There are two templates which need to be modified. Please ensure that you add all markers to both files, as otherwise the fields wont work for frontend editing. .. ### BEGIN~OF~TABLE ### .. _EXT-cal-template-create-event-tmpl: EXT:/cal/template/create\_event.tmpl ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row File (Default) EXT:/cal/template/create\_event.tmpl Usage Event creation and modification template .. _EXT-cal-template-confirm-event-tmpl: EXT:/cal/template/confirm\_event.tmpl ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row File (Default) EXT:/cal/template/confirm\_event.tmpl Usage Template for confirmation of event changes .. ###### END~OF~TABLE ###### .. _Markers-for-registration-related-fields: Markers for registration related fields """"""""""""""""""""""""""""""""""""""" The following markers can be used on the templates. Please notice the double underscore after “MODULE” and the upper/lower case of the markers .. ### BEGIN~OF~TABLE ### .. _MODULE-tx-register4cal-activate: ###MODULE\_tx\_register4cal\_activate### ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Marker ###MODULE\_tx\_register4cal\_activate### Usage Field “Activate registration” .. _MODULE-tx-register4cal-field: ###MODULE\_tx\_register4cal\_field### ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Marker ###MODULE\_tx\_register4cal\_field### Usage Field “fieldset” .. _MODULE-tx-register4cal-regstart: ###MODULE\_tx\_register4cal\_regstart### ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Marker ###MODULE\_tx\_register4cal\_regstart### Usage Field “Start of registration period” .. _MODULE-tx-register4cal-regend: ###MODULE\_tx\_register4cal\_regend### ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Marker ###MODULE\_tx\_register4cal\_regend### Usage Field “End of registration period” .. _MODULE-tx-register4cal-maxattendees: ###MODULE\_tx\_register4cal\_maxattendees### ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Marker ###MODULE\_tx\_register4cal\_maxattendees### Usage Field “Maximum number of attendees” .. _MODULE-tx-register4cal-waitlist: ###MODULE\_tx\_register4cal\_waitlist### ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Marker ###MODULE\_tx\_register4cal\_waitlist### Usage Field “Activate waitlist” .. ###### END~OF~TABLE ###### .. _Create-an-own-tab-for-the-registration-related-fields: Create an own tab for the registration related fields """"""""""""""""""""""""""""""""""""""""""""""""""""" To create an own tab for the registration related fields for Calendar Base frontend editing, the fields should not be added to the fields inside an existing tab. Instead a new div section has to be created whose id has to be numbered consecutively to the existing div sections. .. _Example: Example ~~~~~~~ ::
###MODULE__tx_register4cal_activate### ###MODULE__tx_register4cal_regstart### ###MODULE__tx_register4cal_regend### ###MODULE__tx_register4cal_maxattendees### ###MODULE__tx_register4cal_waitlist### ###MODULE__tx_register4cal_fieldset###
Using the following lines of TypoScript, the caption for the tab is being set: .. _Example: Example ~~~~~~~ :: plugin.tx_cal_controller.view { create_event.tabbedMenu { 7 = TEXT 7.dataWrap =
  • Registration
    • } edit_event.tabbedMenu { 7 = TEXT 7.dataWrap =
  • Registration
    • } } On a multilanguage site you may want to replace the static text “Registration” in the above example with :: {LLL:EXT:register4cal/locallang_db.xml:tx_cal_event.tx_register4cal_tablabel} This will translate the caption if this extension contains a proper translation for the language used. .. _Using-rlmp-dateselectlib: Using rlmp\_dateselectlib """"""""""""""""""""""""" This extension supports the extension rlmp\_dateselectlib for front end editing. With rlmp\_dateselectlib a date selector can be added to the “Start/End of registration period” fields. If you want to activate this feature perform the following steps: - Ensure the rlmp\_dateselectlib extension is installed - Set the TypoScript setting plugin.tx\_register4cal.edit.useDateSelector to 1 - Configure the date selector in TypoScript section plugin.tx\_register4cal.edit.calConf. The settings in this section are taken from the rlmp\_dateselectlib extension, therefore please refer to the manual of rlmp\_dateselectlib for further details on these settings By default, the use of rlmp\_dateselectlib is activated in this extension, so that the only task would be to install rlmp\_dateselectlib. .. _Example-templates-for-Calendar-Base: Example templates for Calendar Base """"""""""""""""""""""""""""""""""" This extension contains modified templates for Calendar Base for frontend editing. These files can be found in EXT:register4cal/templates/cal\_standard and EXT:register4cal/templates/cal\_classic. If you are using a Calendar Base version less than 1.4.0, use cal\_classic. For version from 1.4.0 on, use cal\_classic if you are using the “Classic” templates from Calendar Base and cal\_standard for the “Standard” templates from Calendar Base. With some lines of TypoScript, you can use the template files from this folder, where the required markers for frontend editing have been added already. .. _Typoscript: Typoscript ~~~~~~~~~~ :: plugin.tx_cal_controller.view { create_event.template = EXT:register4cal/templates/cal_standard/create_event.tmpl edit_event.template = EXT:register4cal/templates/cal_standard/create_event.tmpl confirm_event.template = EXT:register4cal/templates/cal_standard/confirm_event.tmpl create_event.tabbedMenu { 7 = TEXT 7.dataWrap =
  • {LLL:EXT:register4cal/locallang_db.xml:tx_cal_event.tx_register4cal_tablabel}
    • } edit_event.tabbedMenu { 7 = TEXT 7.dataWrap =
  • {LLL:EXT:register4cal/locallang_db.xml:tx_cal_event.tx_register4cal_tablabel}
    • } } .. _Telling-users-that-they-need-to-log-in: Telling users that they need to log in ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ By default no registration forms will be shown if no frontend user has logged in. You may want to change this, so that in this case an information will be shown and links to registration pages will be presented in event single view. It's not possible to use the “need to login” form for the event list view. To enable the “need to login” form, se the following TypoScript parameter: :: plugin.tx_register4cal_pi1.needLoginForm.disable = 0 By default the form now shows two buttons: - Login using an existing account - Create an one-time account Both buttons need some additional customizing. .. _Login-using-an-existing-account: Login using an existing account """"""""""""""""""""""""""""""" To login with an existing account, usually the TYPO3 system extension felogin is being used. You need to set the following TypoScript parameters, which reside in the “plugin.tx\_register4cal\_pi1” section: .. ### BEGIN~OF~TABLE ### .. _needLoginForm-loginpid: .needLoginForm.loginpid ~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Parameter .needLoginForm.loginpid Usage Page id of page, containing the “Login” plugin from the felogin extension .. _needLoginForm-loginreturnparam: .needLoginForm.loginreturnparam ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Parameter .needLoginForm.loginreturnparam Usage URL parameter name, telling the login plugin to which page the user should be forwarded, once he has logged in successfully. For felogin this is “redirect\_url”. .. ###### END~OF~TABLE ###### If these parameters have been set properly, the user can click on the “Login using an existing account” button and will be forwarded to the login form. After sucessfully loggin in, he will be sent back the event single view where he can register. .. _Create-an-one-time-account: Create an one-time account """""""""""""""""""""""""" This option requires the extension onetimeaccount to be setup and configured as described in it's manual. In addition the following TypoScript parameters need to be set, which also reside in the “plugin.tx\_register4cal\_pi1” section: .. ### BEGIN~OF~TABLE ### .. _needLoginForm-onetimepid: .needLoginForm.onetimepid ~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Parameter .needLoginForm.onetimepid Usage Page id of page, containing the “One-time FE account creator” plugin from the onetimeaccount extension .. _needLoginForm-onetimereturnparam: .needLoginForm.onetimereturnparam ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Parameter .needLoginForm.onetimereturnparam Usage URL parameter name, telling the plugin to which page the user should be forwarded, once he has created an account successfully. For onetimeaccount this is “redirect\_url”. .. ###### END~OF~TABLE ###### If these parameters have been set properly, the user can click on the “Create an one-time account” button and will be forwarded to the account creation form. After sucessfully creating his account, he will be sent back to the event single view where he can register. .. _Displaying-event-related-fields: Displaying event-related fields """"""""""""""""""""""""""""""" Usually, no event-related fields are contained in the message, telling the user that he needs to log in. It may be required to show such fields (e.g. the number of free places). In this case you can add the relevant markers (for example ###MAXATTENDEES###, ###NUMATTENDEES###, ###NUMWAITLIST### oder ###NUMFREE###) in template section ###SINGLE\_NEEDLOGIN###. .. _Display-of-users-which-have-already-registered-during-after-registration: Display of users which have already registered during/after registration ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ It may be requested that a list of users which have already registered for an event should be displayed in the registration form. This functionality can be activated via TypoScript Parameters in section „plugin.tx\_register4cal\_pi1.showOtherRegisteredUsersAtRegistration“: .. ### BEGIN~OF~TABLE ### .. _enable: .enable """"""" .. container:: table-row Parameter .enable Usage Activates the display of other registered users (1=Active, 0=Inactive).Default: Inactive .. _onlyAfterRegistration: .onlyAfterRegistration """""""""""""""""""""" .. container:: table-row Parameter .onlyAfterRegistration Usage Configure if the list should only be displayed when an user has registered or if it will be displayed always. (1=Only after registration, 0=always). Default: Only after registration .. _includeOwnRegistration: .includeOwnRegistration """"""""""""""""""""""" .. container:: table-row Parameter .includeOwnRegistration Usage Show the own registration of an user in the list (1=Yes, 0=No). Default: Yes .. _includeWaitlist: .includeWaitlist """""""""""""""" .. container:: table-row Parameter .includeWaitlist Usage Show registrations on the waitlist in the list (1=Yes, 0=No). Default: No .. _includeCancelled: .includeCancelled """"""""""""""""" .. container:: table-row Parameter .includeCancelled Usage Show cancelled registrations in the list (1=Yes, 0=No). Default: No .. ###### END~OF~TABLE ###### As this function may lead to questions related to data privacy, every user can decide whether his data should be visible for other users or not during registration. For this purpose an additional checkbox will be displayed in the registration form if this functionality is activated. Other users get to see the data only, if the user ticked this checkbox. Differing from this the organizer of the event can see all registered users. To configure the displayed data the section “OTHER\_USERS\_LIST” is available in the template, which encloses the complete List. Inside this section “OTHER\_USER” encloses a single registration from another user. Inside this sections all markers available in the registration form can be used. It only needs to be considered, that all markers in this sections relate to the registration of the other user. Though the checkbox to confirm that other users may see the registration is being displayed in the listview registration form, the list of other registrations is not supported there. .. _vCard-files-with-participant-or-organizer-information: vCard files with participant or organizer information ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ From version 0.19.0 on register4cal can create vCard files containing participant or organizer information. If the vCard functionality for participant information is active, a vCard file with participant information will be attached to the notification email sent to the organizer of an event. If the vCard functionality for organizer information is active, a vCard file with organizer information will be attachet to the confirmation email sent to the participant. For the list “Registrations for events of the frontend user”an additional marker “PARTICIPANTVCARDLINK” is available. It allows the download of a vCard filewith participant informationfrom the list.In the list “Registrations of the frontend user” the marker “ORGANIZERVCARDLINK” allows the download of a vCard file with organizer information. The settings for this functionality are contained in the TypoScript sections “plugin.tx\_register4cal\_pi1.vcardParticipant” and “plugin.tx\_register4cal\_pi1.vcardOrganizer” .. ### BEGIN~OF~TABLE ### .. _enable: .enable """"""" .. container:: table-row Parameter .enable Usage Activation of vCard functionality (1=Active, 0=Inactive).Default: Active .. _typeNum: .typeNum """""""" .. container:: table-row Parameter .typeNum Usage typeNum parameter used for the link to download vCard file. The setup for the vCard download page is contained in the typoScript configuration of register4cal. As the same typeNum needs to be used there, the value is being read from constant plugin.tx\_register4cal\_pi1.vcard.typeNum. Therefore, you should not change this value here. Change the value of the constant instead. typeNum parameters have to be unique in an Typo3 Installation. If the default value from register4cal is being used from another extension, you should change the value in register4cal. To do so, change the value of constant plugin.tx\_register4cal\_pi1.vcard.typeNum to any nummeric value that is not used by another page/extension. Default: 159 .. _filename: .filename """"""""" .. container:: table-row Parameter .filename Usage Filename for the generated vCard file Default: participant.vcf / organizer.vcf .. _fieldmapping: .fieldmapping """"""""""""" .. container:: table-row Parameter .fieldmapping Usage Assignment of table fields to vCard fields. Default values and detailed description can be found in the next section .. ###### END~OF~TABLE ###### .. _Assignment-of-table-fields-to-vcard-fields: Assignment of table fields to vcard fields """""""""""""""""""""""""""""""""""""""""" Inside the section “fieldmapping” in the vCard settings you can define, which table fields will be used for which fields in the vCard file. You can use fields from different tables, using for the registration: .. ### BEGIN~OF~TABLE ### .. _Events: Events ~~~~~~ .. container:: table-row Table Events Setting to get field value EVENT\_[Feldname] .. _Event-locations: Event locations ~~~~~~~~~~~~~~~ .. container:: table-row Table Event locations Setting to get field value LOCATION\_[Feldname] .. _Event-organizer: Event organizer ~~~~~~~~~~~~~~~ .. container:: table-row Table Event organizer Setting to get field value ORGANIZER\_[Feldname] .. _Frontend-user: Frontend user ~~~~~~~~~~~~~ .. container:: table-row Table Frontend user Setting to get field value USER\_[Feldname] .. _Userdefined-fields: Userdefined fields ~~~~~~~~~~~~~~~~~~ .. container:: table-row Table Userdefined fields Setting to get field value UDEF\_[Feldname] .. ###### END~OF~TABLE ###### In a vCard file there are different types of fields: - Fields which appear once and have only a single value (e.g. name, date of birth, company, etc.) - Fields which appear multiple times and additionally have a type classification (phone, email, url and address) .. _Fields-which-appear-only-once: Fields which appear only once ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Simple Fields which appear only once are being assigned directly. The following values will be used as default: .. ### BEGIN~OF~TABLE ### .. _: :: '' .. container:: table-row a :: plugin.tx_register4cal_pi1.vcardParticipant.fieldmapping { uid = USER_uid fullname = USER_name title = USER_title firstname = USER_first_name lastname = USER_last_name additionalnames = USER_middle_name nameprefix = namesuffix = nickname = USER_username birthday = organization = USER_company department = subdepartment = role = revision = geolocation = mailer = timezone = } .. ###### END~OF~TABLE ###### This list is also a final List of the supported simple fields. .. _Fields-for-phone-email-and-URL: Fields for phone, email and URL ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Phone numbers, email addresses and URLs can appear multiple times. They all have a value and additionally a type classification. The sections for phone, email and URL have therefore several subsections. The value of each subsection is the phone number, email or URL. Inside the subsection the available type classifications are listed. Set a type classification to 1 to assign it to the value. .. ### BEGIN~OF~TABLE ### .. _: :: '' .. container:: table-row a :: plugin.tx_register4cal_pi1.vcardParticipant.fieldmapping { phonenumbers { 0 = USER_telephone 0 { PREF = 0 WORK = 0 HOME = 1 OTHER = 0 VOICE = 1 FAX = 0 MSG = 0 CELL = 0 CAR = 0 } 1 = USER_fax 1 { PREF = 0 WORK = 0 HOME = 1 OTHER = 0 VOICE = 0 FAX = 1 MSG = 0 CELL = 0 CAR = 0 } } emails { 0 = USER_email 0 { INTERNET = 0 HOME = 1 WORK = 0 OTHER = 0 PREF = 0 } } urls { 0 = USER_www 0 { WORK = 0 HOME = 1 OTHER = 0 PREF = 0 } } } .. ###### END~OF~TABLE ###### .. _Fields-for-addresses: Fields for addresses ~~~~~~~~~~~~~~~~~~~~ Addresses have the most complex structure. They can appear multiple times and each address has multiple fields and additionally a type classification, too. So addresses have multiple subsections, as well. However, the values of the fields will be assigned inside the subsections. The type classification is being done inside a section “type”, .. ### BEGIN~OF~TABLE ### .. _: :: '' .. container:: table-row a :: plugin.tx_register4cal_pi1.vcardParticipant.fieldmapping { addresses { 0 { postofficeaddress = extendedaddress = street = USER_address city = USER_city zip = USER_zip country = USER_country type { DOM = 0 INTL = 0 POSTAL = 0 PARCEL = 0 HOME = 1 WORK = 0 } } } } .. ###### END~OF~TABLE ###### .. _Configuration: Configuration ------------- The whole extension can be configured via TypoScript. All settings can be done in section “plugin.tx\_register4cal\_pi1”. Besides some general settings, these section contains the following subsections: - foreignUserRegistration: Settings related to the registration of foreign users by event organizers. - needLoginForm: Settings related to the form which informs about the necessarity to login if no frontend user has logged in. - email: Settings related to emails to be send from this extension. - vcardParticipant: Settings related to vCard files with participant information - vcardOrganizer: Settings related to vCard files with organizer information - forms: Settings related to forms displayed from this extension .. _Reference: Reference ^^^^^^^^^ .. _General-settings: General settings """""""""""""""" .. ### BEGIN~OF~TABLE ### .. _templateFile: templateFile ~~~~~~~~~~~~ .. container:: table-row Property templateFile Data type string Description Filename of the template file to use Default EXT:register4cal/templates/register.tmpl .. _dateformat: dateformat ~~~~~~~~~~ .. container:: table-row Property dateformat Data type string Description Date format to use (pear syntax) Default %d.%m.%Y .. _timeformat: timeformat ~~~~~~~~~~ .. container:: table-row Property timeformat Data type string Description Time format to use (pear syntax) Default %H:%M .. _disableWaitlist: disableWaitlist ~~~~~~~~~~~~~~~ .. container:: table-row Property disableWaitlist Data type boolean Description Disable waitlist functionality Default 0 .. _disableUnregister: disableUnregister ~~~~~~~~~~~~~~~~~ .. container:: table-row Property disableUnregister Data type boolean Description Disable unregistering from events for users Default 0 .. _useWaitlistIfNotEnoughPlaces: useWaitlistIfNotEnoughPlaces ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Property useWaitlistIfNotEnoughPlaces Data type boolean Description If an event has a limited number of places and an user tries to register more places than available, you can use this parameter to decide what should happen: 1: Instead of a registration a waitlist entry will be created. The user will be notified of this. 0: The user will receive an error that he can not register this much attendees. This also happens if the parameter is set to 1 and no waitlist is available for the event Default 1 .. _eventFillMode: eventFillMode ~~~~~~~~~~~~~ .. container:: table-row Property eventFillMode Data type integer Description Mode to fill up the event. Used in case someone has enlisted to the waitlist, because there are not enough places left for his registration (see parameter useWaitlistIfNotEnoughPlaces) and for updating waitlist entries to registrations if someone unregisters from the event. **1: First come first serve principle** Everyone else can also enlist to the waitlist only. Even if he requests to register less attendees, which would be possible as there are enough free places for the event, he can only create a waitlist entry because someone else came first. If any other user unregisters from the event, only the first waitlist entry will be checked and transferred to a normal registration if there are enough free places. Later entries in the waitlist will not be checked, even if they contain less attendees. **2: Maximum fill principle** Any other user can register for the event if there are enough places left, even if there are already entries on the waitlist. If an user unregisters the whole waitlist will be checked and any entry, having less or equal attendees than number of free places, will be transferred to a registration. Default 1 .. _keepUnregistered: keepUnregistered ~~~~~~~~~~~~~~~~ .. container:: table-row Property keepUnregistered Data type integer Description Keep registrations after unregistering. These registrations will be shown as “cancelled” for the event organizer. Default 1 .. _adminUsers: adminUsers ~~~~~~~~~~ .. container:: table-row Property adminUsers Data type integer Description id's of frontend users which will be treated as event organizers for every event. Default .. _singleEventPid: singleEventPid ~~~~~~~~~~~~~~ .. container:: table-row Property singleEventPid Data type integer Description page id of page used to show the event single view. Default .. ###### END~OF~TABLE ###### [tsref:plugin.tx\_register4cal\_pi1] .. _Foreign-user-registrations: Foreign user registrations """""""""""""""""""""""""" Settings related to the registration of foreign users by event organizers can be found in section “plugin.tx\_register4cal\_pi1.foreignUserRegistration”. .. ### BEGIN~OF~TABLE ### .. _enable: enable ~~~~~~ .. container:: table-row Property enable Data type boolean Description Enable or disable the registration of foreign users by event organizers Default 0 .. _allowOnlyGroups: allowOnlyGroups ~~~~~~~~~~~~~~~ .. container:: table-row Property allowOnlyGroups Data type string Description List of groups, which need to be assigned to users that should be selectable as participants for foreign user registration. If set, only users having one of these groups assigned, will be shown for foreign user registration. Default .. _denyGroups: denyGroups ~~~~~~~~~~ .. container:: table-row Property denyGroups Data type string Description List of groups whose users must not be selectable for foreign user registration. If set, users having one of these groups assigned, will not be shown for foreign user registration. Default .. ###### END~OF~TABLE ###### [tsref:plugin.tx\_register4cal\_pi1.foreignUserRegistration] .. _Hint: Hint: ~~~~~ allowOnlyGroups overwrites denyGroups. If allowOnlyGroups is set, denyGroups will not be taken into account. .. _need-to-login-form: “need to login” form """""""""""""""""""" Settings related to the form, informing visitors that they need to login can be found in section “plugin.tx\_register4cal\_pi1.needLoginForm”. .. ### BEGIN~OF~TABLE ### .. _disable: disable ~~~~~~~ .. container:: table-row Property disable Data type boolean Description Enable or disable the display of the “need to login” form. If the form is disabled and no user has logged in, nothing will be displayed Default 1 .. _loginpid: loginpid ~~~~~~~~ .. container:: table-row Property loginpid Data type integer Description page id of the page containing the login form for existing users (usually from system extension felogin) Default .. _loginreturnparam: loginreturnparam ~~~~~~~~~~~~~~~~ .. container:: table-row Property loginreturnparam Data type string Description Name of parameter used to tell the login form who which page it should return after a successful login Default redirect\_url .. _onetimepid: onetimepid ~~~~~~~~~~ .. container:: table-row Property onetimepid Data type integer Description page id of the page containing the login form for onetime accounts (from extension onetimeaccount) Default .. _onetimereturnparam: onetimereturnparam ~~~~~~~~~~~~~~~~~~ .. container:: table-row Property onetimereturnparam Data type string Description Name of parameter used to tell the onetime-account login form who which page it should return after a successful login Default redirect\_url .. ###### END~OF~TABLE ###### [tsref:plugin.tx\_register4cal\_pi1.needLoginForm] .. _Sending-emails: Sending emails """""""""""""" Settings related to emails sent from this extension can be found in section “plugin.tx\_register4cal\_pi1.emails”. .. ### BEGIN~OF~TABLE ### .. _sendConfirmation: sendConfirmation ~~~~~~~~~~~~~~~~ .. container:: table-row Property sendConfirmation Data type boolean Description Enable or disable confirmation emails to be sent to the user registering for an event Default 0 .. _sendNotification: sendNotification ~~~~~~~~~~~~~~~~ .. container:: table-row Property sendNotification Data type boolean Description Enable or disable notification emails to be sent to the event organizer Default 0 .. _senderName: senderName ~~~~~~~~~~ .. container:: table-row Property senderName Data type string Description Plain text name which should be used as sender for the emails Default .. _senderAddress: senderAddress ~~~~~~~~~~~~~ .. container:: table-row Property senderAddress Data type string Description Email address which should be used as sender for the emails Default .. _adminAddress: adminAddress ~~~~~~~~~~~~ .. container:: table-row Property adminAddress Data type string Description Email address where all registration emails should be send, too (e.g. event supervisor) Default .. ###### END~OF~TABLE ###### [tsref:plugin.tx\_register4cal\_pi1.emails] .. _Vcard-files-with-participant-or-organizer-information: Vcard files with participant or organizer information """"""""""""""""""""""""""""""""""""""""""""""""""""" Settings related to vCardfiles containing the participant information can be found in section “plugin.tx\_register4cal\_pi1.vcardParticipant”. Settings related to vCardfiles containing the organizer information can be found in section “plugin.tx\_register4cal\_pi1.vcardOrganizer”. Both sections have the same structure. .. ### BEGIN~OF~TABLE ### .. _enable: enable ~~~~~~ .. container:: table-row Property enable Data type boolean Description Enable or disable the attachment of vCardfiles to notification emails Default 1 .. _filename: filename ~~~~~~~~ .. container:: table-row Property filename Data type string Description Filename for attached vCardfile Default Participant.vcf .. _typeNum: typeNum ~~~~~~~ .. container:: table-row Property typeNum Data type integer Description Page typeNum for vCarddownload page. IMPORTANT: Do not change this value here. Change in constants instead Default (Taken from constants) .. _fieldmapping: fieldmapping ~~~~~~~~~~~~ .. container:: table-row Property fieldmapping Data type Description Assignment of table fields to vCardfields. See section “Administration” → “ vCardfiles with participant or organizer information” for details Default .. ###### END~OF~TABLE ###### [tsref:plugin.tx\_register4cal\_pi1.vcardParticipant] / [tsref:plugin.tx\_register4cal\_pi1.vcardOrganizer] .. _Configuring-output: Configuring output """""""""""""""""" All views can be configured via TypoScript in the “plugin.tx\_register4cal\_pi1.forms” section. There is a subsection for every form, allowing the configuration of this form. .. ### BEGIN~OF~TABLE ### .. _single-default: single.default{} ~~~~~~~~~~~~~~~~ .. container:: table-row Subsection single.default{} Form Default settings, used from all “single.” subsections .. _single-noregister: single.noregister{} ~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection single.noregister{} Form Single event view: Notice that the event is fully booked .. _single-needLogin: single.needLogin{} ~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection single.needLogin{} Form Single event view: Notice that the user needs to register .. _single-registration-enter: single.registration.enter{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection single.registration.enter{} Form Single event view: Registration form for event .. _single-registration-alreadyDone: single.registration.alreadyDone{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection single.registration.alreadyDone{} Form Single event view: Notice and data if user has already registered for an event .. _single-waitlist-enter: single.waitlist.enter{} ~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection single.waitlist.enter{} Form Single event view: Waitlist entry form for event .. _single-waitlist-alreadyDone: single.waitlist.alreadyDone{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection single.waitlist.alreadyDone{} Form Single event view: Notice and data if user has already enlisted on waitlist for an event .. _list-default: list.default{} ~~~~~~~~~~~~~~ .. container:: table-row Subsection list.default{} Form Default settings, used from all “list.” subsections .. _list-submit: list.submit{} ~~~~~~~~~~~~~ .. container:: table-row Subsection list.submit{} Form Event list view: Section with submit button .. _list-registration-enter: list.registration.enter{} ~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection list.registration.enter{} Form Event list view: Registration form for event .. _list-registration-alreadyDone: list.registration.alreadyDone{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection list.registration.alreadyDone{} Form Event list view: Notice and data if user has already registered for an event .. _list-waitlist-enter: list.waitlist.enter{} ~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection list.waitlist.enter{} Form Event list view: Waitlist entry form for event .. _list-waitlist-alreadyDone: list.waitlist.alreadyDone{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection list.waitlist.alreadyDone{} Form Event list view: Notice and data if user has already enlisted on waitlist for an event .. _email-default: email.default{} ~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.default{} Form Default settings, used from all “email.” subsections .. _email-registration-enter-confirmation: email.registration.enter.confirmation{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.registration.enter.confirmation{} Form Email: Confirmation after registration .. _email-registration-enter-notification: email.registration.enter.notification{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.registration.enter.notification{} Form Email: Notification after registration .. _email-registration-enter-confirmation-rfu: email.registration.enter.confirmation\_rfu{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.registration.enter.confirmation\_rfu{} Form Email: Confirmation after registration by event organizer (register foreign user functionality) .. _email-registration-enter-notification-rfu: email.registration.enter.notification\_rfu{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.registration.enter.notification\_rfu{} Form Email: Notification after registration by event organizer (register foreign user functionality) .. _email-registration-cancel-confirmation: email.registration.cancel.confirmation{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.registration.cancel.confirmation{} Form Email: Confirmation after canceled registration .. _email-registration-cancel-notification: email.registration.cancel.notification{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.registration.cancel.notification{} Form Email: Notification after canceled registration .. _email-registration-cancel-confirmation-rfu: email.registration.cancel.confirmation\_rfu{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.registration.cancel.confirmation\_rfu{} Form Email: Confirmation after registration canceled by event organizer (register foreign user functionality) .. _email-registration-cancel-notification-rfu: email.registration.cancel.notification\_rfu{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.registration.cancel.notification\_rfu{} Form Email: Notification after registration canceled by event organizer (register foreign user functionality) .. _email-waitlist-enter-confirmation: email.waitlist.enter.confirmation{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.waitlist.enter.confirmation{} Form Email: Confirmation after enlisting to waitlist .. _email-waitlist-enter-notification: email.waitlist.enter.notification{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.waitlist.enter.notification{} Form Email: Notification after enlisting to waitlist .. _email-waitlist-enter-confirmation-rfu: email.waitlist.enter.confirmation\_rfu{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.waitlist.enter.confirmation\_rfu{} Form Email: Confirmation after enlisting to waitlist by event organizer (register foreign user functionality) .. _email-waitlist-enter-notification-rfu: email.waitlist.enter.notification\_rfu{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.waitlist.enter.notification\_rfu{} Form Email: Notification after enlisting to waitlist by event organizer (register foreign user functionality) .. _email-waitlist-cancel-confirmation: email.waitlist.cancel.confirmation{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.waitlist.cancel.confirmation{} Form Email: Confirmation after canceled enlisting to waitlist .. _email-waitlist-cancel-notification: email.waitlist.cancel.notification{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.waitlist.cancel.notification{} Form Email: Notification after canceled enlisting to waitlist .. _email-waitlist-cancel-confirmation-rfu: email.waitlist.cancel.confirmation\_rfu{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.waitlist.cancel.confirmation\_rfu{} Form Email: Confirmation after enlisting to waitlist canceled by event organizer (register foreign user functionality) .. _email-waitlist-cancel-notification-rfu: email.waitlist.cancel.notification\_rfu{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.waitlist.cancel.notification\_rfu{} Form Email: Notification after enlisting to waitlist canceled by event organizer (register foreign user functionality) .. _email-waitlist-upgrade-confirmation: email.waitlist.upgrade.confirmation{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.waitlist.upgrade.confirmation{} Form Email: Confirmation after waitlist entry upgraded to registration .. _email-waitlist-upgrade-notification: email.waitlist.upgrade.notification{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection email.waitlist.upgrade.notification{} Form Email: Notification after waitlist entry upgraded to registration .. _listOutput-events: listOutput.events{} ~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection listOutput.events{} Form List of events for which an frontend user registered .. _listOutput-attendees: listOutput.attendees{} ~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection listOutput.attendees{} Form List of participants for the event organizers .. _listOutput-registerForeignUser: listOutput.registerForeignUser{} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Subsection listOutput.registerForeignUser{} Form Registering foreign users for the event organizer .. ###### END~OF~TABLE ###### In this sections the following properties are possible: .. ### BEGIN~OF~TABLE ### .. _subtemplate: subtemplate ~~~~~~~~~~~ .. container:: table-row Property subtemplate Data type string Description Name of the subpart of the template file used to render the form Can be used in all forms .. _messagetype-i: messagetype\_i ~~~~~~~~~~~~~~ .. container:: table-row Property messagetype\_i Data type wrap Description Possibility to wrap a single message of type “information” Can be used in single event and event list registration forms .. _messagetype-e: messagetype\_e ~~~~~~~~~~~~~~ .. container:: table-row Property messagetype\_e Data type wrap Description Possibility to wrap a single message of type “error” Can be used in single event and event list registration forms .. _messages: messages ~~~~~~~~ .. container:: table-row Property messages Data type wrap Description Possibility to wrap all messages Can be used in single event and event list registration forms .. _userfield: userfield ~~~~~~~~~ .. container:: table-row Property userfield Data type wrap Description Possibility to add a wrap to a single user-defined field. You can use “###CAPTION###” to insert the caption if the field Can be used in all forms .. _fields: fields ~~~~~~ .. container:: table-row Property fields Data type wrap Description Possibility to wrap all user-defined fields Can be used in all forms .. _eventcheckbox: eventcheckbox ~~~~~~~~~~~~~ .. container:: table-row Property eventcheckbox Data type wrap Description Possibility to wrap the event selection checkbox Can be used in event list registration forms .. _onetimeaccountlink: onetimeaccountlink ~~~~~~~~~~~~~~~~~~ .. container:: table-row Property onetimeaccountlink Data type wrap Description Possibility to wrap the link for onetime-account creation Can be used in single event registration forms .. _loginlink: loginlink ~~~~~~~~~ .. container:: table-row Property loginlink Data type wrap Description Possibility to wrap the link for normal login Can be used in single event registration forms .. _submitbutton: submitbutton ~~~~~~~~~~~~ .. container:: table-row Property submitbutton Data type wrap Description Possibility to wrap the submit button Can be used in single event and event list registration forms .. _userselection: userselection ~~~~~~~~~~~~~ .. container:: table-row Property userselection Data type wrap Description Possibility to wrap the user selection Can be used in register foreign user form .. _foreignuserregistration: foreignuserregistration ~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Property foreignuserregistration Data type wrap Description Possibility to wrap the single event registration form if used for registering a foreign user Can be used in register foreign user form .. _adminpanel: adminpanel ~~~~~~~~~~ .. container:: table-row Property adminpanel Data type wrap Description Possibility to wrap the admin-panel functions Can be used in list of attendees .. _subject: subject ~~~~~~~ .. container:: table-row Property subject Data type wrap Description Subject line for emails Can be used in emails .. _any-other-property: [any other property] ~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Property [any other property] Data type wrap Description Possibility to wrap a marker in the template. Marker names will be converted into lower case and if a matching property exists, if will be used for wrapping. Can be used in all forms .. ###### END~OF~TABLE ###### .. _Markers-for-templates: Markers for templates ^^^^^^^^^^^^^^^^^^^^^ .. _Data-from-event-location-organizer-and-user-tables: Data from event, location, organizer and user tables """""""""""""""""""""""""""""""""""""""""""""""""""" All fields from tables containing event, location, organizer and user data can be used via markers. .. ### BEGIN~OF~TABLE ### .. _Events: Events ~~~~~~ .. container:: table-row Table Events Marker for data EVENT\_[fieldname] Marker for label LABEL\_EVENT\_[fieldname] .. _Event-Location: Event Location ~~~~~~~~~~~~~~ .. container:: table-row Table Event Location Marker for data LOCATION\_[fieldname] Marker for label LABEL\_LOCATION\_[fieldname] .. _Event-Organizer: Event Organizer ~~~~~~~~~~~~~~~ .. container:: table-row Table Event Organizer Marker for data ORGANIZER\_[fieldname] Marker for label LABEL\_ORGANIZER\_[fieldname] .. _Frontend-User: Frontend-User ~~~~~~~~~~~~~ .. container:: table-row Table Frontend-User Marker for data USER\_[fieldname] Marker for label LABEL\_USER\_[fieldname] .. _User-defined-fields: User-defined fields ~~~~~~~~~~~~~~~~~~~ .. container:: table-row Table User-defined fields Marker for data UDEF\_[fieldname] Marker for label LABEL\_UDEF\_[fieldname] .. ###### END~OF~TABLE ###### When using user-defined fields please notice, that they can only be used if they are contained in the fieldgroup assigned to the event. Additionaly, the following markers can be used: .. ### BEGIN~OF~TABLE ### .. _Link-to-event-single-view: Link to event single view ~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Link to event single view Marker for data EVENT\_link Marker for label .. _Start-of-event-formated: Start of event (formated) ~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Start of event (formated) Marker for data EVENT\_formated\_start Marker for label LABEL\_EVENT\_formated\_start .. _End-of-event-formated: End of event (formated) ~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function End of event (formated) Marker for data EVENT\_formated\_end Marker for label LABEL\_EVENT\_formated\_end .. _Name-of-event-organizer-independent-if-he-has-been-entered-manually: Name of event organizer (independent if he has been entered manually ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Name of event organizer (independent if he has been entered manually or assigned via an organizer record) Marker for data EVENT\_organizer\_name Marker for label LABEL\_EVENT\_organizer\_name .. _Email-of-event-organizer-independent-if-he-has-been-entered-manually: Email of event organizer (independent if he has been entered manually ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Email of event organizer (independent if he has been entered manually or assigned via an organizer record) Marker for data EVENT\_organizer\_email Marker for label LABEL\_EVENT\_organizer\_email .. _Registration-in-list-view-Checkbox-vor-selecting-events: Registration in list view: Checkbox vor selecting events ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Registration in list view: Checkbox vor selecting events Marker for data EVENT\_CHECKBOX Marker for label .. _Link-to-current-page: Link to current page ~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Link to current page Marker for data LINK Marker for label .. _Link-to-page-with-login-form: Link to page with login form ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Link to page with login form Marker for data LOGINLINK Marker for label LABEL\_login .. _Link-to-page-with-form-to-create-an-onetime-account: Link to page with form to create an onetime-account ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Link to page with form to create an onetime-account Marker for data ONETIMEACCOUNTLINK Marker for label LABEL\_onetimeaccount .. _Number-of-places-for-an-event: Number of places for an event ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Number of places for an event Marker for data MAXATTENDEES Marker for label LABEL\_maxattendees .. _Number-of-currently-booked-places-for-an-event: Number of currently booked places for an event. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Number of currently booked places for an event. Marker for data NUMATTENDEES Marker for label LABEL\_numattendees .. _Number-of-waitlist-entries-for-an-event: Number of waitlist entries for an event ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Number of waitlist entries for an event Marker for data NUMWAITLIST Marker for label LABEL\_numwaitlist .. _Number-of-free-places-for-an-event: Number of free places for an event ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Number of free places for an event Marker for data NUMFREE Marker for label LABEL\_numfree .. _Section-with-user-defined-fields: Section with user-defined fields ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Section with user-defined fields Marker for data FIELDS Marker for label .. _Submitbutton: Submitbutton ~~~~~~~~~~~~ .. container:: table-row Function Submitbutton Marker for data SUBMITBUTTON Marker for label LABEL\_submitbutton .. _Section-with-messages: Section with messages ~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Section with messages Marker for data MESSAGES Marker for label .. _Status-of-registration: Status of registration ~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Status of registration Marker for data STATUS Marker for label LABEL\_status .. _Registration-in-List-view-Label-for-register-unregister-box: Registration in List view: Label for register/unregister box ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Registration in List view: Label for register/unregister box Marker for data TITLE Marker for label .. _Unregistration-on-list-view-Message-for-checkbox: Unregistration on list view: Message for checkbox ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Unregistration on list view: Message for checkbox Marker for data UNREGISTERME Marker for label .. _Admin-Panel-for-list-of-registrations-for-an-event: Admin-Panel for list of registrations for an event ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Admin-Panel for list of registrations for an event Marker for data ADMINPANEL Marker for label LABEL\_admin\_title .. _Foreign-user-registration-Select-field-for-users: Foreign user registration: Select field for users ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Foreign user registration: Select field for users Marker for data USERSELECTION Marker for label .. _Foreign-user-registration-Registration-form: Foreign user registration: Registration form ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function Foreign user registration: Registration form Marker for data FOREIGNUSERREGISTRATION Marker for label .. _List-Registrations-for-events-of-the-frontend-user-Link-to-vCard: List “Registrations for events of the frontend user”: Link to vCard ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function List “Registrations for events of the frontend user”: Link to vCard file with participant information Marker for data PARTICIPANTVCARDLINK Marker for label .. _List-Registrations-of-the-frontend-user-Link-to-vCard-file-with: List “Registrations of the frontend user”: Link to vCard file with ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. container:: table-row Function List “Registrations of the frontend user”: Link to vCard file with organizer information Marker for data ORGANIZERVCARDLINK Marker for label .. ###### END~OF~TABLE ###### .. _Any-other-markers-and-labels: Any other markers and labels """""""""""""""""""""""""""" If for an marker “LABEL\_\*” no definition can be found, the text for object “label\_\*” from the language file EXT:register4cal/view/locallang.xml will be used. If for an marker \* no definition could be found, it is checked if a property with the same name (but lowercase) exists in the TypoScript section for the form. If this is the case, this property will be used as wrap for the marker. .. _Changing-texts-with-TypoScript: Changing texts with TypoScript ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ If it is required to change texts from the language file EXT:register4cal/view/locallang.xml, you should not simply change this file. Changes would be lost if a new version of this extension is installed. Instead, TYPO3 offers an easy way to change texts via TypoScript. There are two different types of texts which require different additions in TypoScript to change then. .. _Texts-used-from-TypoScript: Texts used from TypoScript """""""""""""""""""""""""" Mosts texts in the forms are directly set in TypoScript using the following form of TypoScript coding: :: plugin.tx_register4cal_pi1.[something].dataWrap = {LLL:EXT:register4cal/view/locallang.xml:[text_name]} To change such texts, just replace the default value from the TypoScript template your new text: :: plugin.tx_register4cal_pi1.[something].dataWrap = [new text] If you are familiar with Typo3 language files, and need to change a lot of texts, you may also create your own language file and use it instead of the default file. Using this method eases the changes for multilanguage sites. Conditions, changing texts for each language differently are not required. Only one value needs to be changed in TypoScript: :: plugin.tx_register4cal_pi1.[something].dataWrap = {LLL:path/to/your/locallang.xml:[text_name]} .. _Texts-used-from-Coding: Texts used from Coding """""""""""""""""""""" Other texts, which are used from the coding, can be changed by adding substitution texts in TypoScript setup. To change a text, add the following line to your TypoScript coding: :: plugin.tx_register4cal_pi1._LOCAL_LANG.[language].[text_name] = [new text] Where [language] is the language, in which the text should be changed (e. g. „default“ for english, „de“ for german). [text\_name] is the name of the text to be changed and [new text] is the new text. .. _Known-problems: Known problems -------------- Currently, no major problems are known. For other issues, requested features and so on, please see the `project page at forge.typo3.org `_ . If you encounter problems, please do not hesitate to create a bug message there. .. _To-Do-list: To-Do list ---------- - A backend module should be included which allows the display/management of registrations - A task for the TYPO3 scheduler should enable the deletion of registrations for past events - Created HTML coding should include css classes/ids to ease formatting of elements in frontend display - Several hooks could be implemented to enable the use of other types of userdefined fields - Localize error messages If you require further features, please do not hesitate to create a feature request on the `project page at forge.typo3.org `_ . .. _ChangeLog: ChangeLog --------- The ChangeLog can be found online in the extension repository via the `following link `_ . |img-2| 28 .. ######CUTTER_MARK_IMAGES###### .. |img-1| image:: img-1.png .. :align: left .. |img-2| image:: img-2.png .. :border: 0 .. :height: 21 .. :hspace: 9 .. :id: Grafik2 .. :name: Grafik2 .. :width: 87 .. |img-3| image:: img-3.png .. :align: left .. :border: 1 .. :id: Grafik1 .. :name: Grafik1 .. :width: 100% .. |img-4| image:: img-4.png .. :align: left .. :border: 1 .. :id: Grafik3 .. :name: Grafik3 .. :width: 100% .. |img-5| image:: img-5.png .. :align: left .. :border: 1 .. :id: Grafik4 .. :name: Grafik4 .. :width: 100% .. |img-6| image:: img-6.png .. :align: left .. :border: 1 .. :id: Grafik7 .. :name: Grafik7 .. :width: 100% .. |img-7| image:: img-7.png .. :align: left .. :border: 1 .. :height: 391 .. :id: Grafik5 .. :name: Grafik5 .. :width: 665 .. |img-8| image:: img-8.png .. :align: left .. :border: 1 .. :id: Grafik8 .. :name: Grafik8 .. :width: 100% .. |img-9| image:: img-9.png .. :align: left .. :border: 1 .. :id: Grafik9 .. :name: Grafik9 .. :width: 100% .. |img-10| image:: img-10.png .. :align: left .. :border: 1 .. :id: Grafik10 .. :name: Grafik10 .. :width: 100% .. |img-11| image:: img-11.png .. :align: left .. :border: 1 .. :id: Grafik11 .. :name: Grafik11 .. :width: 100% .. |img-12| image:: img-12.png .. :align: left .. :border: 1 .. :id: Grafik14 .. :name: Grafik14 .. :width: 100% .. |img-13| image:: img-13.png .. :align: left .. :border: 0 .. :id: Grafik15 .. :name: Grafik15 .. :width: 100% .. |img-14| image:: img-14.png .. :align: left .. :border: 1 .. :id: Grafik12 .. :name: Grafik12 .. :width: 100% .. |img-15| image:: img-15.png .. :align: left .. :border: 0 .. :id: Grafik13 .. :name: Grafik13 .. :width: 100% .. |img-16| image:: img-16.png .. :align: left .. :border: 0 .. :id: Grafik18 .. :name: Grafik18 .. :width: 82%