saving the user can fail when the new ign or name are already assigned to a different user.
it's not worth implementing automatic correction because there can be multiple or even circular
'dependencies' of unique names that need to be changed
You should now be able to resend the confirmation mail with the click of
a link that is next to the warning that the mail isn't confirmed.
Resend the confirmation mail cleaning
Just a way to re use the files and stuff we already have instead of the
file I created even though I could use the register_mail we have.
Change of route and link to button
I changed the route from GET to POST because of security reasons, and
changed the link_to to a button_to
changed the notice
I changed the notice so it said check for the mail instead of check for
the link
Changed notice and button
Changed the notice to say "Check your inbox" instead of "Check your
mail" also changed the way the class looks
Removed the haspaid?, correct_case?, ign_is_not_skull and
ign_is_not_mojang methods because they aren't used anymore, since we now
have a connection between the server and the website to check if they
have paid and that the skull is a skull. I also removed the
account_exists? method because it makes problems when you setup the
database since some users can be seen to not exist.
browsers will calculate the sha256 hash of the script and compare it to the value of the integrity attribute
if the values do not match, the browser will refuse to execute it.
note: the shasum is written in base64 encoding, not the (more common) hex format!
In Firefox a <textarea> with a padding-top preserves the padding when scrolling down,
whereas in Chrome the padding will scroll up altogether with the content
