Registration with EmailVerification could do with better description for users

[gary.martin@…]

A minor problem but the combination of messages on the registration form (The email address is required for Trac to send you a verification token.) and on successful registration (Registration has been finished successfully. You may login as user testuser now.) seem to lead people to believe that they should wait for an email rather than login as instructed to trigger the email.

It might be a bit clumsy to append a message to the existing message, so a new msgid might be better. Perhaps something like

Your username has been successfully registered but your account still requires activation. Please login as user %(user)s, and follow the instructions.

or something like that?

[Steffen Hoffmann]

Hm, why not? I can imagine better wording helps some users, sure.

But I have to replay the procedure to see how it goes.

Side note: Using code wiki markup for long-running lines isn't a good idea. I've edited your description for you to make it look nicer.

[gary.martin@…]

Replying to hasienda:

Hm, why not? I can imagine better wording helps some users, sure.

But I have to replay the procedure to see how it goes.

Side note: Using code wiki markup for long-running lines isn't a good idea. I've edited your description for you to make it look nicer.

I did not that when I submitted. Unfortunately I was already late for something so I had to leave it. Sorry about that.

Thanks for considering this.

[Steffen Hoffmann]

(In [11841]) AccountManagerPlugin: Add better registration success message, refs #10123.

Thanks to Gary Martin for the suggestion.

In addition registration errors won't delete all user input anymore, but only password fields.

If ignore_auth_case is True, username conversion to lowercase is required. I guess, that adding a corresponding hint to the registration page will avoid confusion about this conversion of all user input for the username field.

[Steffen Hoffmann]

(In [12398]) AccountManagerPlugin: Releasing version 0.4, pushing development to acct_mgr-0.5dev.

Availability of that code as stable release closes #874, #3459, #4677, #5295, #5691, #6616, #7577, #8076, #8685, #8770, #8791, #8990, #9052, #9079, #9090, #9139, #9246, #9252, #9547, #9618, #9676, #9843, #9852, #9940, #10023, #10028, #10123, #10142, #10204, #10276, #10397, #10412, #10594, #10625 and #10644.

Some more issues have been worked-on, yet without confirmed resolution, refs #5464 (for JiraToTracIntegration), #8927 and #10134.

And finally there are some issues and enhancement requests showing progress, but known to require more work to resolve them satisfactorily, refs #843, #1600, #5964, #8217, #8933.

Thanks to all contributors and followers, that enabled and encouraged a good portion of this development work.