1 | <?php |
---|
2 | if ( $_SERVER['REQUEST_METHOD'] != "GET" && $_SERVER['REQUEST_METHOD'] != "POST" && $_SERVER['REQUEST_METHOD'] != "HEAD" ) { |
---|
3 | /** |
---|
4 | * If the request is not a GET or POST then they must really want caldav.php! |
---|
5 | */ |
---|
6 | include("./caldav.php"); |
---|
7 | exit; // Not that it should return from that! |
---|
8 | } |
---|
9 | |
---|
10 | include("./always.php"); |
---|
11 | include("DAViCalSession.php"); |
---|
12 | $session->LoginRequired(); |
---|
13 | |
---|
14 | include("interactive-page.php"); |
---|
15 | include("page-header.php"); |
---|
16 | |
---|
17 | echo <<<EOBODY |
---|
18 | <h1>Administration</h1> |
---|
19 | <p>You are logged on as $session->username ($session->fullname)</p> |
---|
20 | EOBODY; |
---|
21 | ?> |
---|
22 | <h2>Administration Functions</h2> |
---|
23 | <p>The administration of this application should be fairly simple. You can administer:</p> |
---|
24 | <ul> |
---|
25 | <li>Users (or Resources or Groups) and the relationships between them</li> |
---|
26 | <li>The types of relationships that are available</li> |
---|
27 | </ul> |
---|
28 | <p><i>There is no ability to view and / or maintain calendars or events from within this administrative interface.</i></p> |
---|
29 | <p>To do that you will need to use a CalDAV capable calendaring application such as Evolution, Sunbird, Thunderbird |
---|
30 | (with the Lightning extension) or Mulberry.</p> |
---|
31 | |
---|
32 | <h3>Principals: Users, Resources and Groups</h3> |
---|
33 | <p>These are the things which may have collections of calendar resources (i.e. calendars).</p> |
---|
34 | <p><a href="<?php echo $c->base_url; ?>/admin.php?action=browse&t=principal&type=1">Here is a list of users (maybe :-)</a>. You can click on any user to see the full detail |
---|
35 | for that person (or group or resource - but from now we'll just call them users).</p> |
---|
36 | <p>The primary differences between them are as follows:</p> |
---|
37 | <ul> |
---|
38 | <li>Users will probably have calendars, and are likely to also log on to the system.</li> |
---|
39 | <li>Resources do have calendars, but they will not usually log on.</li> |
---|
40 | <li>Groups provide an intermediate linking to minimise administration overhead. They might not have calendars, and they will not usually log on.</li> |
---|
41 | </ul> |
---|
42 | |
---|
43 | <h3>Groups & Grants</h3> |
---|
44 | <ul> |
---|
45 | <li>Grants specify the access rights to a collection or a principal</li> |
---|
46 | <li>Groups allow those granted rights to be assigned to a set of many principals in one action</li> |
---|
47 | <li>Groups may be members of other groups, but complex nesting will hurt system performance</li> |
---|
48 | </ul> |
---|
49 | |
---|
50 | <h2>Configuring Calendar Clients for DAViCal</h2> |
---|
51 | <p>The <a href="http://rscds.sourceforge.net/clients.php">DAViCal client setup page on sourceforge</a> have information on how |
---|
52 | to configure Evolution, Sunbird, Lightning and Mulberry to use remotely hosted calendars.</p> |
---|
53 | <p>The administrative interface has no facility for viewing or modifying calendar data.</p> |
---|
54 | |
---|
55 | <h2>Configuring DAViCal</h2> |
---|
56 | <p>If you can read this then things must be mostly working already.</p> |
---|
57 | <p>The <a href="http://rscds.sourceforge.net/installation.php">DAViCal installation page</a> on sourceforge has |
---|
58 | some further information on how to install and configure this application.</p> |
---|
59 | |
---|
60 | <?php |
---|
61 | include("page-footer.php"); |
---|