设计注册不显示“某些”嵌套表单字段Rails 4 [英] Devise Registration not showing "some" nested form fields Rails 4

问题描述

我有一个修改的Devisesign_up表单（新注册），其中包含要与用户一起创建的子对象和孙子对象的字段。所有的模型关系都可以正确地设置，以访问孩子的属性。但是，当窗体呈现时，只会显示设计用户的字段和一个的子孙。

I've got a modified Devise "sign_up" form (new registration) that includes fields for child and grandchild objects to be created along with the user. All of the model relationships are set up properly with access to the child's attributes. However, when the form renders, only the fields for the Devise user and one of the grandchildren is shown.

当用户创建，他/她将被自动分配一个客户对象，一个帐户对象和一个地址对象。如下面的用户模型中的关系所示，用户有一个客户，客户有很多帐户和一个地址。以前有一个渲染表单的问题，我通过更改传递给builder方法的值来解决这个问题。 为什么不这样工作？这是我到目前为止：

When a User is created, he/she will automatically be assigned a Customer object, an Account object, and an Address object. As you can see by the relationships in the User model below, User has one Customer and Customer has many Accounts and one Address. There was previously an issue with rendering the form at all, which I solved by changing the values passed to the builder method. WHY WON'T THIS WORK??? This is what I have so far:

* user.rb

*user.rb

class User < ActiveRecord::Base
  before_create :generate_id

  # Virtual attribute for authenticating by either username or email
  # This is in addition to a real persisted field like 'username'
  attr_accessor :login

  has_one :customer, :dependent => :destroy
  has_many :accounts, through: :customer
  accepts_nested_attributes_for :customer, :allow_destroy => true
  accepts_nested_attributes_for :accounts, :allow_destroy => true

  has_one :address, through: :customer
  accepts_nested_attributes_for :customer, :allow_destroy => true
  accepts_nested_attributes_for :address, :allow_destroy => true

  has_one :administrator

  validates_uniqueness_of :email, :case_sensitive => false
  validates_uniqueness_of :id
  validates :username,
    :presence => true,
    :uniqueness=> {
        :case_sensitive => false
    }

  # User ID is a generated uuid
  include ActiveUUID::UUID
  natural_key :user_id, :remember_created_at
  belongs_to :user
  # specify custom UUID namespace for the natural key
  uuid_namespace "1dd74dd0-d116-11e0-99c7-5ac5d975667e"

  # Include default devise modules. Others available are:
  # :confirmable, :lockable, :timeoutable and :omniauthable
  devise :database_authenticatable, :registerable, :timeoutable, :recoverable, :trackable, :validatable

  # Generate a random uuid for new user id creation
  def generate_id
    self.id = SecureRandom.uuid
  end

  # Allow signin by either email or username ("lower" function might have to be removed?)
  def self.find_for_database_authentication(warden_conditions)
      conditions = warden_conditions.dup
      if login = conditions.delete(:login)
        where(conditions.to_h).where(["lower(username) = :value OR lower(email) = :value", { :value => login.downcase }]).first
      else
        where(conditions.to_h).first
      end
  end  
end

registrationrations_controller.rb

class RegistrationsController < Devise::RegistrationsController

    before_filter :configure_permitted_parameters

    # GET /users/sign_up
  def new
  @user = User.new

  build_resource({})
  self.resource[:customer => Customer.new, :account => Account.new, :address => Address.new]
    respond_with self.resource
  end

  def create
  @user = User.new
  # Override Devise default behavior and create a customer, account, and address as well

  resource = build_resource(params[:sign_up])

  if(resource.save)
    sign_in(resource_name, resource)
    respond_with resource, :location => after_sign_up_path_for(resource)
  else
    render :action => "new"
  end
  end

  protected

  def configure_permitted_parameters
    devise_parameter_sanitizer.for(:sign_up) { |u|
      u.permit(:username, :email, :password, :password_confirmation,
               customer_attributes: [:title, :firstname, :lastname, :phone1, :phone2],
               account_attributes: [:acct_type],
               address_attributes: [:address1, :address2, :zip_code])
    }
  end
end

application_controller.rb

