Thank you @davcon for the new login module! It's been fun testing this over the past few days on a new app.
Hey everyone,
I'm wondering where the sign-up page should live?
Would you add it as a child module and configure it as a setting within config/login.php, since sign-up should be scoped to the user level?
Or would you just create a new module?
Best practice for sign-up pages alongside the new multi-level login module?
4 months ago
4 months ago
#1
3 months ago
#2
Hello,
I would not put it in config as a child, because config is special.
I would have it a module. Easy to protect with security.
Dan
I would not put it in config as a child, because config is special.
I would have it a module. Easy to protect with security.
Dan
3 months ago
#3
Hi Dan
Thank you.
I wasn't exactly clear, as I didn't mean to throw it within the config folder. Instead, I was wondering if we should create a separate module called sign-up or a child module within the login module?
Then activate it in config/login.php for example, like this:
Jim
Thank you.
I wasn't exactly clear, as I didn't mean to throw it within the config folder. Instead, I was wondering if we should create a separate module called sign-up or a child module within the login module?
Then activate it in config/login.php for example, like this:
Jim
3 months ago
#4
Hey David, I’m thinking something similar to the “Forgot Password” flow within the login module. Give me a couple of days, and I’ll see what I can come up with and submit it as a pull request.
Jim
Jim
3 months ago
#5
Yes I think that would work nicely
Dan
Dan
3 months ago
#6
Yes, good suggestion David.
I submitted the password-child-refactor pull request.
I've updated all login form links to use the custom route when one exists, rather than falling back to the default. This ensures consistency across the board.
On logout, I've changed the redirect pointed at the base URL rather than login page. Happy to revert that part if you'd prefer it scoped to the login form default or custom route.
Working on "join" tomorrow.
I submitted the password-child-refactor pull request.
I've updated all login form links to use the custom route when one exists, rather than falling back to the default. This ensures consistency across the board.
On logout, I've changed the redirect pointed at the base URL rather than login page. Happy to revert that part if you'd prefer it scoped to the login form default or custom route.
Working on "join" tomorrow.
3 months ago
#7
No problem. I changed my mind and didn't want to submit until I heard back. I'll revise and submit with just the password_handler child module and any related changes.
3 months ago
#8
Add password_handler child module submitted.
Yes, the plan is to launch my YouTube channel in July. I’d really appreciate some 1-on-1 feedback from you on the plan.
Yes, the plan is to launch my YouTube channel in July. I’d really appreciate some 1-on-1 feedback from you on the plan.
3 months ago
#9
Great initiative! I really hope you get on board with this, Jim. I'm sure you would put together an amazing tutorial. If there's anything you need assistance with, just let me know!
3 months ago
#10
Thanks guys! Offer accepted and email sent.