As a total Ruby noob i need to do a simple thing but doing it the ruby way is not clear for me.
What is want to do is the following:
I have a devise User model with a one to one association "Account"
In the devise registration view i want to add extra form fields for this account, and that is where i am stuck.
It seems i cannot add the account fields to the view
for example this will not work:
# address is a field of Account
<%= f.text_field :address %>
How can i bring the Account model into the scope? Or is there a way to do something like this
<%= f.text_field :account['address'] %>
I have really no clue how to add account into scope or how i can access the User assoc Account properly.
Thx for the help
You need to use accepts_nested_attributes_for :account to able to add parameters from registration form.
Then whitelist these parameters by overriding devise method configure_permitted_parameters.
def configure_permitted_parameters
devise_parameter_sanitizer.permit(:sign_up, keys: [account_attributes: [:address]])
end
You might need to change which parameters needs to be whitelisted.
Then in view, you need to use fields_for like
f.fields_for(:addresss) do |address_fields|
<%= address_fields.text_field :address %>
end
Hopefully, this solves the problem. Try to search about nested attributes if something doesn't work.
you need to override devise RegistrationsController from there modify on create method to build account record when user successfully sign up
Related
I am sending an invitation to a new user using Devise Invitable. I have a related table to Users called Organizations, with a belongs_to/has_many relationship. When the new user goes to accept the invitation, it states that there must be an organization specified. How would I go about making sure the user is assigned to the inviting user's organization automatically, so that the database is updated and the invitation can be accepted?
Thank you!
Modeling after the invitation token as a hidden field, I added
<%= f.hidden_field :plan_id, :value => 1 %>
<%= f.hidden_field :organization_id, :value => 1 %>
to the edit.html.erb invitations view. This works to submit the information I'm looking for, but I'm worried that it is not secure, as those parameters could be adjusted. I also tried adding the following to the edit control in the invitations controller, but it did nothing.
resource.plan_id = 1
resource.organization_id = 1
I have a similar setup, have you tried something like this in the create section of your invitations controller?
This approach works for me, but you'll need to override the default invitations controller do it this way.
def create
#invited_user = User.invite!({:email => "bob#someone.com"}, current_user)
#invited_user.update(organization: current_organization)
...
end
I have current_organization defined in my application_controller.rb file as:
def current_organization
#current_organization ||= current_user.organization
end
if you use devise invitable, Overwrite your invitations controller's new and update actions.
In the new action associate the new user to the group, in the update action permit the foreign key and you should be good to go.
I am currently working on a rails project using devise, and I have ran into a bit of an issue.
I have the default devise:install running with my User model, and I have a another model called Profile. It belongs_to :user, and the user has_one :profile.
The issue I have, is that I require the user to have a username, so it must be done on sign up; so this is passed into the users table through devise. But I need to use the username for the users profile url, and this means crossing an attribute from the Users table, with the Profiles view.
In the user model I am using: after_create :build_profile to build a profile for that user. This creates a profile with first_name and last_name etc into the profiles table.
So, using the 'friendly_id' gem I can link to attributes from the 'profiles/index'page to the users profile. The problem is I can only use things that have been passed into the profiles table, such as first_name or last_name I can't link to :username as that is in the Users table, not the Profiles table.
In the profile_model.rb file, at the moment I am using:
extend FriendlyId
friendly_id :first_name
and in the profiles/index.html.erb file I am using:
<% #profiles.each do |profile| %>
<p><%= link_to profile.user.username, profile %></p>
<% end %>
This works for making URLs such as /profiles/John but John is no good as it is not unique.
Have you considered using nested routes? In your routes.rb file you can have:
resources :users do
resources :profiles
end
That way, you then use something like <%= link_to user_profile_path(#profile.user, #profile), #profile %>
I'm trying to user Devise invitable to add multiple users at once. Basically when someone creates an account, the first thing they'll want to do is add a bunch of users using the invitable form...
just not sure how to duplicate fields in the form and have them send a create request for each entry.
Thanks in advance!
This is how I would do it.
Provide a text area that accepts a comma-separated email list. Define
a new action that sends an invitation to each email in this list.
Lets assume a User model and a users controller for this example.
Define a route for the batch_invite action.
resources :users do
collection do
post 'batch_invite'
end
end
Define the batch_invite action in the users_controller
def batch_invite
#Validate the user_emails field isn't blank and emails are valid
params[:user_emails].split(",").each do |email|
User.invite!(:email => email)
end
#redirect_to appropriate path
end
A form that accepts a comma-separated list of emails in a textarea.
<%= form_tag batch_invite_users_path, :method => :post do %>
<%= label_tag "Email ids of people you'd like to invite." %>
<%= text_area_tag :user_emails %>
<%= submit_tag "Invite!" %>
<% end %>
A couple of notes :
If you like your controller skinny, you could move the logic to the model, for instance, by creating a send_batch_invitations method in your User model and pass the params[:user_emails] as an argument to that method from the users controller.
Since the method that sends the invitations could take sufficient time to complete, I would suggest you assign this task to a background job processor, such as delayed_job or resque.
There are railscasts that demonstrate the usage of these two background job processors.
I would like to have access to the user information in the invitation/accept route. When I go to the form and use
<%= resource.name %>
it won't display the User. It also appears that it isn't loading the user during the accept. Is there an easy way to show the user some information about the invite?
I can think of two options:
You could override the devise invitable controller, see:
Anyone have experience with devise_invitable?
In my case, I wanted to pass the name of the invitor.
I add an integer attribute 'invitor' to the User class. This is the id of the invitor Person. Don't forget to add 'invitor' as attr_accessible in the model.
I already had a 'name' string attribute in the User class.
In the app/views/{users|devise}/invitations/new.html.erb (path may vary depending on how you generated the views) add a hidden form field with the logged in user (invitor):
... <%= f.text_field :invitor, :value => current_user.id, :hidden => true %> ...
In the email text app/views/{users|devise}/mailer/invitation.html.erb I can refer to the invitor:
... <%= (User.find #resource.invitor).name %> has invited you to <%= root_url %>, you can accept it through the link below....
Not that elegant, but it works. Improvements that survive updates of the devise_invitable gem are welcome.
I have a model, and I have a view that displays a form for creating a new object based on that model. Let's call that form, Form1.
Once the user submits Form1, the object is created. I then want to display, on the following page, a second form Form2, which asks the user to check off various options before the object is saved to the database.
My problem is probably extremely basic. I don't know how to create Form2, given that it is not tied directly to the model. Because I am a Rails newbie, I have only created forms as following:
form_for(#object) { |f| ... }
#object is an object instantiated from the model
Problem: I do not believe that kind of code will work for my purposes here. How do I create Form2, given that it must not be based on #object or #object's model?
Some specifics from my app:
The site accepts values (Form1) before redirecting to an OAuth server.
When the user verifies her credentials on the OAuth server, she is redirected back to my site. An XML-RPC request then retrieves information about the user's account on the OAuth server.
The XML response may indicate that the user has only one account on the OAuth server. If so, some values are retrieved from the XML and added to the object--which is then (finally) saved in the database--and the user is redirected to a success page.
However, if the XML response indicates that the user has multiple accounts on the OAuth server, I want to display a form (Form2) that allows the user to select which accounts on the OAuth server to associate with my site. So Form2 really asks the user how many objects to create, rather than about specific attributes of an object.
Use form_tag instead of form_for, then use the appropriate form helpers: text_field_tag instead of f.text_field, text_area_tag instead of f.text_area, etc. Example:
<%= form_tag "/my_controller/update2" do %>
<%= text_field_tag "account", "default info" %>
<%= submit_tag "Save" %>
<% end %>
The Rails API site has a great reference to all of the _tag helpers: http://api.rubyonrails.org/classes/ActionView/Helpers/FormTagHelper.html
Starting in rails3, validations have been decoupled from ActiveRecord so you can create vanilla objects that can be used as validators with the form helpers:
class Person
include ActiveModel::Validations
attr_accessor :first_name, :last_name
validates_each :first_name, :last_name do |record, attr, value|
record.errors.add attr, 'starts with z.' if value.to_s[0] == ?z
end
end
and then in your template:
<%= form_for(Person.new) do |f| %>
...
It's a handy way to get the benefits of the form helpers for things like email forms without having to create a model object tied to your schema.
To create a table-less model,
class Person
include ActiveModel::Model
attr_accessor :first_name, :last_name
validates :first_name, :last_name, presence: true
end
Then in your view,
<%= form_for(Person.new) do |f| %>
.... your form ....
<% end %>
Another similar solution can be found at RailsCasts:
Active-Model
If you are looking to use SimpleForm then there is a specific answer for that here Does form_tag work with Simple_form?