Thread

I’m using ExpressionEngine 1.6.0 - Build:  20070726 logged in as a Super Admin, and when I go to update a person’s username it doesn’t take (save).

Anyone have a clue as to where to start trouble-shooting this?

Are you sure it’s not saving?  It may be that it’s just auto filling with the old username, if you use a browser or extension with form auto-filling. Double check in the database to make sure it’s actually working, or even in the member list.

Thanks for the reply Lisa. I have tried this in both Firefox and Safari on OS X.

Here are three screenshots in order of action.

Have you checked the database to see if the username has been updated?

I’m with Lisa here; it’s probably just your browser auto populating the form.

I double checked the DB and confirmed that it has not been updated.

I’m not trying update my user, I’m updating other users so form auto-population doesn’t seem to be the case here. This outcome is the same for all attempts so far.

I can take a screenshot of the ajax request with Firebug if you’d like so you can see if it’s making the proper request and getting the proper response.

Let me know.

Ajax?  Have you modified your installation?  We do not use Ajax there.

Oops, sorry about that.  🙄  My mistake…

No I have not modified my install. I even updated to the latest build to see if that was an issue.

Do you have “Allow members to change their username?” set to “No”?  I have just found and fixed a bug where Super Admin were not being properly excluded from that check.

Do you have “Allow members to change their username?” set to “No”?  I have just found and fixed a bug where Super Admin were not being properly excluded from that check.

I’m positive I reported this bug quite a while back… but can’t find it anywhere :ohh:
Must have been dreaming about EE again when I reported it! (happens quite often)

Do you have “Allow members to change their username?” set to “No”?  I have just found and fixed a bug where Super Admin were not being properly excluded from that check.

That’s what it was! In the security settings I updated that setting to “yes” and bingo.

So this could be good for more info on tracking down that bug because our install date for this install was back in March 2006 and was probably version 1.4.1 or something. So over time this install was version updated to today’s current version.