Fossil Forum
Post: Self-registration email verification.
I'm trying to figure out how self-registration works. I have set up a repository with the following settings:
✅ Allow users to register themselves
✅ Email verification required for self-registration
Now, when a user creates a new account, they get an option "Email Alerts?". When they choose "Yes", they get a confirmation mail. The text of this mail refers to confirmation for subscribing to alerts. It doesn't actually seem like a confirmation of creating an account. Following the link in the mail does however update the account's capabilities from 7 to u.
When the user on the other hand selects "No" for "Email Alerts?" during the account creation, they don't get an email to actually complete the self-registration. They are stuck with only the 7 capability. Even if they later configure email alerts, no confirmation mail is sent.
Is this how the functionality is intended to work? If so, does it make sense to offer the user an option that can break the self-registration process? As the confirmation email only seems to be sent during self-registration, I think it would be less confusing if it mentions account creation rather than alert subscription. Z 3
I ran into this (or similar at least) problem a few years ago.
As far as I am aware it remains unresolved, but it turned out to not be much of a problem, as people seem not to actually read what they are signing up to...
I ran into this (or similar at least) problem a few years ago.
Funnily enough: your recent post in the pikchr forum is closely related, and now (after seeing schelte's post) i understand why the user permissions in the pikchr forum are the way they are: some users sign up for notifications without an account (which i didn't realize was possible).
@schelte - i cannot say off hand which of the behaviors you describe are intended as-is and which are undesired side-effects but will attempt to sort it out as soon as the dogs allow me to. (i'm their sole caretaker for the next month and it's exhausting.)
I suspected as much 😉
I did try to walk through the code and try to get my head around what might be happening, but it was a bit too deep magic for me at the time.
There was clearly a logic error somewhere when I did look at it - the page redirects nearly but not quite allowed subscription and addition of an email for a self registered account that didn't subscribe at the time of registration.
But I didn't ever find time to trace all the moving parts.
I know a tiny bit more C and coding in general these days, mainly by trying to hack althttpd into different shapes. It's not my day job!
But I might go back and see if I can tease the issues apart a little more if I can find the time. Z
I found your thread before posting this, but thought it was a different problem. After creating a test account with "Email Alerts?" set to "No", I am able to change the alert settings.
Good to hear about your experience that it doesn't turn out to be much of a problem in practice. Although I did get a report from someone indicating that he never got the confirmation mail. But when examining the account, the capabilities had been updated from 7 to u. So he must have clicked the link. I guess he also thought it was just a link for accepting the alert subscriptions, not the account confirmation.
Oh thank you. I probably do need to take another look at this then.
I'm still very aware it may have been a problem on my end, in my particular case.