Rails%203%20In%20Action

200 CHAPTER 8 More authorization
The path for this link_to (which is not yet defined) takes you to the Admin
::PermissionsController’s index action. To get this link_to to work, define that
permissions are nested under users in the config/routes.rb, and add the admin
namespace in the definition using this code:
namespace :admin do
root :to => "base#index"
resources :users do
resources :permissions
end
end
With these changes in the config/routes.rb file, the admin_user_permissions_path
used in the link_to will now be defined. When you run the feature using bin/cucumber
features/assigning_permissions.feature, you see there’s more to be done for this
step:
And I follow "Permissions"
uninitialized constant Admin::PermissionsController
➥(ActionController::RoutingError)
Ah, of course! You must create the controller for this link!
THE PERMISSIONS CONTROLLER
You can generate the Admin::PermissionsController file by running this command:
rails g controller admin/permissions
Along with an app/controllers/admin/permissions_controller.rb file, this command
generates other goodies, such as a helper and a directory for the views at app/views/
admin/permissions. Before you go further, you must modify this file to make the class
inherit from the right place so that only admins can access it. Open the file, and
change the first line to this:
class Admin::PermissionsController < Admin::BaseController
This line makes the controller inherit from the Admin::BaseController class, which
restricts all actions in this controller to only admin users. When you run the feature
again, the index action is missing from this controller:
And I follow "Permissions"
The action 'index' could not be found for Admin::PermissionsController
Obviously, you need to define this action before you carry on. Inside this action, load
all the permissions for the user you’re currently looking at, and then, with the view,
display a page from which an admin can choose what permissions this user has on
each project. It’d be helpful if this user was loaded by a before_filter because you’ll
need it for the action that updates the permissions later. With all this in mind, update
the entire controller to resemble the following listing.