EXT: GLZ Calendar¶

What does it do?¶

Yet another calendar, because I found no one, which fits my requirements. Features: Each event can be assigned to one or more "organisators". The view can be configured to show only events from specified organisators. Also the number of events or days to display can be limited. As for the rendering, the events are grouped into month and day.

Screenshots¶

Events only from Organisator 1

April 2006

Plugin options¶

Reference¶

All values are subkeys of plugin.tx_glzcalendar_pi1.

Example¶

The following listing shows the Typoscript setup provided with the extension and explains it.

First, a temporary object to access the template is made, because it is used often.

temp {

template = TEXT

template.field = template

}

Now, the real setup starts. The timezone is set to 1, which means GMT+1. With this information all time values (start time and end time) are transformed into UTC time. This is important for the strftime function of stdwrap, because the PHP strftime function assumes as input a timestamp in UTC and formats it according the PHP locale settings (setlocale).

plugin.tx_glzcalendar_pi1 {

# timezone of *entered* date/time values in database

timezone = 1

The next step is to setup the objects month\_begin and month\_end . They can be any valid Typoscript object. In the setup below, an object of type TEMPLATE is used. The HTML template is not selected directly over a file object. The plugin provieds the contentof the selected template file (plugin options) in the field '”template”. So the template property of the TEMPLATE object is set as TEXT object where the value is the field “template” (this setup is done in temp.template and copied).

The next step is to select the desired subpart of the HTML template and replace the markers. Here, the marker MONTH is replaces the by output of the strftime function with the start date as input.

As for the month\_end , only the HTML content of the template is taken without any replacements (contains only the table end tag </table> ).

month_begin = TEMPLATE

month_begin {

template < temp.template

workOnSubpart = MONTH_BEGIN

marks {

MONTH = TEXT

MONTH {

field = start_date

strftime = %B %Y

}

}

}

month_end = TEMPLATE

month_end {

template < temp.template

workOnSubpart = MONTH_END

}

Very similar to the two objects before, the day\_begin and day\_end are initialized.

day_begin = TEMPLATE

day_begin {

template < temp.template

workOnSubpart = DAY_BEGIN

marks {

DAY = TEXT

DAY {

field = start_date

strftime = %d. %A

}

}

}

day_end = TEMPLATE

day_end {

template < temp.template

workOnSubpart = DAY_END

}

Now, the object for the event itself is set. To substitute the TIME mark, some more effort than usual is necessary. A Content Object Array (COA) is used to render the the start time and optional end. With the if property of the stdwrap function and the related fields, the second part is made optional.

event = TEMPLATE

event {

template < temp.template

workOnSubpart = EVENT

marks {

TIME = COA

TIME {

10 = TEXT

10 {

field = start_time

strftime = %H:%M

if.isTrue.field = has_start_time

}

20 = TEXT

20 {

value = <br>to

if.isTrue.field = has_range

}

30 = TEXT

30 {

field = end_date

wrap = &nbsp;|

strftime = %d.%m

if.isTrue.field = end_date

}

40 = TEXT

40 {

field = end_time

strftime = %H:%M

wrap = &nbsp;|

if.isTrue.field = end_time

}

}

TITLE = TEXT

TITLE.field = title

ORGANISATOR = TEXT

ORGANISATOR {

field = organisator_name

wrap = |:&nbsp;

}

DESCRIPTION = TEXT

DESCRIPTION.field = description

}

}

}