Re: Behaviours and Parent/Child Self-Joins

No it's not view stuff. Just because it says "markup" doesn't mean it
should be in a view.

This is a behaviour to modify model data as it is retrieved. It's
logic applied to data in a model behaviour.
A helper could do a similar thing although less efficiently, however
that isn't my intention, and won't solve the problem I'm having with
threaded finds.

This seems to be "by design" issue with behaviours not being attached
on threaded finds.
Is it a bug? Is it by design?
Is their a work-around that doesn't involve re-coding the threaded
find to call each model individually?

The core shows the callback being set to true, however it's the
behaviour callbacks that are lost on subsequent models.

Would going back to the old way of coding a self-join in the model
rather then with the automagical parent_id threaded find setup work?

-Ben

On Oct 1, 7:28 pm, AD7six <andydawso...@gmail.com> wrote:
> On Oct 1, 9:21 am, Mr-Yellow <meisteryel...@gmail.com> 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 cake-php+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---