Read the statement by Michael Teeuw here.
Calendar shows late day events on next day but at correct time
-
@natmash so, I think I finally have a fix for this.
Would you like to try it?Which MagicMirror version are you using?
-
@sdetweil I am going to test your fix with my calendar too, as it was the cause for the initial fix.
-
@MarcLandis you want it on 2.28 or 2.29?
-
@sdetweil 2.29 please
(2.28 is too old :) )
-
@MarcLandis understood, but I don’t want to force upgrade to test
-
here is a test version of the fixes for all kinds of calendar date problems.
best to make a new folder and git clone there
git clone https://github.com/sdetweil/MagicMirror cd MagicMirror git checkout fixcaldates npm run install-mm
copy your config.js and custom.css from the prior folder
and the non-default modules you have installed…this ONLY changes the default calendar
but DOES ship an updated node-ical library tooif you need to fall back, just rename the folders around again so that
your original is called MagicMirrorall the testcases for node-ical and MagicMirror execute successfully.
the ‘BIG’ change here is to get the local NON-TZ dates for the
rrule.between()all the checking and conversion code is commented out or not used
the node-ical fixes are for excluded dates (exdate) values being adjusted for DST/STD time… waiting to submit that PRone fix in calendar.js for checking if a past date was too far back,
but it never checked to see IF the event date was in the past… (before today) so it chopped off too manyand one change in calendarfetcher.js to put out a better diagnostic message of the parsed data… (exdate was excluded cause JSON stringify couldn’t convert the complex structure)
-
@sdetweil I testet your branch and so far it looks good with my test calendar and also with my real ones.
-
@MarcLandis thanks. i still have some reported issues. so use it and let me know. will advise when i make nect updates
we wouldn’t release til jan anyhow, so we have time
-
@natmash please see my latest test update this entry is now added to the testcases run
(I had NOT fixed it before today)
-
@MarcLandis can you retest at your convenience
git pull and npm run install-mm