EXT: Events

EXT: Events 

Version

main

Classification

t3events

Description

t3events manages events. It provides integrators with the option to display event items in a list or a single view. Each event can contain one or more performances. For each performance, integrators have the option to list as many ticket classes as needed as well as various other information about the events. Performance locations can be accorded the following meta information: address, link, image etc. A quick menu allows users to filter the list view by genre. The extension was built from scratch with extbase and fluid. Originally designed to fulfill the specific requirements of a client project, this extension remains under development. We appreciate any feedback or suggestions for improvement.

Keywords

event, performance, ticket, forEditors, forIntermediates

Author

Dirk Wenzel, Michael Kasten

Email

t3events@gmx.de

Language

en

Copyright

2013-2016, Dirk Wenzel and Michael Kasten

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

What does it do? 

t3events manages events. It provides integrators with the option to display event items in a list or a single view. Each event can contain one or more performances. For each performance, integrators have the option to list as many ticket classes as needed as well as various other information about the events. Performance locations can be accorded the following meta information: address, link, image etc. A quick menu allows users to filter the list view by genre.

The extension was built from scratch with extbase and fluid.

Originally designed to fulfill the specific requirements of a client project, this extension remains under development. We appreciate any feedback or suggestions for improvement.

Don't hesitate to write an email to t3events@gmx.de or ask in the German or English TYPO3-Mailinglist, which we actively follow.

Visit the project page of t3events on github for information about new features and current issues.

Overview 

  • Create records for events, performances, locations, genres etc
  • Insert a plugin at any page and configure it to display teasers, events or a quick menu

|img-createRecords|

Auxiliary Records 

Genre 

Help to categorize your events. An event may belong to multiple genres (i.e. Classic, Rock, Comedy etc.)

Event Type 

Another kind of category. An event can belong to only one event type (i.e. concert, theater, congress). Since this attribute is not being considered anywhere at the moment you may use a standard type or nothing. We will implement a feature for filtering list views by event type later on.

Venue 

The facility with wich the event is associated. This might be an arena, a hall, congress center, an exhibition ground or any other venue. You should create at least one venue record.

Hint: The name of this record type might be misleading – especially for native english speakers. The customer for whom we developed this extension runs a bunch of facilities in different cities (congress centers, stadiums and so on). Each of them has multiple actual venues (rooms, stages etc). All facilities have their own websites mangaged within one TYPO3 instance. Since all teasers for events should be stored in a common sysfolder we needed an attribute to distinguish teasers by 'facility' (and called this 'venues'). So this attribute is useful to manage the visibility of teasers for editors and to select certain teasers for display in frontend. If you don't have to regard multiple facilities just create a standard entry and configure your frontend plugin to show all teasers related with this 'facility/venue'.

Event Location 

The actual location where the event takes place. This might be a room, a stage, a stand at a trade fair or something similar.

Organizer 

The person or organization who organizes the event. Contains address, phone, www and so on.

Status 

An indicator which may change during existence of the event. It is related to performances (see below for further information about events and performances). It's intention is to show the status of a performance (i.e. planned, sold out, bookable, few tickets available etc.). We plan to implement an automatic status update mechanism wich for example could change the availabilty of tickets according to current time.

All this record types are fairly simple and self explaining. They are created by inserting a new content element and choosing the appropriate type.

Events 

Create a new Event by inserting a new record and choosing the type 'event'.

General Tab 

Here you may provide a

  • headline (mandatory)
  • subtitle
  • description
  • image
  • event type

This information will be shown in the list and detail view of events and may be choosen for display in teasers.

|img-3|

Extended Tab 

Provide additional information:

  • Organizer: Select one from list (if there is none available you may create them and select one afterwards)
  • Genre: Genres are useful to categorize your events. The frontend plugin 'Quick Menu' allows the website user to filter the event list by genres. Genres may be created and edited directly by clicking the appropriate button.
  • Keywords: may be displayed or included in meta information

|img-4|

Performances Tab 

You have to create at least one performance for each event and may add as many as you like.

Single Performance 

General Tab

  • Date (mandatory)
  • Event location (select field, has to be created before)
  • Admission, Begin and End time
  • Status (select field. Status record must be created beforehand to be selectable). The status is displayed as a signal in the list view. Therefore you can assign one or more CSS classes. Since there might be more than one performance related to an event Status records can be priorized. The most crucial status will be displayed in list view then (For example if there are some performances sold out and others not yet you can mark the event with 'bookable' in list view by giving the status 'bookable' the highest priority i.e. lowest number)
  • Status information: additional information for the selected status. For example: 'online booking not available anymore please order by phone'
  • Image: Will be shown in list and single view of events

Links Tab

Provide links to external or internal providers (for tickets or booking)

Tickets Tab

  • Plan: an image containing a floor plan or color coded seating plan
  • Price Notice: additionl information for prices
  • No handling fee: useful for booking for example when using a shopping cart
  • Ticket Class: one or more ticket classes. Contains fields for color (for example for seating plan), title, price and type (normal, reduced, special)

Insert Plugins 

Insert a record of type plugin, in tab 'Plugin' select 'Events' and choose what to display (Event List or Quick Menu).

In tab 'Behavior' Select the system folder with your records as Record Storage Page.

(more detailed description coming soon)

Overview 

  • Include static template 'Events' and have a look at default settings in TypoScript Object Browser or Template Analyser in module Template.
  • There are quite a lot debug view helpers in templates which can be enabled by TypoScript.

(more detailed description will come soon)

To-Do list 

  • FEATURE: Enable linking events and/or performances to tt_address record
  • add content elements to events