-
Notifications
You must be signed in to change notification settings - Fork 11k
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
migrate:rollback Call to a member function supportsSchemaTransactions() on null, after last composer update #15892
Comments
|
this method used in laravel/framework/src/Illuminate/Database i have problem from this commit 7a35d72#diff-a66c98fc0ca13ef8851970c40f8342d1 |
Hi @kashtanoff ! Facing the same issue you're having, I dug into the framework a bit and replaced Hope I helped you out on this! 😀 |
@kashtanoff do a composer update now, they fixed it already 😀 |
I'm using latest version 5.3.19 but I'm still facing this problem when using a custom connection ( I've used jenssegers/laravel-mongodb as my mongodb package.
class CreateLogTable extends Migration {
protected $connection = 'mongodb';
public function up() {}
} @ellej16 #15892 Can anyone help me please? |
+1 to @ahmadazimi. Rolled back to Laravel v5.3.18, which works. |
Hi @dondencker and @ahmadazimi , As far as I checked jensessegers/laravel-mongodb's source code, it's missing a few key methods/attributes introduced by this particular PR: #15780 . If I remember correctly, one of those are: As @dondencker has pointed out rolling back to v5.3.18 works, that could be the easiest route to take, though if you can contact/make a pull request for laravel-mongodb to keep it up to date that'd be lovely. Cheers! . |
FatalErrorException in MediaController.php line 23: Showing this issue when i try to store my image to folder. |
Hi @OmarFaruque , I think you should post that somewhere else, this specific thread is for migration files not being rolled back (and the current topic being laravel-mongodb encountering the same issue). Hope you find the answer to your problem! |
Thanks @ellej16 for your replay, my problem Also solved. |
composer.json contents:
The text was updated successfully, but these errors were encountered: