Member Since 4 Years Ago
790 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 Upgrade To Laravel 6.18.35 Breaks Auth:api Route Authentication
Just in case it may save someone's day, I want to share an issue I resolved earlier today.
After running a Composer update, the API routes were failing authentication with Error 401! After some hours l hours of desperate search, I decided to try and update laravel/passport after which all was working fine again.
$ composer update $ npm run dev
The above included an update of Laravel 6.18.25 to 6.18.35 that seems to have broken all auth:api routes; failing with “401”
$ composer require laravel/passport $ npm run dev
This updated Laravel Passport from 8.4 to 9.3, which fixed the issue.
Would there have been a way to avoid falling into this update trap?