Each time you make an ajax request you invalidate the existing security token. To use SecurityComponent and Ajax you would have to send the latest token with each form (and make sure you get a new one back from the server on each ajax request). And that is what in part amounts to SecurityComponent and Ajax being incompatible. It is just too much javascript-tangle.
On Jun 3, 5:34 pm, "Dave Maharaj :: WidePixels.com" <[email protected]> wrote: > You might be onto something there. > > Initial profile page loads with a "edit" button by the users profile section > to update part of the profile....click edit loads the form into a > div...."submit" saves the form via a second Ajax request...success: jQuery > effects form fades out...updated selections fade in the users profile. > > Dave > > -----Original Message----- > From: Martin Westin [mailto:[email protected]] > Sent: June-03-09 9:09 AM > To: CakePHP > Subject: Re: Security Component and AJAX > > Hi, I'm just buttin in with a quick question. Something for you to check. > > There is no other ajax request after the page loads and before the form is > posted? If so then this will also cause problems for SecurityComponent since > the token will be old. > > /Martin > > On Jun 3, 7:20 am, Miles J <[email protected]> wrote: > > At /joesmith/update/systems/, if you can debug the data you should be > > able to save it. What exactly happens, a white page? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
