Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start_date values in table tx_calendarize_domain_model_index become faulty after switch to summer/winter time #169

Closed
topson opened this issue May 5, 2017 · 3 comments

Comments

@topson
Copy link

@topson topson commented May 5, 2017

Database entries in the column "start_date" in the table "tx_calendarize_domain_model_index" become faulty after crossing a time change date.
Example:
For reading puropses I've used from_unixtime() to read the database start_date values.
An event is created with the start date February the 2nd 2017 and takes place daily.
The database entries for the time period of Feb. 2nd to March the 26th will be flawless, meaning the start date would look like "2017-02-20 00:00:00".
However in 2017, the 26th of March marks the time change to summertime. The database entry of March the 27th will be faulty because the start date would look like "2017-03-27 01:00:00".
This problem also occurs going from summer to wintertime:
An Event with the start date of September 28th would have an database entry like "2017-09-28 00:00:00". Once October the 29th is reached database entries would look like "2017-10-30: 23:00:00".

If you have more that one reoccuring event, the FE-calendar will produce sorting issues.

@topson topson changed the title Start_date value in table tx_calendarize_domain_model_index becomes faulty after switch to summer/winter time Start_date values in table tx_calendarize_domain_model_index become faulty after switch to summer/winter time May 5, 2017
@No5251

This comment has been minimized.

Copy link

@No5251 No5251 commented May 8, 2017

Maybe this one gets also fixed through these:
https://forge.typo3.org/issues/68651
https://forge.typo3.org/issues/61110

@neonaut

This comment has been minimized.

Copy link
Contributor

@neonaut neonaut commented May 29, 2017

Hi! I've created a patch for the core. Would be nice if you could review it! https://review.typo3.org/#/c/52952/

Greetings. Paul

@lochmueller

This comment has been minimized.

Copy link
Owner

@lochmueller lochmueller commented Aug 25, 2017

Hey... seems to be a mix up beween core and calendarize. I added also this patch:
857e067
I will close this issue... if there are more problems I need more technical information about it...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.