501

(2 replies, posted in Problems)

Hi Stefan,

You are right. Neither bug nor feature wink
In LuxCal version 4.6 we introduced a user number, which could be specified when creating/editing a user account.
This user number however, was used nowhere and our plans to use it changed.

So in LuxCal version 4.7 we removed it again, because just entering a number which is never used does not make much sense.
I commented out the code to enter the number and left it, just in case we would need it later for the future "participation feature.

Roel

502

(11 replies, posted in Need Help)

Hi Stefan,

In the calendar's index.php file the function "isMobile" is called and the return value is stored in the variable $isMob. The return values can be: 0: not mobile, 1: mobile tablet, or 2: mobile small display.
So if you do a global search with "$isMob" through all calendar files you will find the places where measures are taken to make the calendar more responsive.
(Just in case: To do global text searches, you could use the free application TextCrawler)
Roel

During his holidays Gérard has update and completed the French language files for LuxCal version 4.7.0.
The updated language pack can be downloaded on the Downloads page.
Roel

504

(2 replies, posted in Need Help)

Ha ha, yes great question, why exactly at 3:15am? Actually it does not matter so much when lcalcron.php is started.
Since this file triggers the sending of email reminders for the day, it should start before the early rising calendar users open the calendar.
So why not start lcalcron.php just after midnight, or at 1:00am? Because various countries have Summer and Winter times (DST) and the DST change is not always at the same hour in each country. If you would start the lcalcron.php file for instance at 2:00am and at the end of the Summer at 2:00am  the clock is set 1 hour back, during that night it will be 2:00am twice! This would then start the lccron.php script twice resulting in duplicate reminder messages.
So, to make a long story short, we said let's suggest 3:15am; this will not interfere with DST changes in the various countries and it's still early enough to send reminders for the day to come.
I hope this sufficiently explains the 3:15am mystery smile
Roel

505

(4 replies, posted in Suggestions)

Hi there,

That's a fair request and good suggestion.
So, yes, I will add this possibility.
It should not take too long to implement; if you are interested and send me your email address (via the Contact Us page), I will send you a changed file, with this option added, most probably within one week.

Roel

Hi there,
Currently selecting a calendar, in case of multiple calendars in one install, is only possible for users with administrator rights. This is done because for a certain user the rights for one calendar can be completely different from the rights for an other calendar. For instance if a certain user would have view or post rights in one calendar and would have no access rights in an other calendar, then if the user could switch to the other calendar, he/she would get the log-in dialogue (no Options Panel) and there would be no way back to the first calendar anymore.

As said by John in the other thread, we're planning to review the concept of multiple calendars (in one install and in different folder) for the next calendar version.

If this is not exactly what you meant, please let me know.
Roel

507

(6 replies, posted in Problems)

Hi Luigi,

Hmm, I did exactly the same, I created a user group Operators with exactly the same parameters as in your last post.
Then I created a user and assigned the user to the group Operators and thereafter I could create/edit events and I could also edit the events of other users. So it worked fine, as expected.

The error message 'no edit rights (event). Please log in.' should normally never appear. This error message only shows if something unusual happens.
Are you sure that the user Test can successfully log in? Is the user name Test displayed in the right upper corner of the calendar after log in?

Could you send me (via the Contact Us page) a link to your calendar and a temporary user account with admin or manager rights? I will then have a thorough look at what is happening.

Il tuo inglese è molto meglio del mio italiano wink

Roel

When running the file lcalcron.php via a cronjob, a PHP notice message may occur, saying "PHP Notice:  Undefined index: xda in /home/eakpvwdu/public_html/kal.irweb/cronjobs/notify.php on line 39".
This PHP Notice issue was already reported "solved" in the latest calendar version 4.7.0, but for mysterious reasons the solution was not included in the V4.7.0 zip-file.
This PHP Notice has no detrimental effects on the functioning of the email reminder function, but if you want to solve the issue, then you can download the changed file here.

You can also fix this problem by applying the following changes:
Edit the file cronjobs/notify.php and replace lines 37 - 39 . . .

if ($evt['mde'] <= 1 and //first day
  ($daysDue == $evt['nom'] or $date == $todayD00) and //email due
  !($evt['r_t'] and strpos($evt['xda'],$date))) { //date not excluded if repeating event

by . . .

if ($evt['mde'] <= 1 and //single day event or first day of multi-day event
  ($daysDue == $evt['nom'] or $date == $todayD00)) { //email due

and replace lines 93 - 95 . . .

if ($evt['mde'] <= 1 and //first day
  ($daysDue == $evt['nos'] or $date == $todayD00) and //SMS due
  !($evt['r_t'] and strpos($evt['xDates'],$date))) { //date not excluded if repeating event

by . . .

if ($evt['mde'] <= 1 and //single day event or first day of multi-day event
  ($daysDue == $evt['nos'] or $date == $todayD00)) { //SMS due

Use cut and paste!

Roel

Hi Mike,

Thanks for reporting this error.
The PHP Notice issue was already reported "solved" in the latest calendar version 4.7.0, but for mysterious reasons the solution was not included in the V4.7.0 zip-file.
Coincidentally this PHP Notice has no detrimental effects on the functioning of the email reminder function.

Nevertheless I have posted the solution under Known Issues and Fixes.

Roel

510

(2 replies, posted in Need Help)

Hi Luigi,
There could be two reasons:
1. You have selected maybe via the Options Panel the English language and this is saved in a PHP session variable. During the PHP session, the calendar will take the language from this PHP session variable, unless you select an other language. PHP sessions last normally no longer than 22 minutes (of calendar inactivity), so this problem should solve itself when you close the calendar for more than 22 minutes.
2. On the Settings page, under User Accounts you have checked "Restore last user selections" and you have once selected English, which was subsequently stored in a cookie. If you log out now and log in again, it will take the last user selections, i.e. English. To overrule this, take care that on the Settings page, under User Accounts, "Restore last user selections" is checked and in the Options Panel select the Italian language. Now the last selections, including the Italian language will be stored in a cookie. Now the problem should be solved.

Roel

A bug in V4.7.0 causes the following problem:
When editing one occurrence of a repeating or multi-day event, the other days of the event disappear.
When deleting one occurrence of a repeating or multi-day event, the whole event is deleted.

To fix this problem changes to two files are required. You can download the changed files here.

You can also fix this problem by applying the following changes:
1. edit file pages/eventform1.php and just after line 49 (<input type='hidden' name='eid' value='{$eid}'>) add the following line . . .

<input type='hidden' name='evD' value='{$evD}'>

2. edit file pages/event.php and change line 107 from . . .

$ediN = 0;

to . . .

$ediN = (isset($_POST['ediN'])) ? $_POST['ediN'] : 0; //0: not relevant, 1: occurrence, 2: series

and change line 115 from . . .

$ediN = ($mode == 'edi' and is_numeric($_POST['action'][3])) ? $_POST['action'][3] : 0; //0: not relevant, 1: occurrence, 2: series

to . . .

if ($mode == 'edi' and is_numeric($_POST['action'][3])) { $ediN = $_POST['action'][3]; } //0: not relevant, 1: occurrence, 2: series

and change line 222 from . . .

if (!empty($evD)) { $sda = IDtoDD($evD); }

to . . .

if (!empty($evD) and empty($sda)) { $sda = IDtoDD($evD); }

Use cut and paste!

All users of v4.7.0 are advised to implement these changes.

Roel

When you have upgraded the calendar to a new version and you discover some unexpected behavior, like certain buttons are not working, some form fields are not pre-filled properly, etc., then  . . .

TRY REFRESHING /RELOADING THE PAGE IN THE BROWSER (Ctrl-F5)

this will reload the styles and JavaScript tools which are often kept in the computer's cache.

Roel

There is a flaw in the upgrade script. In the upgrade script the thumbnail privileges in the user groups are not initialized. The result is that, when upgrading, all existing user groups in the database have the Thumbnail privileges set to a non-existing value, which results in no privileges at all.

Solution:
- Go to the admin's User Groups page. A number of PHP notices will be displayed. Ignore these messages.
- Edit each user group and set the Thumbnail privilege to one of the values from the drop-down menu.
That's all.
After going through the steps above, there are no further adverse effects on the functioning of the calendar itself.

Only the upgrade script has this flaw; new installations are fine.

Roel

514

(3 replies, posted in Need Help)

Hello Dan,
Yes, right, I will look into this and change the privileges for the default user groups.

I will also look at the Notice messages; they should not appear. Could be a cache problem.
Kind regards,
Roel

Great!
Thanks Gérard, good point.
For the next calendar version I will change the upgrade script too.

Roel

516

(7 replies, posted in Need Help)

Great Michael! You too.
Roel

517

(7 replies, posted in Need Help)

Try the following:
- edit the file pages/login.php and to get rid of the "Remember me" check box delete line 204:

<span class='floatR'><input type='checkbox' id='cookie' name='cookie' value='1' ".(isset($_COOKIE['LCALuid']) ? " checked" : '')."><label for='cookie'> {$ax['log_remember_me']}</label></span>

- edit the file index.php in the calendar root and before line 65 (session_start();) add the following line:

session_set_cookie_params(1440);

and replace "1440" (in the line above) by the number of seconds you would like a session to last. E.g. 600 = 10 minutes.

Roel

518

(7 replies, posted in Need Help)

This depends . . .
Do you want to set the automatic logout time to < 24 minutes, in other words: do you want to abort the PHP session?
I assume that if you want to automatically logout users after a limited number of minutes, you also want to remove the "Remember me" check box from the login page.
Let me know if I'm correct and thereafter I will try give you a hint on what should be done.

What calendar version are you using?
Roel

Hi Dan,

Interesting link!
Most of these editors have a lot of functions which require changes to the calendar as well. I will investigate if I can find an editor which is not too sophisticated and not depending on jQuery. Thereafter I will have to see if and how this can be integrated in the calendar. Quite a challenge wink

Regards,
Roel

520

(7 replies, posted in Need Help)

Hi there,

I'm not quite sure what you mean. Would you like to force a log out after a certain number of minutes?

This is how it works at the moment:
- If a user logs in and checks the "Remember me" check box, then a cookie with the user ID is stored. So each time the user starts the calendar he/she will be logged in automatically. If the "Remember me" check box was not checked, the user will have to log in each time he/she starts the calendar.
- When the calendar is started, the PHP session mechanism is used to remember the current user and his/her last selections during the time the user is using the calendar (the calendar session).
- The PHP session length stored in the PHP installation (php.ini file) is for most installations set to 1440 seconds which is 24 minutes. This means that if a user stays inside the calendar without any activity, his/her session will expire after 24 minutes. This means that at the following action a message will be displayed and the user will have to refresh the page.

Maybe with this knowledge you could give me further details of what you would like to do.
Regards,Roel

Hi there,

No there is currently no WYSIWYG editor available. There are more users interested in a WYSIWYG editor. This should be done on the client side via JavaScript. We will see if this can be done without too many troubles.

Roel

522

(3 replies, posted in Need Help)

Hi there,

Yes indeed, recurring events taking place (partially) in the future will not automatically be deleted.
Please note that a recurring event is only one event in the database and as such takes up very little space. If you want, deleting past occurrences is fine, but it will not free up any space in the database.
Roel

Highlights

This new LuxCal version 4.7.0 contains a number of important new features and has quite some technical issues improved and bugs solved.
Most important new features:
• A new thumbnail management page to upload and manage thumbnail images and a more user-friendly way to add thumbnails to events
• A new side menu (hamburger button), replacing the majority of the buttons on the right side of the navigation bar.
Hereafter you will find a full summary of all changes since LuxCal version 4.6.1 . . .

This new release has beens tested with the help of the two extremely competent beta testers John from Denmark and Bill from New Zealand!

New features/Improvements
• A thumbnails management page has been added where users can upload and manage thumbnail images. On the user group page the admin can specify for each user group the thumbnail rights. And on the Settings page the admin can specify the maximum thumbnail image size (W x H).
All thumbnails must be stored in the thumbnails folder. Consequently the thumbnail folder is not shown anymore in the description fields.
• A new section File Uploads has been added to the admin's Settings page, where the accepted file extension and the maximum file size for uploaded attachment files and for uploaded thumbnails can now be specified by the administrator.
• Through the introduction of a side menu, the number of buttons on the right side of the navigation bar has been reduced significantly. The majority of the buttons has been replaced by one 'hamburger' button, which when selected will open the side menu. The menu items shown in the side menu depend on the current page and the user rights. This gain of space is especially important when the calendar is shown on a display or in an area with a limited width.
• The options panel now drops down gently, rather than being shown instantly.
• To have a calendar wide uniform approach to deleting items, on the Categories page, the Users page and the Groups page, the button "Show delete buttons" has been removed. Instead, to avoid users to accidentally delete an item, a confirmation dialog will be shown before deleting the item.
• In the Event window, to avoid users to accidentally delete an event, a confirmation dialog will be shown before deleting the event.
• On the admin's Categories page a minimum gap between two events which may not overlap can be specified.
• On the admin's Category page a check box has been added to select a fixed event duration, rather than a default duration. If checked, when adding or editing an event in this category, a notice will be shown at the top of the Event window and the fields end date, end time and all day will be hidden. When the event is saved, the calendar will automatically add the fixed time duration to the start date and time. If the end time falls on the next day, a multi-day event will be created.
• On the admin's Category page the event duration can now be specified in hours and minutes, rather than just minutes. Since the calendar can now cope with event durations which span more than one day, the upper limit has been extended from 720 minutes to 99 hours and 59 minutes.
• If on the Categories page a default event duration has been specified, when adding or editing an event in this category, a notice will be shown at the top of the Event window.
• A simple visits counter has been added, which can be enabled on the Settings page. When enabled, available visitor or web-bot data will be logged in the
    files respective files logs/hitlog.log and logs/botlog.logs and a counter of visitors and web-bots will be kept in the respective files hitcnt.log and botcnt.log. Users with access right >= manager will see a visits counter of the real visitors in the left lower corner of the calendar. When clicking counter the contents of the logs/hitlog.log file will be shown in a new window. Visits of users with admin rights will not be logged.
• URL and email links have been added to the User Interface Styling page and can now be given their own text and background color.
• Thumbnails shown in the Event Report window are now hyperlinks. When clicked, the thumbnail will be shown full-size in a new window.
• When on the admin's Category page a category symbol has been defined, display0 (aka mini Calendar), will now display this symbol, instead of a mini square (similar to the matrix view).
• Since on the admin pages there is enough space on the navigation bar, the page titles on these pages have moved to the navigation bar.
• Embellishment of the pages Upcoming Events, Added / Edited Deleted Events and Text Search. The page with search results is split in one-day events, multi-day events and recurring events. The latter has been done to avoid repetitions of multi-day events and recurring events.
• If on the Settings page "Send notification of calendar changes" is activated, messages of changed events now also contain for each event the date and time of adding and editing and the names of the owner and editor.


Technical issues
• In the makeE function, for the "td" type events, if no labels have been specified for the extra fields 1 & 2, the colon (:) was still displayed.
• In the Event window the number of columns of the event table were not always correct and the width of column 4 was not defined. On some displays this made the Event window higher than necessary.
• To save some space in the Event window, the max. file size for uploaded attachments is now displayed right of the browse button.
• In the Event window the mail Help "?" was not removed when selecting the Print button.
• The cursor in the Event and Event report windows was not always an arrow in passive areas.
• In the cron job summary the email and SMS reminder recipients were not shown each on an individual line.
• MySQL calendar only. The way to find the calendars in use, based on finding MySQL database tables names in the format xxxx_settings, has been improved. It is now based on the intersection of found table names xxxx_groups and xxxx_styles.
• Function eol2txt changed. Before the crlf characters are converted to text, clfl characters are removed form the start and the end of the source string.
• SQL queries related to testing dates for value '9999-00-00' (no date) have been simplified.
• When a category symbol was defined on the Categories page, in Matrix view these symbols were each displayed on a separate line, rather than in-line with other mini squares or symbols in the same day cell.
• HTML symbols (e.g. ⚫) which can be defined on the Categories page have a number of blank pixels at the top. Because of these blank pixels, in Matrix view and in the display1 (mini calendar), symbols were not vertically aligned with the the mini-squares. Solved.
• Both image links and attachment links are now relative to the calendar root. I.e. "./thumbnails/" and "./attachments/" respectively. This makes these link independent of the location of the calendar and thus improves the portability of the calendar.

Bug fixes
• Dutch language only. The help text for the email list in the Event window did not pop up because of an un-escaped quote in the text of the Dutch language file.
• If on the admin's Settings page in the general template the 7, signifying "added & edited, date, time, name", was removed, in the event window these fields were still displayed.
• Since the introduction of the three log message levels errors, warnings and notices, the cronjob messages produced by the lcalcron.php script were not logged correctly. Solved
• When checking if dates are due for a notification message, for repeating events the check for excluded dates went wrong and produced a PHP notice.
• When cloning (Save as new) an event in a category for which no overlap is allowed, in the overlap test the original event was not taken into account.
• The function repeatText, which creates the repeat text did not treat empty "until dates" (9999-00-00) correctly.

Roel

The EU's General Data Protection Regulation, aka "GDPR", which was adopted April 2016, will be enforced as of 25 May 2018. The regulation contains provisions and requirements pertaining to the processing of personally identifiable information.
Although the LuxCal calendar is using cookies and does not ask users to accept the use of cookies, we believe the calendar complies with the GDPR. As required by the GDPR we are applying data protection by design and default in the following way:

  • the calendar does not use so-called tracking cookies,

  • the calendar is only collecting the calendar ID (e.g. 'mycal') and numbers (i.e. User ID, and the current page, category, group, language) which are meaningless to other parties; so no sensitive data is stored in the cookies,

  • the data stored in cookies is serialized and as such not understandable by the human eye.

If you prefer, you could of course add a notice on your calendar web page saying that the calendar is using cookies and is compliant with the EU's GDPR.
Roel

525

(2 replies, posted in Need Help)

Hi Meena,

Like Dan said above, I assume you have created a MySQL database. If so, then "problem connecting to database" means one of the following parameters you entered during the calendar installation is wrong: db host, db username, db password or db name.

Again like Dan said above, if you have difficulty to get the MySQL database connection working, I suggest to install the SQLite version of the calendar, which has exactly the same functionality, is very fast and easier to install.

Roel