Closed eflames closed 9 years ago
rappasoft
commented
9 years ago This package doesn't have a logout method, it uses the default logout method that ships with L5. If you're having an issue with it, it is probably erroring from some other part in your project. Are you doing anything special anywhere when the user logs out?
eflames
commented
9 years ago No @rappasoft nothing special... Deleted_at field is updated when i edit any user... I want make you a question... In the installation section, do i need to add deleted_at field by myself?
rappasoft
commented
9 years ago Yes one of the per-requisites is to have deleted_at columns already. The reason for me not adding them in the migration is that if it was an existing project and the person already had then, the migration would fail.
On 4/3/15 10:21 AM, eflames wrote:
No @rappasoft https://github.com/rappasoft nothing special... Deleted_at field is updated when i edit any user... I want make you a question... In the installation section, do i need to add deleted_at field by myself?
— Reply to this email directly or view it on GitHub https://github.com/rappasoft/vault/issues/17#issuecomment-89302323.
eflames
commented
9 years ago oh i see... My project is completely new, with vault package only and cant edit users because the system updates "deleted_at" column eliminating my user...
If u want i will close this issue, i will create a new one project with new changes about "foreach problem" and let u know the results...
My mail is eflames at gmail, i added u to hangout.
Thanks for all Anthony
Kind regards.
rappasoft
commented
9 years ago I don't think you need to make a new project, but if you want to use my boilerplate, should be set up well to work with vault.
Vault update "deleted_at" field on logout action. This deletes my user and need to "null" the field again to log in.