Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: No message for new user about checking and verifying email #246

Open
introkun opened this issue Mar 31, 2024 · 13 comments
Open

bug: No message for new user about checking and verifying email #246

introkun opened this issue Mar 31, 2024 · 13 comments
Assignees
Labels

Comments

@introkun
Copy link
Contributor

What version of MyFinances are you currently using?

v0.2.1

What device type are you currently facing the issue on?

Desktop

Describe the bug

Steps:

Expected result:

  • user-friendly message to check the inbox and activate account by verifying email
@introkun introkun added the bug label Mar 31, 2024
@introkun
Copy link
Contributor Author

Related to #245

@ssheth75
Copy link

ssheth75 commented Apr 1, 2024

I would like to work on this issue, thanks!

@kryptokun
Copy link

Same, we are working together so wanted to know if we both could be assigned?

@TreyWW
Copy link
Owner

TreyWW commented Apr 1, 2024

Sure thing! Sorry I completely missed your messages.

@kryptokun
Copy link

kryptokun commented Apr 2, 2024

I'm having trouble finding the code where the message for new user function is. Could I get some help locating it? I know that the functionality will occur in the login_initial.html

@TreyWW
Copy link
Owner

TreyWW commented Apr 2, 2024

It's probably in backend/views/core/auth/login.py

@TreyWW
Copy link
Owner

TreyWW commented Apr 20, 2024

Any progress @kryptokun?

@kryptokun
Copy link

Sorry was packed with a lot of school work. Will get on it this weekend

@TreyWW
Copy link
Owner

TreyWW commented Apr 20, 2024

Amazing, no problem, just making sure you aren't stuck :)

@TreyWW
Copy link
Owner

TreyWW commented May 1, 2024

Would you like to be unassigned from this issue @kryptokun?

@Domejko
Copy link
Contributor

Domejko commented May 5, 2024

@TreyWW This issue is outdated since PR #270 have resolved that problem. Unfortunately latest PR #362 have broke that functionality since it wasn't caught in tests and I just discovered this while testing on server.

I will revert that change and this issue can be closed.

Edit:
Now I noticed that your latest commit have fixed that issue from #362 so I will just send update for type: ignore

One thing is that to have this functionality working we need to provide some testing random API key in .env, for example:

SENDGRID_API_KEY=asd87aFDASDFE*f7fsd86asHDZSDJHAs87212b121

I can update .env.sample with it if you like. Let me know, then I will send both changes in one PR.

@TreyWW
Copy link
Owner

TreyWW commented May 5, 2024

Hmm since we've moved to SES for emails we've not continued support for Sendgrid. Maybe I should do a revamp for emails and allow for either to be used?

@Domejko
Copy link
Contributor

Domejko commented May 5, 2024

I think that since it's open source project it will be good to have a choice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants