building a has_one relation with devise user in rails -


im new rails , having difficulty creating profile devise user

here profilecontroller:

class profilescontroller < applicationcontroller    before_action :set_profile, only: [:show, :edit, :update, :destroy]   before_action :authenticate_user!  def index  @profiles = profile.all end  def new  @profile = current_user.build_profile end  def create @profile = current_user.build_profiles(profile_params) redirect_to profiles_path end  def show  end  def edit  end  def update @profile.update(profile_params) redirect_to(profiles_path(@profile)) end  def destroy @profile.destroy redirect_to profiles_path end  private def profile_params params.require(:profile).permit(:university, :degree) end  def set_profile @profile = profile.find(params[:id]) end  end

when run rails server can submit form nothing getting stored in model 'profile'

here index.html.erb data should appear:

<h2>profiles</h2>  <% @profiles.each |profile| %>    <%= link_to profile %>     <%= profile.university %>   <% end %>     <%= profile.degree %>  <% end %>

user.rb file:

has_one :profile

and profile.rb file:

belongs_to :user

nothing seems getting saved profile model , nothing getting displayed on index.html.erb. have created migration store user_id in profile model.

thank help

by far best way create profile user build when user object created:

#app/models/user.rb class user < activerecord::base    has_one :profile    before_create :build_profile    accepts_nested_attributes_for :profile end  #app/models/profile.rb class profile < activerecord::base    belongs_to :user end

this build blank profile each time new user created. means each user only ever have one profile, they'll able populate & edit.

in regards issue, there several points:

  1. don't list "profiles" index, list users & pull profile data
  2. if managing profile, nest under associative user model

here's how that:

# config/routes.rb resources :users, only: :index resource :profile, only: [:show, :update]  #app/controllers/profiles_controller.rb class profilescontroller < applicationcontroller    def show    end     def update       redirect_to :show if current_user.update profile_params    end     private     def profile_params       params.require(:user).permit(profile_attributes: [:name])    end end  #app/views/profiles/show.html.erb <%= form_for current_user, url: profile_path |f| %>    <%= f.fields_for :profile |p| %>       <%= p.text_field :name %>    <% end %>    <%= f.submit %> <% end %>

update

my post above do.

the way works simple -- when user created (ie have gone trouble of filling out details), rails backend automatically creates blank profile object.

this several things:

  1. always makes sure have profile each user (you don't have go bother of making them "create" profile).

  2. gives ability validate inputted data on created profile (not having guess whether it's been done).

--

if you're getting undefined method build_profile, means associations incorrect.

all singular associations have build_[association] defined instance methods. code provided fires build_profile has_one association. time "undefined" if association plural

--

update

enter image description here

this suggests routing error.

considering appears @ root, think problem here:

#app/views/layouts/application.html.erb <%= link_to "profile", profile_path %>

you don't have edit_profile_path -- should profile_path


Comments

Post a Comment

Popular posts from this blog

authentication - Mongodb revoke acccess to connect test database -

i have ec2 instance mongodb 3.2.0 installed. have user admin access. can connect user , perform operation remotely. 1 can connect database test remote if knows ip mongo 11.11.11.11. although not able make operations, want restrict access user credentials can connect server. first need create users , grant roles users, example: use admin db.createuser( { user: "myuseradmin", pwd: "abc123", roles: [ { role: "useradminanydatabase", db: "admin" } ] } ) then need start server --auth parameter mongod --auth more information here
Read more

r - Update two sets of radiobuttons reactively - shiny -

i have read ( how make choices in radiobuttons reactive in shiny? ) shows me how update radiobutton s in reactive way. however, when try , update 2 sets of buttons same data, 1 set renders. example: server: # create example data wafer <- rep(c(1:3), each=3) length <- c(1,1,2,1,1,1,3,5,1) width <- c(3,1,6,1,1,1,1,1,6) dd <- data.frame(wafer, length, width) shinyserver(function(input, output, session){ # create reactive dataframe store data values <- reactivevalues() values$df <- data.frame() # lengths , widths of wafer user input <- eventreactive(input$do, { subset(dd, wafer %in% input$wafer, select = length:width) }) # update reactive data frame lengths , widths have been selected user input observe({ if(!is.null(a())) { values$df <- rbind(isolate(values$df), a()) } }) output$wl <- renderdatatable({ a() }) # update radio buttons unique length , widths stored in values$df # ever "observe" put first in co...
Read more

ios - Realm over CoreData should I use NSFetchedResultController or a Dictionary? -

i'm working on app using core data , nsfetchedresultcontroller many reasons switch use realm. saw there "realm version" of nsfetchedresultcontroller on github wouldn't compatible current code using core data. the view controller displaying list of people same school, address book. list sublist of people studied in same city. so thinking make 1 unique request database retrieve list of people , filter locally list within 1 dictionary per school [string: anyobject] string section name within tableview , anyobject array of people. first solution, make nsfetchedresultcontroller each school predicate filtering location. delete actions etc.. handled delegates -> not compatible realm create dictionaries , update them each actions... -> works realm it's annoying code. any better solution? edit: i need clarify request: i'd write class inherit uitableviewcontroller. this class has list of people sorted in alphabetical order the tableview has ...
Read more