From: Marcel v. d. B. <ma...@hs...> - 2002-02-26 20:50:48
|
That would indeed solve most of the problems. Even the more complex problems somewhere in the middle of my initial comments. As the situation has occurs I'll post our experiences. Thanks guys. Marcel Jeff Dairiki wrote: >Marcel van der Boom said: > >>But (at least in the PN module version) the instructions of the >>error message are wrong. When hitting the back button, the page is >>retrieved from the db again, so the last changes are lost. (maybe that >>is the error). >> > >Yes. That's a function of the cache-control HTTP headers sent by >PHP. This started happening when we starting using PHP's session >support. It's now been fixed (in the main PhpWiki CVS) by doing >a > > session_cache_limit('none'); > >before the first call to any other session handling functions. > > > >Also note that (though I haven't played with it yet, so I might >have details wrong) Lawrence has added "merge conflicting edits" >functionality to the latest CVS version of PhpWiki: If you try >to save your edits, when there has been an intervening save by >another user, you get returned to the edit form, but the text in >the edit form will contain the latest changes merged with your >changes. You can simply hit "save" again to save the merged >version, if that's what you want. > >I think that ought to solve most problems arising from >simultaneous edits... > > > > -- Marcel van der Boom HS-Development BV Kwartiersedijk 14B Fijnaart, The Netherlands Tel. : 0168-468822 Fax. : 0168-468823 Email: ma...@hs... |