8000 auth:reminders migration does not support rollback · Issue #1391 · laravel/framework · GitHub
[go: up one dir, main page]
Skip to content

auth:reminders migration does not support rollback #1391

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom
Closed
PavelPolyakov opened this issue May 24, 2013 · 4 comments
Closed

auth:reminders migration does not support rollback #1391

PavelPolyakov opened this issue May 24, 2013 · 4 comments

Comments

@PavelPolyakov
Copy link

If you create the "password reminders" migration using php artisan auth:reminders, then it's not possible to use php artisan migrate:reset for this migration , because Migrator is not able to find the CreatePasswordRemindersTable class.

Probably it takes the place because those procedures:

Generating optimized class loader...
Compiling common classes...

Are not initialized when creating the auth:reminders migration.
@robclancy
Copy link
Contributor

do composer dumpautoload?

@PavelPolyakov
Copy link
Author

@robclancy
Sorry, what do you want to check this way?
The "app/database/migrations" is present in the composer autoload classmap.

I've solved the issue the next way:

  1. did php artisan migrate:make create_password_reminders_table
  2. copied the code which was generated with the php artisan auth:reminders command
  3. profit

@robclancy
Copy link
Contributor

See if the rollback works if you do composer dumpautoload before running it?

@PavelPolyakov
Copy link
Author

I can't say for sure, because I haven't done the clean experiment, but if I remove working auth migration, then create it again and try to do php artisan migrate:reset then it fails (because it would try to load an old file).

But after the composer dumpautoload it would work fine.

Thanks, but anyway I think it's expected that the auth:reminders migration should work by default.

@taylorotwell taylorotwell mentioned this issue May 24, 2013
Closed
This was referenced Sep 1, 2014
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@PavelPolyakov @robclancy
0