Last modified: 2014-09-11 18:20:41 UTC
When choosing the home wiki, if any accounts are in privileged groups, only the privileged accounts are considered for the home selection. However, any blocked accounts are removed *after* this check. If all the privileged accounts are blocked at the moment (for instance, a sysop account who has blocked himself temporarily), the working set ends up being empty, no home wiki is chosen, and an exception is thrown. The simplest solution is probably to strike out the blocked accounts before the privileged check; that is, just ignore any blocked accounts. This would, however, potentially allow a non-priveleged account to take advantage of a temporary or accidental block of a sysop account to take over. If it's desired to block that condition, then a more friendly error should be returned instead of the low-level exception.
*** Bug 13671 has been marked as a duplicate of this bug. ***
I swear I searched for dupes before reporting - is bugzilla's search function broken? It didn't seem to find any bugs in this component.
Not broken, just sucks. ;)
Interesting distinction. I searched for any open bugs in this component whose summaries included the word "privileged" - how did this bug not come up? (I then searched for any bugs in this component and it still found nothing...)
Considering that I usually have to try four times and use a spell checker to spell 'privileged', I wouldn't be too surprised. :)
I'll admit to looking it up...
Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734
Was this fixed with I32384d6423d3cb633f99cdcd2745f8ce6d8c597e? I don't see anything in CentralAuthUser::chooseHomeWiki that has to do with blocks.
