Re: Bootstrap access to a model?

Why are you allowing users to define routes?

On Jan 6, 8:59 am, majna <majna...@gmail.com> wrote:
> http://mark-story.com/posts/view/using-custom-route-classes-in-cakephp
> But this will break reverse routing, if used. All routes must be
> "connected" for reverse routing to work.
>
> On Jan 6, 4:57 am, Greg Skerman <gsker...@gmail.com> wrote:
>
> > Hi,
>
> > So i've ditched the idea of having one controller call another. Instead,
> > i've decided a better approach might be to use routes, and have "custom"
> > routes stored in a database, added at runtime in bootstrap.php, and of
> > course cached.
>
> > This will allow people to define their own simple routes for site map
> > organization.
>
> > So, I know I can probably use App::Import('Controller', 'CustomRoutes'); in
> > bootstrap, and manually initialize the class, but are there any reasons why
> > i shouldn't do this? I'd appreciate thoughts on whether bootstrapping a
> > controller/model is a good thing or a bad thing.
>
> > Have at it :)

Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions.

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