Hey guys, I actually found a (better) solution by accident.  Check
this link for anyone else that is interested:

http://cakebaker.42dh.com/2008/05/18/new-core-behavior-containable/



On Jun 24, 12:09 pm, "Turnquist, Jonah" <[EMAIL PROTECTED]> wrote:
> Yeah I guess I'm going to need to do a lot of thinking about this.
> Thanks.  And thanks for the link Renan, it actually helped.  I now see
> there is a 'fields' option in the hasMany field, maybe I could use the
> bind() or bindModel() function to temporarily change that setting
> before using find().  I'll try it if I end up needing this again.
>
> On Jun 24, 12:56 am, "dr. Hannibal Lecter" <[EMAIL PROTECTED]>
> wrote:
>
> > Your routes are really a matter of preference and your decision would
> > depend on the structure of your site and your plans for the future.
> > Think carefully how you want to expand one day and see what's the best
> > way to start.
>
> > On Jun 24, 1:39 am, "Turnquist, Jonah" <[EMAIL PROTECTED]> wrote:
>
> > > I actually figured out I don't need to do this.  But I am still
> > > curious.
>
> > > Does it make more sense to you guys that a category page would be at
>
> > > scripts/category/<id>
> > > or
> > > /categories/view:scripts/<id>
>
> > > ??
> > >  And also /entries/index redirects to /categories/scripts which lists
> > > all the categories
>
> > > Note I have one of these for all types of entries: scripts, examples
> > > and tutorials
>
> > > Hmm... maybe I should just use a tree category system and scripts,
> > > examples and tutorials could be the top level categories.  than in the
> > > future I could also add classes, cakephp helpers and etc  wow writing
> > > really helps me brainstorm
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to