Just throwing one thing out there:

Often when I have a problem in only one controller, it's because I'm
overriding the constructor or the beforeFilter, and forgetting to call
the parent class version too...

Any chance this is relevant?



On Jun 25, 2:22 pm, Alessio <[EMAIL PROTECTED]> wrote:
> yes with security level is set to high.
> The ajax question is good..
> I have a return in the BeforeFilter...
> If request comes from ajax I return...
> I had a lot of notices...unable to unlink file in cache..and blah-..
>
> I dont know how but this lesson was very useful to clean all my
> code...
> I discovered that many times the code in beforeFilter is triggered
> many times...so I have put some condition...
>
> beforeFilter is called always, if you use ajax , maybe you don't
> need ...or maybe you need... depend of your application...
> for example i use comment in ajax...if you force the loggin....
>
> I don't know how but now it works...
> I recreate all my site..with rc1..and clean a lot the code...
>
> Essentially I learned this..that if the beforeFilter triggers two
> times, the auth component becomes instable...
>
> So you have to check all your code...
>
> for example in my application i had an image not present in server...
> so the controller triggered more times...
> and the auth went to be crazy...
>
> REply to Chris..
>
> I am use this logic..because I process all request... and my
> application is built only for seo criterials...
>
> also the forum...
>
> surely with normal management the auth would work greatly...
>
> Thanks to all.
>
> On 25 Giu, 00:21, francky06l <[EMAIL PROTECTED]> wrote:
>
> > 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to