class ApplicationController < ActionController::Base
  # Prevent CSRF attacks by raising an exception.
  # For APIs, you may want to use :null_session instead.
  protect_from_forgery with: :exception

  before_filter :configure_permitted_parameters, if: :devise_controller?

  def after_sign_in_path_for(resource)
    if current_user.role == 'admin'
        adminview_administrator_path(current_user, format: :html)
    else
        accounts_path(current_user, format: :html)
    end
  end

  protected
    def configure_permitted_parameters
        devise_parameter_sanitizer.for(:sign_up) { |u| u.permit(:username, :email, :password, :password_confirmation,
                                            customer_attributes: [:title, :firstname, :lastname, :phone1, :phone2],
                                            account_attributes: [:acct_type],
                                            address_attributes: [:address1, :address2, :zip_code]) }
        devise_parameter_sanitizer.for(:sign_in) { |u| u.permit(:login, :username, :email, :password) }
        devise_parameter_sanitizer.for(:account_update) { |u| u.permit(:username, :email, :password, :password_confirmation, :current_password) }
    end
end

views / devise / registrations / new.html.erb

<h1>Create an account</h1>
  <div class="panel panel-default" style="width: 50%; padding: 0 25px;">  

    <%= bootstrap_nested_form_for(resource, as: resource_name, url: user_registration_path(resource_name)) do |f| %>
      <%= devise_error_messages! %>
      <h3>User Info</h3>
        <!-- fields for User object -->
        <%= f.text_field :username, autofocus: true %>
        <%= f.email_field :email %>
        <%= f.password_field :password , autocomplete: "off"%>
          <% if @validatable %>
            <em>(<%= @minimum_password_length %> characters minimum)</em>
          <% end %><br />
        <%= f.password_field :password_confirmation, autocomplete: "off" %>

        <!-- fields for Customer object -->
        <%= f.fields_for :customer do |customer_fields| %>
          <%= customer_fields.text_field :title %>
          <%= customer_fields.text_field :firstname %>
          <%= customer_fields.text_field :lastname %>
          <%= customer_fields.text_field :phone1 %>
          <%= customer_fields.text_field :phone2 %>
        <% end %>

        <!-- fields for Account object -->
        <%= f.fields_for :account do |account_fields| %>
          <%= account_fields.text_field :acct_type %>
        <% end %>

        <!-- fields for Address object -->
        <%= f.fields_for :address do |address_fields| %>
          <%= address_fields.text_field :address1 %>
          <%= address_fields.text_field :address2 %>
          <%= address_fields.text_field :zip_code %>
        <% end %>
      <br />
      <div class="actions">
        <%= f.submit "Create My Account", :class => "btn btn-info" %>
      </div>
      <% end %>
  </div>
</div>

再次，上述视图呈现，但该窗体仅显示Devise新用户和一个字段（acct_type）用于帐户字段。如何获得其余的表单来显示和创建所有这些事情提交？我尝试过的一切以及我读过的所有内容都导致我认为Rails 4的strong_parameters无法识别数组中允许的属性（见上面的控制器）有问题。这可能是问题吗？如果是这样，那么怎么去传递构建所有这些东西所需的参数？

Again, the above view does render, but the form only displays the fields for Devise new user and the one field (acct_type) for the account fields. How to get the rest of form to display and create all of these things on submission? Everything I've tried and everything I've read leads me to think that there's a problem with Rails 4's strong_parameters not being able to recognize the permitted attributes (see above controllers) in an array. Could that be the issue? If so, how does one go about passing the parameters necessary to build all these things?

路由可能有问题吗？
routes.rb

Could be problem with the routes? routes.rb

Rails.application.routes.draw do
  devise_for :users, :controllers => { :registrations => "registrations" }

  devise_scope :user do
    # authentication
    post "/accounts/adminview" => "devise/sessions#new"
  end

  root 'home#index'

  resources :administrators do
    member do
      get :adminview
    end
  end

  resources :users do
    resource :customers
    resource :accounts
    resource :addresses
  end

  resources :account_types, :accounts, :addresses, :administrators, :customers, :transaction_types, :transactions, :users

end

我尝试了在SO上找到的各种方法。这已经花了几天宝贵的时间。我看不出有什么不了解的原因。有人有更好的做法吗？有没有宝石可以帮助？如果有必要，我愿意撕毁Devise并重建。

I've tried every combination of ways that I could find on SO. This has taken up days worth of valuable time. I don't see any reason why it can't work. Does anyone have a better way of doing this? Is there a gem that would help? I'm willing to tear Devise apart and rebuild if necessary.

F.Y.I。它是Rails 4和Devise 3.4.1。我还添加了nested_form gem，但没有什么不同。

F.Y.I. It's Rails 4 and Devise 3.4.1. I've also added nested_form gem, but it doesn't make a difference.

谢谢

推荐答案

如果你在控制器中提出你的参数可能看到account_attributes而是account_attributes，你正在application_controller中设置许可证，尝试替换它。

If you raise your params in controller you probably see accounts_attributes instead account_attributes you are setting in permit at application_controller, try replace it.

这篇关于设计注册不显示“某些”嵌套表单字段Rails 4的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！