Thanks for that!! smile

Hi Roel,
you wrote that PHP VERSION REQUIRED IS 7 now. Are there any experiences/problems with using php 8 ?
Would like to know before switching php version. (A lot of webhosters are forcing their customers to do so...)

Thanks, Stefan

So you were faster than me.
I just came to the forum in order to present my solution smile
Now I'm very interested in yours wink

Hi Roel,

for me it seems like a bug, but perhaps you have another point of view.
My scenario:
There is some kind of repeating event with an category which is not allowed to overlap.
Now I edit one occurrence as single and change - lets say - the venue. After saving this is a single event and the original repeating event will get an entry in the xDates column.

Next step: I edit the original repeating event and save it again.
Now there will be the overlap error message for the date of the event which now is a single event.
But it is not really an overlap because the repeating event has an xDate entry for that date.

I hope that was not to confusing smile

In this context: Wouldn't it be enough for an overlap check to check only events in the future!?
In our calendar there are some repeating events which where started in 2018 - so a lot of years get checked for overlap if those events are edited.

Greetings!

Hi,
think there is something wrong in the "calcFTDate" function of the displays 1 to 3.
Found this, because of setting "First Day Of Week" to "1". But this did not work within the display files. So I tried to figure this out:

First: A PHP error is shown when using "WEEK" for from or till date

Notice: Undefined variable: set in /volume1/web/lc521ff090/display3.php on line 151 Notice: Trying to access array offset on value of type null in /volume1/web/lc521ff090/display3.php on line 151

To fix this the function should have the $set variable as global:

global $futEvts, $set;

Second: wrong brackets within in the function under "case: 'WEEK' "
Instead of

$dStamp = time() + ($set['weekStart'] + $wkDay * 86400) + ($mult * 604800); //time first day

it should be

$dStamp = time() + (($set['weekStart'] + $wkDay) * 86400) + ($mult * 604800); //time first day

6

(12 replies, posted in Problems)

Hi Roel,

are there any changes/ anything new concerning subcategories in 5.2.1 ?
I find the new string "cat_scat_must" in the language files but nothing else ...
Am I missing something?

Thanks and greetings

   Stefan

7

(2 replies, posted in Need Help)

Thanks!!!

I thougt I tried the described way allready - but perhaps I was doing something wrong.
Just tried again and it works!

So sorry for asking at all wink

Hi Roel,

again it's me with a question:
Is it possible to add different languages to the files in the "help" folder - similar to the "lang" folder?
I just tried this but did not work.

I think this would need some changes in header.php and/or toolbox.js

But nothing important so far - only nice to have ...:-)

Stefan

9

(2 replies, posted in Problems)

Hi Roel,

I allready was at that line in the file but couldn't find out more ...
Thanks for that.
Yes - because of all my trials and coding arround "flexible fields" I have to test a lot and find more and more functions of luxcal I did not use till now - but sometimes there are bugs too wink

Stefan

10

(1 replies, posted in Problems)

behave strange on week and day view and give warning:

A non-numeric value encountered in /volume1/web/luxcal/common/vfunctions.php on line 33

First occurences are stretched over the whole day - last occurence shows up in the "earlier" row.

Sorry  - but this looks like something to be fixed wink

Stefan

11

(2 replies, posted in Problems)

Hi,
after fresh install of  5.2.0 Mysql I realised, that the timepicker fields are not closing after clicking a time.

Javascript error:
Uncaught TypeError: Cannot read properties of null (reading 'style')
at updateTimeField (dtpicker.js:185:8)
at HTMLSpanElement.onclick (index.php:1:1)

Is it just me? Nobody noticed? roll

Stefan

12

(12 replies, posted in Problems)

Of corseI can!
I am a little sorry for being the reason for that much work for you roll
But at the end perhaps someone else will need that functionality too.
So - thanks a lot smile

13

(12 replies, posted in Problems)

Hy Roel,

yes, this works.
Important to me was when "none" subcat ist selected, that the category is shown only with the main cat.
What I mean - it is shown like "public" not like "public - none".
And so it is ... - yes, good solution. Hopefully not onlyfor me
Thanks for that!

Only thing, that perhaps confuses a little bit is the need of setting colors for the "-" subcat without any effect ...

   Stefan

14

(12 replies, posted in Problems)

I really can understand not wanting to change the DB scheme!

A little less work would be to have an option via the settings page for all categories.

But - as far as I am the first and only one asking for that I can live with the workaround wink

