On Sun, Jun 22, 2008 at 5:39 PM, Kevin Triplett <[EMAIL PROTECTED]> wrote: > Men of Heroku, I pushed my app and broke it. Now getting a > 500 error.
I don't see the 500 error on triplettelectronic.heroku.com, but I looked in your log/development.log and saw this: /!\ FAILSAFE /!\ Sun Jun 22 16:48:52 -0700 2008 Status: 500 Internal Server Error Session contains objects whose class definition isn't available. Remember to require the classes for all objects kept in the session. (Original exception: uninitialized constant Cart [NameError]) My guess was that you are stashing full Ruby objects instead of just the id of the object. Something like this: session[:cart] = @cart Instead of: session[:cart_id] = @cart.id So when you make code changes, there's a chance that it will unmarshall in a weird way that throws an error like this. Best practice here is to only store basic object types - integers, strings, or arrays/hashes of such. You can probably fix the error you're getting by clearing the cooke in your browser. Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" 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/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
