There are two sections in TS setup that contain setting for this extension: plugin.tx_seminars and plugin.tx_seminars_pi1.
You can configure the plug-in using your TS template setup in the form plugin.tx_seminars.property = value. The values in this table can only be configured using your TypoScript setup, but not via flexforms.
Property: | Data type: | Description: | Default: |
|---|---|---|---|
templateFile | string | File name of the HTML template for e-mail | EXT:seminars/seminars.tmpl |
salutation | string | switch whether to use formal/informal language for some shared code (in e-mails, some labels and some error messages).Allowed values are:formal | informal | formal |
hideFieldsInThankYouMail | string | comma-separated list of field names that shouldn't be displayed in the thank-you e-mail to the user allowed values are in: hello, title, accreditation_number, credit_points, date, time, place, room, price_regular, price_special, paymentmethods, url, footer | credit_points |
generalPriceInMail | boolean | whether to use the label “Price” for the standard price (instead of “standard price”) in e-mail to the participant | |
hideFieldsInNotificationMail | string | Comma-separated list of field names from the registration that shouldn't be displayed in the notification e-mail to the organizers. These fields are the big blocks in that e-mail, and some are further divided. Allowed values are in:
| |
showSeminarFieldsInNotificationMail | string | comma-separated list of field names from seminars that should be mentioned in the notification e-mail to the organizers (in the “seminardata” block)allowed values are in: uid, type, title, subtitle, titleanddate, date, time, room, place, speakers, price_regular, price_special, attendees, vacancies, enough_attendees, is_full | title,uid,date,place,price_regular,price_special,attendees,vacancies,enough_attendees,is_full |
showFeUserFieldsInNotificationMail | string | comma-separated list of field names from fe_users that should be mentioned in the notification e-mail to the organizers (in the “feuserdata” block)allowed values are all column names from fe_users. | username,name,email,address,zip,city,telephone,tx_seminars_phone_mobile,date_of_birth |
showAttendanceFieldsInNotificationMail | string | comma-separated list of field names from attendances that should be mentioned in the notification e-mail to the organizers (in the “attendancedata” block)allowed values are in: interests, expectations, background_knowledge, known_from, notes, seats | interests,expectations,background_knowledge,known_from,notes |
sendAdditionalNotificationEmails | boolean | whether to send the additional notification e-mails to the organizers or not. Additional notification mails are sent if for example an event gets full. | 1 (= active) |
timeFormat | string | the time format (in strftime format) | %H:%M |
dateFormatY | string | the strftime format code to extract the year from a date string(usually this shouldn't be changed) | %Y |
dateFormatM | string | the strftime format code to extract the month from a date string(usually this shouldn't be changed) | %m. |
dateFormatD | string | the strftime format code to extract the day of month from a date string(usually this shouldn't be changed) | %d. |
dateFormatYMD | string | the strftime format code for the full date(change this to your local date format) | %d.%m.%Y |
dateFormatYM | string | the strftime format code for the year and month(change this to your local date format) | %m.%Y |
dateFormatMD | string | the strftime format code for the month and day of month(change this to your local date format) | %d.%m. |
abbreviateDateRanges | boolean | whether date ranges should be shortened when possible, for example 11.10.2005-13.10.2005 becomes 11.-13.10.2005 | 1 |
currency | string | ISO3 code of the currency to be used (XXX not used yet)(taken from the static_info_tables extension) | EUR |
attendancesPID | page_id | PID of the page (or system folder) where seminar registrations (attendances) are stored | None |
eventType | string | The event type for all events that is displayed on the seminar details page.Please note that this configuration value will go away once it is possible to manage more than one event type. | Workshop |
showTimeOfRegistrationDeadline | boolean | whether to also show the time of the registration deadline instead of just the date | 0 |
showVacanciesThreshold | integer | If there are at least this many vacancies, “enough” (localized) is displayed instead of the exact number. Set this to a number higher than the highest number of vacancies if you want the exact number to be always displayed. | 10 |
[tsref:plugin.tx_seminars]
You can configure the plug-in using flexforms of the front-end plug-in or your TS template setup in the form plugin.tx_seminars_pi1.property = value.
If your want to set a value for all instances of the plug-in in one place, use the TS template setup. If you use flexforms, make sure to set the values at all relevant instances of the plug-in: It doesn't do to specify the fields for the online registration in the seminar list front-end plug-in—you need to set these fields in the online registration front-end plug-in.
If you set any non-empty value in the flexforms, this will overwrite the TS template setup setting.
Property: | Data type: | Description: | Default: |
|---|---|---|---|
baseURL | string | Base URL of your TYPO3 site (including the protocol and the trailing slash), e.g. http://www.mytypo3site.net/ | |
what_to_display | string | The kind of front-end plug-in to display. Allowed values are in: seminar_list, seminar_registrationThis must be set using flexforms. | seminar_list |
templateFile | string | File name of the HTML template | EXT:seminars/pi1/seminars_pi1.tmpl |
cssFile | string | location of the CSS file (set as empty to not include the file) | typo3conf/ext/seminars/pi1/seminars_pi1.css |
salutation | string | Switch whether to use formal/informal language on the front end.Allowed values are:formal | informal | formal |
timeframeInList | string | the timeframe from which event should be displayed in the list view. Select one of these keywords:all, past, pastAndCurrent, current, currentAndUpcoming, upcoming, deadlineNotOver | currentAndUpcoming |
showRegistrationFields | string | comma-separated list of tx_seminars_attendances DB fields to show for the online registration (must not be empty).The order of the values is relevant as it allows to specify the order of the form elements on the front end. Allowed values are in: interests, expectations, background_knowledge, accommodation, food, known_from, seats, notes | interests,expectations,background_knowledge,known_from,notes |
eventFieldsOnRegistrationPage | string | list of comma-separated names of event fields that should be displayed on the registration page (the order doesn't matter)Allowed values are in: uid,title,price_regular,price_special,vacancies | title,price_regular,price_special,vacancies |
hideColumns | string | comma-separated list of column names that shouldn't be displayed in the list view, e.g. organizers,price_special The order of the elements in this list has no influence on the output.Allowed values are in: title, uid, accreditation_number, credit_points, speakers, date, time, place, price_regular, price_special, organizers, vacancies, registrationPlease note that the registration column will only be shown if a front-end user currently is logged in. | accreditation_number,credit_points,time,place,price_special,speakers |
hideFields | string | comma-separated list of field names that shouldn't be displayed in the detailed view, e.g. organizers,price_special The order of the elements in this list has no influence on the output.Allowed values are in: title, subtitle, description, accreditation_number, credit_points, date, uid, time, place, room, speakers, price_regular, price_special, paymentmethods, organizers, vacancies, deadline_registration, registration, back | credit_points |
hideCanceledEvents | boolean | whether to show canceled events in the list view | 1 |
showSpeakerDetails | boolean | whether to show detailed information of the speakersif disabled, only the names will be shown | 1 |
showSiteDetails | boolean | whether to show detailed information of the locationif disabled, only the name of the location will be shown | 1 |
generalPriceInList | boolean | whether to use the label “Price” as column header for the standard price (instead of “Standard price”) | |
generalPriceInSingle | boolean | whether to use the label “Price” as heading for the standard price (instead of “Standard price”) in the detailed view and on the registration page | |
showFeUserFieldsInRegistrationsList | string | comma-separated list of FEuser fields to show in the list of registrations for an event | name |
loginPID | page_id | PID of the page that contains the login form | None |
listPID | page_id | PID of the page that contains the seminar list | None |
registerPID | page_id | PID of the page that contains the seminar registration plug-in | None |
registrationsListPID | page_id | PID of the page that contains the registrations list for participants | None |
registrationsVipListPID | page_id | PID of the page that contains the registrations list for VIPs | None |
[tsref:plugin.tx_seminars_pi1]
For the list view, there are some additional configuration option that can only be set using the TS setup in the form plugin.tx_seminars_pi1.listView.property = value. Those values can not be set via Flexforms.
Property: | Data type: | Description: | Default: |
|---|---|---|---|
orderBy | string | the default sort order in list view (a field name) | begin_date |
descFlag | boolean | whether to show the list view ordered in ascending (=0) or descending order (=1) | 0 |
results_at_a_time | integer | The number of events that shall be displayed per page | 20 |
maxPages | integer | the number of neighboring pages to list in the page browser | 5 |
[tsref:plugin.tx_seminars_pi1.listView]