Search options (Page 12 of 22)

Highlights

This new LuxCal version 4.7.8 includes interesting new features, improved technical issues and bug-fixes.
Most important new features / improvements:
• New function to print calendar events to a nicely formatted PDF file.
• Templates have been added to the settings page to specify the layout of events shown in Month, Week and Day view.
• The stand-alone "displays" have been revised and a log in and a PDF print option has been added.

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.7.

New features/Improvements
• A new PDF file printing facility has been added. When selecting the "PDF File" option in the calendar's side menu, a dialog box will appear where the user can select an A4 or A5 PDF file layout and can specify a start and end date; when clicking "OK", a PDF file with the events in the specified date bracket will be produced and offered for download. The printed content of the PDF file (fields to be printed, colors, etc.) is configurable to a high degree by the administrator.To avoid overwriting the configuration settings of the PDF prints, when upgrading to a new calendar version, the PDF configuration files reside in a new "configs" folder. Example PDF configuration files are available in the "samples" sub-folder.
• Two new templates have been added to the settings page, which are used to specify the fields and layout of the events to be displayed in Month view and Week/Day view respectively. Possible fields are: start time, start and end time, event owner, event title, venue, category, extra field 1 and extra field 2. For each of these fields a unique placeholder can be specified in the templates. In addition a special "new line" placeholder is available, so that the event fields can cover several lines. This new feature supersedes the "Show end time in Month view" setting, which therefore has been removed.
• All displays have been upgraded. Display0 - display3 have now a login option and display0, display1 and display2 have a PDF print option. When enabling the log in option, the user rights of the full calendar will apply. So it is for instance now possible to show more details to logged in users. The displays are distributed again with each new calendar version. This will ensure the compatibility of displays with the calendar.
• To avoid overwriting the configuration settings of displays, when upgrading to a new calendar version, the way to tailor the configuration settings of the displays has changed. The displayX.php scripts reside in the calendar's root folder, whilst the configuration files reside in a new "configs" folder. Example configuration files are available in a "samples" sub-folder.
• When enabled on the Settings page, week numbers will be added to the matrix and gantt chart views. The colors of the week days and dates have been aligned with all other headers and the column widths has been increased to make the weekday and date fit for all languages.
• The positioning of the hover box with event details has been improved for the mini calendar and the matrix views with event squares or symbols. Before it was difficult to move the mouse from the mini square to the hover box.
• The layout of the Log In form has been improved. In the previous version it could easily happen that when logging in the user clicked the "Send new password" button instead of the "Log in" button.
• On the Settings page the setting "Event colors based on category / user group" has moved from the Event section to the Views section and an option "no color" has been added.

Technical issues
• To avoid the need for a manual page refresh (Ctrl-F5) after a calendar upgrade, a toolbox.js and css.php reload is forced after a calendar upgrade by adding the calendar version number to the respective tags in the HTML head section.
• The color of the file selection input dialog text was not aligned with the color for buttons selected when styling the calendar and was with dark background colors difficult to read.
• There were several minor problems with the table columns in the event window, which could lead to problems with long event category names. Tables simplified and number of columns reduced. Dates were in some browsers not fully visible and have been given more space.
• iOS - mobile safari bug fix removed. This bug fix was required for old Safari versions. It was a meta name="viewport" tag sent before <!DOCTYPE html> which is not proper HTML.
• Style iframe.csHelp deleted. Style was not used anymore.
• PHP code for the top bar simplified and current date centered independent of calendar title length.
• In the backupDatabase function the INSERT INTO statement now includes a column list before VALUES, which makes the function less prone to SQL errors when using the .sql file to restore the database. The importSqlFile function has been improved to cope with large backup files with several INSERT queries per table. The counting of imported rows is now accurate.
• Measures have been taken to allow the lctools.php script to download calendar back up files.
• The folder for the side panel image files and info area files is now always the "sidepanel" folder and cannot be specified anymore on the Settings page. The files will not be overwritten with a calendar upgrade, because the example files are now stored in the "samples" sub-folder of the sidepanel folder.

Bug fixes
• The scrolling in the hover box with event details did not work.
• The variable $cat with the category parameters of the current event was not set correctly, which resulted in PHP notices, when using PHP 7.4.
• The color of the text on the Log In page took the color of the navigation bar; so if in the UI styling a light text color on the navigation bar was chosen, the text on the Log In page was hard to read.
• When installing the calendar, at the moment of initializing the styles table, the calendar title (assigned to the row "THEME") was not yet available in the settings ($set), which cause a PHP notice message when running PHP 7.4.
• In the makeE function, when producing the address button in the venue field, the full address was also show on narrow displays. This should be the other way around; the full address should be shown on wide displays only.

When running a PHP version > 7.3 on your server, you may get several of the following PHP notices when adding a new event:

"Notice: Trying to access array offset on value of type bool in /home/caregive/public_html/luxcal/pages/event.php on line 213"

This problem only happens when running a PHP version > 7.3 on your server and can be solved as follows:

Edit the pages/event.php file and chang line 182 from . . .

$cid = isset($_POST['cid']) ? $_POST['cid'] : ($eCats[0] == '0' ? 0 : intval($eCats[0]));

to . . .

