Laravel stopped working locally, all artisan commands and composer commands will not work
I have been working on a project for about a month. There have been no major issues. We are about to launch.
An error was reported that a route was not working as intended on staging. I tried to replicate it locally by putting the route into my browser ( but obviously with the local domain path ) and it didnt work. this is the order of events:
that route was causing a permanent redirect. Code looked fine but i noticed the intended get did not seem to be hitting so I put a dd('test'); after it and refreshed and saw the test. So it was bypassing its intended route::get, which was not happening before.
I tried figuring this out, clearing cache and the normal things that could cause this. I then killed the server ( locally ) shut down terminal and restarted it, now everytime I try to run anything it responds with http://localhost
CO!!@#!@#!@#:directoryproject username$ php artisan cache:clear
"http://localhost"
CO!!@#!@#!@#:directoryproject username$ php artisan config:clear
"http://localhost"
CO!!@#!@#!@#:directoryproject username$ php artisan serve
"http://localhost"
CO!!@#!@#!@#:directoryproject username$
i cannot get anything to work. I tried checking out a different branch, nothing. Composer update, install nothing. I keep getting:
Script @php artisan package:discover handling the post-autoload-dump event returned with error code 1
Any help would be greatly appreciated at this point.
laravel laravel-5.6
asked Nov 13 '18 at 0:25
ScottScott
3802518
add a comment |
I have been working on a project for about a month. There have been no major issues. We are about to launch.
An error was reported that a route was not working as intended on staging. I tried to replicate it locally by putting the route into my browser ( but obviously with the local domain path ) and it didnt work. this is the order of events:
that route was causing a permanent redirect. Code looked fine but i noticed the intended get did not seem to be hitting so I put a dd('test'); after it and refreshed and saw the test. So it was bypassing its intended route::get, which was not happening before.
I tried figuring this out, clearing cache and the normal things that could cause this. I then killed the server ( locally ) shut down terminal and restarted it, now everytime I try to run anything it responds with http://localhost
CO!!@#!@#!@#:directoryproject username$ php artisan cache:clear
"http://localhost"
CO!!@#!@#!@#:directoryproject username$ php artisan config:clear
"http://localhost"
CO!!@#!@#!@#:directoryproject username$ php artisan serve
"http://localhost"
CO!!@#!@#!@#:directoryproject username$
i cannot get anything to work. I tried checking out a different branch, nothing. Composer update, install nothing. I keep getting:
Script @php artisan package:discover handling the post-autoload-dump event returned with error code 1
Any help would be greatly appreciated at this point.
laravel laravel-5.6
asked Nov 13 '18 at 0:25
ScottScott
3802518
Spot on, make this something I can mark as correct and I will do so. Thanks so much.
– Scott
Nov 13 '18 at 1:30
Posted it as an answer, cheers!
– DigitalDrifter
Nov 13 '18 at 1:39
If I had a nickel for every time I've left some debug-lines in my code... I recommend overriding Laravel'sdd()function with one that leverages Php'sdebug_backtrace(), and sends to your error-log the file and line number that the call was made on. It'll head off a lot of headaches.
– Claymore
Nov 13 '18 at 2:36
add a comment |
I have been working on a project for about a month. There have been no major issues. We are about to launch.
An error was reported that a route was not working as intended on staging. I tried to replicate it locally by putting the route into my browser ( but obviously with the local domain path ) and it didnt work. this is the order of events:
that route was causing a permanent redirect. Code looked fine but i noticed the intended get did not seem to be hitting so I put a dd('test'); after it and refreshed and saw the test. So it was bypassing its intended route::get, which was not happening before.
I tried figuring this out, clearing cache and the normal things that could cause this. I then killed the server ( locally ) shut down terminal and restarted it, now everytime I try to run anything it responds with http://localhost
CO!!@#!@#!@#:directoryproject username$ php artisan cache:clear
"http://localhost"
CO!!@#!@#!@#:directoryproject username$ php artisan config:clear
"http://localhost"
CO!!@#!@#!@#:directoryproject username$ php artisan serve
"http://localhost"
CO!!@#!@#!@#:directoryproject username$
i cannot get anything to work. I tried checking out a different branch, nothing. Composer update, install nothing. I keep getting:
Script @php artisan package:discover handling the post-autoload-dump event returned with error code 1
Any help would be greatly appreciated at this point.
laravel laravel-5.6
asked Nov 13 '18 at 0:25
ScottScott
3802518
I have been working on a project for about a month. There have been no major issues. We are about to launch.
An error was reported that a route was not working as intended on staging. I tried to replicate it locally by putting the route into my browser ( but obviously with the local domain path ) and it didnt work. this is the order of events:
that route was causing a permanent redirect. Code looked fine but i noticed the intended get did not seem to be hitting so I put a dd('test'); after it and refreshed and saw the test. So it was bypassing its intended route::get, which was not happening before.
I tried figuring this out, clearing cache and the normal things that could cause this. I then killed the server ( locally ) shut down terminal and restarted it, now everytime I try to run anything it responds with http://localhost
CO!!@#!@#!@#:directoryproject username$ php artisan cache:clear
"http://localhost"
CO!!@#!@#!@#:directoryproject username$ php artisan config:clear
"http://localhost"
CO!!@#!@#!@#:directoryproject username$ php artisan serve
"http://localhost"
CO!!@#!@#!@#:directoryproject username$
i cannot get anything to work. I tried checking out a different branch, nothing. Composer update, install nothing. I keep getting:
Script @php artisan package:discover handling the post-autoload-dump event returned with error code 1
Any help would be greatly appreciated at this point.
laravel laravel-5.6
laravel laravel-5.6
asked Nov 13 '18 at 0:25
ScottScott
3802518
asked Nov 13 '18 at 0:25
ScottScott
3802518
asked Nov 13 '18 at 0:25
ScottScott
3802518
asked Nov 13 '18 at 0:25
ScottScott
3802518
asked Nov 13 '18 at 0:25
ScottScott
3802518
3802518
Spot on, make this something I can mark as correct and I will do so. Thanks so much.
– Scott
Nov 13 '18 at 1:30
Posted it as an answer, cheers!
– DigitalDrifter
Nov 13 '18 at 1:39
If I had a nickel for every time I've left some debug-lines in my code... I recommend overriding Laravel'sdd()function with one that leverages Php'sdebug_backtrace(), and sends to your error-log the file and line number that the call was made on. It'll head off a lot of headaches.
– Claymore
Nov 13 '18 at 2:36
add a comment |
Spot on, make this something I can mark as correct and I will do so. Thanks so much.
– Scott
Nov 13 '18 at 1:30
Posted it as an answer, cheers!
– DigitalDrifter
Nov 13 '18 at 1:39
If I had a nickel for every time I've left some debug-lines in my code... I recommend overriding Laravel'sdd()function with one that leverages Php'sdebug_backtrace(), and sends to your error-log the file and line number that the call was made on. It'll head off a lot of headaches.
– Claymore
Nov 13 '18 at 2:36
Spot on, make this something I can mark as correct and I will do so. Thanks so much.
– Scott
Nov 13 '18 at 1:30
Spot on, make this something I can mark as correct and I will do so. Thanks so much.
– Scott
Nov 13 '18 at 1:30
Posted it as an answer, cheers!
– DigitalDrifter
Nov 13 '18 at 1:39
Posted it as an answer, cheers!
– DigitalDrifter
Nov 13 '18 at 1:39
If I had a nickel for every time I've left some debug-lines in my code... I recommend overriding Laravel's
dd() function with one that leverages Php's debug_backtrace(), and sends to your error-log the file and line number that the call was made on. It'll head off a lot of headaches.– Claymore
Nov 13 '18 at 2:36
If I had a nickel for every time I've left some debug-lines in my code... I recommend overriding Laravel's
dd() function with one that leverages Php's debug_backtrace(), and sends to your error-log the file and line number that the call was made on. It'll head off a lot of headaches.– Claymore
Nov 13 '18 at 2:36
add a comment |
1 Answer
1
active
oldest
votes
You've likely got a dd statement somewhere like dd(request()->getHost()); or similar. Do a recursive search starting in the app's root directory for the pattern dd(. If that doesn't yield anything, start at the very top pulic/index.php and put in dd(__DIR__); statements and attempting to access the app. Then move onto the service providers, http kernel, etc. until you can locate the culprit code.
answered Nov 13 '18 at 1:32
DigitalDrifterDigitalDrifter
7,7772423
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%2f53272043%2flaravel-stopped-working-locally-all-artisan-commands-and-composer-commands-will%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
You've likely got a dd statement somewhere like dd(request()->getHost()); or similar. Do a recursive search starting in the app's root directory for the pattern dd(. If that doesn't yield anything, start at the very top pulic/index.php and put in dd(__DIR__); statements and attempting to access the app. Then move onto the service providers, http kernel, etc. until you can locate the culprit code.
answered Nov 13 '18 at 1:32
DigitalDrifterDigitalDrifter
7,7772423
add a comment |
You've likely got a dd statement somewhere like dd(request()->getHost()); or similar. Do a recursive search starting in the app's root directory for the pattern dd(. If that doesn't yield anything, start at the very top pulic/index.php and put in dd(__DIR__); statements and attempting to access the app. Then move onto the service providers, http kernel, etc. until you can locate the culprit code.
answered Nov 13 '18 at 1:32
DigitalDrifterDigitalDrifter
7,7772423
add a comment |
You've likely got a dd statement somewhere like dd(request()->getHost()); or similar. Do a recursive search starting in the app's root directory for the pattern dd(. If that doesn't yield anything, start at the very top pulic/index.php and put in dd(__DIR__); statements and attempting to access the app. Then move onto the service providers, http kernel, etc. until you can locate the culprit code.
answered Nov 13 '18 at 1:32
DigitalDrifterDigitalDrifter
7,7772423
You've likely got a dd statement somewhere like dd(request()->getHost()); or similar. Do a recursive search starting in the app's root directory for the pattern dd(. If that doesn't yield anything, start at the very top pulic/index.php and put in dd(__DIR__); statements and attempting to access the app. Then move onto the service providers, http kernel, etc. until you can locate the culprit code.
answered Nov 13 '18 at 1:32
DigitalDrifterDigitalDrifter
7,7772423
answered Nov 13 '18 at 1:32
DigitalDrifterDigitalDrifter
7,7772423
answered Nov 13 '18 at 1:32
DigitalDrifterDigitalDrifter
7,7772423
answered Nov 13 '18 at 1:32
DigitalDrifterDigitalDrifter
7,7772423
7,7772423
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.
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%2f53272043%2flaravel-stopped-working-locally-all-artisan-commands-and-composer-commands-will%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
Spot on, make this something I can mark as correct and I will do so. Thanks so much.
– Scott
Nov 13 '18 at 1:30
Posted it as an answer, cheers!
– DigitalDrifter
Nov 13 '18 at 1:39
If I had a nickel for every time I've left some debug-lines in my code... I recommend overriding Laravel's
dd()function with one that leverages Php'sdebug_backtrace(), and sends to your error-log the file and line number that the call was made on. It'll head off a lot of headaches.– Claymore
Nov 13 '18 at 2:36