Event s RadCalendar Daylight event diff - or other problem.
Best to see the screencast to know what I am talking about
Since we wanted to go online tomorrow I am posting it here (as well as opening a ticket) maybe someone in the community can tell me what might be the problem.
Or is it that we are 1 hours from GMT and it saves it as GMT time.
I have answered you in the support ticket you have opened. I am sharing my answer with the community:
Problems with day light saving including the described one have been fixed. The fix will be included in the upcoming release Sitefinity 7.0. If you upgrade your project to this version you will not encounter this problem.
Thank you very much for your feedback. I would like this event to show you how I sometimes feel about bugs / PITS / Feedback portal.
1) You encounter a problem. Of course murphys law will tell you that this happens
a) when you are showing a function to a client
b) just when you want to go online with a site
2) You first spent 5 minutes figuring out what is happening (its actually usually more 30 min +)
3) You try to figure out what you are doing
4) Not finding anything you will seach the forum here
5) Not finding anyhting you post and open ticket (see point 1 its go online week)
6) You make a screencast and send it to support who will come back very fast with....
7) Sorry we are not able to reproduce
Usually its because I did not communicate well but mostly because its an issue with something mulitlingual or so
8) You explain again what is the problem. And give additional feedback
9)Then you get either a PITS you can vote for for month and years or like in this lucky case it is bound to be fixe within one release. Lucky for me in this case its only 1-2 weeks away
10) you go back after the update to see if its really fixed
a) you are lucky and its fixed
b) you are semi lucky its fixed but other bugs are introduced (hello markus this is bug, bug this is Markus)
c) its not fixed, unfortunately we (Terlerik) were not able to, vote or Roadmap next version (3 month away)
The bug took at least 1 hours of my time to figure it out and I assume you did spend about 5-10 minutes as well in reproducing and telling someone to fix it.
A) The bug was not know and once again I am reporting it (I sometimes get the feeling I am the only one running into such stuff)
B) The bug was know but not to me or even you!
Well the ideal thing would be in this order of priority
1) There are no open bugs - I know its wishfull thinking
2) There would be a list of open Issues per module/widget that would let me see through before testing/screencasting/ticket back and forth
Now you could say the feedback portal does this but there are over 1000 open issues. So I am not goint there at the first place.
Sitefinity is a super product
Telerik support is fast and extremely helpfull (they put up with me)
Sitefinity is getting great stuff with each release.- Thing we are hoping for a long time
And most of all. It makes a feature absolutely UNUSABLE. Again in this case I might get lucky to have a fix within 2 weeks (still has to be proven)
But in many other cases have to wait for month (look at the image ordering bug in sub libraries)
But a simple small case like this take away the fun sometimes and a bit of engery.
Please don't get me wrong. Again Sitefinity is the only CMS for me. Love Telerik products and support is going way out of what you can expect so many times, but I hope that Telerik will cut down the open issues to 100-200 and display them by module/widget so before we spend/waste our and Teleriks support time we can go and look there.
I guess it would make the sitefinity team also feel good if they could cross out some open issues as solved.
Thank you for your feedback.
I would like to give you some information why the problem has not been logged in our Feedback portal and why we were not initially aware of it.
We have a bug related to Time zones and Day light saving:
Which fix will be included in Sitefinity 7.0. Fixing the bug required a change in how events hours are displayed in the frontend and in the backend. Our Quality Assurance specialists have made a lot of tests scenarios and all the issues related to the recurrent events and daylight saving time have been fixed. One of the test scenario matches the bug reported by you and this is the reason why we haven't logged the bug in out public portal. It was immediately fixed this week. We are fixing problems reported by customers, by our developers, Quality Assurance specialists or us.
Furthermore, I would like to inform you that these notes for the events daylight saving problems will be included in our release notes.
Your information in highly appreciated and I agree with you that you should be aware of the problems that are in process of fixing. I will make sure that your feedback is forwarded.
Thanks for the time you took to answer.
a) the bug was opend 6 month ago! It seems I have to wait two weeks others for 6 month (see point 9 from original post)
b) I am aware of all bugs beeing worked on according to Feedback.telerik.com 18 are worked on 649 are not done yet (exactely the same amount as done - what a coincident :-)
c) a list of fixed stuff is always nice. but it would be nice if all known issues would be listed by module. This sure would put some presser on bugifixing because the release note would be quite long (649 open bugs)
Well at the end I am happy that this should be fixed in 7.0 and do appreciate the great efford of the Sitefinity team to make the product better with every release.
I completely agree with you. I have forward all the information to the people responsible for these areas.
We appreciate your constructive feedback.
Bug really seems to be fixed in 7.0. Thanks’.