Why laravel queries appear on browser












1















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!










share|improve this question


















  • 1





    add your code which you wrote to the post for better help please

    – Iman
    Nov 19 '18 at 8:43
















1















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!










share|improve this question


















  • 1





    add your code which you wrote to the post for better help please

    – Iman
    Nov 19 '18 at 8:43














1












1








1








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!










share|improve this question














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






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 19 '18 at 8:40









user10659018user10659018

113




113








  • 1





    add your code which you wrote to the post for better help please

    – Iman
    Nov 19 '18 at 8:43














  • 1





    add your code which you wrote to the post for better help please

    – Iman
    Nov 19 '18 at 8:43








1




1





add your code which you wrote to the post for better help please

– Iman
Nov 19 '18 at 8:43





add your code which you wrote to the post for better help please

– Iman
Nov 19 '18 at 8:43












1 Answer
1






active

oldest

votes


















1














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.






share|improve this answer
























  • After do changes in the .env file please run " php artisan config:clear ".

    – Harish Patel
    Nov 19 '18 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 '18 at 15:47











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
});


}
});














draft saved

draft discarded


















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

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














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.






share|improve this answer
























  • After do changes in the .env file please run " php artisan config:clear ".

    – Harish Patel
    Nov 19 '18 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 '18 at 15:47
















1














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.






share|improve this answer
























  • After do changes in the .env file please run " php artisan config:clear ".

    – Harish Patel
    Nov 19 '18 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 '18 at 15:47














1












1








1







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.






share|improve this answer













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.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 19 '18 at 8:55









nakovnakov

2,589189




2,589189













  • After do changes in the .env file please run " php artisan config:clear ".

    – Harish Patel
    Nov 19 '18 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 '18 at 15:47



















  • After do changes in the .env file please run " php artisan config:clear ".

    – Harish Patel
    Nov 19 '18 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 '18 at 15:47

















After do changes in the .env file please run " php artisan config:clear ".

– Harish Patel
Nov 19 '18 at 10:52







After do changes in the .env file please run " php artisan config:clear ".

– Harish Patel
Nov 19 '18 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 '18 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 '18 at 15:47




















draft saved

draft discarded




















































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.




draft saved


draft discarded














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





















































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







這個網誌中的熱門文章

Xamarin.form Move up view when keyboard appear

Post-Redirect-Get with Spring WebFlux and Thymeleaf

Anylogic : not able to use stopDelay()