|
|
About Us – WRRJ Radio - Google Chrome_981.jpg (108,037 bytes) |
|
|
Thanks for the report. Investigating. |
|
|
Automated response: DST shifts not detected correctly in the calendar Recurring events with a time component may not compensate for a DST shift. E.g. an event started at 2PM, may shift to 3PM. |
|
|
Fixed in git commit c332626 (https://github.com/chrisgraham/Composr/commit/c332626 - link will become active once code pushed) A hotfix (a TAR of files to upload) have been uploaded to this issue. These files are made to the latest intra-version state (i.e. may roll in earlier fixes too if made to the same files) - so only upload files newer than what you have already. Always take backups of files you are replacing or keep a copy of the manual installer for your version, and only apply fixes you need. These hotfixes are not necessarily reliable or well supported. Not sure how to extract TAR files to your Windows computer? Try 7-zip (http://www.7-zip.org/). hotfix-1610, 2014-03-24 2pm.tar (60,928 bytes) |
|
|
For reference, there were a couple more issues... The "fast forward" code, designed to let a recurring event calculate itself into a future month window, extrapolating rather than looping through each recurrence, forgot to compensate for DST shift. The DST shift detection had a bug which was using the wrong variable to track the change, missing it, or counting it multiple times, in different cases. Whether the bug caused an issue depended on exactly what kind of recurrence was set up. |
|
|
Thank you Chris. This is to confirm the hotfix has fixed the issue. |
- Anonymous
