General Settings:

viewMode

string / stdWrap

Code to define what view should be rendered. You may override this setting by choosing a different value directly in the Insert Plugin content element.

Possible values:

Example:

plugin.tx_rlmpeventdb_pi1.viewMode = eventlist

eventlist

showCategories

pidList

list of integer

Comma separated list of page UIDs which contain event records and should be taken into account when rendering the list- or search-view. When this is not set, all event records found anywhere in the installation will be used.

Example:

plugin.tx_rlmpeventdb_pi1.pidList = 32,37

recursive

boolean

defaultPaymentMethods

string / stdWrap

Comma separated list of payment method keys which sets the by default available payment methods for all events. Selection of payment methods in the event record overrides this setting.

Note: This property only has an effect if the extension paymentlib and at least one payment method is installed.

Example:

plugin.tx_rlmpeventdb_pi1.defaultPaymentMethods = paymentlib_ipayment_cc_visa2,paymentlib_ipayment_cc_mastercard

Registration::

addressPid

integer

Page ID, typically of a sysfolder, of a page containing existing and newly created address records.

Example:

plugin.tx_rlmpeventdb_pi1.registration.addressPid = 26

FEuserPid

integer

Page ID, typically of a sysfolder, of a page containing existing and newly created frontend user records.

Example:

plugin.tx_rlmpeventdb_pi1.registration.FEuserPid = 28

confirmationPopupHeaderInclude

cObj

A content object which renders some content to be inserted as a header in the popup window containing the confirmation of a registration.

Example:

plugin.tx_rlmpeventdb_pi1.registration {

   confirmationPopupHeaderInclude = FILE

   confirmationPopupHeaderInclude.file = myHeader.html

}

agentUserGroupId

integer

ID of the agents frontend user group. All frontend users being member of this group will be considered as agents.

Example:

plugin.tx_rlmpeventdb_pi1.registration.agentUserGroupId = 2

requiresLogin

integer

This option controls access to registration for events in general. Depending on the value, a login is required in order to register for an event:

0 = does not require a login

1 = requires any logged in FE user

2 = requires logged in agent

Example:

plugin.tx_rlmpeventdb_pi1.registration.requiresLogin = 2

0

registration.confirmationMail

sender

string

Sender email address for confirmation emails.

Example:

plugin.tx_rlmpeventdb_pi1.registration.confirmationMail {   sender = noreply@typo3.org}

subject

stdWrap

The subject line for confirmation emails.

Example:

plugin.tx_rlmpeventdb_pi1.registration.confirmationMail {   subject = Your registration   subject.lang.de = Ihre Anmeldung}

template

cObj

Template for the message body. Can be overriden by the event record.

Example:

plugin.tx_rlmpeventdb_pi1.registration.confirmationMail {

   template = FILE

   template.file = EXT:rlmp_eventdb/res/confirmation-mail.txt

}

see example

registration.notificationMail

sender

string

Sender email address for notification emails.

Example:

plugin.tx_rlmpeventdb_pi1.registration.notificationMail {   sender = noreply@typo3.org}

subject

stdWrap

The subject line for notification emails.

Example:

plugin.tx_rlmpeventdb_pi1.registration.notificationMail {   subject = New registration!   subject.lang.de = Neue Anmeldung!}

template

cObj

Template for the message body. Can be overriden by the event record.

Example:

plugin.tx_rlmpeventdb_pi1.registration.notificationMail {

   template = FILE

   template.file = EXT:rlmp_eventdb/res/notification-mail.txt

}

see example

recipient

stdWrap

Recipient(s) for notification emails. You can override this setting via the event record.

Example:

plugin.tx_rlmpeventdb_pi1.registration.notificationMail {   recipient = admin1@typo3.xy, admin2@typo3.xy}

registration.steps

features.infoText

stdWrap

This text will be displayed before the first field of the features form. The special stdWrap property current contains the content of the infotext field from the event record.The following example also reflects the default setting.

Example:

plugin.tx_rlmpeventdb_pi1.registration.steps {

   features {

      infoText.current = 1

      infoText.wrap = | <br /><br />

   }

}

see example

features.hide

Boolean

If set, the step displaying the available features will be hidden in the registration form.

0

address.infoText

stdWrap

This text will be displayed before the first field of the address / personal data form. The special stdWrap property current contains the content of the infotext field from the event record.

The following example also reflects the default setting.

Example:

plugin.tx_rlmpeventdb_pi1.registration.steps {

   address {

      infoText = 

      infoText.wrap = | <br /><br />

   }

}

see example

address.fieldList

stdWrap

With this option you may define the fields which are shown in the registration step “Address”. All field names must exist in the table tx_address_addresses and have a proper TCA configuration (which is the case by default).

By prepending a field name with an asterisk (*) you can define that entering data for this field is required, regardless of the original TCA configuration. By using standard TypoScript techniques you even can control the requirement of certain fields depending on user logins!

Example:

plugin.tx_rlmpeventdb_pi1.registration.steps {

    address {

       fieldList = *first_name, *last_name, home_street, home_zip, home_city, home_country, tel_home1_voice, email

    }

}

see example

paymentmethod.infoText

stdWrap

This text will be displayed before the payment details form. The special stdWrap property current contains the a default localized info text.

The following example also reflects the default setting.

Example:

plugin.tx_rlmpeventdb_pi1.registration.steps {

   paymentmethod {

      infoText.current = 1

      infoText.wrap = | <br /><br />

   }

}

see example

remarks.infoText

stdWrap

This text will be displayed before the first remarks form. The special stdWrap property current contains the content of the infotext field from the event record.

The following example also reflects the default setting.

Example:

plugin.tx_rlmpeventdb_pi1.registration.steps {

   remarks {

      infoText = 

      infoText.wrap = | <br /><br />

   }

}

see example

overview.infoText

stdWrap

This text will be displayed before the overview screen. The special stdWrap property current contains a message asking the user to check the details of the booked features before finally submitting the registration form.

The following example also reflects the default setting.

Example:

plugin.tx_rlmpeventdb_pi1.registration.steps {

   overview {

      infoText.current = 1

      infoText.wrap = | <br /><br />

   }

}

see example

participantsList

adminUserGroupId

integer

UID of the user group for administrators of the list of participants

requiresLogin

integer

0 = does not require a login

1 = requires any logged in FE user

2 = requires logged in list admin

2

listView:

results_at_a_time

10

maxPages

10

displayIcons

showTodayMessage

boolean

1

listView.displayConditions:

registrationEnabled

boolean

Only show those events for which the registration was enabled.

0

registrationPossible

boolean

Only show those events for which the registration was enabled and is (still) possible. This option checks

0

singleView

menu

cObj

USER

name

cObj

USER

frequency

cObj

USER

features

cObj

USER

termofreservation

cObj

USER

numberofparticipants

cObj

USER

user1

cObj

USER

user2

cObj

USER

user3

cObj

USER

user4

cObj

USER

user5

cObj

USER