Why laravel queries appear on browser
up vote
1
down vote
favorite
yesterday I made some test on my localhost on a website with Laravel. And I saw some queries that I executed on my text editor (Sublime Text) appear on browser. I never seen like that before. I took with capture tool image
Sorry if I made some mistake on my post, I'm a biginner learning english and programmation. Someone could help me please to understand that!
laravel
asked Nov 19 at 8:40
user10659018
113
add a comment |
up vote
1
down vote
favorite
yesterday I made some test on my localhost on a website with Laravel. And I saw some queries that I executed on my text editor (Sublime Text) appear on browser. I never seen like that before. I took with capture tool image
Sorry if I made some mistake on my post, I'm a biginner learning english and programmation. Someone could help me please to understand that!
laravel
asked Nov 19 at 8:40
user10659018
113
1
add your code which you wrote to the post for better help please
– Iman
Nov 19 at 8:43
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
yesterday I made some test on my localhost on a website with Laravel. And I saw some queries that I executed on my text editor (Sublime Text) appear on browser. I never seen like that before. I took with capture tool image
Sorry if I made some mistake on my post, I'm a biginner learning english and programmation. Someone could help me please to understand that!
laravel
asked Nov 19 at 8:40
user10659018
113
yesterday I made some test on my localhost on a website with Laravel. And I saw some queries that I executed on my text editor (Sublime Text) appear on browser. I never seen like that before. I took with capture tool image
Sorry if I made some mistake on my post, I'm a biginner learning english and programmation. Someone could help me please to understand that!
laravel
laravel
asked Nov 19 at 8:40
user10659018
113
asked Nov 19 at 8:40
user10659018
113
asked Nov 19 at 8:40
user10659018
113
asked Nov 19 at 8:40
user10659018
113
asked Nov 19 at 8:40
user10659018
113
113
1
add your code which you wrote to the post for better help please
– Iman
Nov 19 at 8:43
add a comment |
1
add your code which you wrote to the post for better help please
– Iman
Nov 19 at 8:43
1
1
add your code which you wrote to the post for better help please
– Iman
Nov 19 at 8:43
add your code which you wrote to the post for better help please
– Iman
Nov 19 at 8:43
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
The query is shown because it is an error, and it is used for debugging purposes, on your local machine, so in your .env file you have this
APP_DEBUG=true
Change that to
APP_DEBUG=false
and you won't see the query, but then it will be hard for you to develop, so it is good to have this flag as true on your local machine, once you push the code to production you would want that flag to be false and read the storage/logs files instead in case an error occurs.
answered Nov 19 at 8:55
nakov
1,663188
After do changes in the .env file please run " php artisan config:clear ".
– Harish Patel
Nov 19 at 10:52
Yes, I had my .env file exactly like that with APP_DEBUG=true for showing errors which will occur througout my test on localhost. Thank's, I fixed settings and it's work.
– user10659018
Nov 19 at 15:47
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
The query is shown because it is an error, and it is used for debugging purposes, on your local machine, so in your .env file you have this
APP_DEBUG=true
Change that to
APP_DEBUG=false
and you won't see the query, but then it will be hard for you to develop, so it is good to have this flag as true on your local machine, once you push the code to production you would want that flag to be false and read the storage/logs files instead in case an error occurs.
answered Nov 19 at 8:55
nakov
1,663188
After do changes in the .env file please run " php artisan config:clear ".
– Harish Patel
Nov 19 at 10:52
Yes, I had my .env file exactly like that with APP_DEBUG=true for showing errors which will occur througout my test on localhost. Thank's, I fixed settings and it's work.
– user10659018
Nov 19 at 15:47
add a comment |
up vote
1
down vote
accepted
The query is shown because it is an error, and it is used for debugging purposes, on your local machine, so in your .env file you have this
APP_DEBUG=true
Change that to
APP_DEBUG=false
and you won't see the query, but then it will be hard for you to develop, so it is good to have this flag as true on your local machine, once you push the code to production you would want that flag to be false and read the storage/logs files instead in case an error occurs.
answered Nov 19 at 8:55
nakov
1,663188
After do changes in the .env file please run " php artisan config:clear ".
– Harish Patel
Nov 19 at 10:52
Yes, I had my .env file exactly like that with APP_DEBUG=true for showing errors which will occur througout my test on localhost. Thank's, I fixed settings and it's work.
– user10659018
Nov 19 at 15:47
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
The query is shown because it is an error, and it is used for debugging purposes, on your local machine, so in your .env file you have this
APP_DEBUG=true
Change that to
APP_DEBUG=false
and you won't see the query, but then it will be hard for you to develop, so it is good to have this flag as true on your local machine, once you push the code to production you would want that flag to be false and read the storage/logs files instead in case an error occurs.
answered Nov 19 at 8:55
nakov
1,663188
The query is shown because it is an error, and it is used for debugging purposes, on your local machine, so in your .env file you have this
APP_DEBUG=true
Change that to
APP_DEBUG=false
and you won't see the query, but then it will be hard for you to develop, so it is good to have this flag as true on your local machine, once you push the code to production you would want that flag to be false and read the storage/logs files instead in case an error occurs.
answered Nov 19 at 8:55
nakov
1,663188
answered Nov 19 at 8:55
nakov
1,663188
answered Nov 19 at 8:55
nakov
1,663188
answered Nov 19 at 8:55
nakov
1,663188
1,663188
After do changes in the .env file please run " php artisan config:clear ".
– Harish Patel
Nov 19 at 10:52
Yes, I had my .env file exactly like that with APP_DEBUG=true for showing errors which will occur througout my test on localhost. Thank's, I fixed settings and it's work.
– user10659018
Nov 19 at 15:47
add a comment |
After do changes in the .env file please run " php artisan config:clear ".
– Harish Patel
Nov 19 at 10:52
Yes, I had my .env file exactly like that with APP_DEBUG=true for showing errors which will occur througout my test on localhost. Thank's, I fixed settings and it's work.
– user10659018
Nov 19 at 15:47
After do changes in the .env file please run " php artisan config:clear ".
– Harish Patel
Nov 19 at 10:52
After do changes in the .env file please run " php artisan config:clear ".
– Harish Patel
Nov 19 at 10:52
Yes, I had my .env file exactly like that with APP_DEBUG=true for showing errors which will occur througout my test on localhost. Thank's, I fixed settings and it's work.
– user10659018
Nov 19 at 15:47
Yes, I had my .env file exactly like that with APP_DEBUG=true for showing errors which will occur througout my test on localhost. Thank's, I fixed settings and it's work.
– user10659018
Nov 19 at 15:47
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53370974%2fwhy-laravel-queries-appear-on-browser%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
1
add your code which you wrote to the post for better help please
– Iman
Nov 19 at 8:43