Page MenuHomePhabricator

Error message after Commons registration from campaign link on mobile
Closed, ResolvedPublic


Steps to reproduce:

  1. use a mobile phone with a browser on which you are not logged on on Commons, nor globally.
  2. go to Commons upload page through a Wiki Loves Monuments campaign link (I used one of the upload links from )
  3. follow the registration link, fill out user name, password and captcha, and submit

I end up on a page with the URL, titled Central user log in; all its content is an error message in red saying "No active login attempt is in progress for your session". There is no indication that I am logged in (the mobile menu even has a "Log in" option), but the local login is actually successful, after navigating back, the upload works. I am not logged in on Wikipedia though.

I can reproduce with these exact steps, but if I use the campaign link with a desktop browser, or use a mobile browser bug don't use the campaign link, the error does not appear and the registration works.
(I don't see any relation, but best still mention that some moths ago I opted in to the mobile beta on some Wikipedias; never on Commons though.)

I wasn't sure where this bug belongs (CentralAuth? MobileFrontend? UploadWizard? WLM?) so I'm filing it here and hope someone can move it along.

Setting severity to major because this is exactly the workflow which most potential new contributors who arrive from the ongoing WLM campaign will go through. After seeing the error once you are logged in and the next upload attempt would work, but that's not what the error message suggests, so people might get discouraged from trying.

Version: unspecified
Severity: major



Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 1:47 AM
bzimport set Reference to bz54123.
bzimport added a subscriber: Unknown Object (MLST).

Thanks for taking the time to report this!

Tentatively moving to MobileFrontend, but might also be a CentralLogin issue. :-/

This happened before shortly after the new CentralNotice login was enabled but I think Chris deployed a patch that might have fixed it. I guess not.

I'm not sure this is a problem in mobile - unless there were some changes to CentralAuth that were not communicated.

  • This bug has been marked as a duplicate of bug 51789 ***