Unable to change full name

[anonymous]

When I try to change my name on the preferences page I get an error message:

The email address specified is already in use. Please specify a different one

And the name is not changed.

I'm running TracAccountManager-0.4.3

[Ryan J Ollos]

I suppose that there must exist an account in the system that is already using that email. This is therefore not a bug, it is a constraint of the software, and we ask that you direct such questions to the ​t:MailingList in the future.

I've previously wondered though, if we might be able relax the requirement for unique email addresses. perhaps through a configuration option. There have been times that I've wanted to have multiple accounts having the same email address. I've worked around this by creating email aliases on my mail server.

[anonymous]

I'm changing the full name of my existing account, so of course the email exists. Shouldn't this be possible? Maybe I'm misunderstand what this form is for?

[Ryan J Ollos]

I see. I read your question quickly and carelessly. Sorry about that.

I will try to reproduce your issue in the morning.

[Ryan J Ollos]

I wasn't able to reproduce running the latest trunk code r12686. I will try with 0.4.3 in a development environment. In the meantime, could you paste some of your configuration details here? What version were you running prior to the recent upgrade to 0.4.3?

[Steffen Hoffmann]

Replying to rjollos:

I suppose that there must exist an account in the system that is already using that email. This is therefore not a bug, it is a constraint of the software, and we ask that you direct such questions to the ​t:MailingList in the future.

Yes and yes.

I've previously wondered though, if we might be able relax the requirement for unique email addresses. perhaps through a configuration option. There have been times that I've wanted to have multiple accounts having the same email address. I've worked around this by creating email aliases on my mail server.

You'll find, that the constrained is connected only to enabled email verification. If you disable it, the constraint checks and associated messages go away.

The issue here likely comes from enabling email verification later-on, and now the user in question is forced to clean-up.

[anonymous]

Correct. If I uncheck "Force users to verify their email addresses." in Administration > Accounts > Configuration, the message goes away. I don't remember if I have changed this setting previously, but it's possible. If you can not reproduce this with this setting enabled in trunk, feel free to close this issue.

[Steffen Hoffmann]

Replying to anonymous:

Correct. If I uncheck "Force users to verify their email addresses." in Administration > Accounts > Configuration, the message goes away. I don't remember if I have changed this setting previously, but it's possible.

Currently this is the only way to get into this sort of trouble, but it was possible to change the email address after completing registration, even to circumvent email verification by deleting a required email address from user account preferences for a long time. So if you installed AccountManager a while after starting to use Trac, or you did upgrade the plugin from an earlier version, we'll never know.

If you can not reproduce this with this setting enabled in trunk, feel free to close this issue.

Clever move. I knew I could, and I can reproduce indeed. Point taken.

Note though, that the upcoming fix does not encourage going on with such insane settings like yours. I do just care to handle transitions more gracefully. Enabling email verification late is nothing a user should have to care for.

[Steffen Hoffmann]

(In [12689]) AccountManagerPlugin: Disregard conflicting, but earlier configured emails addresses, refs #10204 and #10910.

It has been reported, that under certain conditions, i.e. late activation of email verification, a legal name change in user preferences might be rejected, if his/her current email address is not unique among all registered accounts. Consistency checking has been improved lately; anyway I agree, that this should be handled gracefully, if the email address remains unchanged.

At this occasion it appeared sensible to roll full email checks on input to user preferences too, causing much more changes than initially intended.

[Steffen Hoffmann]

I'm grateful for this occasion to do some rather unexpected improvements.

[Steffen Hoffmann]

Note, that the changes are meant for and this issue closed with the release of either acct_mgr-0.4.4 or acct_mgr-0.5, whatever comes first.

[anonymous]

Thank you very much for the quick solution to this.

As far as I can tell, I was running 0.4.2, then moved the installation to another server and installed 0.4.3. I tried to run upgrade, but it said that no upgrade was necessary. I might have created some accounts before enabling Account Manager, but I get the same thing with newly created accounts also. What do you think I did wrong? I'd like to know, so that I don't make the same mistakes in the future.

One thing that I find odd (not sure if it's related) is that when I add an account at "manage user accounts" with the "Skip new email verification" checked, and then log on with the new account it says that it's not verified. I thought that this would not be needed, since I know that the email is correct.

[anonymous]

Forget that last paragraph. I should just disable "Force users to verify their email addresses.". It's working exactly as I want.

[Steffen Hoffmann]

Replying to anonymous:

As far as I can tell, I was running 0.4.2, then moved the installation to another server and installed 0.4.3. I tried to run upgrade, but it said that no upgrade was necessary. I might have created some accounts before enabling Account Manager, but I get the same thing with newly created accounts also. What do you think I did wrong? I'd like to know, so that I don't make the same mistakes in the future.

Don't know exactly, what you're speaking of here. In general email verification enforces unique email addresses among all users. This is how it's meant to be. I.e. lost password/password reset procedure relies on sending sensible information to the right person too, so I think, that it is a good thing to have it that way. What else?

One thing that I find odd (not sure if it's related) is that when I add an account at "manage user accounts" with the "Skip new email verification" checked, and then log on with the new account it says that it's not verified. I thought that this would not be needed, since I know that the email is correct.

Me too feeling uneasy here. I just tested it with latest trunk development code, and it creates 'verified' accounts just fine. And I'm not sure where to start about it. Would you be able to send a complete log for the whole procedure from creating a new user like mentioned before until logging in and seeing the message? You don't need to attach it here, just send it to me directly, if you care.

[Steffen Hoffmann]

Replying to anonymous:

Forget that last paragraph.

No, I wont. :-)

I should just disable "Force users to verify their email addresses.". It's working exactly as I want.

Sure, but this is just disabling the consistency checks - a workaround, nothing more, unless you insist on having on email associated to multiple accounts.

[Steffen Hoffmann]

I forgot about another rather simple check:

Select any account and the click the 'Review account attributes' button. The selection does not restrict the attributes shown there yet. So you'll have to hunt down through the pages to find your newly created account for now. Once you have it, ensure that there are two entries side-by-side: 'email_verification_sent_to' and 'email', both showing the same value - the email address you did provide on creation/registration time.

[anonymous]

I created new accounts today with "Force users to verify their email addresses." enabled and "Skip new email verification" checked. They all look ok[1] with 'Review account attributes' and I didn't get the message on the Preference page this time.

I afraid that this is a case of PEBKAC. Sorry for all the noise.

[1] 'email_verification_sent_to' and 'email' are identical.

[Steffen Hoffmann]

Sounds like at least [12689] made it work for you. Fine, so we'll close this ticket when making the fix available in the next stable release.

Thank you for providing feedback on the case, because this is among the most critical issues with 'anonymous' ticket reporters here.