- 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
- 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
- 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
- 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
- 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