Video instructions and help with filling out and completing Can Form 8815 Verification

Instructions and Help about Can Form 8815 Verification

Music hey everybody and welcome back to the deaf marketer channel today's video is going to be a fun and exciting one we're going to be building a multi authentication system in level 5.4 and I think this will actually work in level 5.3 actually yes it will it's going to be backward compatible with 5.3 nothing really changed between as far as authentication is concerned between the two versions so it'll work in both versions so if you're still on an older version it's going to work most likely you're going to be using a future version and we're going to be talking about how we can build multi authentication into it all right now this is something you guys have been asking for a ton I've getting lots of requests for this and so I'm really excited to finally bring it to you today to be 100% truthful the reason I haven't done it yet is because I honestly didn't really know how to do it it's something that I I've always used a package in the past but I'm getting so sick of tired of using packages that I'm just I decided to do with the level way I'm going to see I wanted to figure out how we actually use label to do it be so that we don't have all the bloat of a package but then the other problem is like every time level updates then we gotta wait for the package to update as well and then you're constantly half these packages there are so many authentication packages that get abandoned you know we used to use in trust while in trust the entrust plugin got abandoned is like 5.1 I think or maybe 5.2 there was a package called multi offs that worked in 5.0 and I think it got operated to 5.1 and then like abandoned there was there's actually a couple packages out there called multi ops there is one currently that people use it's only available in 5.2 it doesn't work in 5.3 there's lera trust which tulare trust a you know credit they're actually maintaining it quite well I think it is actually it is compatible 5.4 but again you're always running into these problems of compatibility and so I wanted kind of a simple clean way I didn't need a huge package I want to import a whole package if I just want a second type of user I wanted a way to do that without having to bring in a package and learn a package and then have the facade that the package has and stuff like that I wanted to use the label facades I wanted to use it as clean and natural to level as possible and that's what I'm going to show you guys to do today okay so this is going to be use the default authentication facade you are authentication system in layer but we're going to extend what you do when you write PHP artisan make off we're extending that whole system we're going to have two different tables one for admins one for users this will work with multiple users though like if you wanted three or four or five different types of users you could do that that would be a pretty edge case scenario what I should mention before we get going is don't get confused between types of users and roles of users okay so if you have a user let's call it a customer right and well let's just call it an admin so we got an admin user well you might have a super admin that has the ability to do everything create new admins you know change every setting in the book you know issue refunds or something like that below then you might have like I don't know like an editor right and the editor can view everybody's blog posts and you know manage all of the media and stuff like that but they can't create new users and they can't add plugins or something and then below then you might have an author who can write their own blog posts but can't you know see everyone else's blog posts or something like that those are user roles okay they're all admins they're just different user roles they have different authority levels that is what we call user roles that's different than what I'm talking about today we're talking about actually building two different systems you would not want to build a table for your super admins another table for your you know editors and then another table for your authors you wouldn't want to do that you would want those all in one table and then just give them different authority levels the use case for what I'm showing you today is if you say have a ecommerce website you have admins that manage the website they're going to create users they can create products they can manage orders as they come in issue refunds right those are all the employees of the company or the admins on the other side you're going to have customers and customers are going to have their own order history they can view their order history they going to have like a wish list they can manage and stuff like that and it's on a completely different backends this like you know interface they've got their own interface and basically looks like a front-end interface and that's how they manage their account basically whereas your admins have like a whole different interface completely different functionality maybe the information you're storing in the tables for the admin is completely different information than what you would store in the customer table okay so this that's kind of what we're doing today is for those two different types of users completely and of course built-in tool arrabal last thing before we get started I want to mention

100%
Loading, please wait...