-
-
Notifications
You must be signed in to change notification settings - Fork 377
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
[Symfony\Component\Debug\Exception\FatalThrowableError] Class name must be a valid object or a string #123
Comments
Take a look at Laravel logs to find which line causes it and what is the backtrace. |
[2017-04-07 07:28:18] local.ERROR: Symfony\Component\Debug\Exception\FatalThrowableError: Class name must be a valid object or a string in C:\xampp\htdocs\Wegorder\vendor\laravel\framework\src\Illuminate\Database\Eloquent\Concerns\HasRelationships.php:487 |
Can't you do some research on you own? P. S. Wrap anything that contains a hashtag(#) in code blocks(```). You just referenced 45 issues and pull requests for no reason.
You can also attach a file to a GitHub comment. |
[Symfony\Component\Debug\Exception\FatalThrowableError]
Class name must be a valid object or a string
when using
$admin->attachPermission($createPost);
// equivalent to $admin->permissions()->attach([$createPost->id]);
$owner->attachPermissions([$createPost, $editUser]);
// equivalent to $owner->permissions()->attach([$createPost->id, $editUser->id]);
$owner->syncPermissions([$createPost, $editUser]);
// equivalent to $owner->permissions()->sync([$createPost->id, $editUser->id]);
The text was updated successfully, but these errors were encountered: