EXT: WSE Eventmanagement

Extension Key: wse_events

Language: en

Keywords: forAdmins, forIntermediates

Copyright 2007-2014, Michael Oehlhof, <typo3@oehlhof.de>

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

This document is related to version 0.2.12 of the extension wse_events.

Development started at 2007-08-03

Table of Contents

EXT: WSE Eventmanagement	1

Introduction	3

What does it do?	3

Key features	3

Planned features	3

Screenshots	4

Credits	6

Installation	7

Requirements	7

Creating system folders	7

Setting up the plug-in	7

Users manual	8

Entering sessions and connected records	8

Insert plug-in on frontend page	10

FAQ	11

Configuration	12

TypoScript settings	12

Template markers	13

Backend configuration	20

Tutorial	25

Development Workflow	26

Who works on further development?	26

Getting the extension from Subversion	26

Submitting bug requests	26

Known problems	27

To-Do list	28

Changelog	29

Introduction

What does it do?

This extension was designed to fit the needs of the yearly events of the OS/2 and eComStation community. Since 2007 the planning of these events has been concentrated at the web sites www.warpstock.eu and www.warpevents.eu. Therefore the abbreviation WSE stands for WARPSTOCK EUROPE.

During setup of the site we tested many of the existing event extensions. Some of them had too many features and the others had less functionality than required. So we decided to create our own extension for the management of sessions and speaker.

If you have to plan events that have a similar structure like our events, you may also use this extension.

Here is a short description of an event:

An event is held on 2 or 3 days at a location.

Every location has a given count of 2-4 rooms for sessions.

The sessions are held mostly twice, at different days.

All sessions are organized in time slots that are of 45 minutes length for the most part.

A session is held by one or two speakers and some speakers hold more than one session.

Key features

front-end plug-in with list view and detailed single view of event data like speaker and sessions.

managing locations, rooms, speakers, speaker attendances, categories, events, sessions, and time slots in the back-end via a back-end module.

Support of workspaces for session and speaker records in the backend and frontend (preview)

visual design is done using templates and CSS

currently full German and English localization, Dutch and French are in progress

the front-end plug-in can be configured via TypoScript and Flexforms

the code follows the TYPO3 coding guidelines (at least it should)

is tested to work with TYPO3 version 4.1.2 in 2007, with version 4.2.1 in 2008 and with version 4.2.8 in 2009 (if you find any bugs, please report them in the bug tracker)

the extension is actively developed

Planned features

session planning via drag & drop

front-end editing of event records

Screenshots

Here are some sample screenshots from the extension used at the warpstock.eu web site.

This is the top of the session list with the category selection.

This is the detail view of a session

This is the speaker list and detail view

This is the presentation timetable

Credits

Thanks go to the following persons for localizations and for testing the extension:

Christian Hennecke

Thomas Klein

Keith Merrington (Dutch translation)

Guillaume Gay (French translation)

Christian Langanke

We also thank the TYPO3 community for their documentation and forums that helped us doing the work.

