This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
There is an account, Parker, that when they log in the site fails to render fully. It looks as if the CSS is downloaded but is not being parsed. So, look into that account and see if there are any issues. I'm honestly not sure where to starts since it is such an odd issue. When done investigating change the username and then make the account "Pkr" to have the name "Parker".
I took a look in the db. His skin is set to "Classic", which looks like this [1]. I renamed "Parker" to "Parker old" and "Pkr" to "Parker". We might wanna get an extension to delete accounts (see bug 20408). Do we need to contact him? [1] http://docs.webplatform.org/w/index.php?title=Main_Page&useskin=standard There are 59 accounts with a skin other than "WebPlatform", which raises the question if we want to force the same skin for everybody. I guess we don't want to put any effort in making other skins compatible. Could be done via: $wgHiddenPrefs[] = 'skin'; Or if we want to limit the list: $wgSkipSkins = array(...);
I had told him if one day he can't login to try the other username. I will still find a way to contact him just in case (I think I can find him on Twitter.) Also, we should lock down themes so only the Web Platform skin is used.
For those users we should change their skin in the database, and yes, we should force the skin to webplatform. It sucks supporting multiple skins (trust me :D). We should generally never delete users. It may actually be a violation of our license to do so, since we'd have content that isn't attributed.