Rails Devise: get object of the currently logged in user?

Question

我最近在rails应用程序上安装了Devise，我想知道是否有可能在其中一个模型或控制器中获取当前登录用户的实例，如果是这样，我该怎么做？

Answer 1

Devise creates convenience methods on the fly that represent your currently logged user.

However you should note that the generated method name includes the class name of your user model. eg if your Devise model is called ' User ' then the currently logged in user can be accessed with ' current_user ', and if your Devise class is ' Admin ' then the logged in admin user can be accessed with ' current_admin '.

There are a number of other methods created with similar conventions, for example ' user_signed_in? ' or again ' admin_signed_in? ', which are really nice.

These methods are available in controllers and views so you might have the following in a view:

<% if user_signed_in? %>
  <div>Signed in as... <%= current_user.email %></div>
<% end %>

Finally, if you are using two or more Devise models in your app (eg User and Admin), you can use the ' anybody_signed_in? ' convenience method to check if either of those types of user are signed in:

<% if anybody_signed_in? %>
  <h2>Special offers</h2>
  <p>All registered users will receive free monkeys!</p>
<% end %>

Update:

Since Devise version 1.2.0, ' anybody_signed_in? ' has been deprecated and replaced by ' signed_in? '

Answer 2

The Devise helper methods are only available at the controller and view layers. They are not available at the model layer (see Controller filters and helpers section of README ).

• Is it possible to get the currently logged in user from within a model? .

It is not possible via the default helper methods that Devise creates for you. However, there are many alternative methods you can use to provide the current_user to a model. The simplest way has already been suggested by Alex Bartlow, and that is to simply pass the current_user via a method to your model.

• Is it possible to get the currently logged in user from within a controllers?

Yes it is possible. Use current_<modelname> , where <modelname> is the name of the model that has Devise authentication capabilities (ie, via rails g devise <modelname> ). If, for example, your model is User , then you would use current_user . If your model is Elmo , then you would use current_elmo .

Answer 3

simple method is:

if @suit.user == current_user

example:

= link_to "Back", root_path, class: "btn btn-default"

  -if @suit.user == current_user

    = link_to "Edit", edit_suit_path, class: "btn btn-default"

    = link_to "Delete", suit_path, method: :delete, data: {confirm: "Are you sure?" }, class: "btn btn-default"

Answer 4

Pass it in as a parameter to the method call :).

One idea is to use Thread.current[:current_user] = @current_user as a before_filter - but if you're using a deployment stack like Thin + EM_Mysql2 + Rack::FiberPool, you'll need to set that to Fiber.current[:current_user] .

Those solutions are really just covering up for a lack of good design logic.