Hi there.
I know that the title might seem a little cryptic, but allow me to elaborate on the problem:
Firstly, I have a controller named +users_controller+ this is not surprisingly used by the users to control there own profiles. In it I have defined a +response_for+ block, so that if the user ticks the "return to edit mode" box, they will be returned to the edit method instead of the show. This is working great.
Secondly, and in ere lies the problem; I have a controller named +admin_users_controller+, which is nested in admin/users_controller.rb and defines +Admin::UsersController+. This controller is also made resourceful (actions: index, edit, update and destroy), and also has a +response_for+ method to ensure that the admin gets redirected to the +admin_users_index_path+ instead of the view path for the user after updating. But the +response_for+ fails for the nested users-controller!
At first glance it would seem that the +response_for+ defined in the +UsersController+ is overwriting the one defined in the +Admin::UsersController+. But why is this? And how to I allow for custom responses in the nested controller?
Best regards.
Emil
) is private.
Btw. Both controllers uses the same model user.rb (placed directly in the app/models directory -- Non-nested).
I very much doubt any interference between the two controllers. However, "+response_for+ fails for the nested users-controller!"
In what way does it fail? It does the default behaviour? It sends you to a particular location?
If you could let me know that, we could definitely clean this stuff up.
Well, I can't figure out if it's being ignored or simply doesn't do anything.
admin/users_controller.rb
response_for :create do
redirect_to A end
users_controller.rb
response_for :create do
redirect_to B end
Hitting the nested controller will trigger the non-nested controllers redirect_to. I have no idea why though.
And you are suuuper sure that the code in those response_for's are actually being executed?
If you are expecting A, getting B, and B is the default behaviour, then this shouldnt' be a problem.
See, m_r doesn't keep some global list of versions of itself or anything. In fact, it would be hard to get it to know where else its installed (without some hooks or something). It just extends the local UsersController. So, all the m_r code and concerns are basically wrapped up in each Controller.
If you want to privately send me some of your problem code, I'd be happy to look at it. Also, I'd need to know what exact version of Ruby and Rails you are running.
-hampton.
I'm going to compile a better description, including some examples and I will PM it to you. It will however take a little time. I need to be absolutely suuuper sure that I'm not making a mistake.
Best regards
Emil