https://bugzilla.wikimedia.org/show_bug.cgi?id=52373
--- Comment #25 from Chris Steipp <[email protected]> --- (In reply to comment #22) > Yes. Ideally, it would be GettingStarted and Echo (not CentralAuth) > disabling a > standard feature in core for their own purposes when they are installed and > they need to do so. It's actually not so much CentralAuth disabling the feature as the new flow actually redirects the browser to loginwiki, then back to a CentralAuth special page to finish the login, so we can't run the core bits at that point. The patch that anomie just put in allows a wiki to set a message like Welcomecreation-msg, for wikis that want to do that. If we merge that patch, the behavior on WMF sites will remain exactly how it is currently, unless CentralAuth-welcomecreation-msg is defined. In that case, we'll show the message with a link to the returnto parameter. However, GettingStarted (or any extension that implements CentralAuthSilentLoginRedirect hook) can blank out the injected html if they want to just redirect the user to the returnto url instead (or they could change all of the html set by CentralAuth-welcomecreation-msg, if it wanted). Hopefully that gives everyone the technical means for each site to do what is best for each community. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
