You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 20, 2019. It is now read-only.
Why does the db need to be reset (rake db:drop db:create db:migrate db:seed) in order to authenticate.
So I get that a feature related to migration might screw up if the db is not migrated properly...
But when there is no changes to the authentication tables, it should work fine....
Instead, when trying to authenticate, our custom "close popup window" view fails, instead redirecting to the home page.
The obvious fix is just reset the db every time... but when we get to a production environment that will not be feasible. We have to migrate only (not drop, create, or seed). So whatever is "patching" this problem when we reset needs to be discovered.
The text was updated successfully, but these errors were encountered:
Why does the db need to be reset (rake db:drop db:create db:migrate db:seed) in order to authenticate.
So I get that a feature related to migration might screw up if the db is not migrated properly...
But when there is no changes to the authentication tables, it should work fine....
Instead, when trying to authenticate, our custom "close popup window" view fails, instead redirecting to the home page.
The obvious fix is just reset the db every time... but when we get to a production environment that will not be feasible. We have to migrate only (not drop, create, or seed). So whatever is "patching" this problem when we reset needs to be discovered.
The text was updated successfully, but these errors were encountered: