This extension uses a couple of different HTML templates:

Note: Do not change the HTML templates directly in the extension directory as then your changes will be overwritten when you upgrade the extension to a new version. Make a copy and modify the copy instead:

You can set up to six different prices for each event: a “standard price” and a “special” price, e.g. for students and people in full employment (each of them can also be saved as an early bird price). In addition, there a two prices including full boarding (“regular” and “special”). In the registration form, the user can select the price to pay.

Events for free: In the single view, the standard price always gets displayed (even if it is 0.00), while the special price only gets displayed if it is not 0.00. This means that if you need to enter a price that is 0.00 (eg. as a special discount), you need to enter this as the standard price and enter the non-zero price as the special price even if the non-free price technically is the standard price.

The early bird prices will only have an effect if you also define an early bird deadline (until when these prices are valid). If no early bird price is set or the deadline has already passed by, these prices won't be visible in the front end.

If you have only one price per seminar, you can configure the list view to not display the special price column (look in the reference for details). In addition, you might want to set some of the following options to just display “price” instead of “standard price”:

If you have two prices for some or all seminars, you can change the default labels “regular price” and “special price”, e.g. to “Adults” and “Children”. You can change them using these variables:

Replace “language” with your two-letter language code if you use a language other than English, e.g. “de” for German. Use “default” as language code for English.

You can change most of the localized strings that are used on the front end and for the e-mails. (The localized strings for the back end and the input form labels for the online registration currently cannot be changed.)

When you want to change some strings, please don't change locallang.xml or pi1/locallang.xml directly as these changes would get overwritten on the next update. Instead, do it like this:

On the second registration page, you can have up to two “terms & conditions” checkboxes. If you would like the checkbox labels to link to the page containing the terms & conditions (or if you would like to open that page as a pop-up), you can use some HTML for the checkbox label. For example, this will add a link to the first terms & conditions checkbox for a German site:

plugin.tx_seminars_pi1._LOCAL_LANG.de.label_terms = <a href="/index.php?id=1106&amp;type=11" onclick="popup(this.href); return false">Die Allgemeinen Gesch&auml;ftsbedingungen</a> habe ich gelesen und erkenne sie hiermit an.

You can do the same for the label_terms_2 label.

The extension provides its own basic set of CSS styles (which work best with a white background and if you're already using a CSS-based design and css_styled_content). These stylesheets usually get included automatically. However, if your have set disableAllHeaderCode = 1 and want to use the provided stylesheet, you need to include the stylesheet typo3conf/ext/seminars/pi1/seminars_pi1.css manually into your page header.

When looking to the source of the HTML output of this extension, you will see that there are some parts of the output (for example table cells) marked to belong to a certain class. But not every part has as 'class=”xyz”'—we have only those classes that are actually used in the CSS file so that the HTML code stays lean. If needed, you can add classes to these parts by adding them to your TypoScript setup (in the template):

By default, the organizer field in the ListView has no class added to keep the HTML-Output as clean as possible. It looks like this:

[...]<td>[name of the organizer]<td>[...]

If you add the following line to your setup,

plugin.tx_seminars_pi1.class_listorganizers  = organizers

the output shows us the following:

[...]<td class="tx-seminars-pi1-organizers">[name of the organizer]</td>[...]

So the resulting class name will be tx-seminars-pi1 and the value from the corresponding TS rule appended. Please not that the last part of the name in the TS setup (“class_listorganizers”) needs to match the string in the HTML template (“###CLASS_LISTORGANIZERS###”). The only difference lies in the capitalization and the “###”.

Then you can add a rule like this to your CSS file:

.tx-seminars-pi1-organizers { ...;}

.tx-seminars-pi1-vacancies-available .tx-seminars-pi1-square {

  background-color: #00a500;

  color: inherit;

}

.tx-seminars-pi1-vacancies-2 .tx-seminars-pi1-square, .tx-seminars-pi1-vacancies-1 .tx-seminars-pi1-square {

  background-color: #ffff3c;

  color: inherit;

}

.tx-seminars-pi1-vacancies-0 .tx-seminars-pi1-square, .tx-seminars-pi1-cancelled .tx-seminars-pi1-square {

  background-color: #c30000;

  color: inherit;

}

In the default configuration, this extension allows each user to register only one seat per event. This can be changed if you need users to register more than one seat per registration (e.g. when you use this extension for a theater, or you would like companies to register all their attendees in one go).

Please note that this doesn't enable users to register multiple times—it just allows them to enter the number of seats for their registration.

This is what needs to be changed:

If the field seats is not filled in (ie. the registration is for 0 seats), the registration is counted as 1 seat.

Please note the the number of seats currently is not included in the automated e-mail to the user. This will be implemented in a later version of this extension.

Only do this if you really trust your users to only enter serious events and no fun or test records.

You can assign VIPs (front-end users) to each single event. These VIPs are allowed to see all registrations for the events where he/she is manually added as a VIP.

If you want to allow a group of VIPs to see the registrations of all events, you can add all those VIPs to a group. Just add the UID of that group to the TS configuration plugin.tx_seminars_pi1.defaultEventVipsFeGroupId.

After clearing the cache, all members of that group will see all events on their “my VIP events” page, and will be able to see the registrations list of all those events.

You can also set the group's uid in the flexform configuration or the plugin. But you will need to set it for each plugin (on every page). It's easier to set it via TypoScript setup on a global page.

The countdown will show the time left (in words) until the next event starts. Only upcoming events with a begin date/time will be selected for this. If no matching event is found, a message will be shown instead.

To set this up, follow these easy steps: