Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
i get the following error on navigtion-menu.blade.php
the debugger indicates that the error orginates from these lines
{{ Auth::user()->name }} {{ Auth::user()->email }}In that case, you do not have an authenticated user.
I expect that you are most likely using a view component/partial which was intended for view(s) to be shown to authenticated users only? Since you own the view template (i.e. it is not in a vender sub-directory), you can wrap relevant parts in an @auth check
// resources/views/navigation-menu.blade.php
@auth
{{ Auth::user()->name }} {{ Auth::user()->email }}
@endauth
@tykus Thanks. It helps me
Do you have Auth::user()->name on the forgot password page as well (separately to the navigation.blade.php template?
🤷♂️
Has the error changed from earlier; is it pointing to another view template?
I don't know your code...
Is this the navigation.blade.php? Where is the opening @auth directive?
Can you answer the second question? And properly format your code snippets?
There are references to Auth::user() everywhere in that view template, but nowhere are there @auth checks?
I expect that you are most likely using a view component/partial which was intended for view(s) to be shown to authenticated users only
I wasn't joking earlier...
Up to you. However, entire divs will not make sense if there is not authenticated user, so it'd make sense to identify these areas of the template and wrap them in the auth check.
👍 Mark it solved if you're all set
If you are using Jetstream, it uses Forty, so if you created user groups and these created with a seeder it does not add a group, if you want to quickly solve it, it is to create a record in team_user and add it to the created users.
ErrorException, Attempt to read property "name" on null, {{ Auth::user()->name }}....I have a similar problem, the login is fine, it's just that when I leave the computer alone and come back, it throws me an error message Auth::user()->name, this must be because the session expired, but the query is I can control this? something that sends the user back to login instead of sending this error
@claudiorigo use the auth middleware on Routes that need an authenticated user (and ultimately that return view(s) that expect an authenticated user). Redirection to login will be automatic whenever the user navigates to such routes after the Session has expired.
Please or to participate in this conversation.