backpack/menucrud

An admin panel for menu items, using Backpack\CRUD on Laravel 5.

Backpack\MenuCRUD

![Software License][ico-license] ![Coverage Status][ico-scrutinizer] ![Total Downloads][ico-downloads], _(*1)

An admin panel for menu items on Laravel 5 or Laravel 6, using Backpack\CRUD. Add, edit, reorder, nest, rename menu items and link them to Backpack\PageManager pages, external link or custom internal link., _(*2)

Usually used for front-end menus, not back-end. Adding a menu item in MenuCRUD will not add an item in the admin sidebar, though you can easily customize Backpack\Base's sidebar.blade.php to show all menu items in the db, if you'd like., _(*3)

Security updates and breaking changes

Please subscribe to the Backpack Newsletter so you can find out about any security updates, breaking changes or major features. We send an email every 1-2 months., _(*4)

Install

This needs Backpack\PageManager to be installed first. If you haven't already, please do that first., _(*5)

Since MenuCRUD is just a Backpack\CRUD example, you can choose to install it one of two ways., _(*6)

(A) Download and place files in your application (recommended), _(*7)

or, _(*8)

(B) As a package, _(*9)

The only PRO of installing it as a package is that you may benefit from updates. But the reality is there is very little (if any) bug fixing to do, so you probably won't need to update it, ever., _(*10)

Installation type (A) - download

1) Download the latest build., _(*11)

2) Paste the 'app' and 'database' folders over your projects (merge them). No file overwrite warnings should come up., _(*12)

3) Copy the page_or_link.blade.php file located in 'resources/views/fields' folder to your project's 'resources/views/vendor/backpack/crud/fields' folder. No file overwrite warnings should come up., _(*13)

4) Replace all mentions of 'Backpack\MenuCRUD\app' in the pasted files with your application's namespace ('App' if you haven't changed it): - app/Http/Controllers/Admin/MenuItemCrudController.php - app/Models/MenuItem.php, _(*14)

5) Run the migration to have the database table we need:, _(*15)

php artisan migrate

6) Add MenuCRUD to your routes file:, _(*16)

Route::group(['prefix' => config('backpack.base.route_prefix', 'admin'), 'middleware' => ['web', 'auth'], 'namespace' => 'Admin'], function () {
    // Backpack\MenuCRUD
    Route::crud('menu-item', 'MenuItemCrudController');
});

7) [optional] Add a menu item for it:, _(*17)

# For Backpack v6
php artisan backpack:add-menu-content "<x-backpack::menu-item title='Menu' icon='la la-list' :link=\"backpack_url('menu-item')\" />"
# For Backpack v5 or v4
php artisan backpack:add-sidebar-content "<li class='nav-item'><a class='nav-link' href='{{ backpack_url('menu-item') }}'><i class='nav-icon la la-list'></i> <span>Menu</span></a></li>"

Installation type (B) - package

1) In your terminal, run:, _(*18)

``` bash composer require backpack/menucrud, <sub>(*19)</sub>

2) Publish the migration:

php artisan vendor:publish --provider="Backpack\MenuCRUD\MenuCRUDServiceProvider", <sub>(*20)</sub>

3) Run the migration to have the database table we need:

php artisan migrate, <sub>(*21)</sub>

4) [optional] Add a menu item for it:

For Backpack v6

php artisan backpack:add-menu-content "<:menu-item title="Menu" icon="la la-list" :link="\"backpack_url('menu-item')\"">", <sub>(*22)</sub>

For Backpack v5 or v4

php artisan backpack:add-sidebar-content ", <sub>(*23)</sub>

#### Usage in your template

Here's a simple example to use in your frontend:

You can access item children with `$item->children`

@foreach (\App\MenuItem::getTree(); as $item) {{ $item->name }} @endforeach ```, <sub>(*24)</sub>

For Installation type (B), change the namespace to Backpack\MenuCRUD\app\Models., <sub>(*25)</sub>

Change log

Please see CHANGELOG for more information what has changed recently., <sub>(*26)</sub>

Overwriting functionality

If you've used installation type A and need to modify how this works in a project: - create a routes/backpack/menucrud.php file; the package will see that, and load your routes file, instead of the one in the package; - create controllers/models that extend the ones in the package, and use those in your new routes file; - modify anything you'd like in the new controllers/models;, <sub>(*27)</sub>

Contributing

Please see CONTRIBUTING and CONDUCT for details., <sub>(*28)</sub>

Security

If you discover any security related issues, please email tabacitu@backpackforlaravel.com instead of using the issue tracker., <sub>(*29)</sub>

Please subscribe to the Backpack Newsletter so you can find out about any security updates, breaking changes or major features. We send an email every 1-2 months., <sub>(*30)</sub>

Credits

• Cristian Tabacitu
• All Contributors

License

Backpack is free for non-commercial use and 49 EUR/project for commercial use. Please see License File and backpackforlaravel.com for more information., <sub>(*31)</sub>

Hire us

We've spend more than 10.000 hours creating, polishing and maintaining administration panels on Laravel. We've developed e-Commerce, e-Learning, ERPs, social networks, payment gateways and much more. We've worked on admin panels so much, that we've created one of the most popular software in its niche - just from making public what was repetitive in our projects., <sub>(*32)</sub>

If you are looking for a developer/team to help you build an admin panel on Laravel, look no further. You'll have a difficult time finding someone with more experience & enthusiasm for this. This is what we do. Contact us - let's see if we can work together., <sub>(*33)</sub>