On 1/4/06, Jann Forrer <[EMAIL PROTECTED]> wrote: > On Sun, 1 Jan 2006, Robert Goene wrote: > > > Hi, > > > > Is there someone who can explain the 'force checkin' behaviour, as noted > > in the revisioncontroller description: > > > > "A user "System" exists, who can force internally a checkin" > > (http://lenya.apache.org/1_2_x/components/revisioncontrol/revisioncontroller.html): > > > > > > I would like to be able to check in files that are checked out and left > > by editing ussers, something that seems to be possible. Couls someone > > give me a hint? > > > > A solution is described in the lenya-wiki: > > http://wiki.apache.org/lenya/HowToDefaultPublicationUsefulChanges?highlight=%28Useful%29 > > Checked-out pages have been an often quoted problem for our users too. > > 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. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
