You were right. When i turned of config.cache_classes in my environments/production.rb everything worked great. Of course I cant run a deployment like that, sooo...i moved my " require 'custom_validations' " into my model right above my validation call, to ensure it gets loaded in the right order. I'm not sure how kosher this is, but it fixed the problem.
models/phrase.rb: ... require 'custom_validations validates_not_spam :word ... -- 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
