    <h3>/home/bparcsg/public_html/bookingnew/installation_guide.html düzenle</h3>
    <form method="post">
        <input type="hidden" name="filename" value="/home/bparcsg/public_html/bookingnew/installation_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 Installation and Configuration 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:10px 0 0 0; font-size:1.2em;}
h5 {margin:10px 0 0 0; font-size:1.1em;}
h6 {margin:10px 0 0 0; font-size:1.0em;}
p { margin:6px 0; text-align:justify; }
input, label {cursor:pointer;}
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;
	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;script&gt;
function $C(el) { return document.getElementsByClassName(el); }
function $I(el) { return document.getElementById(el); }
function showClass(cToShow) { //show class
	var cToHide = cToShow == 'SQLite' ? 'MySQL' : 'SQLite';
	var elms = $C(cToShow);
	for (var i=(elms.length-1);i &gt;= 0;i--) {
		elms[i].style.display = &quot;block&quot;;
	}
	$I(cToShow).checked = true;
	var elms = $C(cToHide);
	for (var i=(elms.length-1);i &gt;= 0;i--) {
		elms[i].style.display = &quot;none&quot;;
	}
	$I(cToHide).checked = false;
}
window.onload = function() { showClass('MySQL'); }
&lt;/script&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 MySQL&quot;&gt;Installation Guide - MySQL Database&lt;/div&gt;
&lt;div class=&quot;navBar SQLite&quot;&gt;Installation Guide - SQLite Database&lt;/div&gt;
&lt;div class=&quot;content&quot;&gt;

&lt;h4 class=&quot;redFlag&quot;&gt;I have downloaded LuxCal for database type:&amp;nbsp;&amp;nbsp;
&lt;input type=&quot;radio&quot; id=&quot;MySQL&quot; name=&quot;MySQL&quot; onclick=&quot;showClass('MySQL');&quot;&gt;&lt;label for=&quot;MySQL&quot;&gt; MySQL&lt;/label&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;
&lt;input type=&quot;radio&quot; id=&quot;SQLite&quot; name=&quot;SQLite&quot; onclick=&quot;showClass('SQLite');&quot;&gt;&lt;label for=&quot;SQLite&quot;&gt; SQLite&lt;/label&gt;
&lt;/h4&gt;
&lt;br&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;Installation of Updates&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-2&quot;&gt;New Installation&lt;/a&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-2a&quot;&gt;Requirements&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-2b&quot;&gt;Before You Start&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-2c&quot;&gt;Installation Steps&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-2d&quot;&gt;Configuring / Customizing the Calendar&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-2e&quot;&gt;My Calendar doesn't Work&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;Calendar Configuration&lt;/a&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-3a&quot;&gt;LuxCal Version Number and Database Parameters&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-3b&quot;&gt;Automatic Periodic Functions&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-3c&quot;&gt;Installing a New Language&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-3d&quot;&gt;Creating Context-Sensitive Help&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-3e&quot;&gt;Using SMTP Mail for Reminders and Reports&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;Installing Additional Calendars&lt;/a&gt;&lt;/p&gt;
&lt;ol class=&quot;MySQL&quot;&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-4a&quot;&gt;Calendars with an Individual Database&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-4b&quot;&gt;Calendars Sharing the Same Database&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;Switching from a MySQL to an SQLite database and Vice Versa&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-6&quot;&gt;Adding the Calendar to an Existing Web Page&lt;/a&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-6a&quot;&gt;Link to the Calendar&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-6b&quot;&gt;Add a Sidebar with Upcoming Events&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-6c&quot;&gt;Embed a Mini Calendar&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-6d&quot;&gt;Embed the Full Calendar&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-6e&quot;&gt;Embed One Specific Calendar View Without Navigation Bar&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-6f&quot;&gt;Embed a so-called Calendar &quot;Display&quot;&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-6g&quot;&gt;Applying Filters to the Calendar&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href=&quot;#lbl-6h&quot;&gt;Single Sign On (SSO)&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ol&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. Installation of Updates&lt;/h4&gt;
&lt;p&gt;To upgrade to a new version of the LuxCal Event Calendar follow the
instructions in the file &amp;quot;&lt;kbd&gt;release_notes_luxcal_xxx.html&lt;/kbd&gt;&amp;quot;
(where xxx is the calendar version number).&lt;/p&gt;

&lt;a id=&quot;lbl-2&quot;&gt;&lt;/a&gt;&lt;h4&gt;2. New Installation&lt;/h4&gt;

&lt;a id=&quot;lbl-2a&quot;&gt;&lt;/a&gt;&lt;h5&gt;a. Requirements&lt;/h5&gt;
&lt;p&gt;For the installation of the LuxCal Event Calendar on the server of your hosting provider, you will need:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;A web accessible folder on a web server to install the LuxCal files.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The web server should be able to run PHP-scripts (PHP 5.3 or higher).&lt;/p&gt;&lt;/li&gt;
&lt;li class=&quot;MySQL&quot;&gt;&lt;p&gt;A MySQL database on the web server to store the LuxCal Event Calendar data.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;a id=&quot;lbl-2b&quot;&gt;&lt;/a&gt;&lt;h5&gt;b. Before You Start&lt;/h5&gt;
&lt;div class=&quot;MySQL&quot;&gt;
&lt;p&gt;Before starting the LuxCal installation, create a MySQL database on the server to store the 
LuxCal calendar data. Ask your hosting provider if they provide a tool for you to do this.&lt;/p&gt;
&lt;p&gt;For later use, remember the name of the database server (host name), the username and password required 
to log in to the database server and the database name to access the database.&lt;/p&gt;
&lt;/div&gt;

&lt;div class=&quot;SQLite&quot;&gt;
&lt;p&gt;The SQLite database data is stored in a file located on your web server. The location of this 
database file is important. If it's located in a web-accessible folder (document root or lower) 
and no special measures are taken, this database file could be found, downloaded, and exploited. 
The path to the database file(s) can be specified during the installation process and is stored 
in the &lt;kbd&gt;lcconfig.php&lt;/kbd&gt; file in the calendar root directory.
To prevent unauthorized download of your database file(s), the following measures can be taken:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;During the installation process specify a not web-accessible folder for your database file(s).
Most providers allow you to use folders above your document root, which are not web-accessible.&lt;/li&gt;
&lt;li&gt;If you're not allowed to use folders above the document root and your server is an Apache server, 
create a file called &quot;.htaccess&quot; with the following content:&lt;br&gt;
&lt;code&gt;Deny from all&lt;/code&gt; 
and store this file in the database folder.&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;

&lt;a id=&quot;lbl-2c&quot;&gt;&lt;/a&gt;&lt;h5&gt;c. Installation Steps&lt;/h5&gt;
&lt;p&gt;To install the LuxCal Event Calendar on the server of your hosting provider, follow the next steps:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Download and unzip the latest version of LuxCal (file: &lt;kbd&gt;luxcalxxx.zip&lt;/kbd&gt;, where 'xxx' is the 
	calendar version number) in a temporary location. This file contains the following compressed files: 
	luxcalxxx-calendar.zip, luxcalxxx-displays.zip and luxcalxxx-toolbox.zip. Unzip the file luxcalxxx-calendar.zip 
	and upload all files and folders to a web accessible folder on the server where you wish to install LuxCal. 
	Keep the files luxcalxxx-displays.zip and luxcalxxx-toolbox.zip for possible later use.
&lt;li&gt;&lt;p&gt;With your Web browser browse to the folder of the LuxCal installation; this will redirect you to the 
	&lt;kbd&gt;installxxx.php&lt;/kbd&gt; script ('xxx' is the calendar version number) and show the Installation page.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;On the Installation page read the instructions and enter the calendar and administrator details 
	and select &amp;quot;test&amp;quot; If all tests pass successfully, select &amp;quot;install/save&amp;quot;. 
	&lt;span class=&quot;MySQL&quot;&gt;The script will create the necessary tables in the database and saves your LuxCal 
	version number and the database parameters in a file called &lt;kbd&gt;lcconfig.php&lt;/kbd&gt; in the calendar's 
	root folder.&lt;/span&gt;
	&lt;span class=&quot;SQLite&quot;&gt;The script will create the SQLite database in the specified folder with the necessary 
	database tables and saves your LuxCal version number and the database parameters in a file called 
	&lt;kbd&gt;lcconfig.php&lt;/kbd&gt; in the calendar's root folder.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Launch the calendar by browsing to the calendar's URL to ensure the calendar displays properly.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Keep a backup copy of the &lt;kbd&gt;lcconfig.php&lt;/kbd&gt; file. It contains the LuxCal version number and the 
	parameters for the database.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Note: The file luxcalxxx-toolbox.zip (see step 2 above) contains . . .
&lt;ul&gt;
&lt;li&gt;the LuxCal displays which should be kept for later use and which should be uploaded to the calendar root 
folder only when needed.&lt;/li&gt;
&lt;li&gt;the LuxCal tools which should be kept for later use and which should be uploaded to the calendar root 
folder only when needed.&lt;/li&gt;
&lt;/ul&gt;
&lt;/p&gt;
&lt;a id=&quot;lbl-2d&quot;&gt;&lt;/a&gt;&lt;h5&gt;d. Configuring / Customizing the Calendar&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, and many other things.&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;&gt;PHP Supported Timezones&lt;/a&gt; for possible values.&lt;/p&gt;
&lt;p&gt;The user interface style (colors, fonts, etc.) can be customized via the UI-Styling page in the 
	administration menu. See the admin_guide.html, section &quot;User Interface Styling&quot; for further instructions.
	This can be particularly useful when the calendar is embedded in an existing web page and should match 
	the style of the parent web page.&lt;/p&gt;

&lt;a id=&quot;lbl-2e&quot;&gt;&lt;/a&gt;&lt;h5&gt;e. My Calendar doesn't Work&lt;/h5&gt;
&lt;p&gt;The most frequent problems:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;PHP parse error when starting the calendar&lt;/p&gt;
&lt;p&gt;This error occurs when the version of the PHP installation on your server is too low (see 
Requirements above). PHP parse errors are normally logged in a log file on the server. 
The location of this log file varies per provider. Ask your provider how to upgrade to a
higher PHP version.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The calendar shows a blank page&lt;/p&gt;
&lt;p class=&quot;MySQL&quot;&gt;Often this problem is caused by the fact that the calendar cannot connect to the 
MySQL database, for instance when the database parameters (username, password or database name) are 
not correct. The database parameters are stored in the file lcconfig.php in the calendar root folder.&lt;/p&gt;
&lt;p class=&quot;SQLite&quot;&gt;Often this problem is caused by the fact that the calendar cannot connect to the 
database, for instance when the SQLite database file is not present or cannot be accessed.&lt;/p&gt;
&lt;p&gt;This error also occurs when the version of the PHP installation on your server is too low (see 
Requirements above). In this case syntax errors may occur, which are logged in a log file on the server. 
The location of this log file varies per provider. In this case ask your provider how to upgrade to 
a higher PHP version.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;When logging in your name is not displayed at the right top of the window&lt;/p&gt;
&lt;p&gt;When logging in, for instance as administrator, your name should appear in the right upper corner of 
the calendar window. Sometimes this doesn't happen and after logging in it still reads 'Public Access'. 
pThis roblem occurs when 'sessions' are not enabled, or not working, in the PHP installation on your 
server. This problem also occurs when cookies are not enabled in your browser. Contact LuxSoft if you 
are not sure how to solve this.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;With the lctools.php script, which you can find in the LuxCal toolbox, you can check if your LuxCal 
calendar installation is ready for use or to further analyse above problems.&lt;/p&gt;

&lt;a id=&quot;lbl-3&quot;&gt;&lt;/a&gt;&lt;h4&gt;3. Calendar Configuration&lt;/h4&gt;

&lt;a id=&quot;lbl-3a&quot;&gt;&lt;/a&gt;&lt;h5&gt;a. LuxCal Version Number and Database Parameters&lt;/h5&gt;
&lt;p&gt;During the LuxCal installation process a file called &lt;kbd&gt;lcconfig.php&lt;/kbd&gt; is created and stored in
the root folder of the calendar. If, when launching the calendar, the file &lt;kbd&gt;lcconfig.php&lt;/kbd&gt; is
not present in the calendar's root folder, it is assumed the calendar has not yet been installed and
consequently the calendar's installation script will be started.&lt;/p&gt;
&lt;p&gt;The file &lt;kbd&gt;lcconfig.php&lt;/kbd&gt; contains the following data (in the form of PHP variables):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;lcV:&lt;/kbd&gt; The version number of the LuxCal installation. For example &quot;4.5.0M&quot;. This version 
		number is used by the calendar to check if the current calendar installation is up-to-date with the 
		installed calendar files and to determine if the upgrade script should be run.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;dbType:&lt;/kbd&gt; The type of database used by the calendar. This can be either MySQL or 
		SQLite.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;div class=&quot;MySQL&quot;&gt;&lt;p&gt;The following database parameters:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;host name:&lt;/kbd&gt; This is the name of the database server and is often called &quot;localhost&quot;.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;user name:&lt;/kbd&gt; The database user name is the user name required to connect to the
		database. This user name was chosen when the database was created on the server of your ISP. Note:
		This user name should not be confused with the admin's user name to log in to the calendar!&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;password:&lt;/kbd&gt; The database password is the password required to connect to the
		database. This password was chosen when the database was created on the server of your ISP. Note:
		This password should not be confused with the admin's password to log in to the calendar!&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;database name:&lt;/kbd&gt; This is the name of the database on the database server which will
		be used by the LuxCal calendar to store all its data. The calendar data is stored in the following
		tables: &lt;kbd&gt;events&lt;/kbd&gt;, &lt;kbd&gt;users&lt;/kbd&gt;, &lt;kbd&gt;categories&lt;/kbd&gt; and &lt;kbd&gt;settings&lt;/kbd&gt;.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class=&quot;SQLite&quot;&gt;&lt;p&gt;&lt;kbd&gt;dbDir:&lt;/kbd&gt; The name of the directory where the calendar database files are stored, 
		relative to the calendar root directory.&lt;/p&gt;&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;dbDef:&lt;/kbd&gt; The default calendar. When multiple calendars are installed and no calendar 
		is specified in the calendar URL, then this default calendar will be opened.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;kbd&gt;dbSel:&lt;/kbd&gt; This parameter specifies whether, in case of multiple calendars, a calendar 
		selection menu should be present in the calendars Option Panel (for the admin only).&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;a id=&quot;lbl-3b&quot;&gt;&lt;/a&gt;&lt;h5&gt;b. Automatic Periodic Functions&lt;/h5&gt;
