Jan 12, 2005, 4:07 PM
Post #3 of 10
(4062 views)
Permalink
I guess a more useful and general question is, "What specific database
operations are required to check a story in?" It apparently goes beyond
just setting story_instance.checked_out to 0 and incrementing the version
number.
--Jason
----- Original Message -----
From: "Scott Lanning" <lannings@who.int>
To: "Jason Justian" <jjustian@clockworklogic.com>
Cc: <users@lists.bricolage.cc>
Sent: Wednesday, January 12, 2005 12:06 PM
Subject: Re: FW: Lost Story
> Yeah, don't have two of the same version
> and the current version both checked in.
> I'd try just deleting one of the duplicates, or incrementing
> one of the IDs and incrementing current version in story.
>
> On Wed, 12 Jan 2005, Jason Justian wrote:
> >> You'll probably flip checked_out to 0 or something,
> >> or set desk__id and workflow__id to reasonable things.
> >
> > Well, I'm sure you're on the right track here. There are seventeen
> > versions of this story in story_instance, and the last one had
> > story_instance.checked_out set to 1. Setting it to zero caused the
> > story to appear a second time on the Find Stories page (two instances of
> > V.16). But still neither instance of the story allows editing, moving,
> > or checking in.
> >
> > The story.desk__id and story.workflow__id are both set at 101, which
> > correspond to the Edit Desk and Story Workflow, respectively.
> >
> > Any other tables and attributes I should poke through?
> >
> > I very much appreciate your time and help.
> >
> > Thanks,
> > Jason
> >
> >
> >
> > -----Original Message-----
> > From: lannings@who.int [mailto:lannings@who.int]
> > Sent: Tuesday, January 11, 2005 2:10 PM
> > To: Jason Justian
> > Cc: users@lists.bricolage.cc
> > Subject: Re: Lost Story
> >
> >
> > On Tue, 11 Jan 2005, Jason Justian wrote:
> >> We are using Bricolage 1.6.4. We have a story that appears
> >> inaccessible. It is in the Edit desk. On the Find Stories screen,
> >> its status shows as "Needs to be Published." The "[_] Checkout"
> >> column for this story is empty. On the Edit Desk screen, the usual
> >> "Move To" box is absent, and instead of the "Check Out" link, it shows
> >
> >> the name of a user. Logging in as this user did not change the
> >> display, nor does logging in as the administrative user. The bottom
> >> line is: I can't figure out how to edit this story, check it back in,
> >> or publish it.
> >>
> >> Has anyone else experienced this?
> >
> > Dozens of times, probably.
> >
> >> More imporant: if so, how did you
> >> fix it?
> >
> > The story's desk information gets in a weird state.
> > It'll be checked out but not on a desk, or something.
> > Find out the story ID ($ID) by hovering over the link
> > in the UI. The do this in the database:
> >
> > select * from story where id = $ID;
> > select * from story_instance where story__id = $ID;
> >
> > You'll probably flip checked_out to 0 or something,
> > or set desk__id and workflow__id to reasonable things.
> >
>