Screenshots and Features

Things you really need.


Based on the iCal standard

iCal or iCalendar was the first calendar application to offer support for multiple calendars and the ability to publish/subscribe calendars similar to RSS Feeds.

The user interface of this TYPO3 extension is based upon the PHP iCalendar project, available at Many thanks to its developers for a great product to build upon.

Import and export of ICS/iCal files and feeds

Mozilla Sunbird and Mac iCal compatible

One powerful feature offered by the Calendar Base is the ability to subscribe to external ICS or iCal feeds. For example this could allow you to import and export events or even subscribe a whole calendar with Mozilla Sunbird (Windows, Linux) or iCal (Mac).

Seamless TYPO3 integration

Dataflow model

If you have ever installed an extension like tt_news you won't have any trouble installing calendar base. The Extension is installed (and updated) using the extension manager in the backend and easily configured using flexform configuration like every modern TYPO3 extension.

Calendar items can be created/edited in the backend and in the frontend, thus being an ideal solution for intranets with many FE users.

Of course this extension can be extended by extensions. Existing extension for example give the possibility of showing news items in the calendar.

Event monitoring and notification for frontend users

monitoring subscription view

Visitors can monitor events by subscribing with a valid e-mail address. For registered FE-users, the e-mail address is not needed - they simply need one click to subscribe. Spam robots are defeated by captcha functionality when not logged in.



- different standard views: day, week, month, year, list, search, rss, ics/ical, event, location, organizer, free & busy
- define your own view and add it to the customViews
- preselect categories to be shown
- define another image path so you can use your own images
- define the viewable time of your calendar: e.g. 8:00 - 22:00
- define the weekstartday: sunday or monday
- redefine the link targets: e.g. the daylink points to a list view
- use the gridLength to divide an hour into x parts for the day- and week-view: e.g. 15 -> 60 minutes / 15 minutes = 4 sections
- standard wrap is enabled for each database-field in each view: {view}.{db-fieldname}_stdWrap
- every time-related value is generated through the server using the language locale setting of TYPO3
- define a different event-style if the fe-user is owner of the event
- connect the calendar with your login form and let user login through the calendar


- preview available (crops description)
- start day & end day
- start time & end time
- title
- description
- has to be assigned to a calendar record
- can have categories
- define a location either: textfield, tx_cal_location record, tt_address record or link to a page
- define an organizer either: textfield, tx_cal_organizer record, tt_address record or link to a page
- add images
- add an attachment file
- define a recurring rule and let the event repeat
- define exception events (negative events) as exceptions of the recurring rule

Location & Organizer

- title
- description
- address
- add images


- define start- and endtime: "now" -> "+30 day" or an archive: "-2 years" -> "now"
- define the maximum events to be displayed
- define a custom heading and use the variable start- and endtime values
- wrap your list by: day, week, month, category or calendar
- use the pagebrowser to minimize your list

Import / Export

- exchange your events through the ical standard.
- importing is also possible: use the calendar record and choose a different type: "local ics" or "url"


- You can search for events, locations or organizer or all of them at once

Event subscription/monitoring & reminder

- allow fe-user and/or public users to subscribe to an event and get updates if it changes
- use captcha extension to protect your events from being spamed
- even changes in the backend can trigger notification emails (therefore it has to be configured in page TS config)
- send out different templates for different users: notify.all.xxxTemplate => template for everyone (fallback), notify.2.xxxTemplate => template for fe-user with uid 2
- you can set up a cronjob and send out reminder emails x minutes before the event start


- create/edit/delete of calendar, category, event, location, organizer (only event is available for none-admins)
- use the frontend date selector from rlmp_dateselectlib in frontend editing

Rights-system for the fe-editing

- enable/disable the fe-editing through one flag: edit = 1 / 0
- define admins with all rights
- define each right for each user/group
- allow anonymous user to create events
- define which fields are allowed to be filled in
- define default values
- add the fe-user per default to the notify list
- add the fe-user per default to the shared list (usefull if only fe-user should be able to edit this event but not the others of the same calendar which belongs to someone else)
- notify fe-user(s) if a public event has been created