#1 User login bug
Ok, thjis is a bug that I have just come accross, it
seems that there is a bug in the user login script that
will not only cause MWT to think that you are logged in
(when you aren't), but will also post nonsense to the
users list. Unfortunately, as of yet I am unable to
replicate it, but here's my theory on what is happening:
Under normal curcumstances, when you are not logged in
it will display "Sign in / crate account" in the
corner. MWT looks for this, and if it finds it then it
prompts for login. Every so often, it will display like
this instead:
http://www.coderwiki.com/wiki/index.php?title=Image:CoderWiki_Broken_Again.png
, so MWT can't find that you aren't logged in, and
attempts to retrieve the user name. It instead
retrieves a ton of garbled mess, which (because it
isn't on the user list) will be submitted to the user
list. This means that every time the bug hits somebody
the user list breaks. This bug is a problem because it
allows editors to use MWT without logging in, which is
not a good thing.
Proposed (temporary) solution:
a) give the user a message box to ask "is this your
user name?"
b) instruct users who are affected by the bug to open
IE, log in (ticking remember me) and then start MWT,
they should then not be affected by it, as they are
*actually* logged in.
Proposed (permanent) solution:
Find a better way to detect if a user is logged in or
not, this is pretty hard without having the HTML source
for the page when it lookss wrong.
Logged In: YES
user_id=1548509
From what I can find, a temporary fix should be possible.
http://en.wikipedia.org/w/index.php?title=User_talk:MichaelBillington&diff=70574231&oldid=70555422
Let's hope it works, or we'll need a new version by tomorrow
Logged In: YES
user_id=1548509
Note: The above workaround failed, it seems this bug will
probably be a b**** to solve, especially seeing as we can't
replicate it outside of the affected user's machine.
For those who don't use the mailing list, I'll quote myself:
(irrelevant rambles) ... concerns me, as no workaround
solution will work, and I haven't a clue what I can do to
fix it other than add safety features to make it stop if it
is using clearly malformatted data. So far it seems that
this bug is an isolated case, so I'm still hopeful that it
wont become a widespread compatibility issue. ... (rambles
on about 0.8 release)