Laravel version 5.6.10 and later has support for a permission element in the configuration (config/logging.php) for the single and the daily driver: ‘daily’ => [ ‘driver’ => ‘daily’, ‘path’ => storage_path(‘logs/laravel.log’), ‘level’ => ‘debug’, ‘days’ => 7, ‘permission’ => 0664, ], No need to juggle with Monolog in the bootstrap script. Specifically, support was added … Read more
I think you should use this code in Laravel version 5+. Also this will work not only with parameter page but also with any other parameter(s): $users->appends(request()->input())->links(); Personally, I try to avoid using Facades as much as I can. Using global helper functions is less code and much elegant. UPDATE: Do not use Input Facade … Read more
One solution would be to flash two variables into the session: The message itself The “class” of your alert for example: Session::flash(‘message’, ‘This is a message!’); Session::flash(‘alert-class’, ‘alert-danger’); Then in your view: @if(Session::has(‘message’)) <p class=”alert {{ Session::get(‘alert-class’, ‘alert-info’) }}”>{{ Session::get(‘message’) }}</p> @endif Note I’ve put a default value into the Session::get(). that way you only … Read more
The ugly, lazy and awful way: At the end of bootstrap/start.php , add an include(‘tools.php’) and place your function in that new file. The clean way: Create a library. That way it’ll be autoloaded ONLY when you actually use it. Create a libraries folder inside your app folder Create your library file, create a class … Read more
I think all patterns / architectures that you present are very useful as long as you follow the SOLID principles. For the where to add logic I think that it’s important to refer to the Single Responsibility Principle. Also, my answer considers that you are working on a medium / large project. If it’s a … Read more
RESTful Resource controller A RESTful resource controller sets up some default routes for you and even names them. Route::resource(‘users’, ‘UsersController’); Gives you these named routes: Verb Path Action Route Name GET /users index users.index GET /users/create create users.create POST /users store users.store GET /users/{user} show users.show GET /users/{user}/edit edit users.edit PUT|PATCH /users/{user} update users.update DELETE … Read more
This is working for me: $user_info = DB::table(‘usermetas’) ->select(‘browser’, DB::raw(‘count(*) as total’)) ->groupBy(‘browser’) ->get();
The “Killed” message usually means your process consumed too much memory, so you may simply need to add more memory to your system if possible. At the time of writing this answer, I’ve had to increase my virtual machine’s memory to at least 768MB in order to get composer update to work in some situations. … Read more
It is possible to extend the relation with query functions: <?php public function comments() { return $this->hasMany(‘Comment’)->orderBy(‘column’); } [edit after comment] <?php class User { public function comments() { return $this->hasMany(‘Comment’); } } class Controller { public function index() { $column = Input::get(‘orderBy’, ‘defaultColumn’); $comments = User::find(1)->comments()->orderBy($column)->get(); // use $comments in the template } } … Read more
Suggestion from vsmoraes worked for me: Laravel >= 5.4 php artisan cache:clear chmod -R 775 storage/ composer dump-autoload Laravel < 5.4 php artisan cache:clear chmod -R 775 app/storage composer dump-autoload