For those of you that are experiencing cookie overflow errors, we too have faced that issue and we solved without having to use database session storage. We faced this problem because we have six activescaffolds (some of them with nested scaffolds) on the same view template. In our application, we have over 100 different active scaffolds. A simple way for us to reliably get the cookie overflow error was to simply render a lot of view templates. Since we have a menu at the top, this is pretty easy to accomplish... just click, click, click ... by the twentieth click, boom.
To solve this problem without resorting to database storage of the session, the trick is to delete the things that active scaffold stores in the session every so often. For us, every so often meant every time a template is rendered. We did this with a before_filter in the controller that renders all of the view templates. All active scaffold session variables start with "as:" which makes it very easy to identify them with a regex. We are not able to delete individual session variables so instead the approach we took is to backup the non activescaffold variables, dump the entire session, then restore the stuff you backed up. Works like a charm. Hope this helps somebody. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ActiveScaffold : Ruby on Rails plugin" 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/activescaffold?hl=en -~----------~----~----~----~------~----~------~--~---
