Last modified: 2014-06-28 22:49:09 UTC
I think this is the extension that displays a message about successful login after the user logs in. A similar message was also displayed by MediaWiki up to and including versipon 1.13. From 1.14alpha onwards, this MediaWiki message has been removed. So, without this extension the user can enjoy message-free logins, but after enabling this extension, at least on Wikipedia/Wikimedia, the user is back at logins that display this annoying and unnecessary message.
CentralAuth relies on images loaded from that 'successful login', so it looks like a WONTFIX.
perhaps, however, you could find a way to not disturb the user with that useless message, even though it would probably require a few changes. When Wikipedia was updated to 1.14 I was happy that I was not seeing this "successful login" message anymore. But then I decided to unify my accounts, and I see this hated message again, which only consumes my precious time without giving me any information that I ever requested or wanted to see. As a user, it is so much a disturbance for me that I am really thinking about cancelling my unified login (not sure how or if possible though, but that's another matter). If I knew that I would have to face this message again if I were to unify my accounts I would surely never have unified my accounts. In fact, before I saw that message I was considering installing a similar unified login for my wikis with the same extension, but after seeing the message on Wikipedia I decided not to use the extension. In fact that similar message present in pre-1.14 mediawiki was always my biggest dislike regarding mediawiki itself. As a user I can see absolutely no need for such a message to even exist at all, as it only eats up my time or makes me undergo a useless click. Don't know what other users think, but I, for one, would think that finding a way to remove this message should be a high-priority fix.
Since people somehow lived with this for years with little complaint, I don't think it's going to be a high-priority as such. One possibility is to redirect back to the 'return to' target immediately after the DOM confirms the cookie-setting images are loaded; this would minimize the trauma. On the other hand, it could make the screen seem to flicker, and might be confusing for people wondering what was loading. If it's re-tooled a little to look more like a "loading..." interstitial, that would probably be reasonably ok. Alternatively, the whole login form could be redone where possible in a more AJAX-y style to submit the form credentials, then load up the cookie-fixer images inline, *then* redirect to the returnto target, without needing to use an interstitial. This would appear more natural, as long as it's feasible to detect the properly-loaded images. (If images don't work right for this we might be able to devise something else, but things can get tricky.)
I suppose another option, if you're going down the "AJAX-y" route, would be to go to the returnto target straight away, and load the images in a banner at the top of that page. Something like the "Your message has been sent" in GMail, but saying "You are now logged in to this site, and also these: [image][image]" Might be a little trickier to implement cleanly, since you'd be modifying the display of standard pages, rather than everything happening on a Special page, but would give a nice user experience.
This was "fixed" with the new SUL2 auto-login system.
