I agree with Brian, that if the data changes you want to make applies every time you read the models data, then the afterFind method is the correct place to make your changes.
But if the data changes only is to take place in a specific method in the controller, then it is there you should do it (or in the model as a new method). As far as I understand, you operate on the data exactly the same way as you operate on the data in the view. When you are finished changing the data, you use the set method to make the data available to the view. Hope this helps you on the way :) Enjoy, John On Mar 20, 5:48 pm, brian <[email protected]> wrote: > You might want to consider using the Model's afterFind() method, > instead. But, if you'd rather do it in the controller, the best way to > figure out how to access your data is to toss a debug($mydata) in > there. (seems to be my standard response these days ;-) You're > probably getting hung up on the numerical indexes for a hasMany > relation or something. > [snip] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
