Member Since 5 Years Ago
2,020 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.
Thanks muchly, I'll see if it just works. if not I'll definitely consider the email/reset option..
Started a new Conversation Laravel 4.2 - 7 Upgrade, Users Passwords Update
So I have an old Laravel 4.2 project I'd like to bring up to date. I realise I can't just upgrade Laravel, I will have to start a, new L7 project and gradually migrate and refractor my old code into it. I plan to start a new project, add auth, tweak user model and go from there.
But it strikes me I going to run into an issue with existing users passwords, which need to continue to work.
I guess I need to add a password-version field to my user model and set that to say v1 for all existing users. New users get set with v2 password from get go and they will just work. Existing users, first time they login, I detect they are v1 and somehow use old hashing algorithm to check password, if correct, rehash password while have it as plaintext, save new hash and set user as v2 pwd version.
Does that sound about right? Any pointers regarding how to call old hashing mechanism?
Replied to Weird Laravel Cors Issues
In case anyone else hits this error, was being dumb, was trying to pull a reference to a vimeo html page into an html5 video player
Started a new Conversation Weird Laravel Cors Issues
So I've got a fairly basic Laravel 5.6(.16) project and I'm having all sorts of issues with Cors.
The latest one is with Vimeo. I'm just trying to pull in a video and I get the error
Cross-Origin Read Blocking (CORB) blocked cross-origin response https://vimeo.com/412841518 with MIME type text/html. See https://www.chromestatus.com/feature/5629709824032768 for more details.
(At the moment that's just a random vimeo video reference)
I gotta be honest I don't understand Cors and I don't understand what we should be doing to fix this. I did try to create a middleware to set response->header('Access-Control-Allow-Origin', '*') but that seemed to make no difference.
Any pointers much appreciated!!