$cid = isset($_POST['cid']) ? $_POST['cid'] : ($eCats[0] == '0' ? 1 : intval($eCats[0]));

(only the 0 before ": intval" changed to 1)

Roel

Highlights

This new LuxCal version 4.7.7 includes interesting new features, improved technical issues and bug-fixes.
Most important new features / improvements:
• In Month, Week and Day view optionally a side panel can be shown right next to the main calendar. This is an important new feature.
• A new "Gantt Chart" view has been added to the calendar, showing a graphical presentation of all events during a certain period in sequential order.

Hereafter you will find a full summary of all changes since LuxCal version 4.7.6.

This new release has been tested again with the help of John from Denmark. Thank you John, you're a hero!

New features/Improvements
• In Month, Week and Day view optionally a side panel can be shown right next to the main calendar. This side panel can contain one or several of the following elements:
   1) a mini calendar, which can be used to look back or ahead in the calendar
    without changing the date of the main calendar.
   2) a decoration image per month.
   3) an optional information area with a message per month.
• A new "Gantt Chart" view has been added to the calendar, showing a graphical presentation of all events during a certain period in sequential order. Gantt Charts are particularly useful for project activity planning.
• On the Settings page, in the section Periodic Functions, when selecting Daily calendar changes summary, an empty Recipients list was not flagged as an error. The default Daily calendar changes summary setting for new installations is now set to 0 (disabled).
• To distinguish the Options button from possible other buttons right of the options button, the caption is printed in bold and the margin on the right side has been slightly enlarged
• When on the admin's Settings page, in the Views section, event sorting was set to category sequence nr, in Week and Day view for some events the width of the event rectangle was not maximized. Solved and code optimized.
• In both Matrix views the dates that were shown in each day cell have been removed and replaced by a date in the column header and footer. This creates more space for events and gives the Matrix views a much less crowded impression.
• In Matrix view "users" a user with post rights could click the day cells in any row - so also in the rows of other users - to open the Add Event window. When saving the event it would appear in the row of the user who added the event, which may be confusing. To avoid this behavior, in the new version a user with post rights can only click a day cell in his own row to open the Add Event window.
• For events that need approval but have not yet been approved the hover box with event details now shows a "still to be approved" bar (red bar) in the left margin. This means that now also in calendar views with only a mini-square or symbol per event (Year and Matrix views) the user can see that an event still needs approval.
• A new setting has been added to the General section of the settings page to specify the upper limit in pixels of a small display. If the calendar is visited from a small display, it will run in responsive mode, which means that certain not-essential elements are left out to better fit the calendar on a narrow width display.

Technical issues
• The variable $_SERVER['HTTP_USER_AGENT'] is not always provided by every web server, so before using it, its existence must be checked.
• On the Edit User Group page, a note has been added that the event categories that can be viewed and added/edited are subject to the selected user rights.
• In the navigation bar the trailing semicolon of the magnifier glass symbol was missing, which resulted in an HTML error.
• In header.php script for the side menu there were two different class tags in the same div, which is incorrect HTML. Both classes have now been merged.
• When the event duration is all day, the function that makes the hover box time now returns the text "All day" (from language file), rather than an empty string.
• In the function that makes the hover box time the "break"s were missing in the switch statement. Performance improvement.
• A function has been added to the toolbox file which produces the HTML code content of the event title hover-box. The hover-box content is now identical in all calendar views.
• In week and day view the code to display the events and the event hover boxes with event details has been scrutinized and optimized.
• For links to the calendar server, like the RSS feeds URL and the URL of the calendar itself, the HTTP protocol is now set to "https" if the calendar was queried through the HTTPS protocol.
• For all messages sent, the meta-tag <meta charset="UTF-8"> has been added to the message's <head> section.
• Users with 'assigned' admin rights (uid != 2) could open the database page and backup the database, but could not download the created backup file.
• When present, the upgrade script will show release notes at the end of a successful upgrade. The release notes should be present in the calendar root in file relnotes.html. This feature can be used to notify the admin of important issues when upgrading the calendar.
• If on the search page the end date < the start date an error message will be displayed

Bug fixes
• When a user with no access rights used the cP URL parameter, the selected page with events was shown. This should not be possible.
• In case of an invalid URL parameter (validGetVars function), the alert page is started while the calendar ID is not known yet, resulting in a PHP error message.
• On the Upcoming Events page, for events with an end time, in the hover box title the end time was displayed twice.
• The function to detect event overlaps didn't work correctly when the time of the new event ended on '9'. Problem solved and script simplified.
• When an event had been added without closing the Add Event window and thereafter the same event was added as a new event (Save as New), resulting in a page number change from 30 to 31, this caused a Session Expired message because there was no token for page 31. Solved by reverting to one single Event page number and using the mode to set the Event window title to either "Event - Add" or "Event - Edit".
• During the calendar upgrade procedure, when the calendar db is V4.7.7 the upgrade function returned V4.7.6, which is incorrect.
• In V4.7.3, on the Settings page, the change summary recipients field was renamed from "chgEmailList" to "chgRecipList". During the upgrade process the old field was copied to the new database, but not renamed, which resulted in the field content being lost.
• In the search SQL statement the category name and group name were not 'escaped' resulting in an SQL error when one of the two contained a single quote (like: don't forget).