Member Since 2 Months Ago
2,280 experience to go until the next level!
In case you were wondering, you earn Laracasts experience when you:
Earned once you have completed your first Laracasts lesson.
Earned once you have earned your first 1000 experience points.
Earned when you have been with Laracasts for 1 year.
Earned when you have been with Laracasts for 2 years.
Earned when you have been with Laracasts for 3 years.
Earned when you have been with Laracasts for 4 years.
Earned when you have been with Laracasts for 5 years.
Earned when at least one Laracasts series has been fully completed.
Earned after your first post on the Laracasts forum.
Earned once 100 Laracasts lessons have been completed.
Earned once you receive your first "Best Reply" award on the Laracasts forum.
Earned if you are a paying Laracasts subscriber.
Earned if you have a lifetime subscription to Laracasts.
Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.
Earned once you have achieved 500 forum replies.
Earned once your experience points passes 100,000.
Earned once your experience points hits 10,000.
Earned once 1000 Laracasts lessons have been completed.
Earned once your "Best Reply" award count is 100 or more.
Earned once your experience points passes 1 million.
Earned once your experience points ranks in the top 50 of all Laracasts users.
Started a new Conversation Assigning Users To Multiple Tables
I'm working on an app that will have Leads, Employees, Members, Volunteers and obviously Users for login credentials. The reason these are not on the same table is that the Leads must have a lot of nullable fields. One of those nullable fields being the email address and password because some of the leads we'll need to register don't have email addresses. So I figured I could have personal information on the leads table. Then only use the users table for login credentials.
The complications are:
A lead can then be a volunteer with a volunteer number and can then add new leads into the system and have all the leads they added under them.
A lead can also be a member but members cannot add leads, they just have a membership number and access to certain pages. To be a volunteer and/or a member, you have to create a user account with your email address.
A lead can be an employee with an employee number and many other fields the other tables don't have.
Viewing a lead should show all the information on the members, volunteers and employees tables respectively depending on which of those are applicable for that user. And they can be a member, a volunteer and an employee at the same time.
I will all suggestion on how one could go about achieving this.
Started a new Conversation Multiuser Database Planning
I'm an upcoming developer and have a project for a political party. They want to have leads of potential voters, volunteers responsible for recruiting these leads and with some referral benefits to all the leads they capture, employees for other tasks within the system and members who will have a membership number and get access to certain areas of the application. I'm battling with whether all these users should be under one users table or just use the users for login credentials and all the other details separated into members table, employees table volunteers table etc. If I go with separate tables, how does Laravel handle this? I know these might be stupid question, I'll never know if I don't ask right?
I appreciate your advice.
Thank you so much for your prompt response, Kind Sir. That resolved my problem.
Started a new Conversation Illuminate\Contracts\Container\BindingResolutionException Target Class [UserController] Does Not Exist.
I'm new to Laravel. I started working on Laravel 7 a week ago, built an API and everything is working fine. I attempted to recreate the same API with Laravel 8 but my api routes don't seem to be working anymore. I get an error that says:
"Illuminate\Contracts\Container\BindingResolutionException Target class [UserController] does not exist."
I have defined api routes like so: Route::resource('users', 'UserController', ['except' => ['create', 'edit']]);