Location: PHPKode > scripts > LuxCal Web Based Event Calendar > release_notes_luxcal_past_versions.html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
	"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>LuxCal Installation and Configuration Guide</title>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<link rel="shortcut icon" href="lcal.ico">
<style type="text/css">
* { padding:0; margin:0; }
body {
	font: 12px arial, helvetica, sans-serif;
	background: #E0E0E0;
	color: #2B3856;
}
h1 { font-size: 18pt; text-shadow: grey 0.2em 0.3em 0.2em; }
h3 { margin: 20px 0 10px 0; font-size: 14pt; }
h4 { margin: 10px 0 0 0; font-size: 12pt; }
h5 { margin: 10px 0 0 0; font-size: 11pt; }
h6 { margin: 10px 0; font-size: 10pt; }
ul { margin: 0 20px; }
li { margin: 10px 0; }
.top { background: #F2F2F2;	padding: 10px; }
.floatR { float: right; }
.marginLR { margin: 0 40px; }
.navBar {
	width: 100%;
	background: #AAAAFF;
	padding: 0px 10px;
	border-top: 1px solid #808080;
	border-bottom: 1px solid #808080;
	line-height: 30px;
	vertical-align: middle;
}
.endBar {
	clear: left;
	background: #AAAAFF;
	padding: 0px 10px;
	text-align: right;
	border-top: 1px solid #808080;
	border-bottom: 1px solid #808080;
}
.content { padding: 10px; }
.flag { color: #FF3300; }
.redFlag { color: #DD3300; }
</style>
</head>

<body>
<div class="top">
<h4 class="floatR">a LuxSoft product</h4>
<h1>LuxCal Event calendar</h1>
</div>
<table class="navBar"><tr><td width="40%" align="right">&nbsp;</td></tr></table>
<div class="content marginLR">

<center><h3>Release Notes / Change Log</h3></center>
<!--
<br />
<center><h4 class="redFlag">THIS IS NOT THE LATEST VERSION OF LUXCAL</h4></center>
<center><h4 class="redFlag">FOR THE LATEST VERSION GO TO <a href="http://www.luxsoft.eu">LUXSOFT</a></h4></center>
<br />
-->
<br /><h4>Installation Instructions - First Time</h4>
<p>For first-time installations of the LuxCal Event Calendar, follow the instructions 
in the <kbd>installation_guide.html</kbd>.</p>
<br />
<h4>Installation Instructions - Upgrade to a new version</h4>
<p>To upgrade your LuxCal calendar to a new version follow the Upgrade Instructions 
under the release below.</p>
<br />
<h4>LuxCal 2.2.0 - Release date: 2010.08.26</h4>
<h5>Upgrade Instructions</h5>
<h6 class="redFlag">Note: Upgrading from LuxCal 2.1 to LuxCal 2.2 is safe and will NOT affect the database contents.</h6>
<br />
<p>If you are upgrading from version 2.1 or older, carefully follow the next steps:</p>
<p>1. Make a backup copy of the <kbd>config.php</kbd> file located in the calendar root 
on the server of your hosting provider.</p>
<p>2. If you have tailored the COLOR AND FONT DEFINITIONS in the style sheet file, make 
a backup of the <kbd>css/css.php</kbd> file and apply the changes to the new 
<kbd>css/css.php</kbd> file after successful installation.</p>
<p>3. If you have translated the language files, then back up your language files 
<kbd>ui-{language}.php</kbd> and <kbd>ug-{language}.php</kbd> and read the section 
Language Files hereafter.</p>
<p>4. Delete all LuxCal files and folders from the server, <span class="redFlag">
<b>EXCEPT THE FILE <kbd>config.php</kbd> IN THE ROOT DIRECTORY</b></span>.</p>
<p>5. Unzip the downloaded file <kbd>luxcal210.zip</kbd> and upload all files and 
folders to the calendar root on the server.</p>
<p>6. Start the calendar by pointing your browser to the calendar root on the server.</p>
<p>7. If the calendar is displayed successfully, delete the following files from the 
calendar root: <kbd>install.php</kbd> and <kbd>upgrade22.php</kbd></b></p>
<p>8. The <kbd>config.php</kbd> file in the calendar root on the server has changed. 
Make a backup copy.</p>

<h5>Language Files</h5>
<p>You should be aware of the following if you have translated the user interface 
language files <kbd>ui-{language}.php</kbd> and <kbd>ug-{language}.php</kbd> into 
an other language.</p>
<p>The following language files exist per language: ({lang} is the name of the 
language)</p>
<ul>
<li>lang/ug-{lang}.php files: User guides for the calendar users</li>
<li>lang/ui-{lang}.php files: User interface language files</li>
<li>lamg/ai-{lang}.php files: Admin pages interface files</li>
</ul>
<p>The language files included in the <kbd>luxcal22.zip</kbd> download file are up to date with 
LuxCal 2.2.</p>
<p>For certain languages we could not translate all new and changed texts. These texts were added / 
changed in English and still need to be translated.</p>
<p>If you have your own translated language files, back up your files, update the new language files 
in line with your translated language files and restore the files to the <kbd>lang/</kbd> directory 
on the server after the installation of LuxCal 2.2.</p>
<h5>Changed Files</h5>
<p>== all .php, .html and .js files ==</p>
<h5>Change Log</h5>
<ul>
<li><b>Back buttons added and usernames and passwords validated</b><br />
A "back" buttons has been added to the users and categories pages. Usernames and passwords are now 
validated.
</li>
<li><b>Duplication of events</b><br />
In the Event window a "leave this window open" checkbox and a new "save as new event" button have 
been added. This makes it possible for a user re-use currently displayed event data, modify 
certain fields - e.g. the data - and save the modified event as a new event. This can be done 
repeatedly to duplicate events.
</li>
<li><b>"Notify Now" check box in Add / Edit Event window</b><br />
A "Notify Now" check box has been added to the Event window. In addition to the normal notify 
capability to send an email reminder to a (list of) email address(es), the user can now tick a 
check box to immediately send an email notification when adding, editing or deleting an event.
</li>
<li><b>Resolution of PHP E_Notices</b><br />
When processing scripts, PHP produces so called E_Notices whenever it encounters situations where 
the attention of the programmer is required (e.g. when referencing undefined variables). E_Notices 
normally don't cause problems but nevertheless should be avoided as much as possible. All LuxCal 
scripts have now been scrutinized to avoid PHP E_Notices, resulting in more stable and "cleaner" 
program scripts.
</li>
<li><b>Language files updated</b><br />
The language files ug-{lang}.php and ai-{lang}.php have been updated in line with LuxCal 2.2.
</li>
<li><b>Cosmetic improvements:</b>
<br />- User interface texts (missed out last time) on the Settings and iCal import pages moved 
to the language files.
<br />- 'set default timezone' added to the sendchg.php script.
<br />- Throughout all scripts the testing on empty date / time fields has been simplified. 
<br />- Box sizes on the Settings page increased because some languages need more space. 
<br />- Added to event window: display warning message if repeat end date < event start date. 
</li>
<li><b>Bug fixes</b>
<br /> - Header problem (day of week not displayed) on the Changes page solved.
<br /> - Processing of start time / end time for multi-day events when start date <> end date.
<br /> - For multi-day events display blank times as "" (empty string) and not as "99:00".
<br /> - Non-existing categories of imported CSV events are reset to 0 (no cat).
</li>
</ul>
<br />
<h4>LuxCal 2.1.0 - Release date: 2010.07.31</h4>
<h5>Upgrade Instructions</h5>
<h6 class="redFlag">Note: Upgrading from LuxCal 2.0 to LuxCal 2.1 is safe and will NOT affect the database contents.</h6>
<br />
<p>If you are upgrading from version 2.0 or older, carefully follow the next steps:</p>
<p>1. Make a backup copy of the <kbd>config.php</kbd> file located in the calendar root on the server of your hosting provider.</p>
<p>2. If you have tailored the COLOR AND FONT DEFINITIONS in the style sheet file, make a backup of the <kbd>css/css.php</kbd> file and apply the changes to the new <kbd>css/css.php</kbd> file after successful installation.</p>
<p>3. If you have translated the language files, then back up your language files <kbd>ui-{language}.php</kbd> and <kbd>ug-{language}.php</kbd> and read the section Language Files hereafter.</p>
<p>4. Delete all LuxCal files and folders from the server, <span class="redFlag"><b>EXCEPT THE FILE <kbd>config.php</kbd> IN THE ROOT DIRECTORY</b></span>.</p>
<p>5. Unzip the downloaded file <kbd>luxcal210.zip</kbd> and upload all files and folders to the calendar root on the server.</p>
<p>6. Start the calendar by pointing your browser to the calendar root on the server.</p>
<p>7. If the calendar is displayed successfully, delete the following files from the calendar root: <kbd>install.php</kbd> and <kbd>upgrade21.php</kbd></b></p>
<p>8. The <kbd>config.php</kbd> file in the calendar root on the server has changed. Make a backup copy.</p>

<h5>Language Files</h5>
<p>You should be aware of the following if you have translated the user interface language files 
<kbd>ui-{language}.php</kbd> and <kbd>ug-{language}.php</kbd> into an other language.</p>
<p>The language files in LuxCal 2.1 have been reorganised as follows: ({lang} is the name of the language)</p>
<ul>
<li>lang/ug-{lang}.php files: User guides for the calendar users</li>
<li>lang/ui-{lang}.php files: User interface language files</li>
<li>lamg/ai-{lang}.php files: Admin pages interface files</li>
</ul>
<p>The language files included in the <kbd>luxcal21.zip</kbd> download file are up to date with 
LuxCal 2.1.</p>
<p>For certain languages we could not translate all new and changed texts. These texts we added / 
changed in English and are marked by two slashes (//). They still need to be translated.</p>
<p>If you have your own translated language files, back up your files, update the new language files 
in line with your translated language files and restore the files to the <kbd>lang/</kbd> directory 
on the server after the installation of LuxCal 2.1.</p>
<h5>Changed Files</h5>
<p>== all .php, .html and .js files ==</p>
<h5>Change Log</h5>
<ul>
<li><b>Import and export of iCalendar files</b><br />
An import / export capability for iCalendar (.ics) files to enable the exchange of calendar events 
between LuxCal and other calendars. This would also be useful to import for instance ics-files with 
public holidays available in iCal format on the web.
</li>
<li><b>'CSV Import' page improved</b><br />
Different date and time formats can now be selected when importing a file. The validation of input 
data is more complete and the user interface has been improved. Furthermore measures have been taken 
to avoid double/triple/etc. upload of the same events. The user-interface texts of the CSV Import 
page have been separated from the script and moved to the language file.
</li>
<li><b>User self-registration</b><br />
A possibility for users to self-register. The user should submit his/her name and email address, and 
the self-registration function will then email a password.
The administrator will be able to enable/disable the self-registration function and set the access 
rights for self-registered users.
</li>
<li><b>RSS-feeds</b><br />
RSS-feeds showing the most recent calendar changes (events added, edited or deleted) during the last 
2 weeks will be available to users having read access. Events marked as "private" will not be shown.
</li>
<li><b>Display event owner</b><br />
In the event hover box and on the pages where event details are displayed, the name of the event 
owner is displayed as well.
</li>
<li><b>'Login' page inproved</b><br />
The Login page has been completely restructured and been made more user-friendly. The main page is 
for Logging in only. From the main page unregistered users can go to a registration page (if enabled 
by the administrator) and registered users can go to a page to change their personal data (user name, 
email address and password).
</li>
<li><b>'Settings' page improved</b><br />
The user interface of the Settings page has been completely restructured and much improved. Some new 
settings have been added (see other changes in this post). On request of several users: The 
user-interface texts of the Settings page have been separated from the settings.php script and moved 
to the language file.
</li>
<li><b>Parameters for "send calendar changes"-script moved to 'Settings' page</b><br />
It appeared that users of LuxCal 2.0, who use the new sendchg.php script to receive email 
notifications of calendar changes (added/edited and deleted events) tend to forget to populate the 
destination email list inside the script file. This destination email list and the number of days to 
look back for changes, have been moved to the new Settings page.
</li>
<li><b>Performance:</b><br />
To avoid a too big language file, the ui-{lang}.php language file has been split in two separate 
files (per language). One file for the "calendar" pages and an other for the "admin" pages.
</li>
<li><b>Cosmetic improvements:</b>
<br />- minor changes to make the navigation bar even more simple
<br />- improved user-interface of users page and categories page
<br />- Name of Public User now language dependent (via language file) 
</li>
</ul>
<br />
<h4>LuxCal 2.0 - Release date: 2010.05.30</h4>
<h5>Upgrade Instructions</h5>
<h6>Note: Luxcal 2.0 is a major upgrade with changes in the structure of several database tables required for the advanced repeat capability and in anticipation of future improvements.
<br />After installation, when starting LuxCal 2.0, the database structure will automatically be updated and for existing recurring events changes will be applied required for the new enhanced repeat capability.</h6>
<p class="redFlag">It is recommended to backup your database tables before running LuxCal 2.0.</p>
<br />
<p>If you are upgrading from version 1.8 or older, carefully follow the next steps:</p>
<p>1. Make a backup copy of the <kbd>config.php</kbd> file located in the calendar root on the server of your hosting provider.</p>
<p>2. If you have tailored the COLOR AND FONT DEFINITIONS in the style sheet file, make a backup of the <kbd>css/css.php</kbd> file and apply the changes to the new <kbd>css/css.php</kbd> file after successful installation.</p>
<p>3. If you have translated the language files, then back up your language files <kbd>ui-{language}.php</kbd> and <kbd>ug-{language}.php</kbd> and read the section Language Files hereafter.</p>
<p>4. Delete all LuxCal files and folders from the server, <span class="redFlag"><b>EXCEPT THE FILE <kbd>config.php</kbd> IN THE ROOT DIRECTORY</b></span>.</p>
<p>5. Unzip the downloaded file <kbd>luxcal20.zip</kbd> and upload all files and folders to the calendar root on the server.</p>
<p>6. Start the calendar by pointing your browser to the calendar root on the server.</p>
<p>7. If the calendar is displayed successfully, delete the following files from the calendar root: <kbd>install.php</kbd> and <kbd>upgrade20.php</kbd></b></p>
<p>8. The <kbd>config.php</kbd> file in the calendar root on the server has changed. Make a backup copy.</p>

<h5>Language Files</h5>
<p>You should be aware of the following if you have translated the user interface language files 
<kbd>ui-{language}.php</kbd> and <kbd>ug-{language}.php</kbd> into an other language.</p>
<p>The language files included in the <kbd>luxcal20.zip</kbd> download file are up to date with 
LuxCal 2.0. Changes with respect to the previous language files are marked by two slashes (//) in 
the new <kbd>ui-english.php</kbd> file.</p>
<p>For certain languages we could not translate all new and changed texts. These texts which are 
still in English, are marked by two slashes (//) and still need to be translated.</p>
<p>If you have your own translated language files, back up your files, update them in line with the 
English LuxCal 2.0 language files and restore your files to the <kbd>lang/</kbd> directory on the 
server after the installation of LuxCal 2.0.</p>
<h5>Changed Files</h5>
<p>== all .php, .html and .js files ==</p>
<h5>Change Log</h5>
<ul>
<li><b>Enhanced repeat function</b><br />
Significant enhancement of the repeat function. It will be possible to repeat an event:
<br />a. every / every other / every third / every fourth day / week / month / year, 
<br />b. every first / second / third / fourth / last Monday / Tuesday / etc. of the month,
<br />until a certain date.
<br />
Multi-day events can be combined with the repeat capability.
</li>
<li><b>Display of multi-day events improved</b><br />
In month view multi-day events are now clearly indicated by "=>", "<=> and "<=", for the first day, 
the intermediate days and the last day respectively.
</li>
<li><b>User interface language selectable by the user</b><br />
If several user interface languages are installed, and if enabled on on the Settings page, the user 
can select his/her preferred language via a drop-down menu in the navigation bar. The language selected 
by a user will be remembered (through the PHP session mechanism).
</li>
<li><b>Display a list of added, edited or deleted events since a specified date</b><br />
A new view has been added to the Views drop-down menu which displays a list with calendar changes 
(added, edited and deleted events) since a specified date. For the administrator a new script 
<kbd>sendchg.php</kbd> is available, which can be run via a cron job, to automatically email 
calendar changes to a list of email addresses. This script could be run for instance once a day.
</li>
<li><b>Print buttons on Upcoming Events page</b><br />
Two print buttons, "Print Today" and "Print All", have been added to the Upcoming Events page. 
A printer-friendly page will be sent to the printer.
</li>
<li><b>Spring cleaning</b><br />
The retrieve function and the showgrid functions  have been significantly simplified. The passing 
of "current page", current date', "current cat" and "current language" all over the calendar are not 
needed anymore; just changes are passed.
</li>
<li><b>Various improvements</b>
<br />- Styles are applied to notification emails (reminders). The emails are now sent with a more attractive layout.
<br />- The max. length of the email list for notification emails (reminders) has been extended from 64 to 256 characters.
<br />- Max. width of hoverbox: When no CRLFs are used in long descriptions of events,text wrapping will be applied if a certain max. width is exceeded.
<br />- The text 'Notify x day(s)' in the hover box is only displayed for users who have 'post all' or 'admin' rights.
<br />- Better validation of dates entered in forms, incl. leap year
<br />- And various other improvements and minor bug fixes. </li>
</ul>
<br />
<h4>LuxCal 1.8 - Release date: 2010.03.28</h4>
<h5>Upgrade Instructions</h5>
<h6 class="redFlag">Note: Upgrading to LuxCal 1.8 is safe and will NOT affect the database contents.</h6>
<p>If you are upgrading from version 1.7 or older, carefully follow the next steps:</p>
<p>1. Make a backup copy of the <kbd>config.php</kbd> file located in the calendar root on the server of your hosting provider.</p>
<p>2. If you have tailored the COLOR AND FONT DEFINITIONS in the style sheet file, make a backup of the <kbd>css/css.php</kbd> file and apply the changes to the new <kbd>css/css.php</kbd> file after successful installation.</p>
<p>3. If you have translated the language files, then back up your language files and read the section 'Language Files' below.</p>
<p>4. Delete all LuxCal files and folders from the server, <b>EXCEPT THE FILE <kbd>config.php</kbd> IN THE ROOT DIRECTORY</b>.</p>
<p>5. Unzip the downloaded file <kbd>luxcal18.zip</kbd> and upload all files and folders to the calendar root on the server.</p>
<p>6. Start the calendar by pointing your browser to the calendar root on the server.</p>
<p>7. If the calendar is displayed successfully, delete the following files from the calendar root: <kbd>install.php</kbd> and <kbd>upgrade18.php</kbd></b></p>
<p>8. The <kbd>config.php</kbd> file in the calendar root on the server has changed. Make a backup copy.</p>
<br />
<h5>Language Files</h5>
<p class="redFlag">You should read this section if you have translated, or want to translate the user 
interface language files into an other language.</p>
<p>The location and the names of the files related to the user interface language have changed. The 
selection of a user interface language in the settings page has been simplified.</p>
<p><b>Location and File Names</b></p>
<p>All language files are stored in the <kbd>lang/</kbd> directory on the server.</p>
<p>Per language the following files exist:</p>
<ul>
<li><kbd>ui-{language}.php</kbd>. This file contains the user interface texts. The part <kbd>{language}</kbd> 
including the braces is the name of the language in lower case characters. For example: 
<kbd>ui-english.php</kbd></li>
<li><kbd>ug-{language}.php</kbd>. This file contains the user guide. The part <kbd>{language}</kbd> 
including the braces is the name of the language in lower case characters.  For example: 
<kbd>ug-english.php</kbd></li>
<li><kbd>ug-layout.png</kbd>. This file contains the calendar layout image used by the user guide. This 
file is identical for each language and in case of multiple languages is only needed once in the 
<kbd>lang/</kbd> directory.</li>
</ul>
<p>If you have translated the language files in previous LuxCal versions, you should update your files, 
to match LuxCal version 1.8, rename your files to the names specified above, and upload your files to 
the <kbd>lang/</kbd> directory on the server.
<p><b>Selecting a UI-Language</b></p>
<p>On the Settings page the administrator can select one of the UI languages present in the 
<kbd>lang/</kbd> directory. The language is selected by specifying the {language} part of the files 
names as described above. On the Settings page the language name is case insensitive.</p>
<p>Example:<br />If the following files exist in the <kbd>lang/</kbd> directory: <kbd>ui-english.php</kbd>, 
<kbd>ug-english.php</kbd> and <kbd>ug-layout.png</kbd> the administrator should select <kbd>English</kbd> 
on the Settings page.</p>
<h5>Changed Files</h5>
<p>== all .php, .html and .js files ==</p>
<h5>Change Log</h5>
<ul>
<li><b>First day of the week selectable: Monday or Sunday</b><br />
New: Via the Settings page, the calendar administrator will be able to set the first day of the week 
to either Monday or Sunday. The first day of the week in the date-picker will change accordingly.
</li>
<li><b>URL hyperlink support</b><br />
New: URLs added in the description field of events will result in a separate line with the hyperlink 
in month view. The hyperlink can also be clicked in Upcoming Events view and in email notifications 
(reminders).
</li>
<li><b>Prefix for database table names</b><br />
New: During the installation process it is possible to enter a prefix for the database table names. 
This may be useful if you are short of databases and want to share the database with other applications 
or want to use several separate LuxCal calendars.
</li>
<li><b>Number of columns in year view configurable</b><br />
New: The number of months displayed per row in year view can be selected via the settings page. This is 
interesting when the calendar is embedded in an other web page and has a limited width.
</li>
<li><b>Easier selection of the user interface language</b><br />
Improved: The selection of the user interface language file and the user guide file in different languages via 
the settings page has been made easier and more flexible. When different languages have been installed, 
switching to an other language is very easy. Furthermore an explanation has been added in the 
installation instructions with regard to the use of special characters and the required character 
encoding.
</li>
<li><b>User interface language also used by the "date picker"</b><br />
New: The user interface language file will now also be used by the Date Picker (Javascript) for the months, 
day of the week and button texts.
</li>
<li><b>Various improvements</b>
<br />- The originator of notification emails (reminders) will now be the calendar email address 
specified on the Settings page and consequently can be changed.
<br />- Various small improvements and bug fixes.
</li>
</ul>
<br />
<h4>LuxCal 1.7 - Release date: 2010.03.08</h4>
<h5>Upgrade Instructions</h5>
<p>If you are upgrading from version 1.6 or older, carefully follow the next steps:</p>
<p>1. Make a backup copy of the <kbd>config.php</kbd> file located in the calendar root on the server of your hosting provider.</p>
<p>2. If you have tailored the COLOR AND FONT DEFINITIONS in the style sheet file, make a backup of the <kbd>css/css.php</kbd> file and apply the changes to the new <kbd>css/css.php</kbd> file after successful installation.</p>
<p>3. If you have translated the language file, then back up your language file; verify and update the file to match the new language file and upload the updated file after successful installation.</p>
<p>4. Delete all LuxCal files and folders from the server, <b>EXCEPT THE FILE <kbd>config.php</kbd> IN THE ROOT DIRECTORY</b>.</p>
<p>5. Unzip the downloaded <kbd>luxcal17.zip</kbd> file and upload all files and folders to the calendar root on the server.</p>
<p>6. Start the calendar by pointing your browser to the calendar root on the server.</p>
<p>7. If the calendar is displayed successfully, delete the following files from the calendar root: <kbd>install.php</kbd> and <kbd>upgrade17.php</kbd></b></p>
<p>8. The <kbd>config.php</kbd> file in the calendar root on the server has changed. Make a backup copy.</p>
<br />
<h5>Changed Files</h5>
<p>== all .php, .html and .js files ==</p>
<h5>Change Log</h5>
<ul>
<li><b>Multi-day events</b><br />
New: In addition to normal repetitive events, events can now span more 
than one day, for instance starting at a certain time on one day and ending at an other time on a next day.
</li>
<li><b>Event category filter</b><br />
New: An 'event category' filter enables the user to only display events 
in a selected category.
</li>
<li><b>Navigation bar - reduced size</b><br />
To better support embedded calendars with a limited width the 
items in the navigation bar have been reduced in size, i.e. the 'Views' buttons have been combined in a 
drop-down menu and to avoid space taken by 'submit' buttons, the drop-down menus and 'go to' input field 
have been made 'auto-submit'.
</li>
<li><b>Improved Add/Edit Event window layout</b><br />
The layout of the Add/Edit Event window has been improved and is now more logical.
</li>
<li><b>URL-hyperlink support</b><br />
When adding/editing events, URL-links in the event description are automatically converted to html 
hyperlinks. These hyperlinks can be clicked in the Upcoming Events view.
</li>
<li><b>Improved Notification feature</b><br />
- The feature to send email reminders (notifications) to users a 
certain number of days before an event is due has been significantly improved. Notifications are not 
any more sent automatically to the owner of the event, but a list of email addresses to be notified 
can be entered. The email address of the logged in user is automatically added to the list, but can be 
removed if desired.<br />
- Notification emails (reminders) will be sent the requested number of days before the event is due 
and automatically an other one will be sent on the day of the event, so in total two reminders will be 
sent.<br />
- Notification emails (reminders) now also contain the name of the sender (event owner).
</li>
<li><b>Log-in page changed</b><br />
The log-in page has changed; users will be able to log in either with 
their username or their email address and of course their password. Users will also be able to change 
their email address.
</li>
<li><b>Various improvements</b>
<br />- URLs in the event's description field will be automatically converted to hyperlinks, which can 
be selected in the Upcoming Events view.
<br />- The current day of the week and date are displayed in the calendar's top bar.
<br />- Notification (reminder) emails will be sent the requested number of days before the event is 
due and automatically an other one will be sent on the day of the event, so in total two.
<br />- Notification (reminder) emails also show the sender (owner) of the event.
<br />- The style and color of the (currently) red border of the current day can now be changed via 
the style sheet.
<br />- If in Month view the full month is displayed (selected via the Settings), the color of the 
days that are not part of the month being viewed can now be changed via the style sheet.
<br />- When the administrator deletes an event category, the events in this category will be 
automatically reset to 'no category'.
<br />- during CSV Upload, start time and end time are not compulsory any more. Blank start and end 
time will be set to 'all day' event.
<br />- Various small improvements and bug fixes.
</li>
</ul>
<br />
<h4>LuxCal 1.6 - Release date: 2010.02.08</h4>
<h5>Upgrade Instructions</h5>
<p>If you are upgrading from version 1.5 or older, carefully follow the next steps:</p>
<p>1. Make a backup copy of the <kbd>config.php</kbd> file located in the calendar root on the server of your hosting provider.</p>
<p>2. If you have tailored the COLOR AND FONT DEFINITIONS in the style sheet file, make a backup of the <kbd>css/css.php</kbd> file and apply the changes to the new <kbd>css/css.php</kbd> file after successful installation.</p>
<p>3. If you have translated the language file, then back up your language file; verify and update the parts for <kbd>event.php</kbd> and <kbd>users.php</kbd> and upload the language file after successful installation.</p>
<p>4. Delete all LuxCal files and folders from the server, <b>EXCEPT THE FILE <kbd>config.php</kbd> IN THE ROOT DIRECTORY</b>.</p>
<p>5. Unzip the downloaded <kbd>luxcal16.zip</kbd> file and copy all files and folders to the calendar root on the server.</p>
<p>6. Start the calendar by pointing your browser to the calendar root on the server.</p>
<p>7. If the calendar is displayed successfully, delete the following files from the calendar root on the server: <kbd>install.php</kbd> and <kbd>upgrade16.php</kbd></b></p>
<p>8. The <kbd>config.php</kbd> file in the calendar root on the server has changed. Make a backup copy.</p>
<br />
<p><b><span class="redFlag">Important! After upgrading, the access rights for each user should be checked and possibly updated via the Users page.</span></b>
<h5>Changed Files</h5>
<p>== all .php and .html files ==</p>
<h5>Change Log</h5>
<ul>
<li>
	<p>When: Adding and changing User Profiles</p>
	<p>Added: New access rights class. The access rights class "Post" has been split in "Post Own" and "Post All".</p>
	<p>Users with access rights "Post Own" and "Post All" can both post events. Users with access rights "Post Own" however, can only edit/delete his/her own events, whilst users with access rights "Post All" can edit/delete all events.</p>
	<p>The access rights "Post Own" will prevent users to edit/delete each others events.</p>
</li>
<li>
	<p>When: In all calendar views</p>
	<p>Improved: On the Settings page the format of all dates used in the headers of the calendar views can be set to US or European; Examples of US formats: Sunday, November 16, 2010 and Nov 16. Examples of European formats: Sunday 16 November 2010 and 16 Nov.</p>
	<p>This is a next step to make the calendar's 'look and feel' suitable for use in the US.</p>
	<p>The format of event dates and times was already configurable since LuxCal 1.5</p>
</li>
<li>
	<p>When: In Month views</p>
	<p>Added: On the Settings page one can set Month view to display exactly one full months, irrespective of what the current day of the month is.</p>
	<p>Clicking the backward and forward arrows above or below the currently displayed month will result in the display of the previous or next full month.</p>
</li>
<li>
	<p>When: Sending an email notification to a user (notify feature)</p>
	<p>Improved: The flexible date and time format introduced in LuxCal version 1.5 is now also applied to the dates and times in the email notifications sent to the user by the notify feature.</p>
</li>
<li>
	<p>When: On the Users page when changing/deleting users and user rights</p>
	<p>Improved: The Users page has been changed to prevent the administrator from deleting his/her own user account or removing his/her own administrator rights or removing his/her view access.</p>
</li>
<li>
	<p>When: NA.</p>
	<p>Fixed: Some bug fixes.</p>
</li>
</ul>
<br />
<h4>LuxCal 1.5 - Release date: 2010.01.18</h4>
<h5>Upgrade Instructions</h5>
<p>Copy the files that have changed in the new release (see below) to the correct locations on the server of your hosting provider.</p>
<p>In order not to forget one, it is better to copy all LuxCal files to the correct locations on the server of your hosting provider.</p>
<p>Be sure to leave the configuration file <kbd>config.php</kbd> on the server unchanged and do NOT copy the file <kbd>install.php</kbd> to the server.</p>
<p>If you have tailored the COLOR AND FONT DEFINITIONS in the style sheet file to you own preferences: Before copying a new style sheet file <kbd>css/css.php</kbd> to the server, first copy your changes to the new file.</p>
<p><b><span class="redFlag">Important! When upgrading from a previous LuxCal version: In addition to the Installation Instructions above, the lines between the +++lines hereafter must be added at the end of your config.php file in the LuxCal root on the server of your hosting provider:</span></b>
<pre>

++++++++++

// Date format (1: dd-mm-yyyy, 2: mm-dd-yyyy, 3: yyyy-mm-dd)
$dateFormat = 1;

// Date separator (. - or /)
$dateSep = ".";

// Time format (0: 12-hour am/pm, 1: 24-hour)
$time24 = 1;

++++++++++

</pre>
<h5>Changed Files</h5>
<p><kbd>release_notes_luxcal.html</kbd> (this file)</p>
<p><kbd>install.php</kbd>&nbsp;&nbsp;<b>(Only needed for new installations from scratch!)</b></p>
<p><kbd>index.php</kbd></p>
<p><kbd>installation_guide.html</kbd></p>
<p><kbd>css/css.php</kbd></p>
<p><kbd>canvas/header.php</kbd></p>
<p><kbd>canvas/header_s.php</kbd></p>
<p><kbd>pages/dt_functions.php</kbd>&nbsp;&nbsp;<span class="redFlag">New file!</span></p>
<p><kbd>pages/event.php</kbd></p>
<p><kbd>pages/uploadCSV.php</kbd></p>
<p><kbd>pages/settings.php</kbd></p>
<p><kbd>views/year.php</kbd></p>
<p><kbd>views/month.php</kbd></p>
<p><kbd>views/upcoming.php</kbd></p>
<p><kbd>views/dw_functions.php</kbd></p>
<p><kbd>js/dtpicker.js</kbd></p>
<h5>Change Log</h5>
<ul>
<li>
	<p>When: NA</p>
	<p>Added: The format of dates and times in the calendar views and input fields can now be selected by the calendar administrator via the Settings page in the Navigation bar.</p>
	<p>Supported date formats: dd.mm.yyyy, mm.dd.yyyy and yyyy.mm.dd.</p>
	<p>Supported date separators: dot ( . ), slash ( / ) and hyphen ( - ).</p>
	<p>Supported time formats: 12-hour am/pm format and 24-hour format.</p>
</li>
<li>
	<p>When: In Year and Month view.</p>
	<p>Added: "Forward" and "backward" arrows added at the end of the calendar view, to enable moving the view forward in time without the need to scroll up first.</p>
</li>
<li>
	<p>When: NA.</p>
	<p>Fixed: Some minor improvements.</p>
</li>
</ul>
<br />
<h4>LuxCal 1.4 - Release date: 2010.01.01</h4>
<h5>Upgrade Instructions</h5>
<p>Copy the files that have changed in the new release (see below) to the correct locations on the server of your hosting provider.</p>
<p>In order not to forget one, it is better to copy all LuxCal files to the correct locations on the server of your hosting provider.</p>
<p>Be sure to leave the configuration file <kbd>config.php</kbd> on the server unchanged and do NOT copy the file <kbd>install.php</kbd> to the server.</p>
<p>If you have tailored the COLOR AND FONT DEFINITIONS in the style sheet file to you own preferences: Before copying a new style sheet file <kbd>css/css.php</kbd> to the server, first copy your changes to the new file.</p>
<h5>Changed Files</h5>
<p><kbd>release_notes_luxcal.html</kbd></p>
<p><kbd>index.php</kbd></p>
<p><kbd>notify.php</kbd></p>
<p><kbd>installation_guide.html</kbd></p>
<p><kbd>css/css.php</kbd></p>
<p><kbd>canvas/header.php</kbd></p>
<p><kbd>canvas/header_s.php</kbd></p>
<p><kbd>lang/en_us.php</kbd></p>
<p><kbd>pages/guide.php</kbd></p>
<p><kbd>pages/event.php</kbd></p>
<p><kbd>pages/uploadCSV.php</kbd></p>
<p><kbd>pages/settings.php</kbd>&nbsp;&nbsp;<span class="redFlag">New file!</span></p>
<p><kbd>views/year.php</kbd></p>
<p><kbd>views/month.php</kbd></p>
<p><kbd>views/week.php</kbd></p>
<p><kbd>views/day.php</kbd></p>
<p><kbd>views/upcoming.php</kbd></p>
<p><kbd>views/dw_functions.php</kbd></p>
<h5>Change Log</h5>
<ul>
<li>
	<p>When: Available when logged in as administrator.</p>
	<p>Added: A new Settings page has been added. This page is available in the calendar's Navigation bar (top right) for the calendar administrator to easily change calendar layout settings (rather than editing the config.php file).</p>
</li>
<li>
	<p>When: During and after installation.</p>
	<p>Updated: Improved Installation Guide.</p>
</li>
<li>
	<p>When: When being visited by search engine robots.</p>
	<p>Updated: Prevent the LuxCal Calendar content from being indexed/followed by search engine robots.</p>
</li>
<li>
	<p>When: NA.</p>
	<p>Improved: Switch-over from ISO-8859-1 to utf-8 character encoding to improve international character support.</p>
</li>
<li>
	<p>When: NA.</p>
	<p>Improved: LuxCal is now ready for PHP6. All deprecated code has been replaced.</p>
</li>
<li>
	<p>When: In several Views.</p>
	<p>Fixed: Some minor layout problems fixed.</p>
</li>
<li>
	<p>When: NA.</p>
	<p>Fixed: Some bug fixes and administrative updates.</p>
</li>
</ul>
<br />
<h4>LuxCal 1.3 - Release date: 2009.12.01</h4>
<h5>Upgrade Instructions</h5>
<p>Copy the files that have changed in the new release (see below) to the correct locations on the server of your hosting provider.</p>
<p>In order not to forget one, it is better to copy all LuxCal files to the correct locations on the server of your hosting provider.</p>
<p>Be sure to leave the configuration file <kbd>config.php</kbd> on the server unchanged and do NOT copy the file <kbd>install.php</kbd> to the server.</p>
<p>If you have tailored the COLOR AND FONT DEFINITIONS in the style sheet file to you own preferences: Before copying a new style sheet file <kbd>css/css.php</kbd> to the server, first copy your changes to the new file.</p>
<h5>Changed Files</h5>
<p><kbd>release_notes_luxcal.html</kbd></p>
<p><kbd>index.php</kbd></p>
<p><kbd>installation_guide.html</kbd></p>
<p><kbd>notify.php</kbd></p>
<p><kbd>css/css.php</kbd></p>
<p><kbd>canvas/footer.php</kbd></p>
<p><kbd>js/dtpicker.js</kbd></p>
<p><kbd>pages/guide.php</kbd></p>
<p><kbd>pages/event.php</kbd></p>
<p><kbd>views/retrieve.php</kbd></p>
<h5>Change Log</h5>
<ul>
<li>
	<p>When: NA.</p>
	<p>Updated: Installation instructions for updates / new versions included.</p>
</li>
<li>
	<p>When: NA.</p>
	<p>Updated: Cascading Style Sheet reorganized and updated to meet changes for this release.</p>
</li>
<li>
	<p>When: When populating the various calendar views.</p>
	<p>Improved: efficiency / speed of retrieving recurring events for the calendar views.</p>
</li>
<li>
	<p>When: When adding / editing / deleting events.</p>
	<p>Fixed: In the event window the text "Start:" was not displayed in front of the start date input field.</p>
</li>
<li>
	<p>When: When running the script notify.php via a cronjob on the server.</p>
	<p>Fixed: For repetitive events ("Repeat" <> "none") notifications were only sent for the first occurence of the event. This has been solved; now notifications are sent for each repetition of an event.</p>
</li>
<li>
	<p>When: When using the date picker on the main calendar page or in the event window.</p>
	<p>Fixed: problem with the "<" (back) and ">" (forward) buttons on the Javascript date picker when passing year boundaries.</p>
</li>
<li>
	<p>When: NA.</p>
	<p>Fixed: Some bug fixes and administrative updates.</p>
</li>
</ul>
<br />
<h4>LuxCal 1.2 - Release date: 2009.10.17</h4>
<br />
<p>Initial controlled release.</p>
<p>No change log available.</p> 
</div>
<br />
<div class="endBar">
	<font size='1'>design 2010 - powered by </font><font size='2' color='#660066'><b><i>LuxSoft</i></b></font>
</div>
<br />&nbsp;
</body>
</html>

Return current item: LuxCal Web Based Event Calendar