Popular tricks

Laravel State Management is a powerful, Redux-inspired solution for managing complex application state across services, requests, and caching layers. This package allows you to define shared state, easily persist and rehydrate data, and implement custom methods for state manipulation. With features like attribute casting, default state handling, and global store access, it provides a robust system for managing state across your Laravel app.

If you know what nested sets are, and use lazychazer/laravel-nestedset package, and tried his example application (https://github.com/lazychaser/nestedset-app), then here is a snippet for replace his simple nav rendering to bootstrap (3.x) navbar compatible output. (Laravel 5 solution)

There are not any option to disable view cache in Laravel but in windows you can use following .bat file out of box and in other OS's you can do something similar...

using same form request for create and update

A Link assets based on which controller is currently requested. Any improvements to this code are welcome

Blade's path syntax is a little odd - it uses dots instead of slashes, and always requires you to start your paths from the views root. This Blade extension allows you to pass paths with slashes, and correctly resolves parent paths via the traditional ../ syntax. Lastly, the quoting of paths is optional.

Starting from 4.1.28, Application::boot() does not initialize sensitive session data anymore. That is, it is accessible, but encrypted. So if you're integrating 3rd party library, which needs external authentification check through sessions, simple checking Auth::check() will not work. However, we can still use old $_SESSION variable. Examples of 3rd party libraries: CkFinder, elFinder (has Laravel package though), MoxieManager. N.B. If you can use Ajax calls for authorization checks, you can still make a custom API with JSON request to user-logged (as an example) to see if user is authentificated.

Here's a simple little scope that you can use to get a random collection of Model objects from the database.

This is a laravel command i wrote to handle the upgrade to 4.1 It covers everything in the upgrade doc except for handling missing method. It should be easily addable if you need it. Make sure to add the following to start/artisan.php Artisan::add(new UpgradeCommand); Artisan::resolve('UpgradeCommand'); Once finished, run the following php artisan auth:reminders-controller