I ran into a similar situation when I tried to cache a login page; when the form was submitted it would just simply show the same view again. I am pretty sure that this is by design - or fixed in the svn (somewhere). If you check out the file in /tmp/cache/views/ you will see why - cake caches the entire view and doesn't call the Controller::action().
IMO, cake should disregard cached views when POST is detected because POST obviously contains data that is unpredictable (ie, a user logging in). On Sep 28, 10:28 am, Baz <[EMAIL PROTECTED]> wrote: > I'm having a sort of stupid problem. I've searched for a resolution, but I > don't see anyone reporting the same issues. > > Maybe I'm doing something wrong. > > I'm using Cake's cache and I'm trying to Cache the whole controller. > > var $cacheAction = '+1 hour'; > > However, Cake now refuses to accept any form submissions. I'm assuming > because on a post, it just calls back the same cached page. Any ideas from > anyone? > > From what I've read, Cake is smart enough to clear the cache if there has > been an update to the model, but it's not letting me update because it won't > accept posts. Am I missing something? Or do I simply have to cache every > controller except those with forms? > > ThanX in advance guys. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
