Skip to content
Discussion options

You must be logged in to vote

This issue exists if the "artisan db:upgrade" command was run before 4.0.0-rc3 - so yes you have to run the fix command

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by samuelwei
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants