Create a user account for session_contributors and co_authors as soon as they have payed.
As soon as payment is received and the person is marked as payed (see #124 (closed)), a user account is created for that person.
@mladen @gandhiano @almereyda
I do not like to create a password for that user and send this password via unencrypted e-Mail. Therefore I would suggest the following method:
We roll a random password and save it to the database, since the presence of a password is required by the has_secure_password
feature of rails. We will then trigger a password-reset with a different mail-text to inform the user that they now can access the system by setting their password. Here we also have to be careful about the roles the person has in different events - session_contributors will have to have access as they are speaking, co-authors CAN have a login. We need to take care that we have different texts for contributors and co-authors.
Do you have another Idea or know another way how to tackle this or is this fine?