451

(4 replies, posted in Need Help)

Yes, that could be interesting.
This would need a bit of development from our side, in particular to make sure that integrity of the calendar is not at stake.

Could you give me a contact at Sitelok (email address) who would be interested to work with us on this feature?
Regards,
Roel

452

(9 replies, posted in Need Help)

Hi there,
If what Dan writes is not good enough, I can send you a simple change to two or three files to add the venue to the time and description, but it will be a modification for you only. So you will have to be careful when upgrading the calendar in the future.
Let me know if you want the modification.
Roel

453

(7 replies, posted in Problems)

Yes, please do so; send me the credentials by email (Contact Us page).
Roel

What version of Opera are you using?
Roel

455

(7 replies, posted in Problems)

What browser are you using?
And what exactly happens, or does not happen, when you press the Add new category or Edit button on the Categories page?

Roel

Have you upgraded the calendar to v4.7.2?
Roel

457

(7 replies, posted in Problems)

Hi there,
I tried our test calendars with Chrome and all worked fine.
After upgrading to V4.7.2M, did you try refreshing the calendar page in Chrome. Just to be sure the cache is cleared.
Roel

458

(9 replies, posted in Need Help)

Hi Greg and John,

You will also find a short explanation in the admin_guide.html document in section 3c.
Please note that in version 4.7.2 there is a problem with the function to check / uncheck the "to-do" check mark.  In this forum, under Known Issues & Fixes you will find a post where you can download a zip-file with two files and instructions. Once you have followed the instructions, the check mark will work correctly.
Roel

Since improving the PHP session cookie mechanism in calendar version 4.7.2 the following functions are not working anymore:
- in the various calendar views the function to toggle the check mark of to-do events and
- in the Add/Edit Event window the function to remove event attachments.

To solve these problems download the .zip file here and follow the included instructions.

Roel

460

(5 replies, posted in Suggestions)

Hi Greg,
Ha ha, some people need more words than others smile
I actually have a lot of sympathy for your suggestion. I will analyze the impact and, if not too complicated, I will do it.
This however requires a change of the database table "groups" and therefore I can't send you a fix for this. So I will include this change in the next calendar version.
Roel

461

(5 replies, posted in Suggestions)

Hi Greg,

On the admin's Settings page, under Navigation bar, . . .
- with "Options panel menus" (2nd item) you can specify which menus are available in the Options panel; if all menus have been unchecked, the Options Panel button is not available.
- with "Available calendar views" (3rd item) you can specify which calendar views are available for public users and identified users
- with "View buttons on navigation bar" (4th item) you can specify which view buttons (e.g. Month, Week, etc.) are displayed on the navigation bar for public and identified users..
So if for instance you don't want to see the Options Panel button, you can uncheck all Option Panel menus and specify that instead e.g. a "Year", "Month" and "Week" button is displayed.

So, if I'm correct, the only thing you are asking is to have these settings not on the admin's Settings page, but on the User Group page, so that these settings can differ per user group. Am I correct?

Roel

Highlights
The previous calendar version 4.7.1 did not display correctly in the browsers Safari, Edge and IE. This is due to a problem with the PHP session cookie paths.
This problem has been solved in this new version 4.7.2.

We recommend to upgrade your calendar to v4.7.2 or to apply the fix posted in this forum under "Known Issues and Fixes".

Roel

463

(1 replies, posted in Problems)

Hi Stefan,

You are right, at all places on the Settings page (there are three places) where an email recipient list can be specified it should also be possible to enter a user name and the validation of specified user names should be consistent. In addition, the associated Help information should also reflect the possibility to specify user names.
I will update the files concerned and add them to the next calendar release.

Thanks for reporting this.
Roel

LuxCal version 4.7.1 does not display correctly in the browsers Safari, Edge and IE. This problem can be solved by upgrading to LuxCal version 4.7.2 (recommended), or by applying the following fix:
Edit file index.php in the calendar root, and change line 80 . . .
from:

$calPath = './'.basename(__DIR__);

to:

$calPath = rtrim(dirname($_SERVER["PHP_SELF"]),'/').'/';

and edit file css/css.php and change line 14 . . .
from:

