cake development.
I wasn't sure at the time if my solution was optimal or not, however
answers to my thread suggested that disabling the cache for logged in
users is a common thing to do.
It seems for your case it is not the correct answer however.
On Apr 26, 2:17 pm, Eduardo Pinto <efgpi...@gmail.com> wrote:
> In my case, this problem happens at least with Chrome and Firefox.
> Can't test it at IE right now.
>
> AD, I'll try to follow your suggestion.
>
> On 26 Abr, 12:52, AD7six <andydawso...@gmail.com> wrote:
>
> > On Apr 26, 11:30 am, chris <chris....@internetlogistics.com> wrote:
>
> > > Sounds similar to an issue I was seeing. It only happend on IE, my
> > > thread is here
>
> > >http://groups.google.com/group/cake-php/browse_thread/thread/f92934d0...
>
> > > In the end I disabled the cache for all the time a user is logged in,
> > > with $this->disableCache();
>
> > sDoesn't sound like a very sensible solution..
>
> > cake doesn't randomly generate flash messages, they are provoked when
> > a request is received and shown on the next (html) page to render.
> > Having this happen with IE only should have been a hint.
>
> > If you log requests, or even just edit the flash message such that it
> > includes the URL it came from you'll most likely find that you have
> > requests for a missing css/js/image file which gets captured by the
> > missing-controller logic and sets .... a flash message.
>
> > AD
--
Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions.
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
No comments:
Post a Comment