bret at pectopah
Jun 24, 2009, 12:19 PM
Post #3 of 4
(1545 views)
Permalink
|
I updated bug #93 with these steps.
Cheers,
Bret
On Wed, 2009-06-24 at 11:34 -0400, Greg Heo wrote:
> 0. Create a new story, check it into a desk.
> - story_instance gets version = 1, checked_out = f
>
> 1. Check out the story from the desk.
> - story_instance gets version = 1, checked_out = t
>
> 2. Return to the desk, use the "Check in" link
> - story_instance gets version = 2, checked_out = f
>
> 3. Check out the story again.
> - story_instance gets version = 2, checked_out = t
> ...but the story profile screen still says "Current Version: 1".
> Other
> users will see "Current Version: 2" so I think this is a session/
> caching problem
>
> 4. Return to the desk, use the "Check in" link
> - story_instance gets version = 3, checked_out = f
>
> 5. Check out the story again.
> - story_instance gets version = 3, checked_out = t
> ...again, the story profile says "Current Version: 1".
>
> 6. This time, use the "Check in" button at the bottom of the story
> profile screen.
> - The desk now says the story is at version 2
> - story_instance still has the "version = 3, checked_out = t" record
>
> At this point, the log shows the version number going from 2 to 3 to
> 2
> again. If you check out the story and check in from the story
> profile,
> you'll get an SQL complaint on udx_story__story_instance because
> it's
> trying to create version 3, which already exists.
>
> Callback::Profile::Story->checkin() calls a clear_my_state() method,
> while Callback::Desk->checkin() doesn't have anything like that.
> Does
> this have anything to do with it? Or is it some other difference
> between the two checkin() methods?
--
Bret Dawson
Producer
Pectopah Productions Inc.
(416) 895-7635
bret [at] pectopah
www.pectopah.com
|
