You are not logged in. Please note that you need to log in before posting.
I applied the latest upgrade and then all the appointment times went ahead by one hour. Checked time zones and the system/admin/user had the same time zone. Booked a few test appointment and they were off as well.
Please advise.
Thanks,
Kurtis
Offline
Oh, no! Prior versions had things shifted back one hour. I hope the "fix" didn't break other things.
Did you revert to the prior version to see if the appointments "recovered" to the right time?
Offline
I did go back to the previous version and the appointments were all showing correctly.
Offline
Hey, it gets even BETTER! My schedule, the only one valid for June, shows only a 9am-noon time slot on Saturday. But the user is offered only 8pm, and the admin is offered 9am-1pm PLUS 230-430pm. There is no day of the week where 230-430 is a defined time slot. This just looks like database corruption. That's frightening.
UPDATE: One user had a bad time zone applied, not sure when that happened, which explains the shift between admin and user. Problem solved by making all time zones the same.
Last edited by HowToMove (2010-06-13 14:31:09)
Offline
Maybe it's time to have some users of this script be testers to check out the bugs before it's released to everyone. Specially if your schedule is already "live" and such things like this come up... Just my 2 cents
Offline
When I wrote software I had an extensive test suite that I ran each time. But it was command-line Unix software, no point-and-click or display issues. The transcript and the output could be compared with expected results and EVERY prior bug was tested to see if anything like that crept back in. It was hard to set up and time-consuming to maintain, but it really helped with release quality. It's easier to fix bugs BEFORE releasing.
I also had a debug mode that customers could enable, so they could collect useful logs that helped me figure out what THEIR software was doing. I've seen this in consumer software such as National Geographics "Topo!", which has a (hidden) way to trigger different levels of logging. They'll tell you about it if you ask for support, but it's not in their docs.
Algis, do you have any sort of QA tests before you post a release?
Do you have any sort of built-in tracing or logging to help debug?
Last edited by HowToMove (2010-06-13 14:28:40)
Offline
HowToMove wrote:
UPDATE: One user had a bad time zone applied, not sure when that happened, which explains the shift between admin and user. Problem solved by making all time zones the same.
Hello HowToMove,
is it ok after fixing the user time zone?
Offline
Yes, problem solved.
It was hard to figure out because two schedules accidentally overlapped, making the whole admin schedule confusing. There's no way to find out which schedule a given time slot came from as far as I know. We figured out the time zone after figuring out that when you create a new schedule it automagically assigns a one year duration.
Offline