[Release][WIP] Base 0.9 Upgrade

[tabacitu]

This PR is here to document all major changes between 0.8.x and 0.9.x. It will help us easily detect breaking changes, document them, and create the upgrade guide.

PRs

• [Feature][0.9][Merged] Custom admin middleware #258 Custom admin middleware
• [Feature][0.9][Merged] Allow login with username #257 Allow login with username
• [Feature][0.9][Merged] Alert messages can now have HTML content #251 Alert messages can have HTML content when triggered from PHP
• [Feature][0.9][Merged] publish minimum amount of files; added sidebar_content file #252 Publish minimum amount of files upon installation, add sidebar_content file
• [Feature][0.9][Merged] Custom routes file + command to add to it #254 Custom routes file + command to add content to it
• [Feature][0.9][Merged] Custom auth guard #165 Custom auth guard
• [Feature][0.9][Merged] stacks for CSS and JS after sections #260 stacks for CSS and JS after @section

Upgrade guide

• Replace admin middleware with backpack_middleware() helper. By default, Backpack used a middleware called admin to allow/deny access to admin pages. This middleware name can now be customized in config/backpack/base.php. To future-proof your applications, it's recommended that you change this middleware name everywhere you've used it, to the new backpack_middleware() helper that automatically pulls the name (check your routes and controllers).
• The admin middleware's class has been renamed to CheckIfAdmin; if you were extending Backpack\Base\app\Http\Middleware\Admin anywhere, make sure to extend the new class name: Backpack\Base\app\Http\Middleware\CheckIfAdmin;
• All admin classes and views should now use the backpack_auth() helper instead of Laravel's default Auth facade, so that if any custom guards are specified in config/backpack/base.php, they're taken into account; So if you've used something like Auth::user() anywhere in an admin panel controller/model/view/request, please replace with backpack_auth->user(); we've replaced this ourselves in the following files: sidemenu.blade.php, menu.blade.php, sidebar.blade.php, sidebar_user_panel.blade.php; make sure you apply the changes if you've overwritten them; if you've never ever modified those files, but they're in your resources/views/vendor/backpack/base folder, just delete them from there, and Backpack will pick up the fresh files from the package folder instead; you can also use the backpack_guard() helper if you need the guard name anywhere;
• We no longer use sidebar.blade.php to hold all our sidebar items. We've moved that to a file called sidebar_content.blade.php, so that you can also automatically generate sidebar items; Please create a new file called sidebar_content.blade.php and copy all your sidebar items there, then either delete your sidebar.blade.php file or replace the old sidebar items with @include('backpack::inc.sidebar_content'); take a look here for an example in code;
• By default, Backpack\Base no longer pushes all views in your views folder. Only the absolute necessary (sidebar_content.blade.php). If you have views in resources\views\vendor\backpack\base that you have never modified, please remove them (especially layout.blade.php); This will make sure you benefit from any updates we push, further down the line; Backpack will pick up the new files from the package folder, automatically;
• In order to be able to trigger notification bubbles that include HTML, you need to make a small change to your alerts view. But since you most likely haven't ever modified it, the easiest way to do this would be to just delete the resources/views/vendor/backpack/inc/alerts.blade.php file; Backpack will automatically pick up the original file from the package afterwards;
• Starting with Backpack\Base 0.9.0, we have a new place for you to store your admin routes: routes/backpack/custom.php. That's where CRUD::resource() routes are generated automatically, when you generate a new CRUD. To future-proof your application, you can publish that file using php artisan vendor:publish --provider="Backpack\Base\BaseServiceProvider" --tag=custom_routes, then manually move your existing admin routes there (from your routes/web.php.

[lloy0076]

Shouldn't that be in a config?

[tabacitu]

Right. Totally! Done, thank you!

[tabacitu]

BOOM!

It's done :-) tested, merged, tagged and launched. See:

• changelog
• upgrade guide

Thank you so much for all the help, guys! This has been a HUGE effort.

[shirshak55]

nice :____