search

sleeping-owl / admin

Administrative interface builder for Laravel
http://sleeping-owl.github.io/
MIT License
503 stars 260 forks source link

Error on Laravel 5 : php artisan serve #349

Open patriciorasquetti opened 8 years ago

patriciorasquetti commented 8 years ago

Hi everyone, I'm Patricio from Argentina. I'm new in Laravel 5, and I'm having an error when I try to excecute php artisan serve. The problem appeared after trying to unsuccessfully install compose require intervention/image, with the following error : Using version ^2.3 for intervention/image ./composer.json has been updated Loading composer repositories with package information Updating dependencies (including require-dev) Nothing to install or update Generating autoload files

Illuminate\Foundation\ComposerScripts::postUpdate php artisan optimize [ErrorException]

The use statement with non-compound name 'Image' has no effect

Script php artisan optimize handling the post-update-cmd event returned with an error

Installation failed, reverting ./composer.json to its original content.

[RuntimeException]

Error Output:

Now when I try to run php artisan serve, I get this error: (Please can anyone help me?) [Symfony\Component\Debug\Exception\FatalThrowableError]

Parse error: syntax error, unexpected ';', expecting identifier (T_STRING) or function (T_FUNCTION) or const (T_CONST) or \ (T_NS_SEPARATOR)

The problem is that the error does not describe where that typo is. Does that wrong installation have something to do with the artisan error, or you can tell for sure that is it just a typo somewhere coused by me according to that error? Thanks in advance.-

patriciorasquetti commented 8 years ago

Problem solved, regards.-

mmguide2003 commented 7 years ago

Be helpful to state how you solved this. Because I have a php artisan error that is non-specific, so other than searching through a vast amount of files, how do you find it?

patriciorasquetti commented 7 years ago

Hi, it was long time ago now. But I remember it was a sintax error in one of my controllers. Regards.-

mmguide2003 commented 7 years ago

Thanks. Easy way to find the error is in the laravel.log, which i only just realised.

EvgenyVetrov commented 7 years ago

this version not supported!

new version here: https://github.com/LaravelRUS/SleepingOwlAdmin