Since I did my last Composer update, I always get an 503(Service Unavailable) when I do a dd(), die or exit. Are there any known issues? Google couldn't bring the answer.
I'm using Laravel 5.1,
my last Composer package was barryvdh/laravel-dompdf.
Thank you for your help.
Related
I am new to Lumen so I just downloaded and installed a fresh lumen setup but unfortunately as soon as I hit postman it sends me above error. I have read many posts all says to use isset() i did so but still error persists therefore i request to help me.
Composer update also does not work.
Thanks!
It seems to be an issue between your version of PHP and Lumen 5.*
I found something here https://github.com/DarkaOnLine/SwaggerLume/issues/82
This worked for me
// in bootstrap/app.php
$app->configure('view');
I've recently started studying laravel and found out that I'm unable to create new laravel project in vagrant, using laravel new command:
451 Unavailable For Legal Reasons
It turns out that here, in Russia, cabinet.laravel.com is in the list of forbidden sites and response is actually correct.
If anyone faced the same problem and found out how to solve it, I'd be happy to see the decisions.
Here's what I tried:
Turn on the Tor32 service (I'm on Windows 10). Unfortunately I kept getting permission errors.
Use Proxy. I was able to open url using browser (which wasn't really a problem), but terminal kept throwing the same error.
Don't use the laravel new command. Instead you can use composer create-project laravel/laravel <project-name>. You would then replace <project-name> with the name of your project. For example:
composer create-project laravel/laravel myapp
New installation of Laravel - tried to reinstall and run composer update - same issue.
Laravel api project is returning randomly "Method Illuminate\Support\Carbon::getTimestamp does not exist." after ajax call from axios in separate vue.js client side project. This does not happen for every request. I will greatly appreciate any help.
I am experiencing the same problem, and simple "composer update" after some time should fix this, as Carbon breaks Laravel compatibility.
i have installed the chat package:
https://github.com/dazzz1er/confer
Unfortunately i get an error when i try to publish it. Here is the error:
[Symfony\Component\Debug\Exception\FatalErrorException]
Call to undefined method Illuminate\Support\Facades\View::composer()
Thanks !
As correctly pointed out by #curious_coder confer is not compatible with Laravel 5.2 yet. Please keep an on the open Laravel 5.2 issue on Github and/or ask the author of this package for updates.
I have a Laravel application that refuses to acknowledge controller changes even if the controller doesn't exist anymore!
Using MAMP PRO 5.5.3 and Laravel 4.1
with
/Applications/MAMP/bin/php/php5.5.3/bin/php
I have followed these instructions
Stop caching for PHP 5.5.3 in MAMP
I have deleted the view storage in Laravel.
There was mention of adding - opcache_reset(); in my bootstrap/autoload.php
http://laravel.io/forum/02-06-2014-laravel-and-view-caching-in-development-cant-see-changes-right-away
But not sure how and where you do you do that, I tried but just got an error
Call to undefined function opcache_reset()
The caching still continues!
Despite the controller having been deleted 2 hours ago (to prove controller not being called), it is still showing the page with an imaginary controller.
It's driving me insane.
Any help really appreciated.
Further to this the route file is refusing to accept UserController
Route::get('register', 'UserController#getRegister');
Giving this error
.....controllers/UserControllerb.php): failed to open stream: No such file or directory
UserControllerb.php doesn't exist and was not asked for ?! but the route is wrongly looking for it
When I try this
Route::get('register', 'UserControllerb#getRegister');
Rightly give this error
Class UserControllerb does not exist
So the route has been cached (a previous back-up removed days ago)
I have tried to use composer which decides it doesn't want to work and no-one seems to know the solution for either problem.
Laravel composer signal "11" error symfony osx
Huge kudos to anyone who can solve this.