We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello. I think I may have found a bug.
Simplified version of my routes config looks like this:
1: devise_for :admin_users, {class_name: 'User'}.merge(ActiveAdmin::Devise.config) 2: ActiveAdmin.routes(self) 3: devise_for :users
Luckily I can use switch_user in development environment because view_guard & controller_guard conditions look like:
development
Rails.env.development? || current_user&.email == 'my@email.com
Unfortunately It doesn't work in production environment because current_user is always nil.
comment out the 1st line with devise_for :admin_users and current_user is working again and not nil(for signed in users).
devise_for :admin_users
Does anyone have an idea on how to make it work with ActiveAdmin?
The text was updated successfully, but these errors were encountered:
same here:
config.controller_guard = ->(__current_user, request, original_user) { #users always nil here }
Sorry, something went wrong.
No branches or pull requests
Hello. I think I may have found a bug.
Simplified version of my routes config looks like this:
Luckily I can use switch_user in
development
environment because view_guard & controller_guard conditions look like:Unfortunately It doesn't work in production environment because current_user is always nil.
Steps to reproduce:
comment out the 1st line with
devise_for :admin_users
and current_user is working again and not nil(for signed in users).Does anyone have an idea on how to make it work with ActiveAdmin?
The text was updated successfully, but these errors were encountered: