2016-08-03 91 views
2

我被困在Rails項目中,當用戶註冊Devise時試圖保存has_one模型。使用Devise保存has_one模型與嵌套窗體 - Rails 4

我的應用程序正在保存子模型以及新用戶,但問題是它不保存用戶表中的子ID。

我試過很多在Stackoverflow上找不到的選項。 我做錯了什麼?

用戶模型:

class User < ActiveRecord::Base 
    # Include default devise modules. Others available are: 
    # :confirmable, :lockable, :timeoutable and :omniauthable 
    devise :database_authenticatable, :registerable, 
     :recoverable, :rememberable, :trackable, :validatable, :omniauthable, :omniauth_providers => [:linkedin] 

    # Associations 
    has_one :build, inverse_of: :user 
    # Allow saving of attributes on associated records through the parent, 
# :autosave option is automatically enabled on every association 
    accepts_nested_attributes_for :build, allow_destroy: true 
end 

構建模型

class Build < ActiveRecord::Base 
    belongs_to :user, inverse_of: :build 
    has_one :template 
    # validates_presence_of :user 
end 

註冊記憶控制器

class Users::RegistrationsController < Devise::RegistrationsController 
before_action :sign_up_params, only: [:create] 
before_action :account_update_params, only: [:update] 
# before_filter :configure_permitted_parameters 

    # GET /resource/sign_up 
    def new 
    # super 

    # Override Devise default behaviour and create a build as well 
    build_resource({}) 
    resource.build_build 
    respond_with self.resource 

    # @build = @user.builds.build(template_id: params[:template_id], domain_url: params[:domain_url]) 
    end 

    # POST /resource 
    def create 
    super 
    # @build = current_user.build.build(params[:post]) 

    # @build = @user.build.build(template_id: sign_up_params[:template_id], domain_url: sign_up_params[:domain_url]) 
    # @build.save 
    UserMailer.welcome_email(@user).deliver unless @user.invalid? 
    end 

    # GET /resource/edit 
    # def edit 
    # super 
    # end 

    # PUT /resource 
    # def update 
    # super 
    # end 

    # DELETE /resource 
    # def destroy 
    # super 
    # end 

    # GET /resource/cancel 
    # Forces the session data which is usually expired after sign 
    # in to be expired now. This is useful if the user wants to 
    # cancel oauth signing in/up in the middle of the process, 
    # removing all OAuth session data. 
    # def cancel 
    # super 
    # end 

    # protected 
    # 
    # def configure_permitted_parameters 
    # devise_parameter_sanitizer.for(:sign_up) { |u| 
    #  u.permit(:first_name, :last_name, :email, :password, :password_confirmation, :builds_attributes => [:template_id, :domain_url]) 
    # } 
    # end 

    # If you have extra params to permit, append them to the sanitizer. 
    # def configure_sign_up_params 
    # devise_parameter_sanitizer.permit(:sign_up, keys: [:attribute]) 
    # end 

    # If you have extra params to permit, append them to the sanitizer. 
    # def configure_account_update_params 
    # devise_parameter_sanitizer.permit(:account_update, keys: [:attribute]) 
    # end 

    # The path used after sign up. 
    # def after_sign_up_path_for(resource) 
    # super(resource) 
    # end 

    # The path used after sign up for inactive accounts. 
    # def after_inactive_sign_up_path_for(resource) 
    # super(resource) 
    # end 

    private 

    def sign_up_params 
    devise_parameter_sanitizer.sanitize(:sign_up) 
    params.require(:user).permit(:first_name, :last_name, :email, :password, :password_confirmation, build_attributes: [:template_id, :domain_url]) 
    end 

    def account_update_params 
    params.require(:user).permit(:first_name, :last_name, :email, :password, :password_confirmation, :current_password) 
    end 
end 

新用戶表單 - 查看

<div class="container"> 
<h4 class="center-align">Sign up</h4> 

<div id="signup-row" class="row z-depth-2"> 
    <div id="signup" class="col s6"> 

     <%= form_for(resource, as: resource_name, url: registration_path(resource_name)) do |f| %> 
     <%= devise_error_messages! %> 

     <div class="field"> 
      <%= f.label :first_name %><br/> 
      <%= f.text_field :first_name, autofocus: true %> 
     </div> 

     <div class="field"> 
      <%= f.label :last_name %><br/> 
      <%= f.text_field :last_name %> 
     </div> 

     <div class="field"> 
      <%= f.label :email %><br/> 
      <%= f.email_field :email %> 
     </div> 

     <div class="field"> 
      <%= f.label :password %> 
      <% if @minimum_password_length %> 
      <em>(<%= @minimum_password_length %> 
       characters minimum)</em> 
      <% end %><br/> 
      <%= f.password_field :password, autocomplete: "off" %> 
     </div> 

     <div class="field"> 
      <%= f.label :password_confirmation %><br/> 
      <%= f.password_field :password_confirmation, autocomplete: "off" %> 
     </div> 

     <div class="actions"> 
      <%= f.submit "Sign up", :class => 'btn black' %> 
      <%= render "devise/shared/links" %> 

     </div> 

     <%= f.fields_for :build do |o| %> 
     <%= o.hidden_field :template_id, value: params["template"] %> 
     <%= o.hidden_field :domain_url, value: params["domain"] %> 
     <% end %> 
     <% end %> 
    </div> 

    <div id="linkedin-signup" class="col s6"> 
     <div class="center-align"> 
     <h5>Sign up with LinkedIn </h5> <br> 
     <a href="http://localhost:3000/login/li/oauth2"><%= image_tag('linkedin.png', :class => "linkedIn-logo") %></a> 
     </div> 
    </div> 
    </div> 


