我的rails应用程序使用devise来处理注册,身份验证等.我正在使用可确认模块.错误是这样的 – 当用户注册电子邮件时,Devise正在发送两封带有不同确认链接的确认电子邮件.一个链接有效,另一个链接将用户指向错误页面.
Devise吐出与错误相关的消息:“确认令牌无效”并将用户带到重新发送确认电子邮件页面.
我正在托管heroku并使用sendgrid发送电子邮件.更新:该bug也发生在localhost上.
我不知道这个bug的根源在哪里,这可能比你需要看到的更多代码:
车型/ user.rb
- ...
- devise :database_authenticatable,:registerable,:omniauthable,:recoverable,:rememberable,:trackable,:validatable,:confirmable,:authentication_keys => [:login]
- ...
- ## callbacks
- after_create :account_created
- # called after the account is first created
- def account_created
- # check if this activiy has already been created
- if !self.activities.where(:kind => "created_account").blank?
- puts "WARNING: user ##{self.id} already has a created account activity!"
- return
- end
- # update points
- self.points += 50
- self.save
- # create activity
- act = self.activities.new
- act.kind = "created_account"
- act.created_at = self.created_at
- act.save
- end
- ...
- def confirmation_required?
- super && (self.standard_account? || self.email_changed)
- end
- ...
控制器/ registrations_controller.rb
- class RegistrationsController < Devise::RegistrationsController
- def update
- unless @user.last_sign_in_at.nil?
- puts "--------------double checking whether password confirmation is required--"
- ## if the user has not signed in yet,we don't want to do this.
- @user = User.find(current_user.id)
- # uncomment if you want to require password for email change
- email_changed = @user.email != params[:user][:email]
- password_changed = !params[:user][:password].empty?
- # uncomment if you want to require password for email change
- # successfully_updated = if email_changed or password_changed
- successfully_updated = if password_changed
- params[:user].delete(:current_password) if params[:user][:current_password].blank?
- @user.update_with_password(params[:user])
- else
- params[:user].delete(:current_password)
- @user.update_without_password(params[:user])
- end
- if successfully_updated
- # Sign in the user bypassing validation in case his password changed
- sign_in @user,:bypass => true
- if email_changed
- flash[:blue] = "Your account has been updated! Check your email to confirm your new address. Until then,your email will remain unchanged."
- else
- flash[:blue] = "Account info has been updated!"
- end
- redirect_to edit_user_registration_path
- else
- render "edit"
- end
- end
- end
- end
控制器/ omniauth_callbacks_controller
- class OmniauthCallbacksController < Devise::OmniauthCallbacksController
- skip_before_filter :verify_authenticity_token
- def facebook
- user = User.from_omniauth(request.env["omniauth.auth"])
- if user.persisted?
- flash.notice = "Signed in!"
- # if the oauth_token is expired or nil,update it...
- if (DateTime.now > (user.oauth_expires_at || 99.years.ago) )
- user.update_oauth_token(request.env["omniauth.auth"])
- end
- sign_in_and_redirect user
- else
- session["devise.user_attributes"] = user.attributes
- redirect_to new_user_registration_url
- end
- end
- end
配置/ routes.rb中
- ...
- devise_for :users,controllers: {omniauth_callbacks: "omniauth_callbacks",:registrations => "registrations"}
- ...
如果需要,我很乐意提供更多信息.我也愿意定制/覆盖设计邮件程序的行为,但我不知道如何去做.
非常感谢!
解决方法
解决了!
我能够覆盖Devise :: Mailer并强制执行堆栈跟踪以找出导致重复电子邮件的确切内容. Devise :: Mailer#confirmation_instructions被调用两次,我发现问题出在my:after_create回调中,如下所示:
在models / user.rb中……
- after_create :account_created
- # called after the account is first created
- def account_created
- ...
- # update points
- self.points += 50
- self.save
- ...
- end
以某种方式调用self.save会导致邮件再次被触发.我通过改变添加点的时间来解决问题.我摆脱了after_create调用并覆盖了确认!设计中的方法看起来像这样:
- def confirm!
- super
- account_created
- end