How do I make a method available inside a partial? - ruby-on-rails-4

I'm a rails beginner learning rails 4 and I'm trying to learn by doing. I'm making a simple blog that I want some simple user authentication on. I'm trying to learn here, so I don't want to implement Devise, etc. I have a header partial that takes care of my site header and I'm trying to put a link to logout that only shows if a user is logged in. I have a simple session controller that has a new action for the signup form, a create action that sets the current user after matching the email and password and sets session[:user_id] = #current_user.id, and a destroy action that nils out the session. In my application controller I have a method like this
def logged_in?
!session[:user_id].nil?
end
In my _header.html.erb partial, I have
<% if logged_in? %>
(My link)
<% end %>
When I load the page it tells me it can't find the "logged_in?" method. Anyone know why? Thanks.

Methods on controllers are by default not exposed to the views (which your partial is part of).
2 solutions:
Create your logged_in? method as a helper method, for example in an AuthenticationHelper. Doing this you cannot access it from controllers, though.
Expose your controller method to the view using helper_method:
class ApplicationController < ActionController::Base
helper_method :logged_in?
def logged_in?
[...]
end
end

Couldn't you just use:
if #current_user

Related

Rails 4 undefined method `any?' for nil:NilClass

I am running a chat application on my RoR app. I want to be able to render the user chat conversations from my layouts/application.html.erb to have the user chat conversations across all pages but the chat is only working when I run the index action method under my Users controller [class UsersController < ApplicationController]. When I have my chat on views/users/index.html.erb runs great. Just to make it available in all pages I created a render form under views/users called _chatlist.html.erb which has this line inside:
and rendered this form in my layouts/application.html.erb body as:
<%= render partial: 'users/chatlist' %>
When I do that I get this error: undefined method `any?' for nil:NilClass.
How can I solve this nil issue? Any help will be appreciated.
You are getting that error because #conversations is not initialized.
You have to write an method and call it in application_controller.rb if you want to make it available on all the pages. Your application_controller.rb should look like this.
class ApplicationController < ActionController::Base
before_filter :load_conversatios
def load_conversatios
# load you conversation here
#conversations = Conversation.all
end
end
And I think that is not a good approach to load all the conversations on all the pages. You have to make it available from ajax call.

Getting same style in another page when click to login

I am having a login page for user generated by devise gem.where I removed the registerable from model for only login not for signup.I have also generated an admin which gives default login credentials for user in seed.rb file.I have done some css work in login page. next I have generated an employee page for further process for users.
Here my doubt is the styling part what I have done in login page is also coming in employee page. I dont want that so I wrote some condition in application.html.erb
<% unless user_signed_in? %>
<%= render 'layouts/heading' %>
<% end %>
The method is defined in application.controller.rb
def user_signed_in? %>
render :layouts => 'application'
end
I tried a lot by changing conditions but it is still displaying or showing errors.
You said that you're using "device gem", but since you're talking about authentication, I assume you mean "devise"?
The user_signed_in? method is a helper which should be provided automatically by devise, and you should be able to use it in your views. You shouldn't need to define it in the application controller.
You probably want to make sure you do "before_filter :authenticate_user!" in the relevant controller (you can use the ":only" option if you only want this to apply for certain methods).
It's difficult to give any more information because you haven't said what errors you are getting. I assume you're getting some kind of syntax error on the definition of the "user_signed_in?" method, since you have an invalid "%>"on the end of the line, which I guess you copied-and-pasted from an ERB file.

Button Redirect to a controller in Rails Slim template

I have a rails controller page home_controller.rb
class HomeController < ApplicationController
def index
##users = User.all
#loan_applications = LoanApplication.all
end
def button_listing_show
redirect_to lp_banker_assignments_path
end
end
And I have this Rails Slim button code
button Go to Listings onclick="<%home.button_listing_show%>"
What i want is on the onclick events the page redirects to this path.
Can someone provide an answer for me either in Slim or in Rails.
Thanks
button Go to Listings onclick="#{lp_banker_assignments_path}"
You are just generating a path with that function, so why not just interpolate to the path directly?
Docs for variable interpolation

use devise sign_in view in layout

I have 2 layout
applicattion.html.erb
login.html.erb
I use devise.
in application_controller.rb I write this code:
protect_from_forgery with: :exception
layout :another_by_method
private
def another_by_method
if user_signed_in?
"application"
else
"login"
end
end
by this code, if user don't login_in, login.html.erb show.
I want use devise sign_in form in login.html.erb, but because of this code all of the page are redirect_to login.html.
I use below code too,
<%= render partial: "devise/sessions/new"%>
but get this error:
ActionView::MissingTemplate in Devise::Sessions#new
any idea?!
You are trying to render a partial, but devise/sessions/new is not a partial.
Anyway, have you generated the views with rails generate devise:views? If so, you could do that:
= render file: 'devise/sessions/new'
Use file instead of partial, but you will need all the variables provided by Devise, as resource, resource_name, or devise_mapping.

How to use activemodel to validates date_time_select

I am using rails 4.0
I wonder how to validate date_select with activemodel
let's suppose I have the code as follow
app/models/book.rb
class Book
include ActiveModel::Model
include ActiveModel::Validations
attr_accessor :title, :written_on
validates :title, presence: true, allow_blank: false
# How validates :written_on if I use date_select Please look in my view below
end
app/controllers/books.rb
class BooksController < ApplicationController
#...
def new
#book = Book.new
end
def create
#book = Book.new(book_params)
if #book.valid?
#Do something
end
end
#...
end
app/views/books/new.html.erb
<% form_for #book do |f| %>
...
<%= f.date_select :written_on %>
...
<% end %>
I have also try adding
attr_accessor 'written_on(1i)'
to my book model but I got the error invalid attribute name 'written_on(1i)'
Really appreciated for the help here.
Just to clarify, I think you're asking why you're not even able to set the written_on attribute, let alone validate it-- when I used your exact code locally and tried to create a new book, on submit I got undefined method `written_on(1i)=' for Book.
This is because the Book model isn't inheriting from ActiveRecord::Base; you're just including ActiveModel::Model and ActiveModel::Validations. The Rails guide on form helpers says "when Active Record sees parameters with such names it knows they must be combined with the other parameters and given to a constructor appropriate to the column type."
So I started looking through the Rails source to see where this functionality was implemented, and it's currently in ActiveRecord::AttributeAssignment. There is currently an open pull request that moves this functionality to ActiveModel so that in cases like yours, you'd be able to use it by including ActiveModel::AttributeAssignment.
I'm not sure what you can do until that gets merged in and released. I tried including ActiveRecord::AttributeAssignment and still got the same error, and looking at the pull request, it doesn't seem to be that straightforward. You could fork Rails and apply that pull request, but you'd have to maintain your own Rails for a while until that lands, then get back on a released version.