generated from filamentphp/plugin-skeleton
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Error Call to undefined method App\Models\User::getFilamentName() #29
Comments
What version of filament are you on? add the HasName to the user model from: vendor/filament/filament/src/Models/Contracts/HasName.php |
Did you manage to resolve that issu ? |
@tonypartridge, I'm getting this error message when I add the HasName to the User model: |
sounds like you haven't added it right, it should 'implement' not use within the class.
See: https://filamentphp.com/docs/2.x/admin/users#configuring-the-name-attribute
…On Wed, 18 Dec 2024 at 16:36, Lloyd Magora ***@***.***> wrote:
@tonypartridge <https://github.com/tonypartridge>, I'm getting this error
message when I add the HasName to the User model:
image.png (view on web)
<https://github.com/user-attachments/assets/27cca93c-fb54-4681-9a27-b7cedf118f69>
—
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKWBFSUNRH4AJEVHWSEJK32GGQCPAVCNFSM6AAAAABLYQXSUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJRG44DQMJTGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Installed the plugin and did a change with a user, then let the assigned role for approval check the record. When I click on the row under Approval status, it will give an error "Call to undefined method App\Models\User::getFilamentName()". When commenting out the line in vendor/eightynine/filament-approvals/resources/views/tables/columns/approval-status-column-action-view.blade.php, error is gone.
I found that the getFilamentName might be something coming with a multi tenancy setup, as I found it in the docs here: https://docs.laravel-filament.cn/docs/panels/tenancy/. Now I'm not having this setup for my filament install. Does it mean you need to have a multi tenancy setup ideally?
The text was updated successfully, but these errors were encountered: