Location: PHPKode > scripts > LuxCal Web Based Event Calendar > admin_guide.html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>LuxCal Installation and Configuration Guide</title>
<meta name="description" content="LuxCal web calendar - a LuxSoft product">
<meta name="keywords" content="LuxSoft, LuxCal, LuxCal web calendar">
<meta name="author" content="Roel Buining">
<meta name="robots" content="nofollow">
<link rel="shortcut icon" href="lcal.ico">
<style type="text/css">
* {padding:0; margin:0;}
body {
	font: 12px arial, helvetica, sans-serif;
	background: #E0E0E0;
	color: #2B3856;
}
a {text-decoration:none; cursor:pointer;}
h1 {font-size:18pt; text-shadow:grey 0.2em 0.3em 0.2em;}
h3 {margin:20px 0 10px 0; font-size:14pt;}
h4 {margin:30px 0 6px 0; font-size:12pt;}
h5 {margin:15px 0 0 0; font-size:10pt;}
h6 {margin:10px 0 0 0; font-size:9pt;}
p { margin:6px 0; }
ul, ol {margin:0 20px;}
ol ol {list-style-type:lower-alpha;}
code {display:table; line-height:1.5; background:#FFFFFF;}
.top {background:#F2F2F2;	padding:10px;}
.floatR {float:right;}
.center {text-align:center;}
.marginLR {margin:0 40px;}
.redFlag {color:#DD3300;}
.footLB {font:italic bold 1.1em arial,sans-serif; color:#0033FF;}
.footLR {font:italic bold 1.1em arial,sans-serif; color:#AA0066;}
.navBar {
	width:100%;
	background:#AAAAFF;
	padding:2px 10px;
	border-top:1px solid #808080;
	border-bottom:1px solid #808080;
	line-height:20px;
	vertical-align:middle;
}
.endBar {
	clear:left;
	background:#AAAAFF;
	padding:0px 10px;
	text-align:right;
	border-top:1px solid #808080;
	border-bottom:1px solid #808080;
	font-size:0.8em;
}
.content {padding:10px;}
</style>
</head>

<body>
<div class="top">
<h5 class="floatR">a LuxSoft product</h5>
<h1>LuxCal Event calendar</h1>
</div>
<div class="navBar">&nbsp;</div>
<div class="content marginLR">

<h3 class="center">Administrator's Guide</h3>
<!--
<br>
<center><h4 class="redFlag">THIS IS NOT THE LATEST VERSION OF LUXCAL</h4></center>
<center><h4 class="redFlag">FOR THE LATEST VERSION GO TO <a href="http://www.luxsoft.eu">LUXSOFT</a></h4></center>
<br>
-->
<h4>Table of Content</h4>
<ol style="margin:0 40px">
<li><p><a href="#lbl-1">Introduction</a></p></li>
<li><p><a href="#lbl-2">Managing the Calendar</a></p>
<ol>
<li><p><a href="#lbl-2a">Event Categories</a></p></li>
<li><p><a href="#lbl-2b">Calendar Users</a></p></li>
<li><p><a href="#lbl-2c">Calendar Database</a></p></li>
<li><p><a href="#lbl-2d">CSV File Import</a></p></li>
<li><p><a href="#lbl-2e">iCal File Import/Export</a></p></li>
</ol></li>
<li><p><a href="#lbl-3">Advanced functions</a></p>
<ol>
<li><p><a href="#lbl-3a">Event Check Mark and To Do List</a></p></li>
<li><p><a href="#lbl-3b">Proposing / Approving Events</a></p></li>
<li><p><a href="#lbl-3c">Sidebar with Upcoming Events or Todo List</a></p></li>
<li><p><a href="#lbl-3d">Color-coding of Events</a></p></li>
</ol></li>
<li><p><a href="#lbl-4">Calendar Settings</a></p>
</li>
</ol>
<br>

<a id="lbl-1"></a><h4>1. Introduction</h4>
<p>After the LuxCal calendar has been installed or upgraded, using the <kbd>installation_guide.html</kbd>, 
this Administrator's Guide is meant to help the calendar administrator to set up the more advanced functions 
of the LuxCal calendar and to maintain the calendar so that it's functionality meets the needs of the users 
in the best possible way.</p>

<a id="lbl-2"></a><h4>2. Managing the Calendar</h4>
<p>Managing the LuxCal calendar is the responsibility of the calendar administrator, who has all calendar
		access rights.</p>
<p>In order to define users, to set up categories for the calendar, to change configuration settings and
		to add events, you must select Log In in the navigation bar at the top right corner of the screen.
		Enter the administrator name or email address and password you specified during the installation,
		and log in. On the right side of the navigation bar the administrator drop down menu will be
		displayed.</p>

<a id="lbl-2a"></a><h5>a. Event Categories</h5>
<p>A good place to start in managing your calendar is to create a number of categories for your events, each
		with its own color. Adding categories with different colors - though not required - will greatly enhance
		the views of the calendar. Categories can be for example: meeting, important, holiday, birthday, etc.</p>
<p>The initial installation has only one category which is named "no cat". To manage categories, select
		Categories in the administrator drop down menu. This takes you to a page with a list of all categories
		where you can add new categories and edit or delete current categories.</p>
<p>When adding / editing events the defined categories can be selected from a pull down list. The order in
		which categories are displayed in the pull down list is determined by the Sequence field on the
		Categories page.</p>
<p>The field "Repeat" can be used to pre-define recurring events. A category "birthday" or "anniversary" can
		be set to repeat every year. If a repeat value is specified, all events defined in this category will
		repeat as specified. The repeat value specified here will overrule possible user 'repeat' settings.</p>
<p>When activated, the field "Event needs approval" will activate the propose/approve feature for events in 
		this category. For a detailed description, see "Proposing / Approving Events" in section 3 below.</p>
<p>The checkbox "Public" can be unchecked to exclude certain event categories from being viewed by the
		"Public User" and from the RSS feeds.</p>
<p>A check mark can be activated which will be displayed in front of the event title for all events in this 
		category. The user can use this check mark to flag events, for example, as "approved" or "completed". 
		Events in this category will appear in the ToDo list, which can be opened from the calendars navigation 
		bar.</p>
<p>The fields Text Color and Background define the colors used to display events in the calendar assigned
		to this category.</p>

<a id="lbl-2b"></a><h5>b. Calendar Users</h5>
<p>The Users menu in the navigation bar allows the calendar administrator to add and edit users, their
		rights for using LuxCal and their user interface language. There are two main areas that can be edited,
		i.e. the name / e-mail address / password area and the access rights area. Possible access rights are:
		&quot;View&quot;, &quot;Post Own&quot;, &quot;Post All&quot; and &quot;Admin&quot;. It is important to
		use a valid email address for each user to be able to receive email notifications of due dates of
		events. For each user the default user-interface language can be specified. Whenever a user logs
		in, the user-interface language will be set to this language.</p>
<p>The initial installation has two users defined. One is the Public Access user, who initially has "view" 
		access and the other is the calendar administrator, with the administrator name, email address and 
		password specified during the calendar installation. The administrator has all access rights.</p>
<p>Unless the calendar administrator has given &quot;View&quot; access to Public Access users, users must 
		log in to use the calendar using their name or email address and password. Depending on the type of 
		user, a user can have different access rights which can be set by the calendar administrator.</p>
		<p>If the administrator has enabled user self-registration on the Settings page, users can register
		themselves via the Login page. Self-registered users have the access rights specified by the administrator
		on the Settings page.</p>

<a id="lbl-2c"></a><h5>c. Calendar Database</h5>
<p>The Database menu in the navigation bar allows the calendar administrator to start the following functions:</p>
<ul>
<li><p>check and repair the database.</p>
<p>This function checks the 'event' table and the 'dates' table of the database on inconsistencies and, when
found, repairs the inconsistencies. The number of inconsistencies found is indicated for each table.</p></li>
<li><p>compact database</p>
<p>During normal use of the calendar, when deleting events, the event records are not physically deleted from
the database, but are marked as 'deleted'. They can still be used in views and reports; for example in the
Changes view.
The compact database function permanently removes events from the database which have been marked as
'deleted' more than 30 days ago. Thereafter all tables are compressed to free unused space and to reduce
database overhead.</p></li>
<li><p>backup database</p>
<p>This function creates a backup of the structure and contents of all database tables in the <kbd>files/</kbd>
directory. The file name is <kbd>cal-backup-yyyymmdd-hhmmss.sql</kbd> (where 'yyyymmdd' = year, month, and
day, and hhmmss = hour, minutes and seconds). The file type is <kbd>.sql</kbd> and the created file can
directly be used to re-create the database tables structure and contents, for instance by importing the
file in the phpMyAdmin tool which is available on the server of most web hosts.</p></li>
<li><p>delete / undelete events</p>
<p>With this function the administrator can delete or undelete all events in a specified date range. Deleted 
events will be marked 'deleted', but are not yet physically deleted from the database. When the administrator 
runs the 'compact database' function, described above, events which are physically deleted from the database 
cannot be undeleted anymore.</p>
<p>When selecting this function and a date in the date range is not specified, the default will be 'unlimited'. 
This means that if both start and end date are not specified, all events will be (marked as) deleted / 
undeleted.</p></li>
</ul>

<a id="lbl-2d"></a><h5>d. CSV File Import</h5>
<p>CSV (Comma Separated Values) text files with event data can be imported into the LuxCal calendar. This
		function can for instance be used to import a CSV file with event data exported by MS Outlook. The dialogue
		to import CSV files is opened by selecting CSV Import from the admin drop-down menu in the navigation bar.</p>
<p>The CSV file contains one line per event and each line contains a number of fields each separated by a comma
		(or any other unique character). The order of the fields in each line of the CSV file is: title, venue,
		category id, date, end date, start time, end time and description. The first line of the CSV file is ignored
		by the import function and can be used for column descriptions (default in MS Outlook exports).</p>
<p>Sample CSV files - with different date/time formats - can be found in the <kbd>files/</kbd> directory of the
		LuxCal Calendar installation and have the file extension ".csv".</p>

<a id="lbl-2e"></a><h5>e. iCal File Import/Export</h5>
<p>Events from iCalendar files can be imported into the LuxCal calendar. The content of the iCal file to be
		imported must meet the [<u><a href='http://tools.ietf.org/html/rfc5545' target='_blank'>RFC5545
		standard</a></u>] of the Internet Engineering Task Force. The LuxCal calendar can also export events
		into an iCal file which can be downloaded by the calendar administrator. The dialogue to import/export
		iCal files is opened by selecting iCal Import / iCal export from the admin drop-down menu in the
		navigation bar.</p>
		<p>This function can for instance be used to back up the events of your LuxCal calendar, or to exchange
		events with other calendars, e.g. to import public holidays available in iCalendar format on the internet.
		Please note that some LuxCal event fields are not supported in the iCalendar format (e.g. private event, notify,
		email addresses) and consequently are not copied to the iCal file. Some iCal event repetition rules are not
		supported by the LuxCal calendar; these events will be displayed and earmarked as such, but will not be
		added to the calendar.</p>
	<p>Various sample iCal files can be found in the <kbd>files/</kbd> directory of the LuxCal Calendar
		installation and have the file extension ".ics".</p>

<a id="lbl-2f"></a><h5>f. Calendar Settings</h5>
<p>The Settings page in the administrator's menu on the navigation bar can be used to easily change the
		calendar's configuration settings which are stored in the <kbd>settings</kbd> table of the database.
		These settings, for instance, define the calendar title, the time zone, the language file to be used for
		the user interface, the default initial view when the calendar is started, the number of weeks/months
		displayed in the various views, the date and time format, etc.</p>
<p>IMPORTANT: Currently the TimeZone is set to &quot;Europe/Amsterdam&quot;. If you are in a different time
		zone, change the TimeZone to your local time zone. See the
		<a href="http://us3.php.net/manual/en/timezones.php">PHP Supported Timezones</a> for possible values.</p>
		
<a id="lbl-3"></a><h4>3. Advanced Functions</h4>
<p>The normal day-to-day use of the calendar is explained in the help file which can be viewed by selecting 
	'Help' (or the question mark) on the right side of the calendar's navigation bar. There are however a 
	number of more advanced functions which can be enabled / configured by the calendar administrator.</p>
<p> These advanced functions are described hereafter.</p>

<a id="lbl-3a"></a><h5>a. Event Check Mark and To Do List</h5>
<p>On the admin's Categories page, when adding/editing an event category, if you select "Check mark" and 
specify a label and a check mark, events in this category will have a check mark displayed just in front 
of the event title in the various views. For the owner of the event and users with "manager" rights this 
check mark is a hyperlink and, when clicked, will open a window to check/uncheck the check mark. This 
feature can be used for instance to mark an event as "complete" or "done". Events with a check mark will 
show up in the To Do list, which - when enabled by the administrator - can be selected from the calender's 
navigation bar.</p>

<a id="lbl-3b"></a><h5>b. Proposing / Approving Events</h5>
<p>On the admin's Categories page, when adding/editing an event category, if you select "Events need 
approval", users with post rights can - in this category - create events which are not visible to other 
users until a user with at least "manager" rights has approved the event. Until the event has been 
approved, no other user will see the event and both the originator and users with manager rights 
will see the proposed event in the various views displayed with a red bar on the left side. Once a 
user with "manager" rights has approved the event, the event will become visible to all users and 
the event will be locked and cannot be edited anymore by the originator. A user with at least manager 
rights can still edit the event. Of course, if you don't like the words "proposing" and "approving", 
you could for example also consider the words "booking" and "confirming".</p>

<a id="lbl-3c"></a><h5>c. Sidebar with Upcoming Events or Todo List</h5>
<p>A stand-alone sidebar with upcoming events or a Todo list (see above) can be integrated in your 
web page. The advantage of the sidebar, compared to embedding the calendar in an html iframe, is 
that the sidebar is displayed in a &lt;div&gt; container and can be freely styled to match the style 
of your web page. Further detail on how to add one or more stand-alone sidebars to your web page can 
be found in the <kbd>installation_guide.html</kbd>. Examples of what a sidebar can look like can be 
found on the LuxSoft <a href="http://www.luxsoft.eu/index.php?pge=demo"><b><i>Demo page</i></b></a>.</p>

<a id="lbl-3d"></a><h5>d. Color-coding Events</h5>
<p>When defining user accounts, a background color can be assigned to each user and when defining event 
categories, a text color and a background color can be assigned to each category. On the admin's 
Settings page, under Events, the admin can select whether the color of the event titles in the various 
views should correspond to the color of the user (the originator of the event) or the event category 
assigned to the event.</p>

<a id="lbl-4"></a><h4>4. Calendar Settings</h4>
<p>The calendar settings which are automatically generated during the installation process are stored in
the <kbd>settings</kbd> table of the database. All settings can be changed by the calendar administrator 
via the Settings page in the drop down menu on the navigation bar at the top right corner of the screen.</p>
<p>For those interested in technical details: The following are explanations of the PHP variables stored
in the <kbd>settings</kbd> table of the database:</p>
<ul>
<li><p><kbd>calendarTitle</kbd>: The title of the LuxCal calendar that is displayed in the header
		of the various calendar views.</p></li>
<li><p><kbd>calendarUrl</kbd>: The full URL address of the calendar, used for notification purposes, 
		E.g. http://www.mysite.xxx/calendar/index.php.</p></li>
<li><p><kbd>calendarEmail</kbd>: The sender's e-mail address ("From") in emails sent by the calendar.
		E.g. reminders, cron job summary reports. See also <kbd>notifSender</kbd> below.</p></li>
<li><p><kbd>backLinkUrl</kbd>: URL of parent page. If specified, a Back button will be displayed on 
		the left side of the Navigation Bar which links to this URL. For instance to link back to the 
		parent page from which the calendar was started.</p></li>
<li><p><kbd>timeZone</kbd>: Your local time zone. See the <a href="http://us3.php.net/manual/en/timezones.php">
		PHP Supported Timezones</a> for possible values. Setting the correct time zone is important for the
		"today" indication in the various views and when the "notification" feature is used.</p></li>
<li><p><kbd>notifSender</kbd>: When the calendar sends reminder emails, the sender field of the email
    can contain either the calendar email address, or the email address of the user who created the
    event. In case of the user email address, the receiver can reply to the email.</p></li>
<li><p><kbd>details4All</kbd>: If enabled: event details will be visible to the owner of the event and
		to all other users; if disabled: event details will only be visible to the owner of the event and
		to users with 'post all' rights.</p></li>
<li><p><kbd>eventColor</kbd>: Specifies whether events should be displayed with the event owner color,
		or with the event category color (0: owner color, 1: category color)</p></li>
<li><p><kbd>privEvents</kbd>: Can be disabled, enabled or default. If enabled: The user can choose to 
		create private events, which are hidden from other users. If default: All events entered by a 
		logged in user will default to private.</p></li>
<li><p><kbd>navButText</kbd>: If enabled: The buttons on the navigation bar will be displayed with text</p></li>
<li><p><kbd>navTodoList</kbd>: If enabled: A Todo list button will be displayed on the navigation bar, 
		which can be used to display the Todo list.</p></li>
<li><p><kbd>navUpcoList</kbd>: If enabled: An Upcoming button will be displayed on the navigation bar, 
		which can be used to display the Upcoming Events list.</p></li>
<li><p><kbd>rssFeed</kbd>: If enabled: RSS feed links will be displayed in the calendar footer and will
		be incuded in the HTML head section.</p></li>
<li><p><kbd>userMenu</kbd>: Specifies whether the user filter is displayed in the calendar's options
		panel. Possible values: 0 = disabled, 1 = enabled.</p></li>
<li><p><kbd>catMenu</kbd>: Specifies whether the event category filter is displayed in the calendar's
		options panel. Possible values: 0 = don't display the category filter menu, 1 = display
		the category filter menu.</p></li>
<li><p><kbd>langMenu</kbd>: Specifies whether the calendar users are allowed to select their preferred
		user interface language the calendar's options panel. Possible values: 0 = don't display the
		language selection menu, 1 = display the language selection menu.</p></li>
<li><p><kbd>defaultView</kbd>: The initial calendar view to be displayed when the LuxCal Calendar
		is started. Possible values/views: 1 = Year, 2 = Full Month, 3 = Work Month, 4 = Full Week,
		5 = Work Week, 6 = Day (today), 7 = Upcoming events and 8 = Changes.</p></li>
<li><p><kbd>language</kbd>: The default user interface language. Only installed languages can be
		specified.</p></li>
<li><p><kbd>selfReg</kbd>: Indicates whether users can register themselves via the Log-in page.
		Possible values: 0 = self-registration disabled, 1 = self-registration enabled.</p></li>
<li><p><kbd>selfRegPrivs</kbd>: The access rights for self-registered users. Possible values: 1 = view,
		2 = post self (post events and edit own events), 3 = post all (post events and edit own and other
		user's events).</p></li>
<li><p><kbd>cookieExp</kbd>: Number of days before a 'Remember me' cookie - set during Login - expires</p></li>
<li><p><kbd>selfRegNot</kbd>: Indicates whether a notification should be sent to the admin when a user
		has self-registered. Possible values: 0 = disabled, 1 = enabled.
<li><p><kbd>yearStart</kbd>: The start month in year view (1-12 or 0, 0: current month).</p></li>
<li><p><kbd>colsToShow</kbd>: The number of months to show per row in year view.</p></li>
<li><p><kbd>rowsToShow</kbd>: The number of 4-months rows to show in year view. The default value is
		4.</p></li>
<li><p><kbd>weeksToShow</kbd>: The number of weeks to show in month view. The value 0 (zero) has a
		special meaning and will result in the display of just one single full month. The default value
		is 10.</p></li>
<li><p><kbd>workWeekDays</kbd>: A string of numbers which specify the days of the week to show in
		work month view and work week view. Valid day numbers are: 1 = Monday, 2 = Tuesday, ... , 7 =
		Sunday.</p></li>
<li><p><kbd>lookaheadDays</kbd>: The number of days to look ahead in upcoming view, todo list and RSS
		feeds. The default value is 14 (two weeks).</p></li>
<li><p><kbd>dwStartHour</kbd>: The start of the full time block on the day and week views. The default
		value is 6 (corresponding to 6:00am). This parameter helps to avoid wasting space for the nightly
		hours, where normally no, or very few, events are planned.</p></li>
<li><p><kbd>dwEndHour</kbd>: The end of the full time block on the day and week views. The default
		value is 18 (corresponding to 18.00/6:00pm). This parameter helps to avoid wasting space for the
		nightly hours, where maybe no, or very few, events are planned.</p></li>
<li><p><kbd>dwTimeSlot</kbd>: The time slot size (in minutes) in day/week view. Together with the
		<kbd>dwStartHour</kbd> (see above) this value determines the number of rows in day/week view.</p></li>
<li><p><kbd>dwTsHeight</kbd>: The time slot display height (in number of pixels) in day/week view.
		</p></li>
<li><p><kbd>eventHBox</kbd>: Indicates whether an overlay with events details should pop up when the user
		hovers an event square in Year view or an event title in Month, Week or Day view.
		Possible values: 0 = disabled, 1 = enabled. The default value is 1.</p></li>
<li><p><kbd>showAdEd</kbd>: Specifies whether the date/user added/edited of an event should be shown in
		the hoverbox in the various views, in the Upcoming Events view, in the Changes view and in email
		notification messages.</p></li>
<li><p><kbd>showCatName</kbd>: Specifies whether the event category name should be displayed for the
		events in various views (0: no, 1: yes)</p></li>
<li><p><kbd>showLinkInMV</kbd>: Specifies whether URL-links, specified in the description field of the
		events, should be shown in month view (0: no, 1: yes)</p></li>
<li><p><kbd>dateFormat</kbd>: Text string defining the format of dates in dd, mm and yyyy.
		Possible characters: y: yyyy, m: mm, d: dd and any non-alphanumeric as separator.</p></li>
<li><p><kbd>MdFormat</kbd>: Text string defining the format of dates in dd and month.
		Possible characters: d: dd, M: month in letters and any non-alphanumeric as separator.</p></li>
<li><p><kbd>MdyFormat</kbd>: Text string defining the format of dates in dd, month and yyyy.
		Possible characters: d: dd, M: month in letters, y: yyyy and any non-alphanumeric as separator.</p></li>
<li><p><kbd>MyFormat</kbd>: Text string defining the format of dates in month and yyyy.
		Possible characters: M: month in letters, y: yyyy and any non-alphanumeric as separator.</p></li>
<li><p><kbd>DMdFormat</kbd>: Text string defining the format of dates in weekday, dd and month.
		Possible characters: WD: weekday in text, d: dd, M: month in letters and any non-alphanumeric
		as separator.</p></li>
<li><p><kbd>DMdyFormat</kbd>: Text string defining the format of dates in weekday, dd, month and yyyy.
		Possible characters: WD: weekday in text, d: dd, M: month in letters, y: yyyy and
		any non-alphanumeric as separator.</p></li>
<li><p><kbd>timeFormat</kbd>: Text string defining the format of times in hh and mm.
		Possible characters: h: hours, m: minutes, a: am/pm (optional), A: AM/PM (optional) and
		any non-alphanumeric as separator.</p></li>
<li><p><kbd>weekStart</kbd>: The first day of the week. Possible values: 0 = Sunday, 1 = Monday.
<li><p><kbd>weekNumber</kbd>: Specifies whether week numbers should be displayed in the various
		calendar views. Possible values: 0 = disabled, 1 = enabled. The default value is 1.</p></li>
<li><p><kbd>mailServer</kbd>: Specifies whether PHP mail or SMTP mail should be used for email reminders 
		and periodic reports. Possible values: 0 = mail disabled, 1 = PHP mail, 2 = SMTP mail. The default 
		value is 1.</p></li>
<li><p><kbd>smtpServer</kbd>: Text string specifying the name of the SMTP server. For gmail this is for 
		instance 'smtp.gmail.com'.</p></li>
<li><p><kbd>smtpPort</kbd>: Specifies the SMTP port number. For example 25, 465, 587. Gmail for example 
		uses port number 465.</p></li>
<li><p><kbd>smtpSsl</kbd>: Specifies whether Secure Sockets Layer (SSL) should be used. Possible values: 
		0 = no, 1 = yes. Gmail for instance uses SSL. The default value is 1.</p></li>
<li><p><kbd>smtpAuth</kbd>: Specifies whether authentication should be used when sending SMTP mail. 
		Possible values: 0 = no, 1 = yes. Gmail for instance uses authentication. The default value is 1.</p></li>
<li><p><kbd>smtpUser</kbd>: Text string specifying the SMTP user name. Required when SMTP authentication
		should be used.</p></li>
<li><p><kbd>smtpPass</kbd>: Text string specifying the SMTP password. Required when SMTP authentication
		should be used.</p></li>
<li><p><kbd>adminCronSum</kbd>: Specifies whether the calendar administrator will receive a summary
    report after the periodic functions have been executed. Automatic periodic functions should be
		installed (see below) and emailing cron job output should be enabled on the server.</p></li>
<li><p><kbd>chgEmailList</kbd>: A list with destination email addresses for calendar changes sent by
		the <kbd>sendchg.php</kbd> script. Automatic periodic functions should be installed (see below).</p></li>
<li><p><kbd>chgNofDays</kbd>: The number of days the <kbd>sendchg.php script</kbd> (see previous variable)
    should look back for calendar changes. If the automatic periodic functions have been installed
		(see below), this variable could be set to 1 (one day)</p></li>
<li><p><kbd>icsExport</kbd>: Export events in iCalendar format to a .ics file in the 'files' folder.
		The file name is the calendar name with blanks replaced by a underscore. This function works via 
		a cron job.</p></li>
<li><p><kbd>eventExp</kbd>: The number of days after the event's due date when an event expires and
		will be automatically deleted (0:never). This function works via a cron job.</p></li>
<li><p><kbd>maxNoLogin</kbd>: Indicates after how many 'no-login' days a user account should be
		automatically deleted. Possible values: 0 = never delete a user account, 1 - 365 = number of days.
		Automatic periodic functions should be installed (see below).</p></li>
<li><p><kbd>miniCalView</kbd>: The calendar view for the LuxCal mini calendar. Possible values/views:
		1 = Full Month, 2 = Work Month, 3 = Full Week, 4 = Work Week.</p></li>
<li><p><kbd>miniCalPost</kbd>: Indicates whether events can be added, edited and deleted via the mini
		calendar without opening the full calendar.
		Possible values: 0 = posting of events disabled, 1 = posting of events enabled. The default value
		is 0.</p></li>
<li><p><kbd>miniCalHBox</kbd>: Indicates whether an overlay with events details should pop up when the
		user hovers an event square in the mini calendar.
		Possible values: 0 = disabled, 1 = enabled. The default value is 1.</p></li>
<li><p><kbd>mCalUrlFull</kbd>: When clicking the month at the top of the mini calendar, to go to the 
		full calendar, the user will be directed to this URL. If not specified, the full calendar will 
		open in a new window.
		This URL is in particular useful when the full calendar is embedded in an existing user page.</p></li>
<li><p><kbd>sideBarHBox</kbd>: Indicates whether an overlay with events details should pop up when the
		user hovers an event in the sidebar (0: no, 1: yes).</p></li>
<li><p><kbd>showLinkInSB</kbd>: Specifies whether URL-links, from the description field of the events,
		should be shown in the sidebar (0: no, 1: yes).</p></li>
<li><p><kbd>sideBarDays</kbd>: The number of days to look ahead in the sidebar. The
		default value is 14 (two weeks).</p></li>
</ul>
</div>
<br><h5>&nbsp;- End of Installation Guide -</h5>
<br>
<div class="endBar">
	design 2013 - powered by <a href="http://www.luxsoft.eu"><span class="footLB">Lux</span><span class="footLR">Soft</span></a>
</div>
<br>&nbsp;
</body>
</html>
Return current item: LuxCal Web Based Event Calendar