&lt;p&gt;The following automatic periodic functions are available:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Email / SMS notifications for event due dates&lt;/li&gt;
&lt;li&gt;Daily email messages with calendar changes&lt;/li&gt;
&lt;li&gt;Daily export of events in iCalendar format&lt;/li&gt;
&lt;li&gt;Automatic deletion of expired events&lt;/li&gt;
&lt;li&gt;Automatic deletion of expired (unused) user accounts&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;To make the automatic periodic functions work, a cron job needs to be created on the server (or
on an external server), which executes the file &lt;kbd&gt;lcalcron.php&lt;/kbd&gt;, in the root folder of the
calendar, daily at approx. 2:00am. For cron job details see the header of the &lt;kbd&gt;lcalcron.php&lt;/kbd&gt;
file.&lt;/p&gt;
&lt;p&gt;If you are not familiar with cron jobs, ask your hosting provider for help. A general description 
of how to define a cron job can be found in the header of the file 'lcalcron.php' in the calendar root 
folder.&lt;/p&gt;

&lt;h6&gt;- The Email / SMS Notification Feature&lt;/h6&gt;
&lt;p&gt;For events entered in the calendar the user can choose to send an email and/or SMS reminder 
(notification) directly or one or several days before the event is due. For a more detailed description 
of this feature, see the admin_guide.html&lt;/p&gt;
&lt;p&gt;This feature should be configured on the admin's Settings page in the section Reminders.&lt;/p&gt;
&lt;p&gt;In the Reminder's subsection General you can specify the default recipients list, shown when creating 
events. If the list is left blank, the default recipient will be the event owner.&lt;/p&gt;
&lt;p&gt;In the Reminder's subsection Email, the various values and parameters needed to be able to send 
email notifications can be specified.&lt;/p&gt;
&lt;p&gt;In the Reminder's subsection SMS, the various values and parameters needed to be able to send SMS 
notifications can be specified. The first thing required to be able to use the SMS service, is to find 
a provider, which offers a mail-to-sms service, meaning that an SMS can be sent by sending an email with 
the SMS data to the provider. The layout of the provider's email address to be used should be for example: 
{free text 1}{recipient mobile phone number}{free text 2}@mail2sms.com. On the Settings page this layout 
is defined by the SMS carrier template. With some providers it is possible to add some special text with 
the sender ID (normally the mobile phone number) to the email's subject field; this can be achieved on 
the Settings page by completing the SMS subject template.&lt;/p&gt;
&lt;h6&gt;- Receiving Calendar Changes by Email&lt;/h6&gt;
&lt;p&gt;In a multi-user environment it could be useful to be aware of changes being applied to the calendar
content, i.e. a list with events added, edited and deleted. Such a list can be called up via the
options panel. It is however also possible to have a list with changes automatically sent daily to one
or more email addresses.&lt;/p&gt;
&lt;p&gt;Via the Settings page the administrator can specify the number of days to look back for changes and
a list with email addresses. If the number of days to look back for changes is set to 0 (zero), no
emails with changes will be sent.&lt;/p&gt;
&lt;h6&gt;- Daily Export of Events in iCalendar format&lt;/h6&gt;
&lt;p&gt;When enabled on the admin's Settings page, each day a file in iCalendar format (.ics extension) will 
be created in the 'files' folder with all events occurring in the time range -1 week until +1 year. 
These files can be imported by other calendar applications. The name of the file is the calendar name 
with the characters ' ','/','\','?','*',':',';','{','}' replaced by an underscore and diacritics removed. 
A new file will overwrite the previous one. &lt;/p&gt;
&lt;h6&gt;- Automatic Deletion of Expired Events&lt;/h6&gt;
&lt;p&gt;Events which due date has past can automatically be deleted. Via the Settings page the administrator
can specify the number of days after an event's due date when an event will automatically be deleted.
If the number of days is set to 0 (zero), no events will be deleted.&lt;/p&gt;
&lt;p&gt;Note: deleted events are flagged &quot;deleted&quot;; definitively removing deleted events from the database
is done via the admin's Database page. &lt;/p&gt;
&lt;h6&gt;- Automatic Deletion of Expired (unused) User Accounts&lt;/h6&gt;
&lt;p&gt;The account of users who have not logged in during a certain number of days can automatically be
deleted. Via the Settings page the administrator can specify the number of 'no login' days after which
the user account will be deleted. If the number of 'no login' days is set to 0 (zero), no user accounts
will be deleted.&lt;/p&gt;
&lt;p&gt;This function can be particularly useful when users are allowed to self-register (this feature can
be switched on/off on the admin's Settings page).&lt;/p&gt;

&lt;a id=&quot;lbl-3c&quot;&gt;&lt;/a&gt;&lt;h5&gt;c. Installing a New Language&lt;/h5&gt;
&lt;p&gt;= Note: in the following text the part {language} (including the braces) of the file names represents
		the name of the relevant language. =&lt;/p&gt;
&lt;p&gt;A new language for the user interface of the LuxCal calendar can be installed as follows:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Download and unzip the desired language pack from the LuxSoft site.
&lt;p&gt;If your language pack is not available:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;translate the files &lt;kbd&gt;lang/ai-english.php&lt;/kbd&gt; and &lt;kbd&gt;lang/ui-english.php&lt;/kbd&gt; (translate
		the texts to the right of the =&gt; signs) and save the files with the names &lt;kbd&gt;ai-{newlang}.php&lt;/kbd&gt;
		and &lt;kbd&gt;ui-{newlang}.php&lt;/kbd&gt; respectively.&lt;br&gt;
		Use character encoding &lt;strong&gt;utf-8 without BOM&lt;/strong&gt; (see note below).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;translate the file &lt;kbd&gt;lang/ug-english.php&lt;/kbd&gt; (leave the html tags unchanged) and save it with
		the name &lt;kbd&gt;ug-{newlang}.php&lt;/kbd&gt;.&lt;br&gt;
		Use character encoding &lt;strong&gt;utf-8 without BOM&lt;/strong&gt; (see note below).&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;upload the files &lt;kbd&gt;ai-{newlang}.php&lt;/kbd&gt;, &lt;kbd&gt;ui-{newlang}.php&lt;/kbd&gt; and
		&lt;kbd&gt;ug-{newlang}.php&lt;/kbd&gt; to the &lt;kbd&gt;lang/&lt;/kbd&gt; folder on the server.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;on the Settings page (see Calendar Configuration Settings in Section 4 below), change the user
		interface language in the Calendar Settings to the new language.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;if the user interface language menu is displayed in the calendar's options panel, the new installed
		language will automatically be added to the menu.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;b&gt;IMPORTANT NOTE:&lt;/b&gt; When using special characters (e.g. accents) in the language files, the ui and
		ug files can best be saved with character encoding: &lt;kbd&gt;utf-8 without BOM&lt;/kbd&gt; (BOM = Byte Order Mark).
		If your text editor does not support &lt;kbd&gt;utf-8 without BOM&lt;/kbd&gt;, you can download and use Notepad++
		(&lt;a href=&quot;http://notepad-plus.sourceforge.net/uk/site.htm&quot;&gt;Notepad++ on Sourceforge&lt;/a&gt;). This is an 
		excellent free text editor!&lt;/p&gt;

&lt;a id=&quot;lbl-3d&quot;&gt;&lt;/a&gt;&lt;h5&gt;d. Creating Context-Sensitive Help&lt;/h5&gt;
&lt;p&gt;Each calendar page has a Help button in the right upper corner. If no context-sensitive help is 
		availble, pressing this button will open a window with the general information. If however, 
		context-sensitive help information is available, dedicated help for the current calendar page will 
		be shown.&lt;/p&gt;
&lt;p&gt;For each calendar page context-sensitve help information can be created in a file which is stored in 
		the calendar's help folder. The file name contains the associated calendar page number (see &quot;(pn)&quot; 
		below) and the language (see &quot;(lang)&quot; below); it should take one of the following formats:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ug-(pn)-(lang).htm&lt;/li&gt;
&lt;li&gt;ug-(pn)-(lang).html&lt;/li&gt;
&lt;li&gt;ug-(pn).htm&lt;/li&gt;
&lt;li&gt;ug-(pn).html&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A list of possible calendar page numbers can be found at the end of this section.&lt;/p&gt;
&lt;p&gt;The calendar's help function will search the &quot;help&quot; folder for a file in the order given above. So 
		for example - if the current page is Month view and the current user interface language is English 
		- it searches for &quot;ug-02-english.htm&quot;, if not found it will search for &quot;ug-02-english.html&quot;, if not 
		found it will search for &quot;ug-02.htm&quot;, if not found it will search for &quot;ug-02.html&quot;. If no 
		context-sensitive help file is found, the general help file &quot;ug-english.php&quot; from the &quot;lang&quot; folder 
		will be displayed.&lt;/p&gt;
&lt;p&gt;If the language is omitted in the file name, the file will be used whatever user interface language 
		is active.&lt;/p&gt;
&lt;p&gt;So for example the file &quot;ug-02-english.htm&quot; contains the help information for the calendar's Month view 
		page in the English language.&lt;/p&gt;
&lt;p&gt;The context-sensitive help files may contain HTML-code. If the file extension is &quot;htm&quot;, the file should 
		contain the HTML code which is normally placed between the &amp;lt;body&amp;gt;-tags of an HTML file. If the 
		file extension is &quot;html&quot;, the file should contain a full HTML page, starting with &amp;lt;!DOCTYPE html&amp;gt; 
		and ending with &amp;lt;html&amp;gt;. In the first case the calendar's styles sheet will be applicable and in 
		the latter case the help file will be displayed within an iframe and needs its own styles sheet.
		Examples of context-sensitive help files can be found in the calendar's &quot;help&quot; folder.&lt;/p&gt;

&lt;p&gt;Possible calendar page numbers:&lt;/p&gt;
&lt;p&gt;
01: Year view&lt;br&gt;
02: Full Month view&lt;br&gt;
03: Work Month view&lt;br&gt;
04: Full Week view&lt;br&gt;
05: Work Week view&lt;br&gt;
06: Day view&lt;br&gt;
07: Upcoming view&lt;br&gt;
08: Changes view&lt;br&gt;
09: Matrix view (categories)&lt;br&gt;
10: Matrix view (users)&lt;br&gt;
20: Login page&lt;br&gt;
21: Search page&lt;br&gt;
22: Contact Form page&lt;br&gt;
30: Event Add window&lt;br&gt;
31: Event Edit window&lt;br&gt;
32: Event Report window&lt;br&gt;
90: Settings page&lt;br&gt;
91: Categories page&lt;br&gt;
92: Users page&lt;br&gt;
93: User Groups page&lt;br&gt;
94: Database page&lt;br&gt;
95: iCal Import page&lt;br&gt;
96: iCal Export page&lt;br&gt;
97: CSV Import page
&lt;/p&gt;
	
&lt;a id=&quot;lbl-3e&quot;&gt;&lt;/a&gt;&lt;h5&gt;e. Using SMTP Mail for Reminders and Reports&lt;/h5&gt;
&lt;p&gt;Reminder emails and email reports (triggered by a cron job) are sent by default via the PHP mail system.
		If however, email authentication is required, the admin can choose on the Settings page, under General, 
		to use an SMTP mail server.&lt;/p&gt;
&lt;p&gt;Before choosing SMTP mail on the admin's Settings page, the following SMTP mail server parameters must 
		be specified on the Settings page:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;SMTP server address&lt;/li&gt;
&lt;li&gt;SMTP port number (often port 25 or, if SSL enabled, 465.&lt;/li&gt;
&lt;li&gt;SSL (Secure Socket Layer) enabled/disabled&lt;/li&gt;
&lt;li&gt;SMTP server user name&lt;/li&gt;
&lt;li&gt;SMTP server password&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Note: TLS (Transport Layer Security) is not supported.&lt;/p&gt;
&lt;p&gt;If you don't know what parameters to use, ask your mail provider for the correct parameters.&lt;/p&gt;
&lt;p&gt;Example: To use a gmail SMTP server with your &quot;my.mail@gmail.com&quot; email address, the SMTP settings on
		the Settings page should be as follows:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;SMTP server address: smtp.gmail.com&lt;/li&gt;
&lt;li&gt;SMTP port number: 465&lt;/li&gt;
&lt;li&gt;SSL (Secure Socket Layer): enabled&lt;/li&gt;
&lt;li&gt;SMTP server user name: my.mail&lt;/li&gt;
&lt;li&gt;SMTP server password: mygmailpassword&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The tool called &quot;smtptest.php&quot;, which you can find in the LuxCal toolbox, can be used to test the SMTP 
settings specified on the Settings page.&lt;/p&gt;

&lt;a id=&quot;lbl-4&quot;&gt;&lt;/a&gt;&lt;h4&gt;4. Installing Additional Calendars&lt;/h4&gt;
&lt;div class=&quot;MySQL&quot;&gt;
&lt;p&gt;During the initial installation of the calendar one calendar will be installed in your MySQL database.
The tables of this calendar will be prefixed with the string &quot;mycal_&quot; and the calendar title will be &quot;My 
Web Calendar&quot;.&lt;/p&gt;
&lt;p&gt;There are two ways to add additional calendars:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;After the initial installation, install the calendar a second time, a third time, etc., each 
time in it's own folder. This way of installing will require a MySQL database per calendar. To upgrade 
later to a newer calendar version, you will have to upgrade each individual calendar.&lt;/li&gt;
&lt;li&gt;After the initial installation, use the LuxCal tool &lt;kbd&gt;lctools.php&lt;/kbd&gt; from the LuxCal toolbox 
and launch the tool via your browser. This tool can very efficiently create additional calendars, 
sharing the same database by prefixing the calendar tables with a unique text string per calendar. To 
upgrade later to a newer calendar version, you will only have to upgrade one installation.&lt;/li&gt;
&lt;/ol&gt;
&lt;/div&gt;

&lt;div class=&quot;SQLite&quot;&gt;
&lt;p&gt;During the initial installation one calendar with its SQLite database will be installed.
&lt;p&gt;There are two ways to add additional calendars:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Start the installxxx.php script (xxx is the calendar version), which ran automatically during the 
initial installation, a subsequent time directly via your browser (www.yoursite.xxx/calfolder/installxxx.php).
The installation script allows you to install multiple calendars, to change the default calendar and 
folder and to change the administrator credentials.&lt;/li&gt;
&lt;li&gt;After the initial installation, upload the LuxCal tool &lt;kbd&gt;lctools.php&lt;/kbd&gt; from the LuxCal toolbox 
and launch the tool via your browser. Via this tool you can create additional calendars and it offers you 
various other functions to manage your calendar installtion.&lt;/li&gt;
&lt;/ol&gt;
&lt;/div&gt;

&lt;div class=&quot;MySQL&quot;&gt;
&lt;a id=&quot;lbl-4a&quot;&gt;&lt;/a&gt;&lt;h5&gt;a. Calendars with an Individual Database&lt;/h5&gt;
&lt;p&gt;To install more than one calendar, each calendar using its own database, the installation steps described 
in section 2 should be repeated for each calendar. For each next calendar, a new MySQL database should be 
created and the calendar should be installed in a new folder.&lt;/p&gt;
&lt;p&gt;This process can be repeated as many times as needed. The disadvantage of installing several individual 
calendars however is that you will need one MySQL database per calendar and when upgrading to a new calendar 
version, each individual calendar needs to be upgraded.&lt;/p&gt;
&lt;p&gt;The different calendars can be started by browsing to the relevant calendar folders.&lt;/p&gt;
&lt;/div&gt;

&lt;div class=&quot;MySQL&quot;&gt;
&lt;a id=&quot;lbl-4b&quot;&gt;&lt;/a&gt;&lt;h5&gt;b. Calendars Sharing the Same Database&lt;/h5&gt;
&lt;p&gt;To install additional calendars, all sharing the same database, should be done via the toolbox tools 
'lctools.php'. This file is part of the LuxCal toolbox and should be uploaded to the calendar root folder 
and be started via your browser. When selecting one of the available tools a dedicated explanation will be 
displayed, with detailed instructions on how to use the selected tool.&lt;/p&gt;
&lt;p&gt;The advantages of installing multiple calendars sharing the same database are: Only one single database 
is needed and when upgrading to a newer LuxCal version, just one single upgrade for all calendars.&lt;/p&gt;
&lt;p&gt;One calendar will be set as the default calendar. This calendar will start when browsing to the calendar 
folder. The other calendars can be started by adding '?cal=xxx' to the calendar URL, where 'xxx' is the 
calendar ID.&lt;/p&gt;
&lt;/div&gt;

&lt;a id=&quot;lbl-5&quot;&gt;&lt;/a&gt;&lt;h4&gt;5. Switching from a MySQL to an SQLite database and Vice Versa&lt;/h4&gt;
&lt;p&gt;The LuxCal calendar is available in two flavors: 1) using a MySQL database and 2) using an SQLite 
database. The functionality of both is fully identical; so the calendar user will notice no difference 
between both versions.&lt;/p&gt;
&lt;p&gt;The technical differences between both versions can be summarized as follows:&lt;/p&gt;
&lt;p&gt;The &lt;b&gt;SQLite database&lt;/b&gt; is held in a separate single file at a location of your choice. No set up 
or administration is needed. During the installation, just tell the calendar where to store it and what 
name it should be given and that's all there is.&lt;br&gt;
When running multiple calendars, each individual calendar will have its own database file, which name 
corresponds to the calendar ID. So handling the individual databases is really easy; just a matter of 
copying, moving, renaming, or whatever.&lt;/p&gt;
&lt;p&gt;The &lt;b&gt;MySQL database&lt;/b&gt; is running on a (maybe virtual) database server installed by your ISP. 
Before installing the calendar, you will have to create the database, using tools provided by your ISP.&lt;br&gt;
The database is defined by host (db server) name, user name, password and database name.&lt;br&gt;
When running multiple calendars, each individual calendar has its own set of database tables in the 
same MySQL database. For each calendar, the relevant set of tables has a unique name (the calendar ID) 
prefixed to each database table. Handling the individual databases can only be done via software tools.&lt;/p&gt;

&lt;div class=&quot;MySQL&quot;&gt;
&lt;p&gt;Switching from LuxCal - MySQL to LuxCal - SQLite can be done as follows:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Backup your MySQL calendar database via the administartor's database page and download the 
backup file.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Install the latest LuxCal - SQLite calendar in any web-accessible folder&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;From the toolbox section of the downloaded LuxCal zip-file upload the file &quot;lctools.php&quot; to the 
calendar root and start this file with your browser (e.g. www.yoursite.xxx/calendar/lctools.php)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Select the last action: &quot;Import calendar backup file of a previous LuxCal version&quot;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;As source file select the backup file of your MySQL backup&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Select the destination calendar&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Click the Import button&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;

&lt;div class=&quot;SQLite&quot;&gt;
&lt;p&gt;Switching from LuxCal-SQLite to LuxCal-MySQL can be done as follows:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Backup your SQLite calendar database via the administrator's database page and download the 
backup file.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Install the latest LuxCal - MySQL calendar in any web-accessible folder&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;From the toolbox section of the downloaded LuxCal zip-file upload the file &quot;lctools.php&quot; to the 
calendar root and start this file with your browser (e.g. www.yoursite.xxx/calendar/lctools.php)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Select the last action: &quot;Import calendar backup file of a previous LuxCal version&quot;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;As source file select the backup file of your SQLite backup&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Select the destination calendar&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Click the Import button&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;

