Highlights
This new LuxCal version 4.7.9 includes interesting new features, improved technical issues and bug-fixes.
Most important new features / improvements:
• Various improvements for the stand-alone displays. E.g. More flexible styling possibilities, filtering on event sub-categories, for birthdays automatic display of age, favicon possible.
• More flexibility to tailor the event title in month, week and day view, including and option for birthdays to automatically display the age of the person in your own format.
• The side bar information messages for each month have been grouped together in one file called info.txt. Messages can now be displayed during one single month or during several months.
This new release has been tested again with the help of John from Denmark. Thank you John, you're a hero!
Hereafter you will find a full summary of all changes since LuxCal version 4.7.8.
New features/Improvements
• Stand-alone displays: More flexible styling possibilities. 1) The margins of the event container, containing the event head and body, can now be specified separately. 2) The font attributes of the "No events" text can be specified separately and the text has no background color anymore.
• Stand-alone displays: The possibility to filter events on event subcategories has been added.
• Stand-alone displays: For all displays a new configuration parameter has been added to specify a favicon.
• Stand-alone displays: An option has been added for displays to show for birthdays the age of a person in the event title. E.g. "Harry Potter (18)".
• An option has been added for month, week and day view to add for birthdays the age of a person to the event title. On the settings page you can add the key #a to the Event layout templates. If an event in an event category with "Repeat" set to "every year" has a year of birth in parentheses, e.g. (1982), specified somewhere in it's description field, the key #a in the event layout template will be replaced by the age of the person, which is the difference between the year of birth and the year of the calendar date. E.g. "Harry Potter (18)".
• In the views Upcoming Events and Changes, if an event in an event category with "Repeat" set to "every year" has a year of birth in parentheses, e.g. (1982), specified somewhere in it's description field, the age of that person will be shown in parentheses at the end of the event title.
• The event layout template for Month, Week and Day view has been improved. It now accepts separators (|-character) to split the template in different sections. If in a section with a #-parameter this parameter results in an empty string, then the whole section will be omitted and not be displayed. The template may also contain HTML tags; e.g. <b>#e</b>.
• On the Log-in page and the admin pages a Help button has been added on the right side of the Navigation Bar. On these pages it is not so obvious to open the side menu and select Help to get to the User Guide.
• When the matrix views are loaded, the focus is given to the matrix part of the page, so that the left/right arrow keys can directly be used to scroll the matrix left and right. This doesn't work in Chrome.
• The information messages for each month have been grouped together in one file called info.txt, rather than 12 individual files. It is now possible to define messages to be displayed during one single month or during several months.
• In the calendar URL, when using the cC parameter, it is now possible to specify negative event category sequence numbers for event categories that should be excluded from the calendar (e.g. ?cC[]=-2, &cC[]=-4).
• Drag functions to drag the Todo, To Approve and Upcoming Events lists have improved. The sidebars can not be moved out of the window anymore, they moves smoother and the text in the header cannot unintentionally be selected anymore.
• For the Todo list it is now possible to specify on the settings page the number of days to look back.
Technical issues
• On the admin's settings page, the width of the center box with the field sets was fixed 900px, but is now variable, which avoids field set lines to be wrapped when using languages with longer texts.
Bug fixes
• 01. pdfclass1.php, pdfclass2.php: If in the configuration settings for the pdf print layout no event body fields were specified, then the starting position of the event time(s) was always reset to the left margin.
• The connection to the calendar database was established before a possible pdf.cnf file was included and therefore the $calID setting from the pdf.cnf file did not overrule the default setting.
• The red X in the right upper corner of the User Guide window did not work anymore (since V4.7.7). Solved.
• In the past for new calendar installations the user interface language for the Public User was set to English, fixed. From now on the language for the Public user is left blank, which means the default language specified on the Settings page is taken.
• Stand-alone displays: The user interface language file used in the displays was the one corresponding to the default language on the admin's settings page. However, since the option to login has been added to the displays, the language file should correspond to the language specified in the account of the user.
• When the side panel was enabled, in week and day view the mini calendar in the side bar always showed the work days only, also when the main week view showed the full week.
• When validating the user name in email and sms recipients lists, "\u" was used to specify the range of accented characters. However "\u" is not supported by PCRE. Changed to "\x{}".
• When separating fields of an imported file, if a separator character is escaped by a backslash, the backslash character was not removed from the the field. Solved by using the PHP str_getcsv function, rather than the preg_split function.
• In display0 (the mini-calendar) one could just move one month forward or backward, a next click on the arrows showed the message 'not permitted (display0)'. Solved by replacing REQUEST_URI by PHP_SELF.
• In the event description it is now possible to use image with more than one dot in the file name, for example: pink.2020.png.