This extension contains parts of the Seminar Manager extension which is copyrighted by Oliver Klee (http://www.oliverklee.de) and we also thanks to the other people of the development team of the seminar manager extension (http://typo3.org/extensions/repository/view/seminars/current/), from which we got some “how to do” out of the coding.

Installation

Requirements

You need a working TYPO3 installation. We have developed and tested the extension in 2007 with version 4.1.2. It may run with older versions, but you have to test it yourself. Since the release of TYPO3 4.2 we develop and test with this version.

The extension static_info_tables is required for this extension, you have to install it first.

You also have to install the extension css_styled_content to use this extension correctly.

Download the wse_events extension from the netlabs.org Subversion server or install it from the TER.

Creating system folders

You need to create some system folders for storing records needed by this extension. We recommend using one system folder for storing common data like locations, rooms, categories, and speakers.

Another system folder should be created for the different event data like events, sessions, speaker attendances, and time slots.

This is an example setup for the Warpstock Europe events:

Setting up the plug-in

The plug-in is configured via Flexform input fields. For details look at Insert plug-in on frontend page in the user manual.

Users manual

Entering sessions and connected records

You must set up at least one event before you can enter sessions. In addition, you can set one or more speakers for a session. If you want to enter a session for an event or speakers that haven't been entered into the database yet, it's a good idea to enter those prior to entering the session. Have a look at the tutorial section for how to start best.

Entering and managing locations

At the beginning, you should enter at least one location where an event will be held. This should be entered in a common system folder, so it can be used by more than one event.

A locations record contains the following fields:

Name of Location (required), will be shown in the frontend, and can be selected in the event records

Web site, a link to the web site of the location

Comment, text field for internal comments

Entering and managing rooms

Add one or more rooms records to the system folder that will hold the location, rooms, speaker, and categories records.

A rooms record contains the following fields:

Room name (required), will be shown in the frontend

Comment, text field for internal comments

Number, the number of the room. Must be unique for a location, start with 1 and in successive order

Number of seats, can be set to define how many people fit into the room

Location (required), a location can be selected with a drop-down list showing all defined locations

Entering and managing categories

Add one or more categories records to the system folder that will hold the location, rooms, speaker, and categories records.

A categories record contains the following fields:

Name of category (required), will be shown in the frontend

Comment, text field for internal comments

Short key (required), an abbreviation that can be selected when defining a session

Color, the color which is to be used as background color in backend session planning and in frontend templates

Entering and managing speakers

Add one or more speaker records to the system folder that will hold the location, rooms, speaker, and categories records.

A speaker record contains the following fields:

Name of speaker (required), will be shown on the front end

Comment, text field for internal comments

E-mail address, optional e-mail address of the speaker

Country, the country of origin

Company, the company the speaker works for

Company link, a link to the speaker company web site

Image, a photo of the speaker

Info, rich text field with detailed speaker info

Entering and managing events

For every event you should create an own system folder that will hold the data related to this event.

Add one or more event records to the system folder that will hold the event, session, speaker restrictions, and time slot records.

An event record contains the following fields:

Event name (required), will be shown in the frontend

Comment, text field for internal comments

Location, a location can be selected with a drop-down list showing all defined locations

First day of event, the day when the event begins

Length of event, the number of days the event has

Start time, the time when the first session starts (hh:mm)

End time, the time when the last session ends (hh:mm)

Size of slots, the length of a single slot entity in minutes

Max slots per session, the amount of slots for the longest session

Default slot count, the count of slots the most sessions will have

An event can be considered as a table where the columns are the days of the event and the rows are the slots. The number of rows is computed by the length of time of the event (end time – start time) divided by the size of a slot.

Entering and managing time slots

Add one or more times lot records to the system folder that will hold the event, session, speaker restrictions, and time slot records.

A timeslot record contains the following fields:

Name of time slot (required), will be shown an the front end and can be selected on the sessions records

Comment, text field for internal comments

Name of event (required), will be selected from the event records

Day of event, the day for which the time slot is defined

Name of room, will be select a room from the rooms records

Begin of session, time of beginning of the session

Length of session, length of the session

Entering and managing sessions

Add one or more session records to the system folder that will hold the event, session, speaker restrictions, and time slot records.

A session record contains the following fields:

Event (required), will be selected from the event records

Comment, text field for internal comments

Session name (required), will be shown in the frontend and can be selected on the time slots records

Speaker, one or more speakers can be selected from the list of speakers

Time slots, one or more time slots can be selected from the list of time slots defined for the event

Category, a category can be selected from the list of category records

Session number, a number to identify the session in the category

Teaser text, a short text used as tooltip in the frontend

Session description, a rich text field for a detailed description of the session contents

Documents, one or more documents witch are related to the session

Entering and managing speakers restrictions

Add one or more speaker restriction records to the system folder that will hold the event, session, speaker restrictions, and time slot records. In this table you define the times when speaker are not available for session planning.

A speaker restrictions record contains the following fields:

ID of speaker (required)

Comment, text field for internal comments

Name of event (required), will be selected from the event records

Day of event, the day for which the speaker restriction is defined

Begin of session, time of beginning of the speaker restriction

Length of session, length of the speaker restriction

Insert plug-in on frontend page

Insert a new page content and select “Insert plug-in” as type, then select “WSE Events Flexform Plug-in” from the plug-in list.

The plug-in options are made as flexform input mask.

General settings

Here you enter the general settings for the frontend plug-in.

Event storage

To select the system folder that holds the event, session, and time slot records.

Recursive

Can be used if the session and time slot data is saved in different system folders below the event storage folder.

Common storage

To select the system folder that holds the speaker, location, and rooms records.

Display settings

To be used for selecting the way the data is presented in the frontend.

View mode

You can select what is to be displayed in the frontend.

Selections are:

Session list: A list of all sessions is displayed

Session detail: The detail view of a session

Speaker list: A list of all speakers that hold a session at the event

Speaker detail: The detail view of a speaker

Time slots: A list of time slots of the event ordered by day and time

Session single view page

To select the page that holds the frontend plug-in with the view mode set to session detail.

If a page is set here, a link is set at the session name in the session list to show the details of that session when the link is clicked.

Speaker single view page

To select the page that holds the frontend plug-in with the view mode set to speaker detail.

If a page is set here, a link is created for the speaker name in the session list to show the details of that speaker when the link is clicked.

Lastname, Firstname

If checked the name of the speaker is given as “name, firstname” from the speaker database record. When not checked “firstname name” is used.

Adminstration

ToDo

FAQ

ToDo

Configuration

TypoScript settings

General settings

Configuration of the front end output is done using a template. As default the wseevents.tmpl file in the extension directory is used. To use another template you have to set it in the TypoScript setup. You should copy the template to the fileadmin folder and make changes to this template to fit your needs.

plugin.tx_wseevents_pi1.templateFile = fileadmin/templates/wseevents.tmpl

The directory in which the speaker images are stored can be set with TypoScript setup. The default directory for images of the speaker is uploads/tx_wseevents

plugin.tx_wseevents_pi1.uploadDirectory = fileadmin/images

The target of the link for the session documents can be changed for special purposes.

plugin.tx_wseevents_pi1.documentsTarget = target="_blank"

The delimiter between single speakers, session documents or time slots, if more than one are assigned can be changed with a TypoScript setup. The default for the delimiter is “<br />”

plugin.tx_wseevents_pi1.speakerdelimiter = ,&nbsp;
plugin.tx_wseevents_pi1.slotdelimiter = ,&nbsp;
plugin.tx_wseevents_pi1.sessiondelimiter = <br />
plugin.tx_wseevents_pi1.documentsdelimiter = <br />

Caching is on per default and can be disabled with this setting.

plugin.tx_wseevents_pi1.no_cache = 1

The display of time slots in session and speaker list and detail view can be hide. This is useful during planning the event when times changes and the final time slot list is not finished.

plugin.tx_wseevents_pi1.hideTimeslots = 1

Links to download an iCalendar file can be shown beneath the time slots data.

plugin.tx_wseevents_pi1.showCalendarLink = 1
plugin.tx_wseevents_pi1.calendarLinkLabel = iCal

The output of the session description text can be wrapped with standard stdWrap settings in the session list view, the speaker list view and the speaker detail view.

plugin.tx_wseevents_pi1.sessiondescription_stdWrap

As an example how to crop long text you can use this setting:

plugin.tx_wseevents_pi1.sessiondescription_stdWrap.crop = 200 | ... | 1

The output of the speaker info text can also be wrapped with standard stdWrap settings in the speaker list view.

plugin.tx_wseevents_pi1.infodata_stdWrap

As an example how to crop long text you can use this setting:

plugin.tx_wseevents_pi1.infodata_stdWrap.crop = 200 | ... | 1

Session list settings

To disable some categories from showing up in the session list, you can set the uids of the category records that should be hidden via TypoScript. This can be useful if you define sessions for coffee break or lunch that should be shown in time slot view but not in session list view.

plugin.tx_wseevents_pi1.showSessionList.hideCategories = 5,8

Speaker list settings

The sort order for the speaker list view can be changed via TypoScript setup. The default is sort by name, ascending.

The fields that can be sorted by are name, firstname, email, info, and uid. The sort order is set after a colon, 0 for ascending and 1 for descending.

plugin.tx_wseevents_pi1.sortSpeakerlist = name:0

Time slot settings

The date format used in the time slot list can be changed via TypoScript setup. A configuration for each language can be made. The default is displaying in German date format (second line of following example).

plugin.tx_wseevents_pi1.0.fmtDate = %m/%d/%Y

plugin.tx_wseevents_pi1.1.fmtDate = %d.%m.%Y

To display the slot begin and end times in the time slot list you can set a room number via TypoScript. Begin and end time will then be derived from this room.

plugin.tx_wseevents_pi1.listTimeslotView.showRoomTime = 1

To disable the links for some categories from showing up in the time slot list you can set the shortkeys of the category records which should be have no link via TypoScript. This can be useful if you define sessions for coffee break or lunch that should be shown in time slot view but have no session detail view.

plugin.tx_wseevents_pi1.listTimeslotView.hideCategoryLinks = BRK

To disable the display of “not assigned” in the time slot list you can set it via TypoScript.

plugin.tx_wseevents_pi1.listTimeslotView.hideNotAssigned = 1

To disable the display of “not defined” in the time slot list you can set it via TypoScript.

plugin.tx_wseevents_pi1.listTimeslotView.hideNotDefined = 1

To disable the display of “Time” in the room row of the time slot list you can set it via TypoScript.

plugin.tx_wseevents_pi1.listTimeslotView.hideShowTime = 1

To disable the display of room columns with no time slots for the room at the day are set, you can set it via TypoScript.

plugin.tx_wseevents_pi1.listTimeslotView.hideEmptyRooms = 1

To show a selector for the rooms, you can set it via TypoScript.

plugin.tx_wseevents_pi1.listTimeslotView.showRoomSelector = 1

To show a selector for the categories, you can set it via TypoScript.

plugin.tx_wseevents_pi1.listTimeslotView.showCategorySelector = 1

To show a selector for the hours, you can set it via TypoScript.

plugin.tx_wseevents_pi1.listTimeslotView.showHourSelector = 1

You can use jQuery for the selection of what should be shown or not. Instead of the selectors, a list of chckboxes is shown. You have to include the jQuery library on the page to use this function. You can enable it via TypoScript.

plugin.tx_wseevents_pi1.listTimeslotView.useJQuery = 1

To show checkboxes for a time range instead of begin and end time for the hours, you can define it via TypoScript.

plugin.tx_wseevents_pi1.listTimeslotView.timeSelect {

1.Name = 8:30 - 10:00

1.Slots = 1,2,3,4

2.Name = 10:00 - 12:30

2.Slots = 5,6,7,8

3.Name = 12:30 - 14:30

3.Slots = 9,10,11,12

4.Name = 14:30 - 17:00

4.Slots = 13,14,15,16,17

5.Name = 17:00 - 20:00

5.Slots = 18,19,20,21,22,23

6.Name = 20:00 - 22:30

6.Slots = 24,25,26,27,28

7.Name = 22:30 - open end

7.Slots = 29,30

}

The color of not assigned and not defined slots in the time slot view can be set it via TypoScript. The default is #FFFFFF.

plugin.tx_wseevents_pi1.listTimeslotView.categoryColorNotAssigned = #00CCFF
plugin.tx_wseevents_pi1.listTimeslotView.categoryColorNotDefined = #00CCFF

If you want to have fixed width table columns in time slot view, you can set the width of the first column with the begin and end times to a fixed width. The remaining width is split into identical width for all columns. The value you set for the width via TypoScript is declared in percent.

plugin.tx_wseevents_pi1.listTimeslotView.timeColWidth = 10

When you choose to have fixed width table columns in time slot view and want to have a delimiting column between the days in “all days” view, you can set the width of the delimiting column to a fixed width. The remaining width is split into identical width for all columns. The value you set for the width via TypoScript is declared in percent.

plugin.tx_wseevents_pi1.listTimeslotView.dayDelimWidth = 2

To make special formatting of the day delimiter column, you can set the class name that is used for the delimiter column. The marker ###DAYDELIMITER### is set to the class if it is the day delimiter column.

plugin.tx_wseevents_pi1.listTimeslotView.dayDelimClass = DayDelim

To cut the teaser text in the time slot list if it is longer than a given value, you can set the length via TypoScript. The value is the amount of characters after that the teaser text is cut and a “...” is added.

plugin.tx_wseevents_pi1.listTimeslotView.teaserWidth = 0

To show the days vertical instead of horizontal, you can set it via TypoScript.

plugin.tx_wseevents_pi1.listTimeslotView.showDaysVertical = 1

Template markers

Session list

For displaying the session list the subpart ###SESSIONLIST### is used.

The subpart ###EVENTSELECT### is used for displaying a combo box for event selection. If only one event is found in the event storage folder, no selection is displayed.

The subpart ###CATEGORYSELECT### is used for displaying a combo box for category selection.

The subpart ###SINGLEROW### is used for displaying lines of session data.

The subparts ###ITEM### and ###ITEM_ALT### are used alternating for displaying a row of data.

Marker	Content
###LABEL###	Inside subpart ###EVENTSELECT### The localized value of the key tx_wseevents_sessions.chooseeventday from pi1\locallang.php Inside subpart ###CATEGORYSELECT### The localized value of the key tx_wseevents_sessions.choosecategory from pi1\locallang.php
###FORMSELECT###	Inside subpart ###EVENTSELECT### The name attribute of the HTML select tag, value is: tx_wseevents_pi1[showEvent] Inside subpart ###CATEGORYSELECT### The name attribute of the HTML select tag, value is: tx_wseevents_pi1[showCategory]
###VALUE###	Inside subpart ###OPTIONSELECTED### and ###OPTIONNOTSELECTED### of subpart ###SELECT### inside subpart ###EVENTSELECT### Uid of event record for the select option. Inside subpart ###OPTIONSELECTED### and ###OPTIONNOTSELECTED### of subpart ###SELECT### inside subpart ###CATEGORYSELECT### Uid of category record for the select option.
###OPTION###	Inside subpart ###OPTIONSELECTED### and ###OPTIONNOTSELECTED### of subpart ###SELECT### inside subpart ###EVENTSELECT### Name of event record for the select option. Inside subpart ###OPTIONSELECTED### and ###OPTIONNOTSELECTED### of subpart ###SELECT### inside subpart ###CATEGORYSELECT### Shortdesc and name of category record for the select option.
###SESSIONNUMBER###	Inside subpart ###HEADER### of subpart ###SINGLEROW### The localized value of the key tx_wseevents_sessions.listFieldHeader_number from pi1\locallang.php Inside subpart ###ITEM### and ###ITEM_ALT### of subpart ###SINGLEROW### The session number composed of the short key of the category and the 2 digit session number
###SESSIONCATEGORY###	Inside subpart ###ITEM### and ###ITEM_ALT### of subpart ###SINGLEROW### The category of the session, to be used for CSS selections. Slots that are not defined and slots that are defined but not assigned both have the category 0.
###SESSIONCATEGORYKEY###	Inside subpart ###ITEM### and ###ITEM_ALT### of subpart ###SINGLEROW### The short key of the category of the session, to be used for CSS selections. Slots that are not defined have the key NONE and slots that are defined but not assigned have the key UNUSED.
###SESSIONCATEGORYCOLOR###	Inside subpart ###ITEM### and ###ITEM_ALT### of subpart ###SINGLEROW### The color of the category of the session, to be used for CSS selections. The color of slots that are not defined and slots that are defined but not assigned can be set via TypoScript..
###SESSIONTEASERNAME###	Inside subpart ###ITEM### and ###ITEM_ALT### of subpart ###SINGLEROW### The header of the teaser field, to be used most as title attribute.
###SESSIONTEASER###	Inside subpart ###ITEM### and ###ITEM_ALT### of subpart ###SINGLEROW### The content of the teaser field, to be used most as title attribute.
###SESSIONDESCRIPTIONNAME###	Inside subpart ###ITEM### and ###ITEM_ALT### of subpart ###SINGLEROW### The header of the description field, to be used most as main content attribute.
###SESSIONDESCRIPTION###	Inside subpart ###ITEM### and ###ITEM_ALT### of subpart ###SINGLEROW### The content of the description field, to be used most as main content attribute.
###SESSIONDOCUMENTSNAME###	Inside subpart ###HEADER###, ###ITEM### and ###ITEM_ALT### of subpart ###SINGLEROW### The localized value of the key tx_wseevents_sessions.listFieldHeader_documents from pi1\locallang.php.
###SESSIONDOCUMENTS###	Inside subpart ###ITEM### and ###ITEM_ALT### of subpart ###SINGLEROW### The content of the documents field, to be used most as main content attribute.
###SESSIONNAME###	Inside subpart ###HEADER### of subpart ###SINGLEROW### The localized value of the key tx_wseevents_sessions.listFieldHeader_name from pi1\locallang.php Inside subpart ###ITEM### and ###ITEM_ALT### of subpart ###SINGLEROW### The session name If a Session single view page is set in the plugin than the name is embedded in a link to show the detailed session view
###SPEAKER###	Inside subpart ###HEADER### of subpart ###SINGLEROW### The localized value of the key tx_wseevents_sessions.listFieldHeader_speaker from pi1\locallang.php Inside subpart ###ITEM### and ###ITEM_ALT### of subpart ###SINGLEROW### A list of speaker names delimited by plugin.tx_wseevents_pi1.speakerdelimiter If a Speaker single view page is set in the plugin than the name is embedded in a link to show the detailed speaker view
###TIMESLOTS###	Inside subpart ###HEADER### of subpart ###SINGLEROW### The localized value of the key tx_wseevents_sessions.listFieldHeader_timeslots from pi1\locallang.php Inside subpart ###ITEM### and ###ITEM_ALT### of subpart ###SINGLEROW### A list of time slots delimited by plugin.tx_wseevents_pi1.slotdelimiter

Speaker list

For displaying the list of speakers the subpart ###SPEAKERLIST### is used.

The subparts ###ITEM### and ###ITEM_ALT### are used alternating for displaying a row of data.

If you don't want to use alternating style of the data display, you should only define the subpart ###ITEM###.

Inside the subparts ###ITEM### and ###ITEM_ALT### you can define a subpart ###SESSIONROW### which is included once for every session of the speaker.

Marker	Content
###SPEAKERNAME###	Inside subpart ###HEADER###: The localized value of the key tx_wseevents_speakers.listFieldHeader_name from pi1\locallang.php Inside subpart ###ITEM### and ###ITEM_ALT###: The speaker name concatenated from name and firstname If a Speaker single view page is set in the plugin than the name is embedded in a link to show the detailed speaker view
###EMAILNAME###	Inside subpart ###HEADER###: The localized value of the key tx_wseevents_speakers.listFieldHeader_name from pi1\locallang.php Inside subpart ###ITEM### and ###ITEM_ALT###: The localized value of the key tx_wseevents_speakers.listFieldHeader_name from pi1\locallang.php
###EMAILDATA###	Inside subpart ###ITEM### and ###ITEM_ALT###: The content of the email field
###COUNTRYNAME###	Inside subpart ###HEADER###: The localized value of the key tx_wseevents_sessions.listFieldHeader_country from pi1\locallang.php Inside subpart ###ITEM### and ###ITEM_ALT###: The localized value of the key tx_wseevents_sessions.listFieldHeader_country from pi1\locallang.php
###COUNTRYDATA###	Inside subpart ###ITEM### and ###ITEM_ALT###: The name of the country of origin
###COMPANYNAME###	Inside subpart ###HEADER###: The localized value of the key tx_wseevents_sessions.listFieldHeader_company from pi1\locallang.php Inside subpart ###ITEM### and ###ITEM_ALT###: The localized value of the key tx_wseevents_sessions.listFieldHeader_company from pi1\locallang.php
###COMPANYDATA###	Inside subpart ###ITEM### and ###ITEM_ALT###: The name of the company the speaker works for
###COMPANYLINK###	Inside subpart ###ITEM### and ###ITEM_ALT###: Link to the web site of the speakers company
###IMAGEFILE###	Inside subpart ###ITEM### and ###ITEM_ALT###: The filename of the image with relative path to the root of the web site
###IMAGELINK###	Inside subpart ###ITEM### and ###ITEM_ALT###: Complete link to the image which can be configured with typoscript setup plugin.tx_wseevents_pi1.image { file = GIFBUILDER file { XY = 200,150 5 = IMAGE } } The filename is set into the “file” property of “5”
###IMAGENAME###	Inside subpart ###ITEM### and ###ITEM_ALT###: The name of the speaker to be placed in alt attribute of the image
###INFONAME###	Inside subpart ###HEADER###: The localized value of the key tx_wseevents_sessions.listFieldHeader_speaker from pi1\locallang.php Inside subpart ###ITEM### and ###ITEM_ALT###: The localized value of the key tx_wseevents_sessions.listFieldHeader_speaker from pi1\locallang.php
###INFODATA###	Inside subpart ###ITEM### and ###ITEM_ALT###: The content of the info field
###SESSIONS###	Inside subpart ###HEADER###: The localized value of the key tx_wseevents_speakers.listFieldHeader_speakersessions from pi1\locallang.php Inside subpart ###ITEM### and ###ITEM_ALT###: A list of sessions where the speaker is set for, delimited by plugin.tx_wseevents_pi1.sessiondelimiter If a Session single view page is set in the plug-in, the session name is embedded in a link to show the detailed session view
###SESSIONNAME###	Inside subpart ###SESSIONROW###: The name of a session where the speaker is set for
###SESSIONTEASER###	Inside subpart ###SESSIONROW###: The teaser of a session where the speaker is set for
###SESSIONDESCRIPTION###	Inside subpart ###SESSIONROW###: The description of a session where the speaker is set for
###SESSIONNUMBER###	Inside subpart ###SESSIONROW###: The session number composed of the short key of the category and the 2 digit session number
###SESSIONCATEGORY###	Inside subpart ###SESSIONROW###: The category of the session, to be used for CSS selections. Slots that are not defined and slots that are defined but not assigned both have the category 0.
###SESSIONCATEGORYKEY###	Inside subpart ###SESSIONROW###: The short key of the category of the session, to be used for CSS selections. Slots that are not defined have the key NONE and slots that are defined but not assigned have the key UNUSED.
###SESSIONCATEGORYCOLOR###	Inside subpart ###SESSIONROW### The color of the category of the session, to be used for CSS selections. The color of slots that are not defined and slots that are defined but not assigned can be set via TypoScript..
###SESSIONSLOTS###	Inside subpart ###SESSIONROW###: A list of time slots delimited by plugin.tx_wseevents_pi1.slotdelimiter With a link to download an iCalendar file with the detail of the session.

Session detail

For displaying the session details the subpart ###SESSIONVIEW### is used.

Marker	Content
###SESSIONNAME###	The session name
###SESSIONTEASERNAME###	The localized value of the key tx_wseevents_sessions.listFieldHeader_teaser from pi1\locallang.php
###SESSIONTEASER###	The content of the teaser field
###SPEAKERNAME###	The localized value of the key tx_wseevents_sessions.listFieldHeader_speaker from pi1\locallang.php
###SPEAKERDATA###	A list of speaker names delimited by plugin.tx_wseevents_pi1.speakerdelimiter
###TIMESLOTSNAME###	The localized value of the key tx_wseevents_sessions.listFieldHeader_timeslots from pi1\locallang.php
###TIMESLOTSDATA###	A list of time slots delimited by plugin.tx_wseevents_pi1.slotdelimiter With a link to download an iCalendar file with the detail of the session.
###SESSIONDESCRIPTIONNAME###	The localized value of the key tx_wseevents_sessions.listFieldHeader_description from pi1\locallang.php
###SESSIONDESCRIPTION###	The content of the description field
###SESSIONDOCUMENTSNAME###	The localized value of the key tx_wseevents_sessions.listFieldHeader_documents from pi1\locallang.php
###SESSIONDOCUMENTS###	A list of document names delimited by plugin.tx_wseevents_pi1.documentsdelimiter
###SESSIONNUMBER###	The session number composed of the short key of the category and the 2 digit session number
###SESSIONCATEGORY###	The category of the session, to be used for CSS selections. Slots that are not defined and slots that are defined but not assigned both have the category 0.
###SESSIONCATEGORYKEY###	The short key of the category of the session, to be used for CSS selections. Slots that are not defined have the key NONE and slots that are defined but not assigned have the key UNUSED.
###SESSIONCATEGORYCOLOR###	The color of the category of the session, to be used for CSS selections. The color of slots that are not defined and slots that are defined but not assigned can be set via TypoScript..
###BACKLINK###	A link back to the session list with the localized value of the key back from pi1\locallang.php

Speaker detail

For displaying the speaker details the subpart ###SPEAKERVIEW### is used.

Marker	Content
###SPEAKERNAME###	The speaker name and firstname
###EMAILNAME###	The localized value of the key tx_wseevents_sessions.listFieldHeader_teaser from pi1\locallang.php
###EMAILDATA###	The content of the email field
###COUNTRYNAME###	The localized value of the key tx_wseevents_sessions.listFieldHeader_country from pi1\locallang.php
###COUNTRYDATA###	The name of the country of origin
###COMPANYNAME###	The localized value of the key tx_wseevents_sessions.listFieldHeader_company from pi1\locallang.php
###COMPANYDATA###	The name of the company the speaker works for
###COMPANYLINK###	Link to the web site of the speakers company
###IMAGEFILE###	The filename of the image with relative path to the root of the web site
###IMAGELINK###	Complete link to the image which can be configured with typoscript setup plugin.tx_wseevents_pi1.image { file = GIFBUILDER file { XY = 200,150 5 = IMAGE } } The filename is set into the “file” property of “5”
###INFONAME###	The localized value of the key tx_wseevents_sessions.listFieldHeader_speaker from pi1\locallang.php
###INFODATA###	The content of the info field
###SESSIONSNAME###	The localized value of the key tx_wseevents_speakers.listFieldHeader_speakersessions from pi1\locallang.php
###SESSIONS###	A list of sessions where the speaker is set for, delimited by plugin.tx_wseevents_pi1.sesiondelimiter
###SESSIONNAME###	Inside subpart ###SESSIONROW###: The name of a session where the speaker is set for.
###SESSIONTEASER###	Inside subpart ###SESSIONROW###: The teaser of a session where the speaker is set for.
###SESSIONDESCRIPTION###	Inside subpart ###SESSIONROW###: The description of a session where the speaker is set for.
###SESSIONNUMBER###	Inside subpart ###SESSIONROW###: The session number composed of the short key of the category and the 2 digit session number
###SESSIONCATEGORY###	Inside subpart ###SESSIONROW###: The category of the session, to be used for CSS selections. Slots that are not defined and slots that are defined but not assigned both have the category 0.
###SESSIONCATEGORYKEY###	Inside subpart ###SESSIONROW###: The short key of the category of the session, to be used for CSS selections. Slots that are not defined have the key NONE and slots that are defined but not assigned have the key UNUSED.
###SESSIONCATEGORYCOLOR###	Inside subpart ###SESSIONROW### The color of the category of the session, to be used for CSS selections. The color of slots that are not defined and slots that are defined but not assigned can be set via TypoScript..
###SESSIONSLOTS###	Inside subpart ###SESSIONROW###: A list of time slots delimited by plugin.tx_wseevents_pi1.sessiondelimiter With a link to download an iCalendar file with the detail of the session.
###BACKLINK###	A link back to the session list with the localized value of the key back from pi1\locallang.php

Time slot list

For displaying the time slots the subparts ###SLOTSALL### and ###SLOTSDAY### are used.

###SLOTSALL### is used for displaying all sessions of all days.

###SLOTSDAY### is used for displaying all sessions of one day. If not defined then ###SLOTSALL### is also used for one day display.

The subpart ###EVENTSELECT### is used for displaying a combo box for event selection. If only one event is found in the event storage folder, no selection is displayed.

The ###SLOTCOLUMN### subpart of the ###SLOTROW### subpart is for display of defined time slots.

The ###SLOTCOLUMNEMPTY### subpart of the ###SLOTROW### subpart is for display of free slots.

Marker	Content
###LABEL###	Inside subpart ###EVENTSELECT### The localized value of the key tx_wseevents_sessions.chooseeventday from pi1\locallang.php
###FORMSELECT###	Inside subpart ###EVENTSELECT### The name attribute of the html select tag, value is: tx_wseevents_pi1[showEvent]
###VALUE###	Inside subpart ###OPTIONSELECTED### and ###OPTIONNOTSELECTED### of subpart ###SELECT### inside subpart ###EVENTSELECT### Uid of event record for the select option.
###OPTION###	Inside subpart ###OPTIONSELECTED### and ###OPTIONNOTSELECTED### of subpart ###SELECT### inside subpart ###EVENTSELECT### Name of event record for the select option.
###TITLEBEGIN###	Inside subpart ###TITLEROW###: The content for the time column in the title row. The localized value of the key tx_wseevents_sessions.slot_titlebegin from pi1\locallang.php
###ROOMCOUNT###	Inside subpart ###TITLECOLUMN### of the ###TITLEROW###: subpart The count of rooms for the location, aka the column count for a day.
###TITLEDAY###	Inside subpart ###TITLECOLUMN### of the ###TITLEROW###: subpart The date of an event day.
###TITLEWEEKDAY###	Inside subpart ###TITLECOLUMN### of the ###TITLEROW###: subpart The weekday of an event day.
###HEADERBEGIN###	Inside subpart ###HEADERROW###: The content for the time column in the title row. The localized value of the key tx_wseevents_sessions.slot_headerbegin from pi1\locallang.php
###HEADERROOM###	Inside subpart ###HEADERCOLUMN### of the ###HEADERROW###: subpart The name of the room for the column.
###SLOTBEGIN###	Inside subpart ###SLOTCOLUMN###, ###SLOTCOLUMNEMPTY###, ###TIMECOLUMN### and ###TIMECOLUMNEMPTY### of the ###SLOTROW###: subpart The time of the beginning of the time slot.
###SLOTEND###	Inside subpart ###SLOTCOLUMN###, ###SLOTCOLUMNEMPTY###, ###TIMECOLUMN### and ###TIMECOLUMNEMPTY### of the ###SLOTROW###: subpart The time of the beginning of the time slot.
###SLOTCATEGORY###	Inside subpart ###SLOTCOLUMN### of the ###SLOTROW###: subpart The number of the category of the session. Slots that are not defined and slots that are defined but not assigned both have the category 0.
###SLOTCATEGORYKEY###	Inside subpart ###SLOTCOLUMN### of the ###SLOTROW###: subpart The shortdesc of the category of the session. Slots that are not defined have the key NONE and slots that are defined but not assigned have the key UNUSED.
###SLOTCATEGORYCOLOR###	Inside subpart ###SLOTCOLUMN### of the ###SLOTROW###: subpart The color of the category of the session, to be used for CSS selections. The color of slots that are not defined and slots that are defined but not assigned can be set via TypoScript..
###SLOTDAY###	Inside subpart ###SLOTCOLUMN### of the ###SLOTROW###: subpart The number of the day the slot is on.
###SLOTROOM###	Inside subpart ###SLOTCOLUMN### of the ###SLOTROW###: subpart The number of the room the slot is on.
###SLOTNUM###	Inside subpart ###SLOTCOLUMN### of the ###SLOTROW###: subpart The number of the time slot.
###SLOTSIZE###	Inside subpart ###SLOTCOLUMN###, ###SLOTCOLUMNEMPTY###, ###TIMECOLUMN### and ###TIMECOLUMNEMPTY### of the ###SLOTROW###: subpart The length of the session, aka the row count.
###SLOTWIDTH###	Inside subpart ###SLOTCOLUMN### and ###SLOTCOLUMNEMPTY### of the ###SLOTROW###: subpart The width of the session, aka the room count.
###SLOTNAME###	Inside subpart ###SLOTCOLUMN### of the ###SLOTROW###: subpart The name of the session or if no session assigned then the localized value of the key tx_wseevents_sessions.slot_notassigned from pi1\locallang.php. If no slot is assigned then the localized value of the key tx_wseevents_sessions.slot_notdefined from pi1\locallang.php.
###SLOTLINK###	Inside subpart ###SLOTCOLUMN### of the ###SLOTROW###: subpart The link to the detail view of the session with the category and session number as link text.
###SLOTICAL###	Inside subpart ###SLOTCOLUMN### of the ###SLOTROW###: subpart The link to download an iCalendar file with the detail of the session
###SLOTLINKNAME###	Inside subpart ###SLOTCOLUMN### of the ###SLOTROW###: subpart The link to the detail view of the session with the session name as link text.
###SLOTSESSION###	Inside subpart ###SLOTCOLUMN### of the ###SLOTROW###: subpart The category and number of the session or if no session assigned then the localized value of the key tx_wseevents_sessions.slot_notassigned from pi1\locallang.php. If no slot is assigned, the localized value of the key tx_wseevents_sessions.slot_notdefined from pi1\locallang.php.
###SLOTTEASER###	Inside subpart ###SLOTCOLUMN### of the ###SLOTROW###: subpart The short description of the session or if no session assigned then the localized value of the key tx_wseevents_sessions.slot_notassigned from pi1\locallang.php. If no slot is assigned, the localized value of the key tx_wseevents_sessions.slot_notdefined from pi1\locallang.php.
###SLOTSPEAKER###	Inside subpart ###SLOTCOLUMN### of the ###SLOTROW###: subpart The list of speaker for this session, every name is concatenated from name and firstname.
###COLUMNWIDTH###	Inside subpart ###TITLEROW###, ###HEADERROW### and the subparts ###SLOTCOLUMN###, ###SLOTCOLUMNEMPTY###, ###TIMECOLUMN### and ###TIMECOLUMNEMPTY### of the ###SLOTROW###: subpart and inside subpart ###HEADERCOLUMNEMPTY### of subpart ###HEADERROW### If output of column width is enabled via TypoScript, this marker is filled with the column width including the % sign.
###DAYDELIMITER###	Inside subpart ###TITLEROW###, ###HEADERROW### and the subparts ###SLOTCOLUMN### and ###SLOTCOLUMNEMPTY###. The marker is set to the class which is set in listTimeslotView.dayDelimClass if it is the day delimiter column, otherwise it is empty. This marker should put inside the class parameter of the table cell.

FAQ

ToDo

Backend configuration

For configuration and data input the Web>WSE Events module is to be used.

If you choose the WSE Events module, on the top right border there is a select box to select the mode of the displayed data.

The configuration is divided into event and common data, which you can select with the select box.

When you select the parent sysfolder which contains the different folders for event and common data, you can deal with both data switching the select box. If you select a sysfolder with only the common or the event data, you can only work with this data and have to select the associated sysfolder prior to changing the select box.

If you use translations you have to create alternative language records in all sysfolders for the common and event data and in the parent sysfolder.

Event data

In this view you can input data about the different events.

Sessions

Time slots

While no time slots are defined there is a link “Create many time slots together” that will show a table with a sample definition of time slots for all days and rooms of the event. You can edit the given time slots to your needs and then create all the time slots with one click on “Create time slots”.

Below the time slot table there is a link for updating the names of the time slots. That is very helpful for example when you change the name of a room.

Speaker restrictions

Events

Common data

In this view you can input data that is common to all events.

Speaker

Locations

Rooms

Categories

Session planning

This is not yet implemented.

Tutorial

This little tutorial will show you how to install the extension and what to do in which order to start your event management.

(This time it is only a list of headwords and has to be describe in detail later on)

Install needed extensions static_info_tables and css_styled_content.

Install extension wse_events.

Create a sys_folder with two subfolders, one for common data and one for event data.

In the sys_folder for common data create a location record.

In the sys_folder for common data create some room records for the location.

In the sys_folder for common data create some category records.

In the sys_folder for common data create some speaker records.

In the sys_folder for event data create an event record.

In the sys_folder for event data create some time slot records.

In the sys_folder for event data create some session records.

Create the following front end pages with the plugin on it:

Session list

Session detail, hidden in menu

Speaker list

Speaker detail, hidden in menu

Time slot list

Development Workflow

Who works on further development?

At the moment (August 2009) there is one person involved in the active development of this extension.

Michael Oehlhof

He is the inventor of this extension and is also the chief developer. Michael keeps track of the road map, the global direction of the extension, and provides the new functionality and bug fixes.

Getting the extension from Subversion

To always have the latest and greatest version of this extension for development, you can either download tested builds from http://svn.netlabs.org/wse_events or retrieve the files from the netlabs.org Subversion (SVN). These are the access parameters:

Connection type	http
User	your netlabs.org user name (only needed if you want to commit any changes)
Password	your netlabs.org password (only needed if you want to commit any changes)
Host	svn.netlabs.org
Repository Path	/repos
Module name	wse_events (check out only the “trunk” folder for the latest sources)
Complete link	http://svn.netlabs.org/repos/wse_events/trunk

Submitting bug requests

If you are using this extension and find out a bug or have an idea for an enhancement, feel free to use the bug tracking system to file your bug or enhancement request.

The bug tracking is done with TRAC at svn.netlabs.org/wse_events

Known problems

ToDo

To-Do list

The session number should automatically be created with the next available number for the selected category.

Front end modules for data input.

More and current information can be found in the bug tracker at svn.netlabs.org/wse_events

Changelog

See file ChangeLog in extension directory for a list of added functionality.

A full list of changes is available at http://svn.netlabs.org/wse_events/timeline

EXT: WSE Eventmanagement - wse_events	Changelog

30

EXT: WSE Eventmanagement

wse_events

forAdmins forIntermediates

The keywords help with categorizing and tagging of the manuals. You can combine two or more keywords and add additional keywords yourself. Please use at least one keyword from both lists.
If your manual is NOT in english, see next tab "language"
----
forEditors (use this for editors / german "Redakteure")
forAdmins (use this for Administrators)
forDevelopers (use this for Developers)
forBeginners (manuals covering TYPO3 basics)
forIntermediates (manuals going into more depth)
forAdvanced (covering the most advanced TYPO3 topics)
see more: http://wiki.typo3.org/doc_template#tags
----

Kasper Skårhøj

2002-11-01T00:32:00

Michael Oehlhof

Kasper Skårhøj