Why I always getting logs Auth::user() on null in my blade template?
I use {{ Auth::user()->name }} on all of my blade templates. It successfully shown the user's name though, but why in my logs it written Auth::user()->name is Trying to get property 'name' of non-object. These logs just make things go crazy.
What am I doing wrong? Thanks for your help!
laravel-5.5
asked Nov 13 '18 at 6:14
Muhammad Alfian RasyidinMuhammad Alfian Rasyidin
34
add a comment |
I use {{ Auth::user()->name }} on all of my blade templates. It successfully shown the user's name though, but why in my logs it written Auth::user()->name is Trying to get property 'name' of non-object. These logs just make things go crazy.
What am I doing wrong? Thanks for your help!
laravel-5.5
asked Nov 13 '18 at 6:14
Muhammad Alfian RasyidinMuhammad Alfian Rasyidin
34
add a comment |
I use {{ Auth::user()->name }} on all of my blade templates. It successfully shown the user's name though, but why in my logs it written Auth::user()->name is Trying to get property 'name' of non-object. These logs just make things go crazy.
What am I doing wrong? Thanks for your help!
laravel-5.5
asked Nov 13 '18 at 6:14
Muhammad Alfian RasyidinMuhammad Alfian Rasyidin
34
I use {{ Auth::user()->name }} on all of my blade templates. It successfully shown the user's name though, but why in my logs it written Auth::user()->name is Trying to get property 'name' of non-object. These logs just make things go crazy.
What am I doing wrong? Thanks for your help!
laravel-5.5
laravel-5.5
asked Nov 13 '18 at 6:14
Muhammad Alfian RasyidinMuhammad Alfian Rasyidin
34
asked Nov 13 '18 at 6:14
Muhammad Alfian RasyidinMuhammad Alfian Rasyidin
34
asked Nov 13 '18 at 6:14
Muhammad Alfian RasyidinMuhammad Alfian Rasyidin
34
asked Nov 13 '18 at 6:14
Muhammad Alfian RasyidinMuhammad Alfian Rasyidin
34
asked Nov 13 '18 at 6:14
Muhammad Alfian RasyidinMuhammad Alfian Rasyidin
34
34
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Your code might fail on below code since you don't have a check here if you are logged in or not!
{{ auth()->user()->name }}
answered Nov 13 '18 at 11:50
Ismoil ShifoevIsmoil Shifoev
1,425812
It probably true.{{ Auth::user() && Auth::user()->name }This code is fine. I think we need to handle the exception, even though the app requires user to login first. Thank you!
– Muhammad Alfian Rasyidin
Nov 27 '18 at 16:36
Yes handle exception you need to do. You are welcome!!
– Ismoil Shifoev
Nov 27 '18 at 17:53
add a comment |
First clear out the log file empty it. Assuming its storage/logs/laravel.log
In terminal use following command to look for the live changes in your log file.
{project_root} > tail -f storage/logs/laravel.log
if above doesn't work use following:
{project_root} > sudo tail -f storage/logs/laravel.log
Now, you can keep taps on the log file if anything is logged in it.
Open your browser and terminal/console side by side and go through your App and look for the trigger point when the Exception is logged and shown on the terminal and start debugging from there.
answered Nov 13 '18 at 9:32
Omar AbdullahOmar Abdullah
1967
add a comment |
Did you login your application. when you login then only you can get info from auth.
you don't worry about login sign up process in laravel.
just run php artisan make:auth. laravel scaffolding working for you.
this is simple template. you can customize what ever you want.
answered Nov 13 '18 at 10:17
sathyakrishnapalanisathyakrishnapalani
14
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53274877%2fwhy-i-always-getting-logs-authuser-on-null-in-my-blade-template%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your code might fail on below code since you don't have a check here if you are logged in or not!
{{ auth()->user()->name }}
answered Nov 13 '18 at 11:50
Ismoil ShifoevIsmoil Shifoev
1,425812
It probably true.{{ Auth::user() && Auth::user()->name }This code is fine. I think we need to handle the exception, even though the app requires user to login first. Thank you!
– Muhammad Alfian Rasyidin
Nov 27 '18 at 16:36
Yes handle exception you need to do. You are welcome!!
– Ismoil Shifoev
Nov 27 '18 at 17:53
add a comment |
Your code might fail on below code since you don't have a check here if you are logged in or not!
{{ auth()->user()->name }}
answered Nov 13 '18 at 11:50
Ismoil ShifoevIsmoil Shifoev
1,425812
It probably true.{{ Auth::user() && Auth::user()->name }This code is fine. I think we need to handle the exception, even though the app requires user to login first. Thank you!
– Muhammad Alfian Rasyidin
Nov 27 '18 at 16:36
Yes handle exception you need to do. You are welcome!!
– Ismoil Shifoev
Nov 27 '18 at 17:53
add a comment |
Your code might fail on below code since you don't have a check here if you are logged in or not!
{{ auth()->user()->name }}
answered Nov 13 '18 at 11:50
Ismoil ShifoevIsmoil Shifoev
1,425812
Your code might fail on below code since you don't have a check here if you are logged in or not!
{{ auth()->user()->name }}
answered Nov 13 '18 at 11:50
Ismoil ShifoevIsmoil Shifoev
1,425812
answered Nov 13 '18 at 11:50
Ismoil ShifoevIsmoil Shifoev
1,425812
answered Nov 13 '18 at 11:50
Ismoil ShifoevIsmoil Shifoev
1,425812
answered Nov 13 '18 at 11:50
Ismoil ShifoevIsmoil Shifoev
1,425812
1,425812
It probably true.{{ Auth::user() && Auth::user()->name }This code is fine. I think we need to handle the exception, even though the app requires user to login first. Thank you!
– Muhammad Alfian Rasyidin
Nov 27 '18 at 16:36
Yes handle exception you need to do. You are welcome!!
– Ismoil Shifoev
Nov 27 '18 at 17:53
add a comment |
It probably true.{{ Auth::user() && Auth::user()->name }This code is fine. I think we need to handle the exception, even though the app requires user to login first. Thank you!
– Muhammad Alfian Rasyidin
Nov 27 '18 at 16:36
Yes handle exception you need to do. You are welcome!!
– Ismoil Shifoev
Nov 27 '18 at 17:53
It probably true.
{{ Auth::user() && Auth::user()->name } This code is fine. I think we need to handle the exception, even though the app requires user to login first. Thank you!– Muhammad Alfian Rasyidin
Nov 27 '18 at 16:36
It probably true.
{{ Auth::user() && Auth::user()->name } This code is fine. I think we need to handle the exception, even though the app requires user to login first. Thank you!– Muhammad Alfian Rasyidin
Nov 27 '18 at 16:36
Yes handle exception you need to do. You are welcome!!
– Ismoil Shifoev
Nov 27 '18 at 17:53
Yes handle exception you need to do. You are welcome!!
– Ismoil Shifoev
Nov 27 '18 at 17:53
add a comment |
First clear out the log file empty it. Assuming its storage/logs/laravel.log
In terminal use following command to look for the live changes in your log file.
{project_root} > tail -f storage/logs/laravel.log
if above doesn't work use following:
{project_root} > sudo tail -f storage/logs/laravel.log
Now, you can keep taps on the log file if anything is logged in it.
Open your browser and terminal/console side by side and go through your App and look for the trigger point when the Exception is logged and shown on the terminal and start debugging from there.
answered Nov 13 '18 at 9:32
Omar AbdullahOmar Abdullah
1967
add a comment |
First clear out the log file empty it. Assuming its storage/logs/laravel.log
In terminal use following command to look for the live changes in your log file.
{project_root} > tail -f storage/logs/laravel.log
if above doesn't work use following:
{project_root} > sudo tail -f storage/logs/laravel.log
Now, you can keep taps on the log file if anything is logged in it.
Open your browser and terminal/console side by side and go through your App and look for the trigger point when the Exception is logged and shown on the terminal and start debugging from there.
answered Nov 13 '18 at 9:32
Omar AbdullahOmar Abdullah
1967
add a comment |
First clear out the log file empty it. Assuming its storage/logs/laravel.log
In terminal use following command to look for the live changes in your log file.
{project_root} > tail -f storage/logs/laravel.log
if above doesn't work use following:
{project_root} > sudo tail -f storage/logs/laravel.log
Now, you can keep taps on the log file if anything is logged in it.
Open your browser and terminal/console side by side and go through your App and look for the trigger point when the Exception is logged and shown on the terminal and start debugging from there.
answered Nov 13 '18 at 9:32
Omar AbdullahOmar Abdullah
1967
First clear out the log file empty it. Assuming its storage/logs/laravel.log
In terminal use following command to look for the live changes in your log file.
{project_root} > tail -f storage/logs/laravel.log
if above doesn't work use following:
{project_root} > sudo tail -f storage/logs/laravel.log
Now, you can keep taps on the log file if anything is logged in it.
Open your browser and terminal/console side by side and go through your App and look for the trigger point when the Exception is logged and shown on the terminal and start debugging from there.
answered Nov 13 '18 at 9:32
Omar AbdullahOmar Abdullah
1967
answered Nov 13 '18 at 9:32
Omar AbdullahOmar Abdullah
1967
answered Nov 13 '18 at 9:32
Omar AbdullahOmar Abdullah
1967
answered Nov 13 '18 at 9:32
Omar AbdullahOmar Abdullah
1967
1967
add a comment |
add a comment |
Did you login your application. when you login then only you can get info from auth.
you don't worry about login sign up process in laravel.
just run php artisan make:auth. laravel scaffolding working for you.
this is simple template. you can customize what ever you want.
answered Nov 13 '18 at 10:17
sathyakrishnapalanisathyakrishnapalani
14
add a comment |
Did you login your application. when you login then only you can get info from auth.
you don't worry about login sign up process in laravel.
just run php artisan make:auth. laravel scaffolding working for you.
this is simple template. you can customize what ever you want.
answered Nov 13 '18 at 10:17
sathyakrishnapalanisathyakrishnapalani
14
add a comment |
Did you login your application. when you login then only you can get info from auth.
you don't worry about login sign up process in laravel.
just run php artisan make:auth. laravel scaffolding working for you.
this is simple template. you can customize what ever you want.
answered Nov 13 '18 at 10:17
sathyakrishnapalanisathyakrishnapalani
14
Did you login your application. when you login then only you can get info from auth.
you don't worry about login sign up process in laravel.
just run php artisan make:auth. laravel scaffolding working for you.
this is simple template. you can customize what ever you want.
answered Nov 13 '18 at 10:17
sathyakrishnapalanisathyakrishnapalani
14
answered Nov 13 '18 at 10:17
sathyakrishnapalanisathyakrishnapalani
14
answered Nov 13 '18 at 10:17
sathyakrishnapalanisathyakrishnapalani
14
answered Nov 13 '18 at 10:17
sathyakrishnapalanisathyakrishnapalani
14
14
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53274877%2fwhy-i-always-getting-logs-authuser-on-null-in-my-blade-template%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