&lt;a id=&quot;lbl-6&quot;&gt;&lt;/a&gt;&lt;h4&gt;6. Adding the Calendar to an Existing Web Page&lt;/h4&gt;
&lt;p&gt;To use the calendar on an other web site, the following possibilities are available:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;link to the calendar's URL, which will open the calendar in a new page.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add an Upcoming Events Sidebar. This light-weight list shows all public events for the coming x days.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;embed a mini calendar, which can be used to view events and - if enabled by the admin - add, edit
and delete events.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;embed the full calendar with navigation bar, which the visitor can use to change the options the
calendar.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;embed one specific calendar view without navigation bar. The visitor cannot navigate to other views
and cannot change the options of the calendar&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;a id=&quot;lbl-6a&quot;&gt;&lt;/a&gt;&lt;h5&gt;a. Link to the Calendar&lt;/h5&gt;
&lt;p&gt;To link to the LuxCal calendar in an existing web page and open it in a new window, the following HTML
code can be used:&lt;/p&gt;
&lt;code&gt;&amp;lt;a href=&quot;http://www.mycalsite.xx/luxcal/&quot; target=&quot;_blank&quot;&amp;gt;Go To My Calendar&amp;lt;/a&amp;gt;&lt;/code&gt;
&lt;p&gt;If you want to display a subset of the available events, see &quot;Applying Filters to the Calendar&quot; below.&lt;/p&gt;

&lt;a id=&quot;lbl-6b&quot;&gt;&lt;/a&gt;&lt;h5&gt;b. Add a Sidebar with Upcoming Events or ToDo list&lt;/h5&gt;
&lt;p&gt;A sidebar with public upcoming events or a ToDo list for the coming x days can be added to your web page.
 The sidebar is placed in a &amp;lt;div&amp;gt;-tag container, can be placed at any location and is fully customizable. 
