EXT: Event Management¶

What to display¶

Currently there are six different options in the“What to display”field. These are the function of this options:

Order by¶

In this selectbox you can choose the field by which the listed (List, Archive & Upcoming) event-records should be ordered. Possible options are: “Datetime start” and “title”.

default (= nothing selected) is to order lists by the “Datetime start” field and display the most current items first.

Ascending or Descending¶

With this selectbox you can choose the sorting order.

Artists, Categories and Tours selection¶

In the selectfields you can choose artists, categories and tours to filter events lists (List, Archive & Upcoming). Multiple selections are possible. Multiple selections in the same field are joined with OR and multiple selections in different fields are joined with AND.

Example:

• category1 and category2 selected in the “Category” field: all events with category1 OR category2 are displayed
• category1 in the “Category” field and artist1 in the “Artist” field selected: all events with category1 AND artist1 are displayed

State¶

In this selectbox you can choose a state (like “omitted”) as a list filter.

Max and Limit¶

Here you can set a limit of events displayed in list views.

Max Width/Height for images¶

These 2 fields offer you the possibility to set the image sizes for a certain content element different from the image sizes defined globally by TypoScript. The setting here will be applied to all images, displayed by this content element.

Template file¶

Here you can overwrite the html-template defined globally by TypoScript with another one.

It is not required to define a template in this place, because in most cases several event content-elements under one pagetree use the same html-template. This can be defined directly in the TS-setup or in the Constant-Editor of your main-(TS)template.

Hint: The best way to include your own html-template is to link it directly in TS. Add the following line by hand to your TypoScript setup or edit the default value in the “TypoScript Object Browser” :

plugin.tx_rmevent_pi1.templateFile = fileadmin/templates/rmevent_template.html

Do not edit and save the html-template in the extension directory -> it will be overwritten if you update tt_news.

You can change the event display, by simply creating a new template- file for the display of events. There is a default template-file included with rmevent (EXT:rmevent/template.html).

If you want to change the template, take a look at that file, make a copy of it and modify it to your own design. Observe the comments in the file - they are markers that define where content is inserted and which parts are used for this and that. Self explanatory to a certain degree...

PageId for single event display¶

This tells the extension on which page the single view is located. It's not required to set a value here, cause it's more efficient to set a global value for the single view (singlePid) in the constant- Editor of your root template. See: “Configuration”.

PageId for single report display¶

This tells the extension on which page the single view for reports is located. It's not required to set a value here, cause it's more efficient to set a global value for the single view (singleReportPid) in the constant-Editor of your root template. See: “Configuration”.

Starting point and Recursive level selection¶

"Starting point" is used to tell the extension where the events records are stored. It is possible to select multiple ”Starting points”. This way, you are able to collect events from several folders to display them in one content-element.

If you don't insert a page as "Starting point", rmevent will look for a value for “pidInList” from TypoScript. This is the recommended way to configure many event content-elements from one central point, e.g. from the constants field in your main TS-template. -> see files EXT:rmevent/static/rmevent_default/constants.txt & EXT:rmevent/static/rmevent_default/setup.txt for examples. The “Starting Point” can also be set in the Constant editor.

Recursive level selection:

This tells the extension how many levels of subpages to include below the page(s) given in the "Starting point" field.

Title¶

The value inserted here will substitute the marker ###RMEVENT_TITLE### in the html template.

Start/End Date¶

The value of these fields affect several things:

• The events in list views are ordered by Start Date if no other field is selected (-> see "Order by" this field in section “The rmevent content element”)
• The value of these fields will substitute the html-template markers ###RMEVENT_DATE_START###, ###RMEVENT_TIME_START###, ###RMEVENT_ISO_START###, ###RMEVENT_DATE_END###, ###RMEVENT_TIME_END###, ###RMEVENT_ISO_END### (all parsed through the stdWrap functions “strftime”) and ###RMEVENT_DATE### (combination of the above markers).

Description¶

This is the main text of the event and will substitute the html- template marker ###RMEVENT_DESC###.

Images¶

Here you can define images that will be shown in the event item. All images will be rendered to the marker ###RMEVENT_IMAGES###. This marker will display a single image in list views an a list of images in the single view.

Ticket URL¶

Here you can save a URL for a booking service, either specific for an event or a general one. The template marker ###RMEVENT_TICKET_URL### will be replaced with a link to the URL.

Categories¶

Here you can assign categories to the current event record. The titles of the assigned categories will substitute the html-template marker ###RMEVENT_CAT###.

Tour¶

Here you can assign a tour to the current event record. The title of the tour will substitute the html-template marker ###RMEVENT_TOUR###.

Artists¶

Here you can assign artists to the current event record. The names of the assigned artists will substitute the html-template marker ###RMEVENT_ARTIST###.

Location¶

Here you can assign a location to the current event record. The name, city and country of the location will substitute the html-template marker ###RMEVENT_LOC###.

State¶

Here you can assign a state to the current event record. The title of the assigned state will substitute the html-template marker ###RMEVENT_STATE###.

General settings¶

plugin.tx_rmevent_pi1 {
  templateFile = fileadmin/my_templates/rmevent.html
}

# clear the value
plugin.tx_rmevent_pi1.pidInList >
# display event records located in page 123 & 345
plugin.tx_rmevent_pi1.pidInList = 123,345

# singlePid for a news element inserted by TS
plugin.tx_rmevent_pi1.singlePid = 123

Display settings for “LIST”, “UPCOMING”, “ARCHIVE” and “SINGLE”¶

plugin.tx_rmevent_pi1 {
 singleView {
  categories_stdWrap.wrap = <p class="rmevent_categories">|</p>
        textCategories_stdWrap.noTrimWrap =|<em>|</em>: |
        categoriesList_stdWrap.wrap =
        categoriesItem_stdWrap.wrap =
        categoriesItem_divider = ,
  }
}

plugin.tx_rmevent_pi1 {
 singleView {
  artists_stdWrap.wrap = <div class="rmevent_artists">|</div>
        textArtists_stdWrap.wraprap = <h3> | </h3>
        artistsList_stdWrap.wrap = <ul class=”rmevent_artists_list”>|</ul>
        artistsItem_stdWrap.wrap = <li>|</li>
        artistsItem_divider =
  }
}

plugin.tx_rmevent_pi1.singleView {
  dateStart_stdWrap {
    strftime = %d.%m.%y
    wrap = <span class="rmevent_date_start">|</span>
  }
}

Display settings for “PAGEBROWSER”¶

This is the configuration array for the pagebrowser. All settings here start with “pageBrowser.”. The formating of the pagebrowser is done by CSS.

Example¶