Installing Release 2.2.2
- A Web server (Apache, IIS, etc.)
- PHP 4.2 or higher
- MySQL 3.23 or higher or PostgreSQL
- Install the webserver (Apache, Microsoft IIS etc.), PHP 4.2 (or higher) with the PEAR DB library included and MySQL 3.23 (or higher) or PostgreSQL; Since calendar uses PHP's PEAR database abstraction layer you should also be able to use any other database like Oracle, SQL Server etc. However we haven't tried that.
- Create a database within MySQL or PostgreSQL e.g. called "calendar". For MySQL we recommend using PHPMyAdmin for easy management of your MySQL database.
- Download the calendar software, unzip the archive and copy all files into your webserver root or a sub-directory thereof, e.g. calendar/
- Point your web-browser at the place you just copied the files to, e.g. http://www.myorg.edu/calendar/. It should redirect you to the installation script
- Fill in the installation parameters and click the "Install" button. This will create the database structure and the main configuration file called "config.inc.php" (which you can always adapt later by hand)
- Remove the install/ directory
- Restart your web-browser and see if the calendar looks OK
- Read the the documentation below that gives a brief overview about how the calendar works
- Open the calendar, go to the "Update" tab and login with the administrator user-ID and password you entered on the installation screen
- Change header, footer, colors, permissions etc. through the web interface
From 2.0.2 to 2.0.3:
Just copy the files over the existing ones (after making a backup of course). You do not need to walk through the installation process again. However, make sure you keep your config.inc.php. Last but not least you need to add the following line to the end of your config.inc.php:
The number denotes the number of hours you are ahead or behind GMT. For example Blacksburg/Virginia (USA) is 5 hours behind GMT. Berlin (Germany) is 1 hour ahead of GMT. In this case you would set it to "-1".
From 2.0.3 to 2.0.4:
Just copy the files over the existing ones (after making a backup of course). You do not need to walk through the installation process again. However, make sure you keep your config.inc.php. In your calendar database run the following SQL command: "ALTER TABLE vtcal_user DROP calendarid;"
From 2.0.4 to 2.1.0:
Just copy the files over the existing ones (after making a backup of course). You do not need to walk through the installation process again. The database structure has not changed. However, make sure you keep your config.inc.php.
From 2.1.0 to 2.2.0:
- Backup all files of your previous installation
- Unpack the files of version 2.2.0 (perhaps first in a separate directory so that you minimize downtime in your production environment)
- Copy install/config.inc.template.php to config.inc.php
- Edit the config.inc.php file and adjust it to your needs (copy&paste parameters from your backup of the previous version's config.inc.php)
- Remove the install/ directory
- Run the following statements in your database:
ALTER TABLE vtcal_calendar ADD gridcolor TEXT AFTER todaycolor;
ALTER TABLE vtcal_calendar ADD linkcolor TEXT AFTER todaycolor;
ALTER TABLE vtcal_calendar ADD textcolor TEXT AFTER todaycolor;
ALTER TABLE vtcal_calendar ADD futurecolor TEXT AFTER todaycolor;
ALTER TABLE vtcal_calendar ADD pastcolor TEXT AFTER todaycolor;
UPDATE vtcal_calendar SET pastcolor='#eeeeee', futurecolor='#ffffff', textcolor='#000000', linkcolor='#3333cc', gridcolor='#cccccc' WHERE pastcolor IS NULL;
- Replace the existing files with the new ones of version 2.2.0
- Customize the colors using the calendar's "Update" interface