</div> 

服務器/後日志

Started POST "/users" for 127.0.0.1 at 2016-08-03 13:31:22 +1000 
Processing by Users::RegistrationsController#create as HTML 
    Parameters: {"utf8"=>"✓", "authenticity_token"=>"11DgWCU07EXLJKXbhWah0gREdBiN2PLkF/WxWsuqW5rgQdCUrRH9rLBrKpbusRhtsCzSAQT0ADlxhQxMvWAD6A==", "user"=>{"first_name"=>"john", "last_name"=>"maksksk", "email"=>"[email protected]", "password"=>"[FILTERED]", "password_confirmation"=>"[FILTERED]", "build_attributes"=>{"template_id"=>"1", "domain_url"=>"dddddd.com.au"}}, "commit"=>"Sign up"} 
    (0.1ms) BEGIN 
    User Exists (0.6ms) SELECT 1 AS one FROM "users" WHERE "users"."email" = '[email protected]' LIMIT 1 
    SQL (0.5ms) INSERT INTO "users" ("first_name", "last_name", "email", "encrypted_password", "created_at", "updated_at") VALUES ($1, $2, $3, $4, $5, $6) RETURNING "id" [["first_name", "john"], ["last_name", "maksksk"], ["email", "[email protected]"], ["encrypted_password", "$2a$11$WgJJ.uM2DfaqQhUYatUZnuIJmaqIDVfIuYEkl/U3zSbm.h/OH/yGa"], ["created_at", "2016-08-03 03:31:22.796589"], ["updated_at", "2016-08-03 03:31:22.796589"]] 
    SQL (0.2ms) INSERT INTO "builds" ("template_id", "domain_url", "user_id", "created_at", "updated_at") VALUES ($1, $2, $3, $4, $5) RETURNING "id" [["template_id", 1], ["domain_url", "dddddd.com.au"], ["user_id", 30], ["created_at", "2016-08-03 03:31:22.800033"], ["updated_at", "2016-08-03 03:31:22.800033"]] 
    (1.3ms) COMMIT 
    (0.1ms) BEGIN 
    SQL (0.4ms) UPDATE "users" SET "last_sign_in_at" = $1, "current_sign_in_at" = $2, "last_sign_in_ip" = $3, "current_sign_in_ip" = $4, "sign_in_count" = $5, "updated_at" = $6 WHERE "users"."id" = $7 [["last_sign_in_at", "2016-08-03 03:31:22.804259"], ["current_sign_in_at", "2016-08-03 03:31:22.804259"], ["last_sign_in_ip", "127.0.0.1/32"], ["current_sign_in_ip", "127.0.0.1/32"], ["sign_in_count", 1], ["updated_at", "2016-08-03 03:31:22.805380"], ["id", 30]] 
    (1.2ms) COMMIT 

感謝您的幫助!

PS:構建不是一表我想一個聰明的名字......

托馬斯

回答

0

的問題是,用戶先保存,然後你的關係目的,你可以節省USER_ID保存構建構建而不是保存build_id用戶

+0

感謝。可能就是這樣。有關我如何一次拯救它的任何想法? – apwn

+0

你正在保持你真實的模型懸念,並問你需要共享所有三個模型的答案,你想明確實現什麼。然後我可能會幫忙。 –

0
params.require(:user).permit(:first_name, :last_name, :email, :password, :password_confirmation, build_attributes: [:id, :template_id, :domain_url]) 

build_attributes應表有:id

使得測試

def create 
    user = User.new(sign_up_params) 
    user.save 
end 
+0

謝謝佈雷諾。 但是,它不起作用,因爲它沒有從表單中獲取id。我認爲它首先保存了用戶,並沒有構建ID。 '參數:{ 「UTF8」=> 「✓」, 「authenticity_token」=> 「Atu7B4voCs8T1Rtz82zc3MRABSUfqQa9374ogg1WVBL5W0Kicc9DLrigggOuVJL + rb0FXjHJ5Yu5Bvfo05 + NXA ==」, 「用戶」=> { 「first_name的」=> 「ophk」, 「姓氏」=> 「kddkd」,「email」=>「[email protected]」,「password」=>「[FILTERED]」,「password_confirmation」=>「[FILTERED]」,「build_attributes」=> {「template_id」=> 「1」,「domain_url」=>「khljgjjff.com」}},「commit」=>「註冊」}' – apwn

+0

但是插入一個binding.pry或調試以驗證用戶。錯誤'來識別已建立的對象構建或有錯誤 –

+1

使用binding.pry是個好主意,但是問題已經解決了。問題是用戶先保存然後編譯,但他希望在用戶表中創建id。這是不可能的。 –

0
模型User.rb
has_one :build 
accepts_nested_attributes_for :build, allow_destroy: true 
軌控制檯
user = User.new(name: 'example', build_attributes:{template_id:1, domain_url: 'test'}) 

user.save # this will create user and after that will create has_one build association 
user.errors unless user.save