On 1/4/06, Michael Wechner <[EMAIL PROTECTED]> wrote: > Jann Forrer wrote: > > > On Wed, 4 Jan 2006, Thorsten Scherler wrote: > > > >> El mié, 04-01-2006 a las 16:03 +0100, Robert Goene escribió: > >> > >>> Bob Harner wrote: > >>> > >>>> On 1/4/06, Jann Forrer <[EMAIL PROTECTED]> wrote: > >>>> > >>>>> On Sun, 1 Jan 2006, Robert Goene wrote: > >>>>> > >>>>> > > > > [ ... ] > > > >>>>> > >>>>> Therefore I made a somewhat different solution. > >>>>> It is also a "forcecheckin" usecase wihin our publications > >>>>> including a new > >>>>> action (ForcedCheckInAction). > >>>>> It simple checks wheter a node is really checked-out, get the user > >>>>> who > >>>>> checked the page out and the respective check-out date. > >>>>> The new user who wants to edit this page gets a "warning" screen > >>>>> saying > >>>>> that the page is already checked out by another user xy at 12.12.2999 > >>>>> 12:20.Then he has the possiblity to check the page in (or to > >>>>> cancel of course). > >>>>> We made the usecase available only in the site area. That means > >>>>> everbody > >>>>> who can access the node in the site area might check in the page. > >>>>> > >>>>> If this solution is of interest for you i can document it on the > >>>>> wiki too. > >>>>> > >>>>> Jann > >>>> > >>>> > >>>> > >>>> Yes, please do! This is a key usability feature currently missing > >>>> from Lenya, and IMHO it should be incorporated into Lenya and made the > >>>> default behavior. > >>> > >>> > >>> I was planning to make a usecase like this myself. Would it be possible > >>> to submit a patch? > >> > >> > >> Jann is committer and can check this in (if he wishes). It would be > >> really nice to have it in our code base because this issue is always > >> coming up again. > >> > > > > I did not check it in because it was probably not the intend to enable > > such kind of check-in (by a different user). Anyway it was a feature > > which was often wished from our users. > > > > I can now: > > - document it on the wiki and can upload the source code of the necessary > > Action. - or made it available for the default publication and check > > it in > > (lenya-1.2.x). > > > well, we could add a menu item "Force checkin" or something like that ... > > Michi >
The proposed solution involves prompting the user to break the lock when the user tries to edit the file, right? IMHO that is sufficient for now, but if someone wants to add it to the menu too, okay. Ultimately I'd wish for a screen under the Admin tab that lists all the documents currently locked (and the locker's name and date locked). That page could have controls for forced unlocking of any of the documents listed. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
