Your registration page has a manually coded true hash for the password. That means the password cannot be unencrypted... hash is a one-way encryption.
The MySQLi authenticate user server behavior doesn't support hashed passwords in the UI, so I had to manually update the code to add it... see the line that has ->addHash( in the code. I added that by hand and it will prevent you from editing the server behavior through the server behaviors panel.
You cannot use the password in any lookup query. Since it uses a one-way hash, there is no way to use it in a normal filter. You can save the UserID in the authenticate server behavior and use that to look up the user's record in a recordset.
It is the same issue with the password in the email. You can't send a password since it can't be unencrypted. You have to send a reset password link instead and send them to a page where they can reset the password since you can't look up the old one.
If you run the security assist wizard with MD5 encryption on the password field, it will create the correct style of forgot password page that sends a reset link instead of trying to send the password in the email. That might be a good way to just replace that page since your other pages are working now, back them up and don't use the wizard created pages for those.