15

(12 replies, posted in Problems)

I think Schwartz is right.
Admins should have the possibility to choose between these two options.

But thanks for the workaround.
Didn't think it would be that easy wink

16

(12 replies, posted in Problems)

Hello,

in the help for subcats I read this:
If, when adding/editing and event, no subcategory has been selected, the event will have the normal category colors in the various views.
But it seems not possible to not select a subcategory because allways te first subcat is preselected. There is no empty option in the subcat select.

Or am I doing something wrong???

Stefan

17

(3 replies, posted in Problems)

Hi Roel,

in my case php 7.4 ist running.
I found some hints in the web in relation to different mysql versions and if they are running in strict mode or not. But because my test server ist a synology NAS with mariaDB i was not able to get more information about that.
Next hint I found was, that the error can accour, when a string is compared with a number or something like that.

So I looked in the sql.log file and then found the accordingly line in the common/toolboxx.php.
Its on line 877 and 878
At the end og theese lines I sorrounded the 0 and the 1 with single qotation marks. So the result is:

  } else { //spMiniCal existing (0 -> '', 1-> '2,4,6')
    dbQuery("UPDATE `settingsX` SET `value` = '' WHERE (`name` = 'spMiniCal' OR `name` = 'spImages' OR `name` = 'spInfoArea') AND `value` = '0'");
    dbQuery("UPDATE `settingsX` SET `value` = '2,4,6' WHERE (`name` = 'spMiniCal' OR `name` = 'spImages' OR `name` = 'spInfoArea') AND `value` = '1'");
  }

This solves the error!
To me it makes sense, because the "value" field is of type "varchar".
In other server envirements it may only be a warning instead of an error.

18

(3 replies, posted in Problems)

Hi,

I get this Error in sql.log when trying to restore backuped database.

SQL query error: SQLSTATE[22007]: Invalid datetime format: 1292 Truncated incorrect DOUBLE value: ''
Query string: UPDATE `mycal_settingsX` SET `value` = '' WHERE (`name` = 'spMiniCal' OR `name` = 'spImages' OR `name` = 'spInfoArea') AND `value` = 0

Tried with new installation with only one event in the events table.

Hey Roel,
thanks again for new features wink

I realised that the old, not used field "number" in the user table is gone and instead there is a new field called "msingID". As far as I can see, this field is also not in use.
What are your intentions wirth that field?

Greetings!

Hi Roel,

I thought the question was discussed a long time ago in this forum, but could not find it... If so, I can't remember the answer -  so I ask again wink

I would like to know what the main goal is for using POST instead of GET for all actions within the calendar.

I think it would be much easier if we could use the forward an back buttons of the browser. But this allways produces the reload form message of the browser.

Are there any security reasons for that?

Thanks for your time!

Stefan

Hi Roel,

for me the new "Mark Day" feature only works in month view - not in week or day view?
Is this the way you wanted it?

Stefan

22

(4 replies, posted in Problems)

Upgrading for me is not that easy because of a lot of additional code.

So many thanks for that solution!!!

   Stefan

23

(4 replies, posted in Problems)

Hey,

i have troubles after updateing php to 7.3 from 7.2.
For example it is not possible to save the settings page.
This error comes up:
Warning: preg_match(): Compilation failed: invalid range in character class at offset 20 in /kunden/140346_38108/luxcal/pages/settings.php on line 80

I am running LuxCal Kalender: 4.7.1M
But ist seems that the line 80 has not changed in the newest version of luxcal.

There are somme more warnings - all like: preg_match(): Compilation failed: invalid range in character class

Any ideas?

Roel wrote:

Hi Stefan,

The German language files have been reviewed, corrected and completed just before the release of V5.1.0 and are included in the new version. The only texts that have not been reviewed and updated are the explanations when hovering the items on the settings page (in the ai-deutsch.php file). So when you have a spare moment . . .

Roel

Hi Roel,

it took longer than expected - a lot of rows to read an translate wink
How can I send you the translated file? Or was someone faster than me ?

Btw - is it correct, that some "Help" files are still not translated?

Greetings and still "Happy new year"
   Stefan

Many thanks from me too Roel!
Good to hear, that it will be maintained to stay up to date.
Knowing that there will be no major changes for me this is a good point to switch to the latest version ( still on 4.7.1 wink) and include my own modifications to the code which is needed for our calendar.
If it isn't allready done I will have a look at the german translation!

Thanks again!

   Stefan