Laravel 5.6 on Material Design Lite 1.3 with user authentication, registration with email confirmation, social media authentication, password recovery, and captcha protection. This makes full use of Controllers for the routes, templates for the views, and makes use of middleware for routing. Uses laravel ORM modeling and has CRUD (Create Read Update Delete) functionality for all tasks. Quick setup, can be done in 5 minutes. It will take longer to obtain your Facebook, Twitter, and Google Plus API Keys than it will to set this up.
I'm wondering if this is even an issue or I just messed up something.
I see that
profile
property isn't being instantiated inRegisterController@create
, is this intentional?Because new users registered using email (non-socialite) get a null property error in views that are accessing
Auth::user()->profile->...