Let me rephrase..... I have a custom "foo" behaviour.
By adding this behaviour to a model the afterFind callback checks the data for fields specified in the behaviour params and creates a mirror field "bar" with processed data from the specified field. Hopefully that now isn't view in model :-P The problem is that CakePHP doesn't seem to cascade behaviours to every instance of that model when used via the 'threaded' find method (or self joins in model associations). To my thinking, anything done in the model or attached to the model should exist everytime that model is called regardless of the calling method. This allows models to be setup to be consistent without having to worry about making it work for each different method of querying a model. This has nothing to do with how I setup my MVC and where my code is. The problem is with how models and finds fail to function as expected, not my design. -Ben On Oct 1, 7:28 pm, AD7six <[EMAIL PROTECTED]> wrote: > On Oct 1, 9:21 am, Mr-Yellow <[EMAIL PROTECTED]> wrote: > > > I have a custom wiki markup behaviour. > > > By adding this behaviour to a model the afterFind callback checks the > > data for fields specified in the behaviour params and create a mirror > > field "wiki".$whateveritwascalled which has the content formatted. > > Doesn't that scream view logic in a model? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
