Upgrading
---------
If you don't want to lose any data, run the following queries on your
ezpublish db:
ALTER TABLE `ezcalendarevents` ADD `frequency` VARCHAR( 12 ) DEFAULT
'once' NOT NULL ;
ALTER TABLE `ezcalendarevents` ADD INDEX ( `frequency` ) ;
ALTER TABLE `ezcalendarevents` ADD `number_of_times_` INT DEFAULT '0' NOT
NULL ;
UPDATE ezcalendarevents SET frequency='once';
Installation
------------
Run the following SQL command on your ezpublish databases (only if
you're
installing the module for the first time of course):
CREATE TABLE `ezcalendarevents` (
`userid` int(11) NOT NULL default '0',
`eventid` int(11) NOT NULL auto_increment,
`start_time` int(11) NOT NULL default '0',
`end_time` int(11) NOT NULL default '0',
`description` text NOT NULL,
`frequency` varchar(12) NOT NULL default '0',
`number_of_times` int(11) NOT NULL default '0',
PRIMARY KEY (`eventid`),
KEY `userid` (`userid`),
KEY `frequency` (`frequency`)
) TYPE=InnoDB |
Note: you can use different table types, of course.
Unzip the ZIP file in the base ezpublish directory (usually ezpublish).
Usage
-----
The module creates a new view "calendar". Try admin/calendar/day for a
starting
point.
The following views are available:
day
week
month
year_small
If you want to access a specific timeframe, pass
timestamp=UNIX_TIMESTAMP
to any of the above.
list (has params start_time/end_time, both of which are an
UNIX_TIMESTAMP)
Todo
----
- Shared calendars
- Think about coliding/overlapping events: Should they be allowed? If
so, what is the sanest way to render them?