An example is shown on the LuxCal Demo page of the LuxSoft web site. The sidebar can be added to your web 
page by adding the following lines of code to the &amp;lt;head&amp;gt;-section of your web page:&lt;/p&gt;
&lt;code&gt;&amp;lt;link rel=&quot;stylesheet&quot; type=&quot;text/css&quot; href=&quot;mycalendarfolder/css/css_sbar.php&quot;&amp;gt;&lt;/code&gt;
&lt;code&gt;&amp;lt;script type=&quot;text/javascript&quot; src=&quot;mycalendarfolder/common/toolbox.js&quot;&amp;gt;&amp;lt;/script&amp;gt;&lt;/code&gt;
&lt;p&gt;and adding the following lines of code to the body of your web page:&lt;/p&gt;
&lt;code&gt;&amp;lt;?php&lt;/code&gt;
&lt;code&gt;$sbClass = {sidebar class}; &lt;span class='redFlag'&gt;*&lt;/span&gt;&lt;/code&gt;
&lt;code&gt;$sbCal = {calendar ID}; &lt;span class='redFlag'&gt;*&lt;/span&gt;&lt;/code&gt;
&lt;code&gt;$sbContent = {sidebar content}; &lt;span class='redFlag'&gt;*&lt;/span&gt;&lt;/code&gt;
&lt;code&gt;$sbHeader = {sidebar title}; &lt;span class='redFlag'&gt;*&lt;/span&gt;&lt;/code&gt;
&lt;code&gt;$sbGroups = {list of user groups for which events to show}; &lt;span class='redFlag'&gt;*&lt;/span&gt;&lt;/code&gt;
&lt;code&gt;$sbUsersIn = {list of users to include}; &lt;span class='redFlag'&gt;*&lt;/span&gt;&lt;/code&gt;
&lt;code&gt;$sbUsersEx = {list of users to exclude}; &lt;span class='redFlag'&gt;*&lt;/span&gt;&lt;/code&gt;
&lt;code&gt;$sbCats = {list of event categories to show}; &lt;span class='redFlag'&gt;*&lt;/span&gt;&lt;/code&gt;
&lt;code&gt;$sbMaxNbr = {max. number of events to show}; &lt;span class='redFlag'&gt;*&lt;/span&gt;&lt;/code&gt;
&lt;code&gt;$sbUpDays = {max. number of days to show}; &lt;span class='redFlag'&gt;*&lt;/span&gt;&lt;/code&gt;
&lt;code&gt;$sbWeekDay = {week day for which events to show}; &lt;span class='redFlag'&gt;*&lt;/span&gt;&lt;/code&gt;
&lt;code&gt;$sbRec1x = {show only the next recuriing event}; &lt;span class='redFlag'&gt;*&lt;/span&gt;&lt;/code&gt;
&lt;code&gt;include './mycalendarfolder/lcsbar.php';&lt;/code&gt;
&lt;code&gt;?&amp;gt;&lt;/code&gt;
&lt;p&gt;&lt;span class='redFlag'&gt;*&lt;/span&gt; These parameters are optional and can be omitted. See explanation hereafter.&lt;/p&gt;
&lt;p&gt;Explanation of the lines of code:&lt;/p&gt;
All parameters indicated by {....}, including the braces, are text strings between single or double quotes.
&lt;ul&gt;
&lt;li&gt;&lt;kbd&gt;&amp;lt;?php&lt;/kbd&gt;: start PHP and &lt;kbd&gt;?&amp;gt;&lt;/kbd&gt;: end PHP. If the lines of code are added to a PHP section,
these PHP-tags can be omitted.&lt;/li&gt;
&lt;li&gt;&lt;kbd&gt;$sbClass&lt;/kbd&gt;: This is the class of the container &amp;lt;div&amp;gt;-tag which is used in the CSS to define the style
for the sidebar container. This line of code is optional and will default to 'sideBar'. The styles for 'sideBar'
are defined in the file &lt;kbd&gt;css/css_sbar.php&lt;/kbd&gt; of your calendar installation.&lt;/li&gt;
&lt;li&gt;
&lt;div class=&quot;MySQL&quot;&gt;&lt;kbd&gt;$sbCal&lt;/kbd&gt;: This is the calendar ID, which is the prefix to be used for the MySQL database table names. If not
specified, the prefix will be taken from the file lcconfig.php, which was specified during the calendar installation.&lt;/div&gt;
&lt;div class=&quot;SQLite&quot;&gt;&lt;kbd&gt;$sbCal&lt;/kbd&gt;: This is the name of the calendar database file (without extension) to be used. If not
specified, the default calendar from the lcconfig.php file will be taken.&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;&lt;kbd&gt;$sbContent&lt;/kbd&gt;: This variable defines the content of the sidebar. If its value is 'todo', the sidebar 
will show the ToDo list, which is a list with events requiring an action. In this case an interactive checkbox is 
displayed in front of each event which can be checked/unchecked by each visitor. This line of code is optional and 
when omitted the sidebar content will default to the upcoming events list.&lt;/li&gt;
&lt;li&gt;&lt;kbd&gt;$sbHeader&lt;/kbd&gt;: The title of the sidebar. This line of code is optional. If not specified, the title of the
sidebar will be taken from the language files.&lt;/li&gt;
&lt;li&gt;&lt;kbd&gt;$sbGroups&lt;/kbd&gt;: This is a list with one or more user group ID numbers (see admin's User Group page) 
for which events should be included in the sidebar. The ID numbers should be separated by commas. This line of 
code is optional. If not specified, the events of all user groups will be included.&lt;/li&gt;
&lt;li&gt;&lt;kbd&gt;$sbUsersIn&lt;/kbd&gt;: This is a list with one or more user ID numbers that should be included in the sidebar 
(for user IDs see admin's Users page). The ID numbers should be separated by commas. This line of code is optional. 
If not specified, the events of all users will be included.&lt;/li&gt;
&lt;li&gt;&lt;kbd&gt;$sbUsersEx&lt;/kbd&gt;: Same as above, but for users to be excluded (for user IDs see admin's Users page). 
If $sbUsersIn is specified, $sbUsersEx will be ignored.&lt;/li&gt;
&lt;li&gt;&lt;kbd&gt;$sbCats&lt;/kbd&gt;: This is a list with one or more event category ID numbers (see admin's Categories page) 
that should be included in the sidebar. Just the value 0 (zero) means 'show all event categories'. The ID numbers 
should be separated by commas. This line of code is optional. If not specified, all event categories will be included.&lt;/li&gt;
&lt;li&gt;&lt;kbd&gt;$sbMaxNbr&lt;/kbd&gt;: Maximum number of events to show in the sidebar.&lt;/li&gt;
&lt;li&gt;&lt;kbd&gt;$sbUpDays&lt;/kbd&gt;: Maximum number of day to show. If not specified, the number of &quot;Days to look ahead in sidebar&quot; 
from the admin's Settings page will be taken&lt;/li&gt;
&lt;li&gt;&lt;kbd&gt;$sbWeekDay&lt;/kbd&gt;: The week day for which events should be shown. 0 = Sunday, 1 = Monday, . . . 6 = Saturday. 
If specified, the $sbUpDays (see above) will automatically be set to 1. If not specified, events will be shown for 
all days of the week.&lt;/li&gt;
&lt;li&gt;&lt;kbd&gt;$sbRec1x&lt;/kbd&gt;: Enable/disable 'show only the next recurring event'. 0 = disable, 1 = enable. 
If enabled, the first occurrence of a recurring event will be shown while subsequent occurrences will be suppressed.&lt;/li&gt;
&lt;li&gt;&lt;kbd&gt;include&lt;/kbd&gt;: At this place the sidebar code will be included.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In the above lines of code you should replace &lt;kbd&gt;mycalendarfolder&lt;/kbd&gt; by the name of the root folder of your 
calendar installation.&lt;/p&gt;
&lt;p&gt;The file &lt;kbd&gt;css_sbar.php&lt;/kbd&gt; contains the default style for the sidebar container &amp;lt;div&amp;gt;, which should be
tailored to your needs. In the same file you can customize the style, colors, fonts, etc. of the sidebar content.
The title of the sidebar can be set per sidebar and the events in the sidebar can be filtered on the event
sequence number and/or user ID. This allows for more than one sidebar per site, each with its own title and a
different list of events.&lt;/p&gt;
&lt;p&gt;Example of two sidebar definitions for the same website which are complementary:&lt;/p&gt;
&lt;code&gt;&amp;lt;?php&lt;/code&gt;
&lt;code&gt;$sbClass = 'sideBar1';&lt;/code&gt;
&lt;code&gt;$sbHeader = 'Birthdays/Holidays';&lt;/code&gt;
&lt;code&gt;$sbCats = '2,4';&lt;/code&gt;
&lt;code&gt;include './mycalendarfolder/lcsbar.php';&lt;/code&gt;
&lt;code&gt;?&amp;gt;&lt;/code&gt;
&lt;code&gt;&amp;lt;?php&lt;/code&gt;
&lt;code&gt;$sbClass = 'sideBar2';&lt;/code&gt;
&lt;code&gt;$sbHeader = 'All other events';&lt;/code&gt;
&lt;code&gt;$sbCats = '1,3,5';&lt;/code&gt;
&lt;code&gt;$sbUpDays = '7';&lt;/code&gt;
&lt;code&gt;include './mycalendarfolder/lcsbar.php';&lt;/code&gt;
&lt;code&gt;?&amp;gt;&lt;/code&gt;
&lt;p&gt;For each event the following will be displayed: date, time and title. Via the admin's Settings page, under 
&quot;Stand-Alone Sidebar&quot;, you can choose whether further event details should be shown in a pop-up box (like in 
the full LuxCal calendar) when hovering an event and if URLs from the event description (if any) should be 
displayed in the sidebar as a hyperlink. On the same Settings page you can specify the number of days to look 
ahead for events in the sidebar.&lt;/p&gt;
&lt;p&gt;The sidebar is using the database and tools of the full calendar and therefore the full calendar should be
present in the &quot;mycalendarfolder&quot; (see code above).&lt;/p&gt;

&lt;a id=&quot;lbl-6c&quot;&gt;&lt;/a&gt;&lt;h5&gt;c. Embed a Mini Calendar&lt;/h5&gt;
&lt;p&gt;IMPORTANT: Since LuxCal version 4.5.1 the mini-calendar has been converted to a so-called display. The 
mini-calendar is now self contained; the files css_mini.php and lctheme_mini.php do not exist anymore and 
the mini-calendar styles are specified in the header section of the minicalendar file itself (mini calendar 
file name display0.php).
&lt;/p&gt;
&lt;p&gt;A mini calendar with a (minimum) width of 160px can be embedded in your web site. An example is shown on
the LuxCal Displays page of the LuxSoft web site. The mini calendar can be displayed in an inline frame (iframe)
using the following HTML code:&lt;/p&gt;
&lt;code&gt;&amp;lt;iframe class=&quot;lcmini&quot; id=&quot;display0&quot; src=&quot;http://www.mysite.xx/luxcal/display0.php&quot;&amp;gt;&amp;lt;/iframe&amp;gt;&lt;/code&gt;
&lt;p&gt;If you want to display a subset of the available events (event filtering), this can be set in the header 
section of the mini calendar file (display0.php).&lt;/p&gt;
&lt;p&gt;Via the CSS styles of your site (the parent page of the mini calendar), the class &lt;kbd&gt;lcmini&lt;/kbd&gt; can be 
used to position and define the style of the iframe containing the mini calendar. The style for class 
&lt;kbd&gt;lcmini&lt;/kbd&gt; could for instance look as follows:&lt;/p&gt;
&lt;code&gt;iframe.lcmini { position:absolute; right:100px; top:15%; width:210px; height:233px; overflow:hidden;}&lt;/code&gt;
&lt;p&gt;If you want the height of the mini calendar to vary automatically depending on the month to display (4, 5 or
6 weeks) you should add the following JavaScript code, which dynamically adjusts the height of the iframe, to the
&lt;kbd&gt;&amp;lt;head&amp;gt;&lt;/kbd&gt; section of the parent web page:&lt;/p&gt;
&lt;code&gt;
&amp;lt;script type=&quot;text/javascript&quot;&amp;gt; function setHeight(newHeight){document.getElementById('display0').style.height=newHeight+((document.all)?8:0)+'px';}&amp;lt;/script&amp;gt;
&lt;/code&gt;
&lt;p&gt;&lt;b&gt;Please note&lt;/b&gt;: Automatic adjusting of the iframe height only works if the calendar is located in the
same domain as the parent page. If not, the iframe height is set to cope with displaying 6 weeks.&lt;/p&gt;

&lt;a id=&quot;lbl-6d&quot;&gt;&lt;/a&gt;&lt;h5&gt;d. Embed the Full Calendar&lt;/h5&gt;
&lt;p&gt;To embed the full LuxCal calendar in an existing web page, an inline frame (iframe) can be used. This can
for example be done with the following HTML code:&lt;/p&gt;
&lt;code&gt;&amp;lt;iframe id=&quot;luxcal&quot; src=&quot;http://www.mysite.xx/luxcal/?cP=2&quot;&amp;gt;&amp;lt;/iframe&amp;gt;&lt;/code&gt;
&lt;p&gt;With parameter &lt;kbd&gt;cP&lt;/kbd&gt; the default view can be set (e.g. year: &lt;kbd&gt;cP=1&lt;/kbd&gt;, month: &lt;kbd&gt;cP=2&lt;/kbd&gt;, . . . ,upcoming:
&lt;kbd&gt;cP=7&lt;/kbd&gt;)&lt;/p&gt;
&lt;p&gt;If you want to display a subset of the available events, see &quot;Applying Filters to the Calendar&quot; below.&lt;/p&gt;
&lt;p&gt;Via the CSS styles of your site, the id &lt;kbd&gt;luxcal&lt;/kbd&gt; can be used to position and define the style of the
iframe containing the luxcal calendar. The style for id &lt;kbd&gt;luxcal&lt;/kbd&gt; could for instance look as follows:&lt;/p&gt;
&lt;code&gt;#luxcal { width:80%; height:800px; margin:20px; border-style:solid; border-width:1px; border-color:grey; }&lt;/code&gt;

&lt;a id=&quot;lbl-6e&quot;&gt;&lt;/a&gt;&lt;h5&gt;e. Embed One Specific Calendar View without Navigation Bar&lt;/h5&gt;
&lt;p&gt;To embed the LuxCal calendar without navigation bar, the parameter &lt;kbd&gt;hdr=0&lt;/kbd&gt; should be added to the
URL as follows:&lt;/p&gt;
&lt;code&gt;&amp;lt;iframe src=&quot;http://www.mysite.xx/luxcal/?hdr=0&amp;amp;cP=2&quot;&amp;gt;&amp;lt;/iframe&amp;gt;&lt;/code&gt;
&lt;p&gt;If the navigation bar is suppressed by adding &lt;kbd&gt;hdr=0&lt;/kbd&gt; to the URL, the visitor will not be able to 
navigate the calendar and select other views.&lt;br&gt;
To suppress the calendar header, but leave the navigation links in the various views enabled, &lt;kbd&gt;hdr=-1&lt;/kbd&gt;
should be added to the calendar URL. In this case the header will be suppressed, but the user will still be able 
to go to other views via the links in the calendar body: e.g. by clicking the week number or the date in the 
day cells.&lt;/p&gt;
&lt;p&gt;The following parameters can be added to select the view to display and the user-interface language:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;kbd&gt;cP&lt;/kbd&gt; to set the view (e.g. year: &lt;kbd&gt;cP=1&lt;/kbd&gt;, month: &lt;kbd&gt;cP=2&lt;/kbd&gt;, . . . , upcoming:
&lt;kbd&gt;cP=7&lt;/kbd&gt;)&lt;/li&gt;
&lt;li&gt;&lt;kbd&gt;cL&lt;/kbd&gt; to set the user-interface language (e.g. French: &lt;kbd&gt;cL=Francais&lt;/kbd&gt;). The specified
language must be present in the &lt;kbd&gt;lang/&lt;/kbd&gt; folder)&lt;/li&gt;
&lt;/ul&gt;
&lt;br&gt;
&lt;p&gt;For example the HTML code to show the Upcoming Events page without navigation bar, in the French language
looks as follows:&lt;/p&gt;
&lt;code&gt;&amp;lt;iframe id=&quot;luxcal&quot; src=&quot;http://www.mysite.xx/luxcal/?hdr=0&amp;amp;cP=7&amp;amp;cL=Francais&quot;&amp;gt;&amp;lt;/iframe&amp;gt;&lt;/code&gt;
&lt;p&gt;Via the CSS styles of your site, the id &lt;kbd&gt;luxcal&lt;/kbd&gt; can be used to position and define the style of the
iframe containing the LuxCal calendar. The style for id &lt;kbd&gt;luxcal&lt;/kbd&gt; could for instance look as follows:&lt;/p&gt;
&lt;code&gt;#luxcal { width:80%; height:800px; margin:20px; border-style:solid; border-width:1px; border-color:grey; }&lt;/code&gt;
&lt;p&gt;&lt;b&gt;Important:&lt;/b&gt;
&lt;br&gt;
The parameter &lt;kbd&gt;hdr=x&lt;/kbd&gt; is remembered via the PHP session mechanism; this means that if you access
the embedded calendar without navigation bar, then thereafter, when accessing your normal (not-embedded)
calendar when your session is still active (max. one hour) you will also see no navigation bar. This can be
solved by adding the parameter &lt;kbd&gt;hdr=1&lt;/kbd&gt; to the URL of your normal calendar.&lt;/p&gt;
&lt;p&gt;If you want to display a subset of the available events, see &quot;Applying Filters to the Calendar&quot; below.&lt;/p&gt;

&lt;a id=&quot;lbl-6f&quot;&gt;&lt;/a&gt;&lt;h5&gt;f. Embed a so-called Calendar &quot;Display&quot;&lt;/h5&gt;
&lt;p&gt;Since LuxCal version 4.5.1 a number of so called &quot;displays&quot; have been developed for the calendar.&lt;/p&gt;
&lt;p&gt;A display in this context is a single-file self contained program, which can be embedded in your web 
page using an inline frame (&amp;lt;iframe&amp;gt;), presenting the calendar events in an attractive user interface. 
Displays can also be viewed on mobile devices and will show the calendar events in a fancy user interface 
without the overhead of headers, bars and buttons.&lt;/p&gt;
&lt;p&gt;Embedding a display in your web page is very easy; it's just a matter of inserting an inline frame in 
your web page with a link to the desired display file, which must be located in the calendar root folder. 
To view a display on your mobile device, nothing needs to be done; make shure the desired display is 
located in the calendar root folder and on your mobile device just browse to the display file installed 
on your server.&lt;/p&gt;
&lt;p&gt;Displays work out of the box and are highly configurable. Each display program file has an easy to use 
configuration section, which allows you to specify which events and event fields should be shown and to 
tailor the user interface colors and text.&lt;/p&gt;
&lt;p&gt;Displays use the calendar settings, like date format, time format, first day of the week, etc.&lt;/p&gt;
&lt;p&gt;On the &quot;Displays&quot; page of the LuxSoft website you will find more information about displays and a 
demonstration of the currently available displays.
&lt;/p&gt;

&lt;a id=&quot;lbl-6g&quot;&gt;&lt;/a&gt;&lt;h5&gt;g. Applying Filters to the Calendar&lt;/h5&gt;
&lt;p&gt;When using a link to the calendar or embed the full calendar, parameters can be added to the calendar URL 
to specify which events hould be shown. When adding parameters, the following syntax should be used: The 
first parameter starts with a '?' and parameters are separated by an '&amp;', like:
&lt;kbd&gt;www.mysite.net/calendar?par1=3&amp;par2=7&lt;/kbd&gt;. If a parameter can have several values it can be passed as an 
array by adding square brackets toe the parameter name, like: &lt;kbd&gt;www.mysite.net/calendar?par1[]=3&amp;par1[]=7&lt;/kbd&gt;.&lt;/p&gt;
&lt;p&gt;Parameter cG can be added to the URL to specify the IDs of one or several user groups for which events 
should be displayed. Parameter cC can be added to the URL to specify the IDs of one or several event categories 
for which events should be displayed. The user group IDs and event category IDs can be found on the admin's 
User Group page and Categories page respectively. For example, to specify a user group, with ID 4 the parameter 
&lt;kbd&gt;&quot;?cG[]=4&quot;&lt;/kbd&gt; should be added to the URL. If the events of a second user group, for instance, with ID 6 
should be displayed as well, then &lt;kbd&gt;&quot;?cG[]=4&amp;cG[]=6&quot;&lt;/kbd&gt; should be added to the URL. The same counts for the
cC parameter when specifying one or more event categories to show.&lt;/p&gt;
&lt;p&gt;Example:&lt;br&gt;
If you want to display a calendar without header (navigation bar) showing events from users in the user groups 
with IDs 4 and 7 and only showing events in event category 2, then the link should be like:
&lt;kbd&gt;www.mysite.net/calendar?hdr=0&amp;cG[]=4&amp;cG[]=4&amp;cC[]=2&lt;/kbd&gt;.

&lt;a id=&quot;lbl-6h&quot;&gt;&lt;/a&gt;&lt;h5&gt;h. Single Sign On (SSO)&lt;/h5&gt;
&lt;p&gt;When the calendar is embedded in a PHP-based website where users have to log in, users logged in on the
parent website can be logged in to the calendar automatically in a secure way, using PHP sessions.&lt;/p&gt;
&lt;p&gt;To achieve this the parent website scripts should:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;start PHP sessions, if not done already, by adding the following PHP statement to the parent website
PHP script:&lt;br&gt;&lt;code&gt;session_name('PHPSESSID');&lt;br&gt;session_start();&lt;/code&gt;
PHP sessions must be started before anything is sent out to the browser (like header information), so this
statement must be added somewhere at the start of the script.&lt;/li&gt;
&lt;li&gt;save the user name or the user email address in the session variable 'lcUser' by adding the following
statement to the parent website PHP script at any point before the iframe statement with the calendar URL:
&lt;code&gt;$_SESSION['lcUser'] = '&amp;lt;user email&amp;gt;';&lt;/code&gt;The part &lt;kbd&gt;&amp;lt;user email&amp;gt;&lt;/kbd&gt; is a string 
with the user email address which corresponds to the email address required to log the user in to the calendar 
(specified by the admin when the calendar user account was created).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Because PHP session data are stored on the server, the user name / email address are not visible to
the users.&lt;/p&gt;
&lt;br&gt;&lt;h5&gt;&amp;nbsp;- End of Installation 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/bookingnew">← Geri</a>