Closed herman5 closed 10 years ago
Thanks but there isn't much we can do without taking a look at the application. Can you provide a sample application that reproduces the error? :)
Absolutely! As stated above I have the application hosted on Heroku :-)
URL: http://testdomain.dcmdashboard.com
email: moderator@example.com
password: password
I checked that application linked but I couldn't find anything from external. We need to check the source, debug, access the logs. That's why we need a sample application that reproduces the error.
Sorry for the misunderstanding. I've made the repository public and it can be found at https://github.com/herman5/warthog
@herman5 opened a duplicate ticket for Active Admin: https://github.com/gregbell/active_admin/issues/2839
I'd suggest closing this ticket, as it's much more likely to be AA's problem.
After successfully logging in to my rails application in production mode, I will attempt to click on one of the filter buttons at the top of the table: 'All Servers', 'In Progress', or 'Remediation.' After pressing one of these buttons, the session will be destroyed and redirect the user back to the login page; however, this does not occur in the development environment. In the dev environment, when the user presses one of the filter buttons, the proper scope is applied and no redirection occurs.
After comparing the production logs to the development logs, the error appears to manifest in Devise::SessionsController#new
I have the application hosted on Heroku, so the effects can be seen.
URL: http://testdomain.dcmdashboard.com
email: moderator@example.com
password: password
After logging in and pressing a filter button (GET "/?order=id_desc&page=1&scope=in_progress") in the dev environment:
After logging in and pressing the filter button (GET "/?order=id_desc&page=1&scope=in_progress") in the production environment: