Wcal 2.1 documentation

Creating calendars

A new Calendar is created by adding the calendar definition in the wcal.conf file. For example, the sample wcal.conf file that comes with Wcal distribution contains the definition of three calendars:
  1. commercial
  2. production
  3. savignon
You can add parameters to the calendar definition (see Configuring Wcal). In the sample file, only long name is set for the three calendars.
user=commercial
        long name = Commercial
end user

user=production
        long name = Production
end user

user=savignon
        long name = Joël Savignon
end user 

Creating multiple views on the same calendar

Imagin you want to allow a user john to access to a calendar cal1 in read/write mode and allow another user jack to access to this calendar only in read only mode, you can write in the wcal.conf file:
user=cal1
         long name = Calendar RW
end user

user=cal1ro
         read only = true
         data id = cal1
         long name = Calendar RO
end user
data id = cal1 means that the data of cal1ro is the data of cal1. The calendar cal1ro is the same as cal1 except that you can't modify events in it.

Restricting access to calendars

Now that we have a read/write and a read only version of the calendar, we can change the .htaccess file in the calendars directories to restrict access to certain users.

The file /home/httpd/html/wcal/cal1/.htaccess can be for example:

AuthType Basic 
AuthUserFile /usr/local/apache/conf/htpasswd.users 
AuthName "Calendar RW" 
Require john
And the file /home/httpd/html/wcal/cal1ro/.htaccess can be for example:
AuthType Basic 
AuthUserFile /usr/local/apache/conf/htpasswd.users 
AuthName "Calendar RO" 
Require jack
Login/password will be prompt when accessing to the different calendars. For more information about Apache access restriction, see the Apache documentation on the Apache web site.
Back to the Wcal main page