Mixing
Access the errors in Laravel
I have the following function for a route named /home:
public function home(){
if(Session::has("user_id")){
return view("home");
}else{
return view("welcome", [
'error_message' => "Please log in to access that page!"
]);
}
}
Then, in my welcome view, I show the error like this:
<div class="alert alert-danger alert-dismissible fade show" role="alert">
<p> {{ $error_message }} </p>
</div>
Everything works as expected but the error keeps on showing when I refresh the page again and again. I know that the variable hasn't been unset so it is happening. But, the real question is:
Can't I do the same using MessageBag instance of Laravel?
During form validation, if error occurs, then the error gets showed up and if I refresh the page its get vanished. So, can't I bring the same behavior in my page using the method?
php validation laravel-5.2
asked Nov 20 '18 at 2:10
PHPCoderPHPCoder
386
add a comment |
I have the following function for a route named /home:
public function home(){
if(Session::has("user_id")){
return view("home");
}else{
return view("welcome", [
'error_message' => "Please log in to access that page!"
]);
}
}
Then, in my welcome view, I show the error like this:
<div class="alert alert-danger alert-dismissible fade show" role="alert">
<p> {{ $error_message }} </p>
</div>
Everything works as expected but the error keeps on showing when I refresh the page again and again. I know that the variable hasn't been unset so it is happening. But, the real question is:
Can't I do the same using MessageBag instance of Laravel?
During form validation, if error occurs, then the error gets showed up and if I refresh the page its get vanished. So, can't I bring the same behavior in my page using the method?
php validation laravel-5.2
asked Nov 20 '18 at 2:10
PHPCoderPHPCoder
386
add a comment |
I have the following function for a route named /home:
public function home(){
if(Session::has("user_id")){
return view("home");
}else{
return view("welcome", [
'error_message' => "Please log in to access that page!"
]);
}
}
Then, in my welcome view, I show the error like this:
<div class="alert alert-danger alert-dismissible fade show" role="alert">
<p> {{ $error_message }} </p>
</div>
Everything works as expected but the error keeps on showing when I refresh the page again and again. I know that the variable hasn't been unset so it is happening. But, the real question is:
Can't I do the same using MessageBag instance of Laravel?
During form validation, if error occurs, then the error gets showed up and if I refresh the page its get vanished. So, can't I bring the same behavior in my page using the method?
php validation laravel-5.2
asked Nov 20 '18 at 2:10
PHPCoderPHPCoder
386
I have the following function for a route named /home:
public function home(){
if(Session::has("user_id")){
return view("home");
}else{
return view("welcome", [
'error_message' => "Please log in to access that page!"
]);
}
}
Then, in my welcome view, I show the error like this:
<div class="alert alert-danger alert-dismissible fade show" role="alert">
<p> {{ $error_message }} </p>
</div>
Everything works as expected but the error keeps on showing when I refresh the page again and again. I know that the variable hasn't been unset so it is happening. But, the real question is:
Can't I do the same using MessageBag instance of Laravel?
During form validation, if error occurs, then the error gets showed up and if I refresh the page its get vanished. So, can't I bring the same behavior in my page using the method?
php validation laravel-5.2
php validation laravel-5.2
asked Nov 20 '18 at 2:10
PHPCoderPHPCoder
386
asked Nov 20 '18 at 2:10
PHPCoderPHPCoder
386
asked Nov 20 '18 at 2:10
PHPCoderPHPCoder
386
asked Nov 20 '18 at 2:10
PHPCoderPHPCoder
386
asked Nov 20 '18 at 2:10
PHPCoderPHPCoder
386
386
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Example 1
To set error use
return redirect()->back()->withErrors('my message');
To access errors in blade use
@if ($errors->any())
<div class="alert alert-danger">
<ul class="mb-0">
@foreach($errors->all() as $error)
<li>{!! $error !!}</li>
@endforeach
</ul>
</div>
@endif
And yes, use redirect instead of returning different views on the same route, because it is more clear.
Example 2
But if you want to learn it hard way, set alerts like so
session()->flash('alert', 'your message');
and access it like so
<div class="alert alert-success"> {{ session('alert') }}</div>
Example 3
if you want to use a MessageBag all you need is throw a special exception
throw ValidationException::withMessages([
'message' => ['my message here'],
])->status(400);
and access it as it is shown in example-1
answered Nov 20 '18 at 3:20
Yevgeniy AfanasyevYevgeniy Afanasyev
8,19244470
1
Thank you! That was what I needed!
– PHPCoder
Nov 23 '18 at 13:53
add a comment |
You can do something like this
public function home(){
if(Session::has("user_id")){
return view("home");
}else{
return view("welcome")->with('error_message', 'Please log in to access the page');
}
}
and
@if(!empty($error_message))
<div class="alert alert-success"> {{ $error_message }}</div>
@endif
answered Nov 20 '18 at 3:14
ClnCln
261
Thank you for your answer. Yes it is one unclear question, I also noticed the same problem as you are solving with your answer, but then I read further and it turns out that the member wants to use a MessageBag. :)
– Yevgeniy Afanasyev
Nov 20 '18 at 3:39
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%2f53385240%2faccess-the-errors-in-laravel%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Example 1
To set error use
return redirect()->back()->withErrors('my message');
To access errors in blade use
@if ($errors->any())
<div class="alert alert-danger">
<ul class="mb-0">
@foreach($errors->all() as $error)
<li>{!! $error !!}</li>
@endforeach
</ul>
</div>
@endif
And yes, use redirect instead of returning different views on the same route, because it is more clear.
Example 2
But if you want to learn it hard way, set alerts like so
session()->flash('alert', 'your message');
and access it like so
<div class="alert alert-success"> {{ session('alert') }}</div>
Example 3
if you want to use a MessageBag all you need is throw a special exception
throw ValidationException::withMessages([
'message' => ['my message here'],
])->status(400);
and access it as it is shown in example-1
answered Nov 20 '18 at 3:20
Yevgeniy AfanasyevYevgeniy Afanasyev
8,19244470
1
Thank you! That was what I needed!
– PHPCoder
Nov 23 '18 at 13:53
add a comment |
Example 1
To set error use
return redirect()->back()->withErrors('my message');
To access errors in blade use
@if ($errors->any())
<div class="alert alert-danger">
<ul class="mb-0">
@foreach($errors->all() as $error)
<li>{!! $error !!}</li>
@endforeach
</ul>
</div>
@endif
And yes, use redirect instead of returning different views on the same route, because it is more clear.
Example 2
But if you want to learn it hard way, set alerts like so
session()->flash('alert', 'your message');
and access it like so
<div class="alert alert-success"> {{ session('alert') }}</div>
Example 3
if you want to use a MessageBag all you need is throw a special exception
throw ValidationException::withMessages([
'message' => ['my message here'],
])->status(400);
and access it as it is shown in example-1
answered Nov 20 '18 at 3:20
Yevgeniy AfanasyevYevgeniy Afanasyev
8,19244470
1
Thank you! That was what I needed!
– PHPCoder
Nov 23 '18 at 13:53
add a comment |
Example 1
To set error use
return redirect()->back()->withErrors('my message');
To access errors in blade use
@if ($errors->any())
<div class="alert alert-danger">
<ul class="mb-0">
@foreach($errors->all() as $error)
<li>{!! $error !!}</li>
@endforeach
</ul>
</div>
@endif
And yes, use redirect instead of returning different views on the same route, because it is more clear.
Example 2
But if you want to learn it hard way, set alerts like so
session()->flash('alert', 'your message');
and access it like so
<div class="alert alert-success"> {{ session('alert') }}</div>
Example 3
if you want to use a MessageBag all you need is throw a special exception
throw ValidationException::withMessages([
'message' => ['my message here'],
])->status(400);
and access it as it is shown in example-1
answered Nov 20 '18 at 3:20
Yevgeniy AfanasyevYevgeniy Afanasyev
8,19244470
Example 1
To set error use
return redirect()->back()->withErrors('my message');
To access errors in blade use
@if ($errors->any())
<div class="alert alert-danger">
<ul class="mb-0">
@foreach($errors->all() as $error)
<li>{!! $error !!}</li>
@endforeach
</ul>
</div>
@endif
And yes, use redirect instead of returning different views on the same route, because it is more clear.
Example 2
But if you want to learn it hard way, set alerts like so
session()->flash('alert', 'your message');
and access it like so
<div class="alert alert-success"> {{ session('alert') }}</div>
Example 3
if you want to use a MessageBag all you need is throw a special exception
throw ValidationException::withMessages([
'message' => ['my message here'],
])->status(400);
and access it as it is shown in example-1
answered Nov 20 '18 at 3:20
Yevgeniy AfanasyevYevgeniy Afanasyev
8,19244470
edited Nov 20 '18 at 3:34
answered Nov 20 '18 at 3:20
Yevgeniy AfanasyevYevgeniy Afanasyev
8,19244470
answered Nov 20 '18 at 3:20
Yevgeniy AfanasyevYevgeniy Afanasyev
8,19244470
answered Nov 20 '18 at 3:20
Yevgeniy AfanasyevYevgeniy Afanasyev
8,19244470
8,19244470
1
Thank you! That was what I needed!
– PHPCoder
Nov 23 '18 at 13:53
add a comment |
1
Thank you! That was what I needed!
– PHPCoder
Nov 23 '18 at 13:53
1
1
Thank you! That was what I needed!
– PHPCoder
Nov 23 '18 at 13:53
Thank you! That was what I needed!
– PHPCoder
Nov 23 '18 at 13:53
add a comment |
You can do something like this
public function home(){
if(Session::has("user_id")){
return view("home");
}else{
return view("welcome")->with('error_message', 'Please log in to access the page');
}
}
and
@if(!empty($error_message))
<div class="alert alert-success"> {{ $error_message }}</div>
@endif
answered Nov 20 '18 at 3:14
ClnCln
261
Thank you for your answer. Yes it is one unclear question, I also noticed the same problem as you are solving with your answer, but then I read further and it turns out that the member wants to use a MessageBag. :)
– Yevgeniy Afanasyev
Nov 20 '18 at 3:39
add a comment |
You can do something like this
public function home(){
if(Session::has("user_id")){
return view("home");
}else{
return view("welcome")->with('error_message', 'Please log in to access the page');
}
}
and
@if(!empty($error_message))
<div class="alert alert-success"> {{ $error_message }}</div>
@endif
answered Nov 20 '18 at 3:14
ClnCln
261
Thank you for your answer. Yes it is one unclear question, I also noticed the same problem as you are solving with your answer, but then I read further and it turns out that the member wants to use a MessageBag. :)
– Yevgeniy Afanasyev
Nov 20 '18 at 3:39
add a comment |
You can do something like this
public function home(){
if(Session::has("user_id")){
return view("home");
}else{
return view("welcome")->with('error_message', 'Please log in to access the page');
}
}
and
@if(!empty($error_message))
<div class="alert alert-success"> {{ $error_message }}</div>
@endif
answered Nov 20 '18 at 3:14
ClnCln
261
You can do something like this
public function home(){
if(Session::has("user_id")){
return view("home");
}else{
return view("welcome")->with('error_message', 'Please log in to access the page');
}
}
and
@if(!empty($error_message))
<div class="alert alert-success"> {{ $error_message }}</div>
@endif
answered Nov 20 '18 at 3:14
ClnCln
261
answered Nov 20 '18 at 3:14
ClnCln
261
answered Nov 20 '18 at 3:14
ClnCln
261
answered Nov 20 '18 at 3:14
ClnCln
261
261
Thank you for your answer. Yes it is one unclear question, I also noticed the same problem as you are solving with your answer, but then I read further and it turns out that the member wants to use a MessageBag. :)
– Yevgeniy Afanasyev
Nov 20 '18 at 3:39
add a comment |
Thank you for your answer. Yes it is one unclear question, I also noticed the same problem as you are solving with your answer, but then I read further and it turns out that the member wants to use a MessageBag. :)
– Yevgeniy Afanasyev
Nov 20 '18 at 3:39
Thank you for your answer. Yes it is one unclear question, I also noticed the same problem as you are solving with your answer, but then I read further and it turns out that the member wants to use a MessageBag. :)
– Yevgeniy Afanasyev
Nov 20 '18 at 3:39
Thank you for your answer. Yes it is one unclear question, I also noticed the same problem as you are solving with your answer, but then I read further and it turns out that the member wants to use a MessageBag. :)
– Yevgeniy Afanasyev
Nov 20 '18 at 3:39
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%2f53385240%2faccess-the-errors-in-laravel%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