$calPath = './'.basename(__DIR__);

to:

$calPath = rtrim(substr(dirname($_SERVER["PHP_SELF"]),0,-4),'/').'/';

You can also download the changed files  here.

Roel

Hello Stefan,

As long a you don't set the end time to 24:00 on the Settings page, it will work fine.
In the calendar source code I've changed it as follows.
File "common/dtpicker.js, line 153 . . .
from:

for (var i=dwStartH; i<dwEndH; i++){

to:

for (var i=dwStartH; i<=Math.min(dwEndH,23); i++){

So it will be included in the next calendar version.

Roel

466

(7 replies, posted in Need Help)

Hi Rabalupe,

I assume you have installed version 4.7.1 (the version I released yesterday). If not, I would strongly suggest to upgrade. Both the MySQL and the SQLite version can easily cope with a few thousand users per hour! So, no need to worry wink

Roel

Hello Stefan & John,

Hmm . . . I could add one more line "22:00 22:15 22:30 22:45", but then I will have to make an exception for 24:00, because this is not a valid time (valid times: 00:00 - 23:59).
Is that  what you are looking for? Any thoughts, suggestions?

Roel

468

(7 replies, posted in Need Help)

Haha, I'm glad there is google translate wink
Please note that only users with Manager rights (or Admin rights) can approve events. Events that are not yet approved are only visible to the event owner and users with Manager or Admin rights.

I hope you will enjoy the calendar.
Roel

469

(7 replies, posted in Suggestions)

Hi Dan,

Thanks for your input!
The current import function is the iCal or CSV input. both are rather limited and do not fully match all LuxCal calendar fields. So when you would export all events in iCal format and thereafter import the iCal file again, certain data would be lost.
I will take some time (probably some months) to think about this.

If you are not using the Extra field 1 and 2 and want to get rid of these fields in the Event window, then you should go to the admin's Settings page and under Views, remove the figures 4 and 5 from all three Event templates (first item).

Kind regards,
Roel

470

(7 replies, posted in Suggestions)

Hi there,

If we would implement more event fields, we would indeed prefer to make the number of fields flexible and add another table to the database, but our main problem is that we must keep the possibility to upgrade from all previous calendar version. The calendar already has three "description" fields in the events table, of which at least two should then move to this new table. The biggest problem would be the upgrade script; it would become much more complicated.

If all LuxCal users would agree to start all over again from scratch . . . smile

Roel

471

(3 replies, posted in Need Help)

Hello W.S.

I see. Because it's a rather unusual host name, the URL parser apparently doesn't like it and flags it as invalid.
Please edit the file "common/toolbox.php" and on line 20 (starting with $rxCalURL) do the following:

Replace "localhost" (somewhere in the middle) by "[\w-]{2,10}host". No typing errors please wink

Since you are running a local server, you should set the calendar URL on the Settings page to srv-host/?cal=mycal. I don't think http:// is needed, but I'm not sure.

Please let us know if this solved your problem.
Best regards,
Roel

PS. I will also change this in the next LuxCal version, which is planned for 1 September.

472

(2 replies, posted in Problems)

Hi Stefan,

Yes, you are right, it's missing. I will add this to the next LuxCal version which is planned for 1 September.

Thanks for reporting this anomaly!

Roel

473

(3 replies, posted in Need Help)

Hello W.S.

You should go to the admin's Settings page and under General set the Calendar URL to the real URL (http://www. etc.).

Best regards,
Roel

Highlights

This new LuxCal version 4.7.1 is mainly a bug-fix release with a number of cosmetic and other improvements.
Most important new features:
• Repeating events are now allowed when the event overlap check is enabled.
• The recipients field for email and SMS messages in the Event window and recipients lists in the reciplists folder may now also contain user names.
Hereafter you will find a full summary of all changes since LuxCal version 4.6.1 . . .

As usual this new release has been tested with the help of the experienced beta tester John from Denmark!

New features/Improvements
• Repeating events are now allowed when the event overlap check is enabled. If a repeating event has no end date, the overlap check will be performed for the next 24 months.
• The recipients field for email and SMS messages in the Event window and recipients lists in the reciplists folder may now also contain user names. The calendar will automatically convert these user names to an email address or a mobile phone number. File names of recipients lists in the recipients field in the Event window must now be put between square brackets, to avoid confusion with user names.
• Cosmetic change: The forward and backward buttons in the date picker header have been replaced by the same symbols (black triangle) as used in the calendar.
• Cosmetic change: In the calendar views, the left arrows to open the date picker and time picker have been replaced by calendar and clock symbols.

Technical issues
• When upgrading the calendar, existing user groups will get the following thumbnail privileges:
  - Admin: Manage all
  - Manager: Manage all
  - Post all: Manage own / view all
  - Post own: Manage own
  - Read access: None
  - No access: None.
• When two or more individual calendars were installed in separate folders on the same domain, users logged in in one calendar were sometimes automatically logged in in the other calendar(s) as well. The same kind of interference problems could occur with a single calendar installation with multiple calendars. The full session and cookie mechanism has been revised to fix this problem.
• MySQL version only: During the upgrade process, when testing if the database credentials are present the test on password is removed, because installations on a local server may have an empty password.
• In the database table definitions the default thumbnail privileges is set to '00'. The previous value '01' was wrong and caused a PHP notice message.
• The three sidebars, To do, Upcoming and To Approve, could be moved outside the display area. If the left mouse button was released when the top of the sidebar was outside the viewport, the side bar could not be picked up again. Solved by allowing the sidebar to be moved within the viewport only.
• When on the Settings page the start time was set to 0 and the time format was set to AM/PM, the time picker was showing "00:00 00:15 00:30 00:45" on the first line, which is not correct. From midnight to 01:00, the times are "12:00AM 12:15AM 12:30AM 12:45AM". Furthermore the font-family has been changed to mono-space, to better align the columns in the time picker.
• Due to an error in the user name validation template, existing users could change their user name in any name, including characters like '<' and '>'. Template corrected.
• In email reminder messages the links to possible attachments were relative links and therefore attachments could not be opened from email messages. To solve this anomaly, we've changed the relative attachment links to absolute links.
• To simplify the code, at various places the PHP mktime function has been replaced by the strtotime function.
• The installation and upgrade script will check for a .htaccess file which blocks browser access to .cdb, .log and .txt files. If not found, a .htaccess file will be created or an existing .htaccess file will be updated.
• To cope with local installations, the regex for validating the calendar URL now also accepts host name *host, where * can be 2 - 10 alpha-numeric characters or _, or -.
• The function "logError" has been removed from both toolboxd.php files and has been replaced by the general function "logMessage" in the toolbox.php file.

Bug fixes
• Editing or deleting one occurrence of a repeating or multi-day event was not treated as an occurrence and resulted in updating or deleting the main event.
• When checking if dates are due for a notification message, a check for excluded dates produced a PHP notice. Excluded dates however, are already skipped by the retrieve function, so this check in notify.php was redundant and has been removed.
• MySQL version only: In the database's categories table the default time slot field defslot was of type TINYINT. Because of this the default event duration was limited to 127 minutes (2 hours and 7 minutes). We changed the field type to SMALLINT, which can hold 32767 minutes.
• When on the Settings page, under General "Send notification of  calendar changes" is enabled, no notification was sent when deleting events.  This has been corrected.

Roel

475

(6 replies, posted in Problems)

Hi Stefan,

Indeed for recurring events it is not possible to select "every 5th <weekday> of <month>".
This feature was requested before in November 2014 by a calendar user, so I looked back at what we discussed at that time and found the following . . .
Of course the software could be modified to allow for selecting the 5th weekday, but this could be very tricky. Suppose on the 3rd of November 2018 you would enter an event with a repetition "Every 5th Friday of each month". As of the 3rd of November, the first occurrence of a fifths Friday would be 29 March 2019. This could be very confusing; as soon as you would press the "save" button, the event would be kind of "lost". It would not be visible before the 29th of March 2019.
Another example: If in August 2018 you would enter an event with repetition "Every 5th Thursday of September it would even be worse. Once you press the save button, the event would not be visible until September 2021! So if you wanted to edit this event, you would have to go to September 2021.

For this reason we decided November 2014 to drop this request.
Roel