Laravel E-Commerce - Admin - Dynamic Menus - Part 11

In this video, we continue to build out the admin backend and work on dynamic menus. We replace our main menu and footer menu using Voyager's menu builder.
GitHub Repo: github.com/dre...
LINKS
My courses: codewithdre.com
Sign up for my newsletter: andremadarang.c...
My website: andremadarang.com
Twitter: / drehimself
GitHub: github.com/dreh...
CodePen: codepen.io/dreh...

[@Devdojo]

Great stuff man! Will definitely look at adding these videos on the Voyager site to show people how to use it. Thanks for creating this series :)

[@drehimself]

Thank you to you and your team for creating Voyager!! Excited for future updates.

[@vamsikrishna2241]

where is located voyager.user.index route in project file ?

[@amusarts2169]

Thank you for your work. Very useful

[@drehimself]

Thanks for watching!

[@sodomousprime]

Can you show us how to stop the checkout page from being displayed if the cart is empty, currently the customer can input a valid promo code that place the Subtotal, Tax and Total all into negative values. Also can you show us how to display the total of an item including tax (in the same or a separate field) on all pages other than the checkout page. As tax has to be charged I don't understand why it would be helpful to display any item prices without tax.

[@drehimself]

Sure. I just updated the GitHub repo. To redirect the checkout page, you just have to check if the cart is empty and redirect if it is. Look at the CheckoutController index method. For the tax on the cart page, I would say that most e-commerce sites don't show the tax until checkout. Look at Amazon. Nonetheless, if you wanted to add the tax on the cart page, you would do exactly the same thing I did on the checkout page/controller, just on the cart page/controller. I hope that helps!

[@sodomousprime]

Thank you very much, that is very helpful.

[@mohammedawadelkhalifa4879]

hi andre :) can you explain how to make dropdown menu ? by the menu builder ... there is any trick to extend the menu builder to make it easy ? also what about mutli auth in voyager ? admin model + user model !

[@drehimself]

Thanks for watching! I'm probably not going to do a dropdown menu but let me give you a quick example of how it works using bootstrap. Add menu('test', 'bootstrap') to your code and make a new 'test' menu in Voyager. Nest a few items inside one of the menu items, make sure you have bootstrap css, bootstraps js and jquery installed. Check out your menu in the browser and the dropdown should now work using bootstrap. It's all just CSS and the javascript is just adding and removing classes.
For multi auth, Voyager already comes with Roles and Permissions allowing you to create new roles (i.e. manager, author, etc.) and allows you to set permissions for each role. I might eventually do a video of how to implement this from scratch using just Laravel and packages.

[@mohammedawadelkhalifa4879]

Andre Madarang
thanks a lot o will try to make it and i will show you 👍

[@ThalesReisMS]

Hi Andre. I'm enjoying your videos, you're awesome. Can you share the names of your plug-ins that you are using on your visual studio code? Please.

[@drehimself]

Check out my VSCode vs Sublime video. I also link to my current settings file.

[@jhoanborges6574]

AMAZING ANDRE BRAVO

[@drehimself]

Thanks for watching!

[@dan3460]

Andre, i love your series, told me a lot. I'm new to Laravel and maybe this question is basic but i have not find the answer anywhere: Why do you use {{url(route_name)}} on your a tags or links to other pages? I have been using the name of the route directly on the href, like this href="/website/createItem".
Thanks for your help, awesome series.

[@drehimself]

Thanks for watching! Mostly personal preference for me, referring to the URL directly is fine too. One advantage of using named routes though is if you ever change the URL in your routes file, you don't have to change it anywhere else. If you referred to the URL directly in your views, you would have to change it in all your views.
Example from series:
Say I changed:
Route::get('/shop', 'ShopController@index')->name('shop.index'); to
Route::get('/shopping', 'ShopController@index')->name('shop.index');
As long as I keep the route name the same, I don't have to change anything else. In your case, you would have to change all your views where you referred to /shop and change it to /shopping.

[@lmao_pat]

Damn! Awesome! Love you man!

[@alonewolf2610]

u are cool man