I have to agree - we are certainly using two different devise models and are using the cookie store for our sessions, so there must be more there in your session.
AB On Apr 6, 2014, at 9:10 AM, Chris McCann <[email protected]> wrote: > There are other options for authentication in Rails. Depending on your > needs, Sorcery is a fairly well-written, lighter weight alternative to Devise: > > https://github.com/NoamB/sorcery > > I, along with most other experienced Rails developers here, would strongly > discourage writing your own authentication solution. There's no need to > reinvent something so critical to an app as authentication when there is > battle-tested, community-vetted code already available. > > The bigger question here, though, is why you're getting the cookie overflow > error. Does this Stack Overflow post describe your situation? > > http://stackoverflow.com/questions/7117200/devise-for-twitter-cookie-overflow-error > > You should take a close look at what you're storing in the cookie-based > session, in addition to what Devise is stashing there. > > If you find for some reason that you have to put more than 4k of data in the > session then a database or memcached session store would certainly allow > that. Is there a particular reason why neither of these session stores is an > option? > > Cheers, > > Chris > > On Sunday, April 6, 2014 1:25:49 AM UTC-7, Abiding Dude wrote: > Am building an ecommerce app and finding a problem with overflow on cookies > if I have 2 models with Devise. > > The suggested solution via stack overflow is to use the db to get around this > issue which I'd rather not, or memcache. > > Is there any other solution recommended for authentication? Or maybe write my > own? > > There's customer login, affiliate login and admin login. Neither will login > on same browser at same time, but the overflow issue seems to be common in > exceeding the 4k limit once you do 2 logins using cookies with Devise. Other > than that its been a very user friendly and quite powerful gem. Thanks for > any pointers. > > -- > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby > --- > You received this message because you are subscribed to the Google Groups "SD > Ruby" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby --- You received this message because you are subscribed to the Google Groups "SD Ruby" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
