Hi, actually one of my apps also required what you call edit and page history.
For edit history I used RevisionBehavior by alkemann which is stable and really easy to use. There's a tutorial in Bakery http://bakery.cakephp.org/articles/alkemann/2008/12/18/revision-behavior-revision-control-made-easy and you can get the latest version from github http://github.com/alkemann/CakePHP-Assets/blob/master/models/behaviors/revision.php For the page history I just have a log table and insert a row for every page request by having code like this in the AppController's beforeFilter method: $logData = array ( 'user_id' => $this->Auth->user('id'), 'ip' => $_SERVER['REMOTE_ADDR'], 'url' => $this->here, 'params' => json_encode($this->params), ); $this->loadModel('PageLog'); $this->PageLog->save(array('PageLog' => $logData)); You can probably find some logging component someone has already made with additional functionality if you need it. Or you can use Cake's built-in logging system that writes files. On Oct 15, 11:38 pm, Johny Iversen <[email protected]> wrote: > Hi CakePHP people > > A friend and I are consindering to take the leap, and port our custom > festival booking system to CakePHP, and since we are heading for > reuse, I just wanted to find out if there is perhaps something already > in place that we could use directly with minor modifications, or at > least if there is something we should take into consideration. > > The things it should be able to handle is: > *) Temporary reservation of a spot until the booking is completed or > timed out. > *) Dividing the system into having various entry points or some way to > modify what is displayed to the user (e.g. booking a family spot is > not exactly the same as a tent spot). > *) Book more than one spot at a time (group booking). > *) Book for various spot types (e.g. tent areas). > *) Redirect to payment. > *) Respond to payment results (error, success, rejection, cancellation > etc.). > > That ought to be the basics of it, but we are considering to implement > a few extra things: > *) Full edit history: > Instead of deleting and updating records, we would rather insert new > rows, which then disables the previous record for the same id. This > practice will divide a regular entity table into two tables. One > primary table with information that never changes, and a secondary > table that has a new row for each update an entity recieces. This > would help us to see exactly what is happening to the data, making it > easier for us to debug. > *) Page history: > If this should compliment the above or if it should be only one or the > other, we are not sure of, but we would also like to log exactly what > parts of the booking system the user has visited and when, so we know > how the complete flow has been for the user. This will make it easier > to spot if some browsers are giving us any trouble by e.g. caching > something it should not cache on pressing the Back Button or Refresh. > > Again we already have a running system that can do all but the last to > features and group booking, so we are not sure if it is worth porting > it to CakePHP, but again, by doing so we pressume that our security > would improve as well as code tidyness. :) > > Alternatively is there already a free system out there that can do all > of the above or close to? > > Thank you for your time! > > Best regards, > Johny Iversen > Denmark Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
