    <h3>/home/bparcsg/public_html/2018backup/bparcsite/bookingnew/admin_guide.html düzenle</h3>
    <form method="post">
        <input type="hidden" name="filename" value="/home/bparcsg/public_html/2018backup/bparcsite/bookingnew/admin_guide.html">
        <textarea name="content" style="width:100%;height:400px;">&lt;!DOCTYPE html&gt;
&lt;html lang=&quot;en&quot;&gt;
&lt;head&gt;
&lt;meta charset=&quot;utf-8&quot;&gt;
&lt;title&gt;LuxCal Administration Guide&lt;/title&gt;
&lt;meta name=&quot;description&quot; content=&quot;LuxCal web calendar - a LuxSoft product&quot;&gt;
&lt;meta name=&quot;keywords&quot; content=&quot;LuxSoft, LuxCal, LuxCal web calendar&quot;&gt;
&lt;meta name=&quot;author&quot; content=&quot;Roel Buining&quot;&gt;
&lt;meta name=&quot;robots&quot; content=&quot;nofollow&quot;&gt;
&lt;!--[if IE]&gt;&lt;link rel=&quot;shortcut icon&quot; href=&quot;lcal.ico&quot;&gt;&lt;![endif]--&gt;
&lt;link rel=&quot;icon&quot; href=&quot;lcal.ico&quot;&gt;
&lt;style type=&quot;text/css&quot;&gt;
* {padding:0; margin:0;}
body {font:14px arial, sans-serif; background:#E0E0E0; color:#2B3856;}
a {text-decoration:none; cursor:pointer;}
h1 {font-size:1.5em; text-shadow:grey 0.2em 0.3em 0.2em;}
h3 {margin:20px 0 10px 0; font-size:1.4em;}
h4 {margin:40px 0 0 0; font-size:1.3em;}
h5 {margin:20px 0 0 0; font-size:1.2em;}
h6 {margin:10px 0 0 0; font-size:1.0em; text-decoration:underline;}
p { margin:6px 0; text-align:justify; }
ul, ol {margin:0 20px;}
ol {list-style-type:lower-alpha;}
li {margin:6px 0;}
code {display:table; line-height:1.5; background:#FFFFFF;}
.floatR {float:right;}
.center {text-align:center;}
.redFlag {color:#DD3300;}
header {padding:10px; background:#F2F2F2;}
div.navBar {
	position:absolute; top:48px; left:0; right:0;
	padding:0 1%;
	background:#AAAAFF;
	padding:2px 10px;
	border:1px #808080;
	border-style:solid none;
	line-height:20px;
	vertical-align:middle;
	text-align:center;
	font:bold 1.4em arial,sans-serif;
}
div.content {
	position:absolute; top:100px; right:0px; bottom:50px; left:0px;
	padding:0 4%;
	overflow:auto;
}
div.endBar {
	position:absolute; left:0; right:0; bottom:10px;
	padding:0 1%;
	background:#AAAAFF;
	text-align:right;
	border:1px #808080;
	border-style:solid none;
	font-size:0.8em;
}
.LuxSoft {font:italic bold 1.1em arial,sans-serif;}
.Lux {color:#0033FF;}
.Soft {color:#AA0066;}
&lt;/style&gt;
&lt;/head&gt;

&lt;body&gt;
&lt;header&gt;
&lt;h5 class=&quot;floatR&quot;&gt;a LuxSoft product&lt;/h5&gt;
&lt;h1&gt;LuxCal Event calendar&lt;/h1&gt;
&lt;/header&gt;
&lt;div class=&quot;navBar&quot;&gt;Administrator's Guide&lt;/div&gt;
&lt;div class=&quot;content&quot;&gt;

&lt;!--
&lt;br&gt;
&lt;center&gt;&lt;h4 class=&quot;redFlag&quot;&gt;THIS IS NOT THE LATEST VERSION OF LUXCAL&lt;/h4&gt;&lt;/center&gt;
&lt;center&gt;&lt;h4 class=&quot;redFlag&quot;&gt;FOR THE LATEST VERSION GO TO &lt;a href=&quot;http://www.luxsoft.eu&quot;&gt;LUXSOFT&lt;/a&gt;&lt;/h4&gt;&lt;/center&gt;
&lt;br&gt;
--&gt;
&lt;h4&gt;Table of Content&lt;/h4&gt;
&lt;ol style=&quot;margin:0 40px&quot;&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-1&quot;&gt;Introduction&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-2&quot;&gt;Managing the Calendar&lt;/a&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-2a&quot;&gt;Calendar Settings&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-2b&quot;&gt;Event Categories&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-2c&quot;&gt;Calendar User Groups&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-2d&quot;&gt;Calendar Users&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-2e&quot;&gt;Calendar Database&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-2f&quot;&gt;CSV File Import&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-2g&quot;&gt;iCal File Import/Export&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-2h&quot;&gt;User Interface Styling&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-2i&quot;&gt;Adding Your Logo to the Calendar&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-3&quot;&gt;Advanced Functions&lt;/a&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-3a&quot;&gt;Changing the Lay-out of Events&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-3b&quot;&gt;Adding Attachments to Events&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-3c&quot;&gt;Event Check Mark and To Do List&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-3d&quot;&gt;Proposing / Approving Events&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-3e&quot;&gt;Private Events&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-3f&quot;&gt;Using the Calendar to Book Events&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-3g&quot;&gt;Sending Event Reminder Messages&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-3h&quot;&gt;Sidebar with Upcoming Events or Todo List&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-3i&quot;&gt;Color-coding of Events and Subcategories&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-3j&quot;&gt;Importing Data of Previous LuxCal Versions&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-4&quot;&gt;LuxCal Toolbox&lt;/a&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-4a&quot;&gt;PHP Installation Details&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-4b&quot;&gt;General Toolbox - lctools.php&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-4c&quot;&gt;SMTP Mail Test Utility - smtptest.php&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-4d&quot;&gt;Database administration with phpLiteAdmin&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-5&quot;&gt;Calendar Settings - Description&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;br&gt;

&lt;a id=&quot;lbl-1&quot;&gt;&lt;/a&gt;&lt;h4&gt;1. Introduction&lt;/h4&gt;
&lt;p&gt;After the LuxCal calendar has been installed or upgraded, using the &lt;kbd&gt;installation_guide.html&lt;/kbd&gt;, 
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 suitable way.&lt;/p&gt;
&lt;p&gt;A good place to start in managing your calendar is to . . .&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;customize the calendar settings via the admin's Settings page&lt;/li&gt;
&lt;li&gt;create a number of categories for your events&lt;/li&gt; 
&lt;li&gt;edit the default user groups created during the installation or add new user groups&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;To familiarize yourself with the LuxCal calendar's capabilities, it is important to take note of the 
	other function and possibilities described in this section.&lt;/p&gt;

&lt;a id=&quot;lbl-2&quot;&gt;&lt;/a&gt;&lt;h4&gt;2. Managing the Calendar&lt;/h4&gt;
&lt;p&gt;Managing the LuxCal calendar is the responsibility of the calendar administrator, who has all calendar
		access rights.&lt;/p&gt;
&lt;p&gt;Managing event categories, user profiles and user groups can be done by either the calendar administrator, 
		or users with 'manager' rights.&lt;/p&gt;
&lt;p&gt;In order to change configuration settings, or use other administration functions, 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 the password you specified during the installation, and log in. On the right side of the 
		navigation bar the administration drop down menu will appear.&lt;/p&gt;

&lt;a id=&quot;lbl-2a&quot;&gt;&lt;/a&gt;&lt;h5&gt;a. Calendar Settings&lt;/h5&gt;
&lt;p&gt;The Settings page in the administration menu on the navigation bar can be used to easily change the
		calendar's configuration settings which are stored in the &lt;kbd&gt;settings&lt;/kbd&gt; 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.&lt;/p&gt;
&lt;p&gt;IMPORTANT: Currently the TimeZone is set to &amp;quot;Europe/Amsterdam&amp;quot;. If you are in a different time
		zone, change the TimeZone to your local time zone. See the
		&lt;a href=&quot;http://us3.php.net/manual/en/timezones.php&quot; target=&quot;_blank&quot;&gt;PHP Supported Time Zones&lt;/a&gt; for 
		possible values.&lt;/p&gt;

&lt;a id=&quot;lbl-2b&quot;&gt;&lt;/a&gt;&lt;h5&gt;b. Event Categories&lt;/h5&gt;
&lt;p&gt;It is recommended 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.&lt;/p&gt;
&lt;p&gt;The initial installation has only one category which is named &quot;no cat&quot;. To manage categories, select
		Categories in the administration 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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The field &quot;Repeat&quot; can be used to pre-define recurring events. A category &quot;birthday&quot; or &quot;anniversary&quot; 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.&lt;/p&gt;
&lt;p&gt;If the &quot;No overlap allowed&quot; check box is checked, events within this category may not overlap. If a user 
		tries to create an event in this category which overlaps with an existing event, an error message 
		with the specified error text will be displayed. This feature can be used when you want to use this 
		event category for booking events. For details on how to create a booking calendar, see Advanced 
		Functions hereafter.&lt;/p&gt;
&lt;p&gt;With the field &quot;Default time period&quot; you can specify the default duration of an event in case the user 
		specifies a start time without an end time. This can be useful for instance when using this category 
		for &quot;booking&quot; events which may not overlap (see above).&lt;/p&gt;
&lt;p&gt;When the checkbox &quot;Day color&quot; has been checked, the full day cell in the calendar views will get the 
		background color specified below. This may be useful to clearly mark for example holidays, birthdays, 
		or other special days.&lt;/p&gt;
&lt;p&gt;When activated, the field &quot;Event needs approval&quot; will activate the propose/approve feature for events in 
		this category. For a detailed description, see &quot;Proposing / Approving Events&quot; in section 3 below.&lt;/p&gt;
&lt;p&gt;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 &quot;completed&quot;. Events in this 
		category will appear in the ToDo list, which can be opened from the calendars navigation bar.&lt;/p&gt;
&lt;p&gt;The fields &quot;Text color&quot; and &quot;Background&quot; define the colors used to display events in the calendar assigned
		to this category.&lt;/p&gt;
&lt;p&gt;The field &quot;Sequence&quot; defines the location of this event category in the category drop-down menus.&lt;/p&gt;

&lt;a id=&quot;lbl-2c&quot;&gt;&lt;/a&gt;&lt;h5&gt;c. Calendar User Groups&lt;/h5&gt;
&lt;p&gt;The initial installation has a User Group defined for each possible type of user permission. Each 
		calendar user is assigned to one of the existing user groups. User groups can be edited, and new user 
		groups can be added, by users with administrator or manager rights.
		Adding and editing user groups is done via the Administration drop-down menu in the navigation bar. 
		A user group defines the user access rights of the users assigned to this group and the event 
		categories available to the users in the group. Furthermore a number of check boxes are available to 
		specify whether users in this group may upload event attachements and may enter repeating events, 
		multi-day events and private events. 
		Via a color palette a background color can be selected for each group. On the admin's Settings 
		page the administrator can specify whether calendar events should be displayed with the color of the 
		event category or the color of the group to which the creator of the event belongs.&lt;/p&gt;
&lt;p&gt;Possible access rights:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;None&lt;/p&gt;
&lt;p&gt;The user - normally the Public User - has no access rights and has to log in to use the calendar.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;View&lt;/p&gt;
&lt;p&gt;The user can view the calendar, but has has no rights to add or edit events.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Post/Edit Own&lt;/p&gt;
&lt;p&gt;The user can view the calendar and can add events. The user can only edit his/her own events.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Post/Edit All&lt;/p&gt;
&lt;p&gt;The user can view the calendar and can add events. The user can edit his/her own events as well as  
events of other users.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Post/Edit + Manager&lt;/p&gt;
&lt;p&gt;A user with 'Manager' rights can do the same as a user with 'Post All' rights and in addition:&lt;/p&gt;
&lt;p&gt;- Can change the owner of an event (in the Event window). So for instance a manager can create events for 
other users by creating an event and then assign an owner to it.&lt;/p&gt;
&lt;p&gt;- Can approve events created by other users. See Advanced Functions hereafter.&lt;/p&gt;
&lt;p&gt;- Has access, via the Administration drop-down menu, to the Categories, Users and User Groups pages and 
		consequently can manage event categories, user profiles and user groups.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Administrator&lt;/p&gt;
&lt;p&gt;The administrator has all right described above and in addition has access to all technical, user-interface 
and database related settings and functions.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
		
&lt;a id=&quot;lbl-2d&quot;&gt;&lt;/a&gt;&lt;h5&gt;d. Calendar Users&lt;/h5&gt;
&lt;p&gt;Via the Administration drop-down menu user(s) with manager rights or the calendar administrator can 
		add and edit user profiles. Per user the name, e-mail address, password and the user group can be 
		specified. As described above, the group determines the access rights and the available event categories. 
		It is important to specify a valid email address for the user to be able to receive email notifications 
		of due dates of events. When defined users log in to the calendar they can specify their default user 
		interface language. Thereafter, when a user logs in, the user-interface will be displayed in the 
		specified language.&lt;/p&gt;
&lt;p&gt;The initial installation has two users defined. One is the Public Access user, who initially is assigned 
		to the &quot;Read access&quot; user group and the other is the calendar administrator, who is assigned to the 
		&quot;Admin&quot; user group and has all access rights.&lt;/p&gt;
&lt;p&gt;Unless the calendar administrator has given &amp;quot;View&amp;quot; access (via the &quot;Read access&quot; user group) 
		to Public Access users, users must log in to use the calendar using their name or email address and 
		password. Depending on the group to which a user has been assigned, a user can have different access 
		rights.&lt;/p&gt;
&lt;p&gt;If the administrator has enabled user self-registration on the Settings page, users can register
		themselves via the Login page. Self-registered users will automatically be assigned to the user group 
		for self registered users specified by the administrator on the admin's Settings page and consequently 
		will have the access rights specified for that user group.&lt;/p&gt;

&lt;a id=&quot;lbl-2e&quot;&gt;&lt;/a&gt;&lt;h5&gt;e. Calendar Database&lt;/h5&gt;
&lt;p&gt;The Database option in the administration drop-down menu allows the calendar administrator to start the 
following functions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Compact database&lt;/p&gt;
&lt;p&gt;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. This action can also be done automatically if a cron job has been created and on the admin's 
Settings page, under Periodic Functions, the number of Event expiry days has been specified.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Backup database&lt;/p&gt;
&lt;p&gt;This function creates a backup of the structure and contents of all database tables in the &lt;kbd&gt;files/&lt;/kbd&gt;
directory. The file name is &lt;kbd&gt;cal-dump-yyyymmdd-hhmmss.sql&lt;/kbd&gt; (where 'yyyymmdd' = year, month, and
day, and hhmmss = hour, minutes and seconds). The file type is &lt;kbd&gt;.sql&lt;/kbd&gt; and the created file can
be downloaded and used to re-create the database tables structure and contents, for instance by using the 
Restore database function (see hereafter) or by importing the file a database management tool which is 
available on the server of most web hosts.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Restore database&lt;/p&gt;
&lt;p&gt;This function uploads the database backup file specified by the administartor and uses this file to 
recreate the calendar database. The database backup file must be of the same calendar version as the 
currently running calendar. The restore function accepts back up files from the MySQL version as well as 
the SQLite version of the calendar, as long as the version number matches the current calendar.&lt;/p&gt;
&lt;p&gt; The database will be recreated from scratch, which means that, before recreating a table, the existing 
table and its data will be deleted. For each recreated table the corresponding records from the back-up file 
will be restored to the newly created table.&lt;/p&gt;
&lt;p&gt;To restore backup files of older LuxCal versions the &quot;lctool.php&quot; file from the toolbox should be uploaded
to the calendar root and launched via the browser.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;delete / undelete events&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;a id=&quot;lbl-2f&quot;&gt;&lt;/a&gt;&lt;h5&gt;f. CSV File Import&lt;/h5&gt;
&lt;p&gt;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 administration drop-down menu in the 
		navigation bar.&lt;/p&gt;
&lt;p&gt;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).&lt;/p&gt;
&lt;p&gt;Sample CSV files - with different date/time formats - can be found in the &lt;kbd&gt;files/&lt;/kbd&gt; directory of the
		LuxCal Calendar installation and have the file extension &quot;.csv&quot;.&lt;/p&gt;

&lt;a id=&quot;lbl-2g&quot;&gt;&lt;/a&gt;&lt;h5&gt;g. iCal File Import/Export&lt;/h5&gt;
&lt;p&gt;Events from iCalendar files can be imported into the LuxCal calendar. The content of the iCal file to be
		imported must meet the [&lt;u&gt;&lt;a href='http://tools.ietf.org/html/rfc5545' target='_blank'&gt;RFC5545
		standard&lt;/a&gt;&lt;/u&gt;] 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 administration drop-down menu in the
		navigation bar.&lt;/p&gt;
		&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Various sample iCal files can be found in the &lt;kbd&gt;files/&lt;/kbd&gt; directory of the LuxCal Calendar
		installation and have the file extension &quot;.ics&quot;.&lt;/p&gt;

&lt;a id=&quot;lbl-2h&quot;&gt;&lt;/a&gt;&lt;h5&gt;h. User Interface Styling&lt;/h5&gt;
&lt;p&gt;The UI Styling page in the administration drop-down menu allows the calendar administrator to tailor the 
		styles (text and background colors, fonts family and sizes, etc.) of most elements of the calendar's user 
		interface.&lt;/p&gt;
&lt;p&gt;The Styling page opens in a separate window, which makes it possible to preview style changes in the 
		calendar pages, by browsing the calendar, while the Styling page remains open.&lt;/p&gt;
&lt;div&gt;Buttons and drop-down menu at the top of the page:&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Preview Theme&lt;/b&gt;: When pressed, the currently displayed theme will be temporary activated for the 
		calendar and a Stop Preview button will be displayed. The calendar can now be browsed with these styles, 
		until the Stop Preview button is selected.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Save Theme&lt;/b&gt;: The displayed theme will be saved to the database and from now on this theme will be 
		used by this calendar. The previous theme in the database will be overwritten. When the theme is saved 
		for the first time since the Styling page is opened, prior to overwriting the theme in the database, 
		an automatic backup will be stored in a file in the css folder; the file extension will be &quot;abak&quot;.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Backup Theme&lt;/b&gt;: The theme from the database will be stored in a file in the css folder. The name 
		given to the file will be shown in the information line at the top of the window. The file extension 
		will be &quot;mbak&quot;.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Restore Theme&lt;/b&gt;: This drop down menu will show the LuxCal default theme and all backup files 
		(&quot;.abak&quot; and &quot;.mbak&quot;) in the css folder. When an entry is selected the theme from the selected file 
		will be displayed in the Styling page. This theme can then be previewed, modified and saved.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Close Window&lt;/b&gt;: Close the Styling window. If there are unsaved changes, a warning will be 
		displayed.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Theme title&lt;/b&gt;: Optional theme title which will be stored along with the styles in the database 
		and in backup files. If left blank, this field will default to the calendar title.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Since calendar styles are saved in the calendar database, in case of multiple calendars, each calendar 
has its own styles.&lt;/p&gt;

&lt;a id=&quot;lbl-2i&quot;&gt;&lt;/a&gt;&lt;h5&gt;i. Adding Your Logo to the Calendar&lt;/h5&gt;
&lt;p&gt;On the administrator's Settings page, in the section General, you can specify a path and name of a logo 
	image. Once the image has been uploaded to the server and the path and name have been specified on the 
	Settings page, the logo will be displayed in the left upper corner of the calendar pages. The buttons on 
	the navigation bar will shift right the required number of pixels to make place for the logo. The logo 
	will also be displayed in the left upper corner of possible email messages sent by the calendar&lt;/p&gt;
&lt;p&gt;If on the Settings page, in the section General, also a link to a parent page has been specified, then 
	the logo will become the hyperlink to the parent page.&lt;/p&gt;
&lt;p&gt;The maximum logo image width and/or height is 70 x 70 pixels.&lt;/p&gt;

		
&lt;a id=&quot;lbl-3&quot;&gt;&lt;/a&gt;&lt;h4&gt;3. Advanced Functions&lt;/h4&gt;
&lt;p&gt;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 users with manager rights or by 
	the calendar administrator.&lt;/p&gt;
&lt;p&gt; These advanced functions are described hereafter.&lt;/p&gt;

&lt;a id=&quot;lbl-3a&quot;&gt;&lt;/a&gt;&lt;h5&gt;a. Changing the Lay-out of Events&lt;/h5&gt;
&lt;p&gt;On the Settings page, the admin can specify which fields of the event body are in use and in which order 
they will be displayed in the various views. This can be done via the 'Event template' under &lt;kbd&gt;Events&lt;/kbd&gt; 
by specifying a sequence of numbers in the range 1 - 7, where each number represents an event field.&lt;/p&gt;
&lt;p&gt;Possible fields in the event body:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;1: Venue field&lt;/li&gt;
&lt;li&gt;2: Event category field&lt;/li&gt;
&lt;li&gt;3: Description field&lt;/li&gt;
&lt;li&gt;4: Extra field 1&lt;/li&gt;
&lt;li&gt;5: Extra field 2&lt;/li&gt;
&lt;li&gt;6: Email notification data (only if an email notification has been requested&lt;/li&gt;
&lt;li&gt;7: Date/time added/edited and the associated users&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Fields (numbers) which are not specified, will not be visible in the calendar views. Extra fields 1 and 2 
are extra fields for which the admin can specify a dedicated label on the same Settings page under Events. 
If the these fields have been specified, the field label as well as the content will be displayed. In the 
calendar views active fields which are empty will not be shown. The Event window will of course always 
show all active fields, including the empty fields.&lt;/p&gt;
&lt;p&gt;Example: Event template &quot;43126&quot;, with the label for Extra field 1 set to &quot;Department&quot;, will for instance result 
in the following event body lay-out (explanation between brackets):&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;i&gt;Department: Sales&lt;/i&gt; (extra field 1 with label &quot;Department&quot;)&lt;br&gt;
&amp;nbsp;&lt;i&gt;Emmett Brown will be working on-site for the BTTF project.&lt;/i&gt; (description)&lt;br&gt;
&amp;nbsp;&lt;i&gt;Venue: Hill Valley&lt;/i&gt; (venue)&lt;br&gt;
&amp;nbsp;&lt;i&gt;Category: Absent&lt;/i&gt; (event category)&lt;br&gt;
&amp;nbsp;(&lt;i&gt;Notify: 4 day(s)&lt;/i&gt;) (This line is not displayed, because no email notification was requested)
&lt;/p&gt;
&lt;p&gt;On the Settings page, the fields 'Event fields - general hover box' under Events, 'Event fields - mini 
calendar hover box' under Mini Calendar and 'Event fields - sidebar hover box' under Stand-Alone Sidebar 
can be used by the admin to specify the event fields to be displayed in the various hover boxes. The 
sequence of the fields in the hover boxes depend on the event template described before.&lt;/p&gt;

&lt;a id=&quot;lbl-3b&quot;&gt;&lt;/a&gt;&lt;h5&gt;b. Adding Attachments to Events&lt;/h5&gt;
&lt;p&gt;Users belonging to a User group for which File Upload is enabled, can add pdf, image and video attachments 
to events. Adding and removing attachments to events can be done in the Event window when adding or 
editing events. The actual attachment file is stored in the calendar's subfolder &quot;attachments&quot; and the 
link from the event to the file is saved in the event record in the calendar database. 
Uploaded attachments will be shown as hyperlinks in the event data in the various calendar views. When 
clicking these hyperlinks, the attachment will open in a new window.&lt;/p&gt;
&lt;p&gt;When an attachment file is stored in the attachment folder, its file name is prefixed with the 
current date and time. E.g 20180127203557Agenda.pdf.&lt;/p&gt;
&lt;p&gt;On the administrators Settings page, under Views, in the Event templates it can be specified if and 
at what position within the event data hyperlinks to attachments should be displayed in the various 
calendar views.&lt;/p&gt;

&lt;a id=&quot;lbl-3c&quot;&gt;&lt;/a&gt;&lt;h5&gt;c. Event Check Mark and To Do List&lt;/h5&gt;
&lt;p&gt;On the admin's Categories page, when adding/editing an event category, if you select &quot;Check mark&quot; 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 &quot;manager&quot; rights this 
check mark is a hyperlink and, when clicked, will result in checking/unchecking the check mark. This 
feature can be used for instance to mark an event as &quot;complete&quot; or &quot;done&quot;. Events with a check mark will 
show up in the To Do list, which - when enabled by the administrator - can be selected from the 
calendar's navigation bar.&lt;/p&gt;

&lt;a id=&quot;lbl-3d&quot;&gt;&lt;/a&gt;&lt;h5&gt;d. Proposing / Approving Events&lt;/h5&gt;
&lt;p&gt;On the admin's Categories page, when adding/editing an event category, if you select &quot;Events need 
approval&quot;, users with post rights can - in this category - create events which are not visible to other 
users until a user with at least &quot;manager&quot; 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 &quot;manager&quot; 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 &quot;proposing&quot; and &quot;approving&quot;, 
you could for example also consider the words &quot;booking&quot; and &quot;confirming&quot;.&lt;/p&gt;

&lt;a id=&quot;lbl-3e&quot;&gt;&lt;/a&gt;&lt;h5&gt;e. Private Events&lt;/h5&gt;
&lt;p&gt;When adding/editing events, if the &quot;Private&quot; check box is checked, the event will only be visible 
to the user who created the event and to the administrator. For obvious reasons private events can 
only be created by logged in users.&lt;/p&gt;
&lt;p&gt;On the Settings page, under Events, the administrator can set &quot;posting of private events to 
disabled, enabled, default and always with the following meaning:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;disabled: The &quot;Private&quot; check box will not be visible in the Event window, so no private events can
 be created.&lt;/li&gt;
&lt;li&gt;enabled: The &quot;Private&quot; check box will be visible in the Event window and will initially be 
unchecked.&lt;/li&gt;
&lt;li&gt;default: The &quot;Private&quot; check box will be visible in the Event window and will initially be 
checked.&lt;/li&gt;
&lt;li&gt;always: The &quot;Private&quot; check box will not be visible in the Event window and all created events 
will be private.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The creation of private events can also be enabled/disabled per individual user group (see 
Calendar User Groups above). If for a calendar user group private events have been disabled, this 
will overrule the &quot;Posting of private events = always&quot; setting on the admin's Settings page.&lt;/p&gt;

&lt;a id=&quot;lbl-3f&quot;&gt;&lt;/a&gt;&lt;h5&gt;f. Using the Calendar to Book Events&lt;/h5&gt;
&lt;p&gt;One or several event categories of the calendar can be set up for booking events with event 
overlap checking. The idea is to let users create events which may not overlap with already 
existing events in the same event category. If a user tries to create an event which overlaps, 
an error message will be displayed. Single-day and multi-day events are checked. Recurring events 
and private events are not checked.&lt;/p&gt;
&lt;p&gt;How to set up a booking system, is illustrated by the following example.&lt;/p&gt;
&lt;h6&gt;Billiard table booking example:&lt;/h6&gt;
&lt;p&gt;In this example we will set up a booking system for three billiard tables.&lt;/p&gt;
&lt;p&gt;Create a new event category and give it the name &quot;Billiard table 1&quot;, uncheck the &quot;No overlap 
allowed&quot; check box, and optionally set the error text, displayed in case of creating an event 
which overlaps with an existing event, to &quot;Billiard table 1 in use, choose an other time or 
table&quot;. If desired, the &quot;Default time period&quot; can be specified, which - when creating / editing 
an event - will automatically be added to the start time of an event if no end time is specifies.
Give this category a color (text/background) which belongs to table 1.
&lt;br&gt;
Create two more categories for the other two billiard tables in a similar way but with a 
different name, error text and color.
&lt;br&gt;
Now a user group can be created, for instance with the name &quot;Billiards&quot; for those users who can 
book one of the three billiard tables. For this user group the three categories created for the 
billiard tables should be selected and the check boxes &quot;May post repeating events&quot; and &quot;May post 
private events&quot; should be unchecked. Because the billiard tables can only be booked for a 
limited time, the check box &quot;May post multi-day events&quot; can also be unchecked. So now if a user 
in this group add/edits an event, the Event window will be simplified and will contain no 
&quot;Private&quot; check box, no &quot;End date&quot; field and no &quot;Repeat&quot; feature.
&lt;br&gt;
On the Settings page, under User Accounts, &quot;Self registration&quot; can be enabled and the &quot;Self 
registration user group&quot; should be set to the user group &quot;Billiards&quot; created in the step above.
&lt;/p&gt;
&lt;p&gt;In the above example, users can register themselves and will be part of the &quot;billiard&quot; user 
group; they will have access to the three categories &quot;Billiard table 1&quot;, &quot;Billiard table 2&quot; and 
&quot;Billiard table 3&quot; and will only be able to book a billiard table which is free.&lt;/p&gt;
&lt;p&gt;Note: For a booking system for chalets for instance, in the user group the check box &quot;May post 
multi-day events&quot; should remain checked, to allow for booking the chalets for several days.&lt;/p&gt;

&lt;a id=&quot;lbl-3g&quot;&gt;&lt;/a&gt;&lt;h5&gt;g. Sending Event Reminder Messages&lt;/h5&gt;
&lt;p&gt;The calendar has an email event reminder service and an SMS event reminder service. For the SMS 
reminder service a subscription with a mail-to-SMS provider will be needed. The settings related 
to these services can be set on the administrator's Settings page in the Reminders section. Both 
services can be enabled/disabled individually.&lt;/p&gt;
&lt;p&gt;To be able to send reminders a specified number of days before the start of an event, a cronjob 
must be defined, which starts the script lcalcron.php in the calendar root daily at approx. 2am&lt;/p&gt;
&lt;p&gt;Users belonging to a user group with edit rights, can ask to send email reminders when adding or 
editing events. Users can also ask to send SMS reminders, provided the user group the user belongs 
to has the rights to send SMS reminders.&lt;/p&gt;
&lt;p&gt;A user can ask the calendar to send an email or SMS reminder, directly or a number of days before 
the start of an event. If the user selects to send an email and/or an SMS directly, the email and/or 
SMS is sent as soon as the event is saved. If the user ask to send an email and/or SMS x days 
before the start of the event, an email and/or SMS will be sent x days before the start of the 
event and another one will be sent on the day of the event. If the user specifies to send an email 
and/or SMS 0 (zero) days before the start of the event, an email and/or SMS will be sent on the 
day of the start of the event only. For recurring events (e.g. birthdays) an email/SMS notification 
will be sent to the recipients the selected number of days before each occurrence of the event.&lt;/p&gt;
&lt;p&gt;Email as well as SMS reminders are sent to the recipients specified in the recipients list. 
Recipients can be specified by means of an email address or a mobile phone number. 
For email reminders to a recipient with a mobile phone number, the calendar will use the phone 
number to search the user accounts in the database for a matching email address. If not found, 
no email reminder will be sent. For SMS reminders to a recipient with an email address, the 
calendar will use the email address to search the user accounts in the database for a matching 
phone number. If not found, no SMS reminder will be sent.&lt;br&gt;If the email address or the phone 
number is followed by a $-sign, the calendar will not look for a matching phone number or mail 
address.&lt;/p&gt;
&lt;p&gt;Scheduled reminders and/or SMSes are always sent early in the morning, when the cronjob runs.&lt;/p&gt;

&lt;a id=&quot;lbl-3h&quot;&gt;&lt;/a&gt;&lt;h5&gt;h. Sidebar with Upcoming Events or Todo List&lt;/h5&gt;
&lt;p&gt;A stand-alone sidebar with upcoming events or a Todo list (see above) can be integrated in your 
web page. An advantage of the sidebar, compared to embedding the calendar in an html iframe, is 
that the sidebar is displayed in a &amp;lt;div&amp;gt; container and can be freely styled to match the style 
of your web page. A second advantage is that the hoverbox with many event details is not clipped 
by iframe boundaries.
Further detail on how to add one or more stand-alone sidebars to your web page can be found in the 
&lt;kbd&gt;installation_guide.html&lt;/kbd&gt;. Examples of what a sidebar can look like can be found on the 
LuxSoft &lt;a href=&quot;http://www.luxsoft.eu/index.php?pge=demo&quot; target=&quot;_blank&quot;&gt;&lt;b&gt;&lt;i&gt;Demo page&lt;/i&gt;&lt;/b&gt;&lt;/a&gt;.
&lt;/p&gt;

&lt;a id=&quot;lbl-3i&quot;&gt;&lt;/a&gt;&lt;h5&gt;i. Color-coding of Events and Subcategories&lt;/h5&gt;
&lt;p&gt;When defining user groups, for each group a background color can be specified and when defining event 
categories, a text color and a background color can be specified for each category. On the admin's 
Settings page, under Events, the admin can select whether on the calendar pages the color of the event 
titles in the various views should correspond to the color of the user group to which the originator 
of the event belongs or to the event category to which the event belongs.&lt;/p&gt;
&lt;p&gt;When adding/editing event categories a check box &quot;Day color&quot; can be checked. If this check box is 
checked, in the various calendar views, if an event in this category is displayed for a certain day, 
the background of the whole day will take the color of the event. This can for instance be useful to 
make special events, like holidays or birthdays, more visible.&lt;/p&gt;
&lt;p&gt;On the categories page, for each event category up to four subcategories can be specified. Each 
subcategory has a name and optionally the text color and background color can be specified. If one or 
more subcategories have been specified, in the event add/edit window a drop-down menu will be displayed 
from which the user can select a subcategory. When the subcategory has been selected, in all calendar 
views the event concerned will take the text and background color of the selected subcategory and the 
subcategory name will be added to the event details. When specifying subcategories on the categories 
page, the text/background color fields can also be left blank; in this case the events in this category 
will take the normal category colors. It may be useful for instance to specify a subcategory &quot;None&quot; 
without colors, which - when selected in the event add/edit window - will behave as if no subcategory 
has been selected.&lt;/p&gt;

&lt;a id=&quot;lbl-3j&quot;&gt;&lt;/a&gt;&lt;h5&gt;j. Importing Data of Previous LuxCal Versions&lt;/h5&gt;
&lt;p&gt;There are different ways to import calendar data of previous LuxCal versions, back to LuxCal version 
2.7.2. If you want to import data of a LuxCal version less than 2.7.2, read the Upgrade Instructions 
in the Release Notes (release_notes_xxx.html, where xxx = the LuxCal version).&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Upgrading the calendar&lt;/li&gt;
&lt;p&gt;When upgrading the calendar to a newer version, following the upgrade steps in the Release Notes, 
the calendar(s) in the database will automatically be upgraded to the new Calendar version.&lt;/p&gt;
&lt;li&gt;Importing data via the LuxCal Toolbox (see section 4 below)&lt;/li&gt;
&lt;p&gt;The lctools.php file from the calendar toolbox can be uploaded to the calendar root directory and 
launched via the browser. Via these tools a database back up files of a previous LuxCal version (as 
of LuxCal 2.7.2) can be imported. At the end of the import process, the database schema will be 
upgraded to the current calendar version without loss of data. Thereafter the calendar can be started.&lt;/p&gt;
&lt;li&gt;Importing data via an external tool&lt;/li&gt;
&lt;p&gt;You can use an external tool on your server, e.g. phpMyAdmin or phpLiteAdmin, to import database 
back up files of previous LuxCal versions directly into the database. Before starting the calendar, 
the upgradexxx.php file should be uploaded to the calendar root folder on your server and be launched 
via your browser. Thereafter the calendar can be started.&lt;/p&gt;
&lt;/ul&gt;
&lt;p&gt;When in doubt if the calendar data in your database is up to date, you can at any time upload the 
upgradexxx.php file to the calendar root folder on your server and launch it. The script will verify, 
and if necessary upgrade, the database schema of your calendar(s).&lt;/p&gt;

&lt;a id=&quot;lbl-4&quot;&gt;&lt;/a&gt;&lt;h4&gt;4. LuxCal Toolbox&lt;/h4&gt;
&lt;p&gt;The toolbox contains several tools and utilities, which can help you set up and manage your calendar. 
Below you will find a short description of each of the tools / utilities.&lt;/p&gt;

&lt;a id=&quot;lbl-4a&quot;&gt;&lt;/a&gt;&lt;h5&gt;4a. PHP Installation Details&lt;/h5&gt;
&lt;p&gt;On the admin's Settings page, in the General section, under Versions, just after the PHP version, 
there is a &quot;Show info&quot; link. Clicking this link will display all details of the PHP installation on 
your server in a new window. The PHP installation details can be useful when a PHP related problem is 
encountered.&lt;/p&gt;

&lt;a id=&quot;lbl-4b&quot;&gt;&lt;/a&gt;&lt;h5&gt;4b. General Toolbox - lctools.php&lt;/h5&gt;
&lt;p&gt;The lctool.php file should be uploaded to the calendar's root directory and launched via your browser.
This toolbox is particularly useful when managing multiple calendars. It contains tools to perform 
the following actions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Test the configuration&lt;/li&gt;
&lt;li&gt;Create new calendars&lt;/li&gt;
&lt;li&gt;Set the default calendar&lt;/li&gt;
&lt;li&gt;Delete calendars&lt;/li&gt;
&lt;li&gt;Replicate data and/or settings from file&lt;/li&gt;
&lt;li&gt;Back up calendars&lt;/li&gt;
&lt;li&gt;Download a backup file from the 'files' folder&lt;/li&gt;
&lt;li&gt;Import a calendar backup file of a previous LuxCal version&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Most actions should be used with caution. Always carefully read the displayed instruction!&lt;/p&gt;

&lt;a id=&quot;lbl-4c&quot;&gt;&lt;/a&gt;&lt;h5&gt;4c. SMTP Mail Test Utility - smtptest.php&lt;/h5&gt;
&lt;p&gt;When you prefer to use SMTP mail, rather than PHP mail, for your email reminders and cron job 
reports, you can select SMTP mail on the admin's Settings page of your calendar. Before doing so you 
can use the SMTP Mail Test Utility &quot;smtptest.php&quot;, in the smtpmail folder, to test your SMTP mail and 
its parameters. The smtptest.php file should be uploaded to the calendar's root directory on your 
server. Before launching it via your browser, you should start the calendar and specify the SMTP 
parameters on the admin's Settings page, under Reminders.&lt;/p&gt;

&lt;a id=&quot;lbl-4d&quot;&gt;&lt;/a&gt;&lt;h5&gt;4d. Database Administration with phpLiteAdmin&lt;/h5&gt;
&lt;p&gt;In the phpliteadmin folder you will find phpLiteAdmin, an easy to use web-based SQLite database admin 
tool written in PHP. details on how to use this free tool can be found 
&lt;a href=&quot;https://code.google.com/p/phpliteadmin/&quot; target=&quot;_blank&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In the associated phpliteadmin.config.php file, you should at least set the following variables:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;$password - password to gain access&lt;/li&gt;
&lt;li&gt;$directory - directory of the database file(s) (default for LuxCal: &quot;../db/&quot;)&lt;/li&gt;
&lt;li&gt;$allowed_extensions - array with allowed database file extensions (for LuxCal: &quot;.cdb&quot;)&lt;/li&gt;
&lt;/ul&gt;

&lt;a id=&quot;lbl-5&quot;&gt;&lt;/a&gt;&lt;h4&gt;5. Calendar Settings - Description&lt;/h4&gt;
&lt;p&gt;The calendar settings which are automatically generated during the installation process are stored in
the &lt;kbd&gt;settings&lt;/kbd&gt; table of the database. All settings can be changed by the calendar administrator 
via the Settings page in the administration drop down menu on the navigation bar at the top right corner 
of the screen.&lt;/p&gt;
&lt;p&gt;For those interested in technical details: The following are explanations of the PHP variables stored
in the &lt;kbd&gt;settings&lt;/kbd&gt; table of the database:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;calendarTitle&lt;/kbd&gt;: The title of the LuxCal calendar that is displayed in the header
		of the various calendar views.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;calendarUrl&lt;/kbd&gt;: The full URL address of the calendar, used for notification purposes, 
		E.g. http://www.mysite.xxx/calendar/index.php.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;backLinkUrl&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;timeZone&lt;/kbd&gt;: Your local time zone. See the &lt;a href=&quot;http://us3.php.net/manual/en/timezones.php&quot; target=&quot;_blank&quot;&gt;
		PHP Supported Time Zones&lt;/a&gt; for possible values. Setting the correct time zone is important for the
		&quot;today&quot; indication in the various views and when the &quot;notification&quot; feature is used.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;notifChange&lt;/kbd&gt;: If checked, when a user adds, edits or deletes an event, an email 
		notification message will be sent to the specified recipient email addresses.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;recipList&lt;/kbd&gt;: Recipient email address list. The recipient list can contain a semicolon 
		separated list of mail addresses and/or names of files with recipient mail addresses. Files with 
		email addresses with one email address per line should be located in the folder 'reciplists'. 
		When omitted, the default file name extension of a file with email addresses is .txt&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;rssFeed&lt;/kbd&gt;: If enabled: RSS feed links will be displayed in the calendar footer and will
		be included in the HTML head section.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;logWarnings&lt;/kbd&gt;: Log calendar warning messages (0: no, 1: yes).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;logNotices&lt;/kbd&gt;: Log calendar notice messages (0: no, 1: yes).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;navButText&lt;/kbd&gt;: If enabled: The buttons on the navigation bar will be displayed with text&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;navToapList&lt;/kbd&gt;: If enabled: A To approve list button will be displayed on the navigation 
		bar for users with at least manager rights. The button can be used to display the list of events 
		that need approval.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;navTodoList&lt;/kbd&gt;: If enabled: A Todo list button will be displayed on the navigation bar, 
		which can be used to display the Todo list.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;navUpcoList&lt;/kbd&gt;: If enabled: An Upcoming button will be displayed on the navigation bar, 
		which can be used to display the Upcoming Events list.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;viewMenu&lt;/kbd&gt;: Specifies whether the view menu is displayed in the calendar's options 
		panel. Possible values: 0 = disabled, 1 = enabled.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;groupMenu&lt;/kbd&gt;: Specifies whether the user group filter is displayed in the calendar's 
		options panel. Possible values: 0 = disabled, 1 = enabled.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;userMenu&lt;/kbd&gt;: Specifies whether the user filter is displayed in the calendar's options
		panel. Possible values: 0 = disabled, 1 = enabled.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;catMenu&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;langMenu&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;viewsPublic&lt;/kbd&gt;: Specifies which calendar views are available to the public users. The 
		available views are specified by means of a comma-separated list with view numbers.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;viewsLogged&lt;/kbd&gt;: Specifies which calendar views are available to the logged in users. The 
		available views are specified by means of a comma-separated list with view numbers.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;viewButsPub&lt;/kbd&gt;: View buttons to be displayed on the navigation bar for public users 
		(1:year, 2:month, 3:work month, 4:week, 5:work week 6:day, 7:upcoming, 8:changes, 9:matrix)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;viewButsLog&lt;/kbd&gt;: View buttons to be displayed on the navigation bar for logged in users 
		(1:year, 2:month, 3:work month, 4:week, 5:work week 6:day, 7:upcoming, 8:changes, 9:matrix)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;defViewPub&lt;/kbd&gt;: The initial calendar view for public users 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, 8: Changes and 9: matrix.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;defViewLog&lt;/kbd&gt;: The initial calendar view for logged in users users 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, 8: Changes and 9: matrix.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;language&lt;/kbd&gt;: The default user interface language. Only installed languages can be
		specified.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;ownerTitle&lt;/kbd&gt;: When enabled, the event owner's name will be shown in front of the event 
		title in the various calendar views (0:disabled 1:enabled).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;privEvents&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;aldDefault&lt;/kbd&gt;: When selected, all-day event will be the default in the Event window 
		when adding new events (0:no 1:yes).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;details4All&lt;/kbd&gt;: If disabled: event details will only be visible to the owner of the 
		event and to users with 'post all' rights. If enabled: event details will be visible to the owner 
		of the event and to all other users. If &quot;for logged-in users&quot;: Event details will only be visible 
		to logged-in users.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;evtDelButton&lt;/kbd&gt;: If disabled: the Delete button in the Event window will not be visible.
		If enabled: the Delete button in the Event window will be visible, so all users with sufficient 
		rights can delete events. If manager: the Delete button in the Event window will only be visible
		to users with &quot;manager&quot; rights.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;eventColor&lt;/kbd&gt;: Specifies whether events should be displayed with the event owner color,
		or with the event category color (0: owner color, 1: category color)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;xField1Label / xField2Label&lt;/kbd&gt;: The name of two optional free format text fields, which 
		can be added to the Event window form and in all calendar views and pages. The specified name can 
		be max. 15 characters long. E.g. 'Email address', 'Website', 'Phone number'.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;xField1Public / xField2Public&lt;/kbd&gt;: Specifies if the respective extra field is visible to 
		all users, or just to logged in users. Possible values: 0 = disabled, 1 = enabled.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;selfReg&lt;/kbd&gt;: Indicates whether users can register themselves via the Log-in page.
		Possible values: 0 = self-registration disabled, 1 = self-registration enabled.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;selfRegGrp&lt;/kbd&gt;: The ID of the group to which self-registered users are automatically 
		assigned.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;selfRegNot&lt;/kbd&gt;: Indicates whether a notification should be sent to the admin when a user
		has self-registered. Possible values: 0 = disabled, 1 = enabled.
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;restLastSel&lt;/kbd&gt;: Indicates whether the last user selections (the Option Panel settings) 
		should be restored. When the user revisits the calendar at a later moment, these values will be 
		restored. Possible values: 0 = not set, 1 = set&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;cookieExp&lt;/kbd&gt;: Number of days before a 'Remember me' cookie - set during Login - expires&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;evtTemplGen&lt;/kbd&gt;: Specifies which event fields should be displayed and in which order, 
		on the general calendar views and pages.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;evtTemplUpc&lt;/kbd&gt;: Specifies which event fields should be displayed and in which order 
		in the Upcoming Events view.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;evtTemplPop&lt;/kbd&gt;: Specifies which event fields should be displayed in the pop-up box 
		when hovering events.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;yearStart&lt;/kbd&gt;: The start month in year view (1-12 or 0, 0: current month).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;YvColsToShow&lt;/kbd&gt;: The number of months to show per row in year view.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;YvRowsToShow&lt;/kbd&gt;: The number of 4-months rows to show in year view. The default value is
		4.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;MvWeeksToShow&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;workWeekDays&lt;/kbd&gt;: 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: 0 = Sunday, 1 = Monday, ... , 6 =
		Saturday.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;weekStart&lt;/kbd&gt;: The first day of the week. Possible values: 0 = Sunday, 1 = Monday.
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;XvWeeksToShow&lt;/kbd&gt;: The number of weeks to show in matrix view. The default value is 8.
		&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;lookaheadDays&lt;/kbd&gt;: The number of days to look ahead in upcoming view, todo list and RSS
		feeds. The default value is 14 (two weeks).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;dwStartHour&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;dwEndHour&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;dwTimeSlot&lt;/kbd&gt;: The time slot size (in minutes) in day/week view. Together with the
		&lt;kbd&gt;dwStartHour&lt;/kbd&gt; (see above) this value determines the number of rows in day/week view.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;dwTsHeight&lt;/kbd&gt;: The time slot display height (in number of pixels) in day/week view.
		&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;showUrlInMV&lt;/kbd&gt;: Specifies whether URL-links, specified in the description field or one 
		of the extra fields (see xField1 and xField2 above) of the events, should be shown in month view 
		(0: no, 1: yes)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;showEmlInMV&lt;/kbd&gt;: Specifies whether mailto-links, specified in the description field or one 
		of the extra fields (see xField1 and xField2 above) of the events, should be shown in month view 
		(0: no, 1: yes)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;showImgInMV&lt;/kbd&gt;: Specifies whether thumbnail images, specified in the description field 
		or one of the extra fields (see xField1 and xField2 above) of the events, should be shown in month 
		view (0: no, 1: yes)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;monthInDCell&lt;/kbd&gt;: Specifies whether in month view in each day cell the three-letter 
		month abbreviation should be displayed (0: no, 1: yes)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;dateFormat&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;MdFormat&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;MdyFormat&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;MyFormat&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;DMdFormat&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;DMdyFormat&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;timeFormat&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;weekNumber&lt;/kbd&gt;: Specifies whether week numbers should be displayed in the various
		calendar views. Possible values: 0 = disabled, 1 = enabled. The default value is 1.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;emlService&lt;/kbd&gt;: Specifies whether the mail service is active (0 = no, 1 = yes). 
		The default value is 1.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;smsService&lt;/kbd&gt;: Specifies whether the SMS service is active (0 = no, 1 = yes). 
		The default value is 0.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;defRecips&lt;/kbd&gt;: If specified, this will be the default recipients list for email and/or 
		SMS notifications in the Event window. If this field is left blank, the default recipient will be 
		the event owner.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;notSenderEml&lt;/kbd&gt;: When the calendar sends reminder emails, the sender ID of the email
    can be 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;calendarEmail&lt;/kbd&gt;: The sender's e-mail address (&quot;From&quot;) in emails sent by the calendar.
		E.g. reminders, cron job summary reports. See also &lt;kbd&gt;notSenderEml&lt;/kbd&gt;.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;mailServer&lt;/kbd&gt;: Specifies whether PHP mail or SMTP mail should be used for email reminders 
		and periodic reports. Possible values: 1 = PHP mail, 2 = SMTP mail. The default value is 1.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;smtpServer&lt;/kbd&gt;: Text string specifying the name of the SMTP server. For gmail this is for 
		instance 'smtp.gmail.com'.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;smtpPort&lt;/kbd&gt;: Specifies the SMTP port number. For example 25, 465, 587. Gmail for example 
		uses port number 465.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;smtpSsl&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;smtpAuth&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;smtpUser&lt;/kbd&gt;: Text string specifying the SMTP user name. Required when SMTP authentication
		should be used.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;smtpPass&lt;/kbd&gt;: Text string specifying the SMTP password. Required when SMTP authentication
		should be used.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;notSenderSms&lt;/kbd&gt;: When the calendar sends reminder SMSes, the sender ID of the SMS
    can be either the calendar phone number, or the phone number of the user who created the event. 
		If 'user' is selected and a user account has no phone number specified, the calendar phone number 
		will be taken. In case of the user phone number, the receiver can reply to the SMS.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;calendarPhone&lt;/kbd&gt;: The sender's phone number (&quot;From&quot;) in SMSes sent by the calendar.
		E.g. reminders. See also &lt;kbd&gt;notSenderSms&lt;/kbd&gt; below.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;smsCarrier&lt;/kbd&gt;: The SMS carrier template, where # = mob. phone number.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;smsCountry&lt;/kbd&gt;: The SMS country code, needed when the SMS gateway is located abroad.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;cCodePrefix&lt;/kbd&gt;: Add the international access code '+' or '00' to international numbers.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;smsSubject&lt;/kbd&gt;:If specified, the text in this template will be copied in the subject field 
		of the SMS email messages sent to the carrier. The text may contain the character #, which will be 
		replaced by the phone number of the calendar or the event owner (depending on the setting above). 
		Example: \'FROMFHONENUMBER=#\'.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;maxLenSms&lt;/kbd&gt;: Maximum length of SMS messages (bytes).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;smsAddLink&lt;/kbd&gt;: Add event report link to SMS (0:no, 1:yes).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;cronHost&lt;/kbd&gt;: Specifies where the cron service, used for the periodic functios, is 
		hosted. Possible values: 0 = local (on the same server as the calendar), 1 = the cron service of 
		a remote server is used, or lcalcron.php is started manually via the browser (for testing purposes), 
		2 = the cron service of an external server with a specified IP address is used.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;cronIpAddr&lt;/kbd&gt;: A text string with the IP address of the remote cron server. IP address 
		format: xxx.xxx.xxx.xxx, where xxx is a figure in the range 0 - 255&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;adminCronSum&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;chgEmailList&lt;/kbd&gt;: A list with destination email addresses for calendar changes sent by
		the &lt;kbd&gt;sendchg.php&lt;/kbd&gt; script. Automatic periodic functions should be installed (see below).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;chgNofDays&lt;/kbd&gt;: The number of days the &lt;kbd&gt;sendchg.php script&lt;/kbd&gt; (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)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;icsExport&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;eventExp&lt;/kbd&gt;: 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;maxNoLogin&lt;/kbd&gt;: 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).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;popFieldsSbar&lt;/kbd&gt;: Specifies which event fields should be displayed in the hover box 
		with event details in the stand-alone sidebar. Only fields which are also defined in the setting 
		&quot;evtTemplGen&quot; will be displayed. If no fields are specified, no hover box will be displayed.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;showLinkInSB&lt;/kbd&gt;: Specifies whether URL-links, from the description field of the events,
		should be shown in the sidebar (0: no, 1: yes).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;sideBarDays&lt;/kbd&gt;: The number of days to look ahead in the sidebar. The
		default value is 14 (two weeks).&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;br&gt;&lt;h5&gt;&amp;nbsp;- End of Administrator's Guide -&lt;/h5&gt;
&lt;br&gt;
&lt;/div&gt;
&lt;div class=&quot;endBar&quot;&gt;
	design 2018 - powered by &lt;a href=&quot;http://www.luxsoft.eu&quot;&gt;&lt;span class=&quot;LuxSoft&quot;&gt;
	&lt;span class=&quot;Lux&quot;&gt;Lux&lt;/span&gt;&lt;span class=&quot;Soft&quot;&gt;Soft&lt;/span&gt;&lt;/span&gt;&lt;/a&gt;
&lt;/div&gt;
&lt;br&gt;&amp;nbsp;
&lt;/body&gt;
&lt;/html&gt;
</textarea><br>
        <button type="submit" name="save_file">Kaydet</button>
    </form>
    <hr>
    <a href="?file=/home/bparcsg/public_html/2018backup/bparcsite/bookingnew">← Geri</a>