laravel

问题 Weird problem I'm having with Laravel 5.5 I can update and even delete a controller and yet it appears as if a cached / old version is still being called. I've tried clearing cache, clearing route cache, clearing config cache - doesn't seem to have any effect. On my local test environment if I delete the controller file then try to access it I immediately get a not found error. On my production server I do not. Anyone have any ideas or advice? 回答1: You can try running: php artisan clear

问题 i used laravel 5.3 for my project, i used laravel form collective into it code is below {{ Form::select('size', ['surat' => 'surat', 'mumbai' => 'mumbai','hongkong' => 'hongkong'], 'hongkong',['multiple'=>'true'], array('class'=> 'form-control') ) }} but the array('class'=> 'form-control') is not working for me if i removed ['multiple'=>'true'] then it work properly so how can i apply bootstrap class to my select box. 回答1: The correct syntax: {!! Form::select('size', $citiesArray, 'hongkong',

问题 i used laravel 5.3 for my project, i used laravel form collective into it code is below {{ Form::select('size', ['surat' => 'surat', 'mumbai' => 'mumbai','hongkong' => 'hongkong'], 'hongkong',['multiple'=>'true'], array('class'=> 'form-control') ) }} but the array('class'=> 'form-control') is not working for me if i removed ['multiple'=>'true'] then it work properly so how can i apply bootstrap class to my select box. 回答1: The correct syntax: {!! Form::select('size', $citiesArray, 'hongkong',

问题 In order to reuse code, I created my own validator rule in a file named ValidatorServiceProvider : class ValidatorServiceProvider extends ServiceProvider { public function boot() { Validator::extend('checkEmailPresenceAndValidity', function ($attribute, $value, $parameters, $validator) { $user = User::where('email', $value)->first(); // Email has not been found if (! $user) { return false; } // Email has not been validated if (! $user->valid_email) { return false; } return true; }); } public

问题 I have to user models in my eloquent: User OfficeUser OfficeUser is in defined in the JWT config as standard model. Now I have written a Middleware for authenticate each of them authUser: public function handle($request, Closure $next) { Config::set('auth.providers.users.model', \App\User::class); try { if (! $user = JWTAuth::parseToken()->authenticate()) { return response()->json(['user_not_found'], 404); } } catch (Tymon\JWTAuth\Exceptions\TokenExpiredException $e) { return response()->json

问题 I have to user models in my eloquent: User OfficeUser OfficeUser is in defined in the JWT config as standard model. Now I have written a Middleware for authenticate each of them authUser: public function handle($request, Closure $next) { Config::set('auth.providers.users.model', \App\User::class); try { if (! $user = JWTAuth::parseToken()->authenticate()) { return response()->json(['user_not_found'], 404); } } catch (Tymon\JWTAuth\Exceptions\TokenExpiredException $e) { return response()->json

问题 I have to user models in my eloquent: User OfficeUser OfficeUser is in defined in the JWT config as standard model. Now I have written a Middleware for authenticate each of them authUser: public function handle($request, Closure $next) { Config::set('auth.providers.users.model', \App\User::class); try { if (! $user = JWTAuth::parseToken()->authenticate()) { return response()->json(['user_not_found'], 404); } } catch (Tymon\JWTAuth\Exceptions\TokenExpiredException $e) { return response()->json

问题 I have to user models in my eloquent: User OfficeUser OfficeUser is in defined in the JWT config as standard model. Now I have written a Middleware for authenticate each of them authUser: public function handle($request, Closure $next) { Config::set('auth.providers.users.model', \App\User::class); try { if (! $user = JWTAuth::parseToken()->authenticate()) { return response()->json(['user_not_found'], 404); } } catch (Tymon\JWTAuth\Exceptions\TokenExpiredException $e) { return response()->json

问题 Given the webpack.mix.js of a fresh Laravel project : const mix = require('laravel-mix'); /* |-------------------------------------------------------------------------- | Mix Asset Management |-------------------------------------------------------------------------- | | Mix provides a clean, fluent API for defining some Webpack build steps | for your Laravel application. By default, we are compiling the Sass | file for the application as well as bundling up all the JS files. | */ mix.js(

问题 Given the webpack.mix.js of a fresh Laravel project : const mix = require('laravel-mix'); /* |-------------------------------------------------------------------------- | Mix Asset Management |-------------------------------------------------------------------------- | | Mix provides a clean, fluent API for defining some Webpack build steps | for your Laravel application. By default, we are compiling the Sass | file for the application as well as bundling up all the JS files. | */ mix.js(