Implement Forgot Password Functionality - Build Expense Tracker App With PHP 8
HTML-код
- Опубликовано: 19 июн 2023
- Continuing our series on building Expennies, this tutorial is all about enhancing security. We dive deep into implementing a 'Forgot Password' functionality, a crucial feature for user management in any web app.
SOME OF THE WAYS YOU CAN SUPPORT THE CHANNEL
👍 Smash the like button
🤝 Subscribe to the channel & turn the notifications on
💬 Post comments, any feedback is greatly appreciated
⭐ Become a Patreon: / programwithgio
THANK YOU!
🛠️ TOOLS & SERVICES I USE
Digital Ocean Hosting - Get 100$ credit - m.do.co/c/38b935ad74e5
Domains on Namecheap - namecheap.pxf.io/rnRjdQ
Envato Elements - 1.envato.market/c/2937311/298...
LESSON P.33
Starting Source Code - github.com/ggelashvili/expenn...
Ending Source Code - github.com/ggelashvili/expenn...
Behind the scenes changes - github.com/ggelashvili/expenn...
Course Outline - github.com/ggelashvili/learnp...
Course Playlist - • Learn PHP The Right Wa...
** Affiliate Disclaimer: Some of the above links may be affiliate links, which may generate me a sales commission at no additional cost to you.
fantastic course for modern php explained in every detail that make the diference from all other php lessons i watched, Program With Gio is the best teacher he keeps the same perfect style of explain every think we need to undarstand and each video is the 1 and only php course in my opinion, thank you Program With Gio
Happy to hear this, thank you
Exactly what I was looking for you are such a blessing😊
Glad it's helpful
What a great channel! Thank you very much!
Thank you, glad you like it
More goodies. Thanks a lot Gio.
You're welcome
Hey Gio, amazing videos as always 🤍.
Regarding the exercise I dedicated a new route for the reset password functionality.
The callback routine is a function in the "profile controller".
I modified the update password modal to include a confirm password field and created a custom request validator. it contains a custom rule that checks the password length, checks for upper and lower case letters and numbers and special characters.
what do you think about that ? do you recommend a better approach ?
I also have another question, I’m think of extracting the mentioned custom rule and putting it in a dedicated request validator, in order to use it in multiple places like the register form. what do you think about that ?
Thank you so much bro
You're welcome
Hi ! I am currently starting out with the 3rd section of the course and have completed the 1st and 2nd sections. I just wanted to know that whether functional and integration testing is covered in this course or not ? And would you be implementing these in this project ? Thanks in advance :)
Hello. We covered basics of unit testing in third section. I don't have time unfortunately to add tests to this project since we are wrapping it up now in just a few more videos. People don't seem too interested in this project so I want to wrap it up fast.
@@ProgramWithGio I would love to learn about functional and integration testing, as we have an app that currently only has unit tests.
We want to include integration testing using guzzle. Can you help out with that by making some videos? If not, would you share some resources and examples that would help out. Once again thanks in advance and truly amazing content.
You've brought back PHP from the dead . Lol
@@mayankpathak3415 not in my plans currently unfortunately, maybe in future. I would browse Laracasts, they have plenty of resources around testing.
Hi Gio. Thanks again for this great lesson. I've done the exercise. Apart from the required, I kinda did the validation with the user entity. I'm thinking that there can be slight differences. Lemme explain what I mean.
To validate required I used the valitron request validator.
Then to validate that the current password is different from the new password I actually did it with valitron at first. But there's a need to still check if the user is reusing the current password saved in the database as the new password which is slightly different from filling the current password field and the new password field with the same value.
So since I'm using the user entity to check if the current password is the same as the one saved in the database, I might as well use that too to check if the current password saved in the dB is the same with the new password and then throw a validation exception if it is.
So in the end I'm using the valitron validator to validate required, lengthmax and lengthmin and maybe I'll add some alphanumeric rule as well. But using the user entity to validate the correctness of the current password and the assurance that the new password is different from the current password before setting the new password and synching it with the dB
Thanks alot Gio
Sounds good, great job
I was avoiding accessing the user entity in the request validator, but It sounds like I need to use it. 👍
You are a good teacher ! I am really looking forward to the Laravel course, can you start it in August? I don't know what to say other than wishing you all the best!
Thank you. Unfortunately, no. It takes a lot of work & effort to create video tutorials. I have not started planning or recording Laravel course yet so I dont have a set date when I'll be able to work on it. Possibly end of the year or start of next year, we'll see
You are amazing. I wish someone like you could teach Laravel in such a great way by creating a project with Laravel Nova, for example.
Thank you. I'll be working on Laravel course soon. I don't use Nova though