-
Notifications
You must be signed in to change notification settings - Fork 204
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.
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
after migrating artisan migrate:refresh causes Fatal Error #44
Comments
I found a solution to the problem: I had to rename the laravel provided users and password_resets migrations to reflect a date prior to the migrations provided by the inventory package. Afterwards running |
Yup you're right, this is a bug. Apologies for the long response. To avoid this issue, I'd personally recommend publishing the migrations (using I could change publish method to rename the migration file names on the fly to use the current date, but this could also be an issue since using |
Thanks for your reply. I would have to try setting the package up again from a fresh install to know for sure, but I believe that I have to do a Some googling didn't lead me to any concrete answers to the problem, but a couple threads on the laravel repo mention making the migrations configurable through your config file. This thread laravel/framework#3265 for example discusses table name conflicts in packages. The suggestion is to make the table names configurable. Maybe it is possible to hook in here as well. If I come up with something I'll make a PR. |
To reproduce from new laravel 5.2 project:
php artisan make:auth
php artisan migrate
php artisan inventory:install
php artisan migrate:refresh
Fatal Error:
Stacktrace:
The text was updated successfully, but these errors were encountered: