No, that's rails itself, it would amaze if the trouble came from that file.. I'm guessing here, but, in config/environment.rb, do you have a live that says "config.frameworks -= [ :action_mailer ]", or "config.disabled_extensions = [:action_mailer]"? Radiant disabled action_mailer by default for quite a long time, comment out that line if it isn'nt commented yet.
If that's not it, run the site in development mode, then you should get a stacktrace, that'll make it easier to debug. Op dinsdag 23 oktober 2012 18:35:55 UTC+2 schreef marshal het volgende: > > Thanks Benny. I think I'm a bit closer to finding the culprit. > > Following your suggestion, I uninstalled all the gems I could find that > were not needed, including Mail, Actionmailer, Rails, etc. No change -- > same error message. > > But you said "... you have something in your application that redefines > Mail.", so I started looking through all the gems for any that defined a > Mail class. The radiant-mailer-extension gem has one that includes a > valid_config? > method and then there is this one that I'm guessing supersedes it: > > > /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.1/vendor/rails/actionmailer/lib/action_mailer/vendor/tmail-1.2.7/tmail/mail.rb > > The tmail/mail.rb defines a Mail class without any valid_config? method. > > Now what? > -- > marshal >
