Got a strange one here.
We run a scheduler in timeline mode to show a bunch of bookings for an ad server.
90% of the time it works flawlessly.
But around once or twice a day out of many 10s of hits per day by our staff, the appointments render truncated in the view.
On closer inspection I noticed they are all exactly half-sized. It's set to 1 day per slot, so ads that are booked for a full day take up half a slot, and a ten-day campaign stretches 5 slots leaving the next 5 days as incorrcectly available. Hitting F5 will always remedy the error, only for it randomly trigger later in the day.
I have applied the actual start and end dates to the tooltip for the appointment and have confirmed that when they truncate, the actual data behind it is still correct. So it seems it is just a rendering issue, not a data source issue.
I can't seem to find any reference to this being a known bug, so I'm still looking at what might be causing it in our implementation. But it is strange that such a bug should be intermittent. We're using Firefox v 3.6.3.
Just thought I'd throw it out there in case it rings any bells with anyone.
Thanks for your time
We run a scheduler in timeline mode to show a bunch of bookings for an ad server.
90% of the time it works flawlessly.
But around once or twice a day out of many 10s of hits per day by our staff, the appointments render truncated in the view.
On closer inspection I noticed they are all exactly half-sized. It's set to 1 day per slot, so ads that are booked for a full day take up half a slot, and a ten-day campaign stretches 5 slots leaving the next 5 days as incorrcectly available. Hitting F5 will always remedy the error, only for it randomly trigger later in the day.
I have applied the actual start and end dates to the tooltip for the appointment and have confirmed that when they truncate, the actual data behind it is still correct. So it seems it is just a rendering issue, not a data source issue.
I can't seem to find any reference to this being a known bug, so I'm still looking at what might be causing it in our implementation. But it is strange that such a bug should be intermittent. We're using Firefox v 3.6.3.
Just thought I'd throw it out there in case it rings any bells with anyone.
Thanks for your time