Have you looked at the folder and file permissions? Are they 0755?
Roel
252 2020-06-25 10:03:04
Re: Time Picker interval (3 replies, posted in Need Help)
Hi Berns,
On line 155 of the "common/dtpicker.jd" file, in the for-statement, the variable i is compared to the minimum of dwEndH and 23. See code below:
for (var i = dwStartH; i <= Math.min(dwEndH,23); i++) {It is this dwEndH. If it is set to 20 (on the Settings page), the time picker should stop at 19.45.
Note: After each dtpicker.js file change refresh the browser page (Ctrl-F5) to clean the cache.
Hope this helps.
Roel
253 2020-06-24 19:55:31
Re: Time Picker interval (3 replies, posted in Need Help)
Hi Berns,
The time picker can be found in the "common/dtpicker.js" file (lines 135 - 185).
The time interval of 15 minutes is determined by the condition in the for-loop at line 160.
If you need help, I can modify the time-picker for you. In this case you should tell me in detail what it should look like. And be aware that the total time picker box can not be much bigger, because there is not much room left.
If you want me to do it for you, drop me an email, so that I can send you a modified file.
Roel
254 2020-06-04 10:07:14
Re: integration of birthday overview script with LuxCal? (19 replies, posted in Suggestions)
Hi guys,
I've sent Lucas the changed files and instructions to create a birthday calendar. If someone else is interested, drop me a mail (Contact US page).
Roel
255 2020-06-02 22:35:42
Re: integration of birthday overview script with LuxCal? (19 replies, posted in Suggestions)
Hi Lucas,
The modification is available.
Roel
256 2020-06-02 13:47:43
Re: integration of birthday overview script with LuxCal? (19 replies, posted in Suggestions)
Hi Lucas,
Example:,
You create an event with title "Harry Potter" for the 16th of May and a description field you put "2003" and for this event category (birthdays) you check the "show age" checkbox (the checkbox I propose to add).
Now each time the event is displayed, the software will make the calculation 2020 - 2003 = 17 and add "(17)" to the event title. So in 2021 the event title will be "Harry Potter (18)" and in 2026 the event title will be "Harry Potter (23), and so on.
Roel
257 2020-06-02 10:11:09
Re: integration of birthday overview script with LuxCal? (19 replies, posted in Suggestions)
Hi Guys,
What I could do for you is the following:
For the event category "birthday", where the Repeat is set to "every year" I can add a check box "show age". When this check box is selected, the software will look in the event description field and if it finds a "year" (1987, 2013, etc.) it will automatically add the age to the event title. So the title could look as follows:
Harry Potter's birthday (2003)
Or something similar.
Would that help?
Roel
258 2020-05-30 22:28:07
Re: integration of birthday overview script with LuxCal? (19 replies, posted in Suggestions)
Hello Lucas,
First a little note: I suggest to upgrade to the latest LuxCal version 4.7.8. In the calendar sidebar of your current verion, when you click an event, then you get a message "PHP session expired". This problem has been solved in the latest version.
Your question about integrating a birthday calendar with the LuxCal calendar: Yes, I think this makes sense! As already mentioned by Schwartz, actually LuxCal has a number of so-called displays (see LuxCal website - LuxCal Displays). Displays are almost the same as the sidebar you are currently using, but they are very easy to use and highly configurable (user interface styles and content). With the displays of the last LuxCal version, you have the option to force the users to log in. So you could have a calendar category "public birthdays" and another category "private birthdays" and then have a display with the public birthdays, where users don't need to log in and another display with a log in button, where users will have to log in to see the birthdays.
Alternatively, if you prefer, you can also have one single birthday display where public users will see the public birthdays and when logged in they will in addition see the private birthdays.
When you decide to go into this direction, then I or Schwartz (he knows exactly how it works), can help you.
Kind regards,
Roel
259 2020-05-29 21:36:59
Re: integration of birthday overview script with LuxCal? (19 replies, posted in Suggestions)
Hello Lucas,
I've been very busy lately with other IT matters the last couple of days. I have read your post and will reread it again tomorrow and come back to you with more details or questions 
Grüße,
Roel
260 2020-05-13 11:05:17
Re: Todo list to show past unchecked events (5 replies, posted in Suggestions)
Hi Brian,
Done, added it to the settings! In the next calendar version the days to look back in the Todo list can be specified on the admin's Settings page.
Roel
261 2020-05-05 10:33:45
Re: Error in regex (/common/messaging.php) (1 replies, posted in Problems)
Hi there,
Thanks very much for reporting this problem. I've changed the code and the problem will be fixed in the next LuxCal release.
Roel
262 2020-04-28 09:38:01
Re: Task List (4 replies, posted in Suggestions)
Hi there,
That's a good point, just one text file for all month, rather than 12 separate text files. I will change that for the next calendar version. If you want this change now, send me your email address (via the Contact Us page) and I will mail it to you.
Roel
263 2020-04-27 08:14:35
Re: Views - Event colors based on (2 replies, posted in Problems)
Thank you for reporting this issue.
We will check the upgrade script.
Roel
264 2020-04-12 10:49:37
Re: RE: PHP Session Expired Please Restart the Calendar (11 replies, posted in Problems)
Hello Greig,
I'm afraid there is not much we can do about this. The calendar is using PHP sessions, which (normally) have a lifetime of 20 minutes.
Correct, in the (long) past this didn't happen, because at that time the security measures in the calendar were not so strong. But since quite some time we have introduced strong security measures to keep evil hackers out of the door.
It's a trade-off between the risk of unauthorized access (and damage) to your calendar database and the inconvenience of the need to reload the calendar page after not having used it for more that 20 minutes.
Roel
265 2020-04-12 10:36:32
Re: SQL query error: 1115 Unknown character set 'utf8' (2 replies, posted in Problems)
This is the first time I hear that the utf8 character set is not available on the server.
Correct, comment out the mentioned line (line 369) should solve the problem.
Roel
266 2020-04-04 11:12:05
Re: Mobile Calendar (2 replies, posted in Need Help)
Hi Kim,
Could you send me a kink to your display so that I can have a look myself, please (via the Contact Us form).
Roel
267 2020-04-04 11:09:13
Re: Can't get SMS to work (2 replies, posted in Need Help)
Hi Kim,
To send SMSes you will need a paid subscription to a mail2sms service provider.
Have you subscribed to one of the mail2sms providers?
Roel
268 2020-04-04 11:00:22
Re: Task List (4 replies, posted in Suggestions)
Isn't that the same as the Todo list in the side menu!?
Roel
269 2020-03-29 10:50:19
Re: Fwd and back buttons don't work on the iPhone 6 or 8 (14 replies, posted in Problems)
Thanks for your very clear explanation. And when looking at the image I see your point, But my problem is that I don't understand how this h3 area can influence the position of the arrow heads. (Actually on the image the arrow heads are not messed up).
The h3 area is part of a div which is positioned "absolute" and "absolute" positioned elements do not affect on the positioning of other elements on the page.
I'm now wondering if there is no misunderstanding
The calendar's behavior w.r.t. narrow screens works as follows:
At the very moment the calendar page is loaded in the browser, it tests the width of the screen and if the width is less than Max. width of small screens (settings page), it forces a reload of the page in "narrow screen mode".
This means that if you load a calendar page on your smart phone in landscape position (screen width > setting) and thereafter turn your phone to portrait position (screen width < setting), then the calendar doesn't fit anymore and you should reload the page so that the calendar can serve the page in "narrow width mode".
In other words: If you load the calendar in landscape position and turn your phone to portrait position, yes the arrow heads (and more) won't fit, if you then reload the page, it should fit.
Roel
270 2020-03-27 00:32:15
Re: Fwd and back buttons don't work on the iPhone 6 or 8 (14 replies, posted in Problems)
Thanks Greig.
I followed the steps in your last post, but the problem is that I don't see a problem
The forward / backward arrows show at the correct spot for all mobile phones.
It's hard to debug a problem which doesn't show up 
Roel
271 2020-03-26 23:00:53
Re: Fwd and back buttons don't work on the iPhone 6 or 8 (14 replies, posted in Problems)
Hi Greig,
That's not naughty, that's clever
It's a good hint of what is causing the problem, but I don't understand how this is possible.
The onClick is part of an absolutely positioned element, which should have no influence on other elements like the arrows.
Unfortunately I cannot reproduce the problem; so it's hard to experiment and solve it.
How do I tell Chrome to be a mobile phone?
Roel
273 2020-03-19 18:03:18
Re: Fwd and back buttons don't work on the iPhone 6 or 8 (14 replies, posted in Problems)
Hello Greig,
Could you please try the following: Edit the file "css/css.php" and . . .
- on line 237: of style ".viewHdr" change the minimum width to "min-width:230px;"
- on line 238: of style ".arrowLink" chnage the padding to "padding:0 10px;"
This should make a difference
Roel
274 2020-03-18 20:47:36
Re: LuxCal 4.7.8 - MySQL and SQLite - released 20 March 2020 (5 replies, posted in What's New)
Hi Stefan,
That's a fair question. The number field is still present in the next version 4.7.8.
In a next release we could add a "real name" field to the user profile, but the question is: what are we going to use it for? Should it be displayed somewhere?
I will put it on my list for further consideration.
What are you doing with it?
Roel
275 2020-03-17 17:51:34
Topic: LuxCal 4.7.8 - MySQL and SQLite - released 20 March 2020 (5 replies, posted in What's New)
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.