Issue Details (XML | Word | Printable)

Key: BOOK-7
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Critical Critical
Assignee: David Peterson
Reporter: Rohit Kumbhar
Votes: 2
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Confluence Extension: Booking Plugin

Incorrect day/date combination

Created: 29/Sep/06 03:31 AM   Updated: 18/Oct/07 06:29 AM
Component/s: {booking}
Affects Version/s: 1.2
Fix Version/s: 1.4.0

Time Tracking:
Not Specified

File Attachments: None
Image Attachments:

1. incorrect.JPG
(20 kB)
Environment: Windows 2003 SP1, Sun JDK 1.5, Confluence 2.2.6a, booking plugin 1.2, running on EST


 Description  « Hide
When I used the booking plugin, the day/date shown is as Friday, Sep 30, 2006 instead of Saturday, Sep 30
I am using the macro in the following way [with the right braces]:

[booking:My resource}
09:00-10:00
10:00-11:00
11:00-12:00
12:00-13:00
13:00-14:00
14:00-15:00
15:00-16:00
16:00-17:00
{booking]

NOTE: This works correctly for some installations [I've seen examples, it didnt work at my place]
Check the day/date combination in the screenshot!



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
bgillespie added a comment - 20/Apr/07 12:12 AM
I'm seeing the same problem with a similar configuration:
Windows 2003 SP1, Sun JDK 1.4.2_13, Confluence 2.4.3, booking plugin 1.3, running on PST

bgillespie added a comment - 24/May/07 10:57 PM
Has there been any progress on this issue? I would be happy to pay for support on this if that helps.

Thanks


David Peterson added a comment - 25/May/07 02:17 AM
Hi Burke,

The booking plugin has been on the back-burner for a while now. We will eventually get around to fixing it, but if you would like to accelerate it, arranging a support contract would probably be the best way. Go here to get the wheels in motion.

David


David Peterson added a comment - 18/Oct/07 06:29 AM
I an uncertain since I cannot replicate this issue on my own system, but I suspect that updating to Joda Time 1.4 will have resolved this issue. Can anyone confirm whether this is or is not the case?