Closed geekingfrog closed 5 months ago
Also tested the flow when registering a new user through chobby, and got the email fine:
For the sake of testing, how would you force that password reset email send to fail?
For the sake of testing, how would you force that password reset email send to fail?
I rebased this branch on top of latest master, this way it's using the new config system. In the integration server, the easiest would be to change the host/password for the mailer configuration to something that will fail. This way, any attempt to send an email would fail and trigger this codepath.
Locally I force the email integration and don't start the local docker container that simulate the smtp server (same thing as putting a wrong hostname).
I don't think there's a way to test that without config/code change otherwise.
Address https://github.com/beyond-all-reason/teiserver/issues/289
If, for whatever reason, sending the password reset email fails, then attempt to delete the reset code so that the operation can be retried.
Also fixed a template so that flashes are shown on the login page as well.
This is what the admin UI looks like:
and this is what the user facing interface looks like: