Rails 4.1 -> 4.2 has caused an after_create callback that sends an e-mail to stop working -

-

in note model (note.rb) have snippet below being triggered active record callback:

def creation_email   case self.notable_type   when 'application'     notemailer.run('application', self)   when 'appointment'     notemailer.run('appointment', self)   end    self.inbounded = 1   self.save end

in notemailer have switch statement send different e-mail templates based on polymorphic notable_type. here snippet:

  def run(type, note)     @note = note      case type     when 'application'       app = application.find(@note.notable_id)        app.users.each |user|         if user.id != @note.user.id && user.email           mail(to: user.email,                from: @note.user.name + " <application." + app.id.to_s + "." + user.id.to_s + "@mail.mysecretdomain.com>",                subject: "my secret subject",                template_name: "application.html.erb").deliver_now         end          end     when 'appointment'       = appointment.find(@note.notable_id)        a.users.each |user|         if user.id != @note.user.id && user.email           mail(to: user.email,                from: note.user.name + " <appointment." + a.id.to_s + "." + user.id.to_s + "@mail.mysecretdomain.com>",                subject: "my secret subject",                template_name: "appointment.html.erb").deliver_now         end       end     end   end

since upgrading rails 4.2 rails 4.1, e-mails not sending out used to.

what causing problem? did change mail(..).deliver mail(..).deliver_now.

i've tried adding puts "test" in run method @ top, , not put string console. no errors @ thrown

the problem run never called. need call deliver_now in proper place.

try :

def creation_email   case self.notable_type   when 'application'     notemailer.run('application', self).deliver_now   when 'appointment'     notemailer.run('appointment', self).deliver_now   end    self.inbounded = 1   self.save end

instead of calling deliver_now in mailer.

see http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-4-1-to-rails-4-2


Comments

Post a Comment

Popular posts from this blog

python - TypeError: start must be a integer -

-
i trying draw 5 turtles, getting typeerror on line 25. here code: import turtle wn = turtle.screen() redrose = turtle.turtle() color = input("what background color be?") fillcolor_f = input("what color of rose be?") redrose.hideturtle() redrose.speed(30) redrose.penup() redrose.left(180) redrose.forward(175) redrose.right(90) redrose.forward(30) redrose.right(90) redrose.pendown() def drawrose(red): redrose.color("pink") redrose.fillcolor(fillcolor_f) redrose.fill(true) in range(red): redrose.forward(i) redrose.right(49) in range(5): drawrose(redrose) redrose.penup() redrose.forward(350) redrose.right(144) redrose.pendown() redrose.fill(false) drawrose(50) wn.bgcolor(color) i trying draw 5 roses, produces errors. doing in interactivepython.org. you recursively calling drawrose wrong parameter. on line 23 ( for in range(red): ) expect red integer...
Read more

c# - DevExpress RepositoryItemComboBox BackColor property ignored -

-
i have following code almost works properly; private void cbstatus_drawitem(object sender, listboxdrawitemeventargs e) { string item = e.item string; if (item != null) { switch (item) { case "1": e.appearance.forecolor = color.green; e.appearance.backcolor = color.green; break; case "2": e.appearance.forecolor = color.orange; e.appearance.backcolor = color.orange; break; case "3": e.appearance.forecolor = color.red; e.appearance.backcolor = color.red; break; } } } when dropdown shown, items forecolor correct, backcolor remains whatever backcolor of theme is; i.e. if i've got set dark theme, backcolor dark, cells in gridview, rather being green/orange/red. i've tried setting e.appearance.options.usebackcolor trying set e....
Read more

django - Creating multiple model instances in DRF3 -

-
1) create multiple model instances 1 api call, asked here: how create multiple model instances django rest framework? tried solution named in link, no success. i trying upload multiple files in 1 api call. result: files uploaded (only once overwrote perform_create) 1 instance created (if send 2 files, latter created instance). my code: class fileuploadserializer(serializers.modelserializer): def __init__(self, *args, **kwargs): many = kwargs.pop('many', true) super(fileuploadserializer, self).__init__(many=many, *args, **kwargs) class meta: model = fileupload read_only_fields = ('created', 'datafile', 'owner') class fileuploadviewset(viewsets.modelviewset): queryset = fileupload.objects.all() serializer_class = fileuploadserializer parser_classes = (multipartparser, formparser, ) def perform_create(self, serializer): file_list = self.request.data.getlist('file') ...
Read more