I guess if this Auth->user() looses the user, it's linked to session.
What are you security.level in core ? What is your check.agent (do you
do lot's of ajax ?). Do you have some other "notices, warnings"
before ?
On Jun 24, 5:30 am, aranworld <[EMAIL PROTECTED]> wrote:
> I'm curious to know why you are routing everything to the
> Contents_Controller rather than just put the functionality of the
> Contents_Controller into the app_controller?
>
> I think that one of the frustrations people have with the Auth
> component is that when a problem crops up, it can take a lot of
> digging around to solve. I don't think this is a critique of the
> component, but in the heat of the moment, I think people just get
> frustrated when something isn't "just working".
>
> On Jun 23, 6:45 pm, "Chris Hartjes" <[EMAIL PROTECTED]> wrote:
>
> > On Mon, Jun 23, 2008 at 9:33 PM, Alessio <[EMAIL PROTECTED]> wrote:
>
> > > Ok thanks Chris...
> > > I believe that you have not problems with the component...
>
> > I wasn't try to be snarky or anything, but I realize it might come
> > across that way. I just never run into those problems with Auth that
> > people report. Again, I keep things very simple and haven't gone
> > wrong with that approach.
>
> > > Maybe I have found the reason...
> > > I believe that it doesn't work when you use a particular route::
> > > // Custom URL route
> > > Router::connect('/*', array('controller' => 'contents', 'action' =>
> > > 'ProcessAllRequest'));
>
> > > Essentially when in my site the user write something, I redirect all
> > > to the Content_Controller...
>
> > > So When, the user enter in mycontroller by route, the component forces
> > > to logout...
>
> > Why would you do it that way? Is there a requirement that every
> > single request has to go through just one controller? It makes no
> > sense to me, but I probably don't understand the problem you are
> > trying to solve.
>
> > > Essentially I say to the auth component to allow all request of
> > > COntent_controller...
> > > But I saw after many hour of debugging that the Auth COmponent is not
> > > able to manage this situation...
>
> > I think (again, just my opinion) you are trying to use Auth for
> > something it is not intended to do. You're not necessarily wrong,
> > you're just trying to do something that maybe Auth just cannot handle.
>
> > It might help if you paste some code tohttp://bin.cakephp.orgit
> > might be helpful.
>
> > --
> > Chris Hartjes
> > Internet Loudmouth
> > Motto for 2008: "Moving from herding elephants to handling snakes..."
> > @TheKeyBoard:http://www.littlehart.net/atthekeyboard
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
