-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NoMethodError: undefined method `subject' #9
Comments
I'm seeing this too. But for me it's balking at the 'from" method. I imagine it just has to do with which method you call first, though. I'm thinking this has to do with the refactored Mailer in Rails 3.1 or 3.2 and the ridiculously out of date MadMimiMailer gem. Did you learning anything new on how to fix the issue, conradwt? |
@pdobb I decided to move away from the MadMimiMailer and use the MadMimi Ruby gem with Rails. |
@conradwt thanks. I ended up following a somewhat similar path. I actually forked the mail-mad_mimi gem and got it working with Rails 3.2.6 and Ruby 1.9.3 with standard ActionMailer synatx. My fork is at https://github.com/pdobb/mail-mad_mimi if anyone is in the same boat. |
@pdobb Nice work. I went this path because the engineers at MadMimi were more intimate with their own Ruby gem and my client was using their service to delivery e-mails. Also, I'm in the process of moving e-mail delivery into their own external service which will be separate from the core Rails application. Lastly, I would recommend becoming the maintainer of the gem, bump the version, and make it available on rubygems.org. I forgot to mention that you might also want to let madmimi.com know about the existence of the gem so that their clients using Rails can benefit from it. |
You will need to add { and } around that block and subject: or :subject => |
Hi, I'm started to see the following messages with Ruby 1.9.3. Did the API change. Here's my mailer:
users_mailer.rb:
Error:
The text was updated successfully, but these errors were encountered: