Fernando Perez wrote: >> Does this mean that flash messages and authentication is an impossible >> combination? Is there any way to work around this?
> That's an easy one. For your case you cannot use page or action caching > as you have a flash. You can only cache using fragment caching, and you > have to place your fragments in the correct places otherwise you will > have the behavior you describe. > > Caching is a double edged sword. I think you're right. I have been googling around to find something, and it appears to be, that I'm not the only one having these kind of problems. I have seen solutions like displaying flash messages with Javascript (that requires a 5000 lines Prototype library, though), I've been reading about conditional caching, clever caching with memcached and so forth. But nothing actually solves the problem without giving new ones. So I guess I have to use fragment caching? -- David Trasbo. http://twitter.com/datra -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
