On Thu, Feb 5, 2009 at 9:50 AM, Dwayne <[email protected]> wrote:
>
> Yeah, I'm a bit iffy on taking specific actions on the pages as well,
> but they aren't static content. I need some way of interacting with
> the controllers that modify the content that won't leave the end user
> confused as to which page their changes will show up on. But that
> feature is still somewhat provisional until I know for certain I can
> do it without breaking everything.

But this is for a CMS? Are you trying to make it so that the user can
modify the views for certain controller actions? That might be tricky.

> Thanks for the code snippets, the SQL in particular should prove
> extremely helpful.

Keep in mind that I did that quite a while ago. It definitely needs refactoring.

> While I'd rather not push the find logic into one
> of my models (since that would require a route that gobbles up
> everything) I'll probably end up trying something similar in the
> routes file. What I'm hoping is that I'll have access to my Model at
> that point (or at least be able to build the necessary access). If I
> do, I'll be able to use the Tree behavior to build a list of all the
> current paths and then connect those paths directly to the correct
> controller/action/etc. Then I'd just need to figure out how to cache
> these results until the page hierarchy changes. (This is an I idea I
> had while I was asleep, so I won't be surprised if it turns out to not
> work at all. In that case I probably will end up pushing the entire
> path into a find method on the model.)

Brother, I know all about trying to implement ideas that came to me in
my sleep. Sometimes, they do actually work!

Sometimes.

--~--~---------~--~----~------------~-------~--~----~
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