Last modified: 2014-08-20 19:42:51 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T69133, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 67133 - $wgDefaultUserOptions['rememberpassword'] = 1 stopped working in 1.23
$wgDefaultUserOptions['rememberpassword'] = 1 stopped working in 1.23
Status: PATCH_TO_REVIEW
Product: MediaWiki
Classification: Unclassified
User login and signup (Other open bugs)
1.23.0
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: code-update-regression
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-26 13:45 UTC by Jeremy
Modified: 2014-08-20 19:42 UTC (History)
9 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Jeremy 2014-06-26 13:45:34 UTC
Upon upgrading from 1.21 to 1.23, I noticed that the (now labeled) "Keep me logged in" checkbox is no longer checked by default. 

I saw that in bug 52342 the "Remember my login" user preference was removed since it was redundant with the login page. Would that preference be needed in order for "$wgDefaultUserOptions['rememberpassword'] = 1" to work in LocalSettings?
Comment 1 Gerrit Notification Bot 2014-07-03 17:19:27 UTC
Change 143908 had a related patch set uploaded by Rohan013:
$wgDefaultUserOptions['rememberpassword'] now sets the value of "keep me logged in" checkbox

https://gerrit.wikimedia.org/r/143908
Comment 2 Tyler Romeo 2014-07-03 17:27:40 UTC
This is due to the user preference being removed in https://gerrit.wikimedia.org/r/94614.

What does everybody think about how to handle this?
Comment 3 Jeremy 2014-07-03 17:46:32 UTC
Patch applied and confirmed working in REL1_23. Whether this is the final solution or not I'll leave to the experts, but this will work as a workaround for now. 

Thanks Rohan!
Comment 4 Rohan Rawat 2014-07-03 18:18:47 UTC
I understand that the user preference was removed.

But why can't we repurpose this variable for the login form ? After all, it is still doing the same job it was designed for, just for a different component
Comment 5 Tyler Romeo 2014-07-03 18:23:03 UTC
IMO I think this is functionality that we should have, so that leaves us with a couple of options:

1) Make a new global, backport it to 1.23, and indicate in the release notes how to work around the removed preference.

2) Restore the user preference, but set it to an immutable preference type so that users cannot change it and it exists only as a default.

I really hate adding new globals, but at the same time it doesn't really feel right adding a user preference that is not actually a user preference. However, option 2 does allow seamless upgrading and means admins will not experience any change in functionality.
Comment 6 Kunal Mehta (Legoktm) 2014-08-20 19:42:51 UTC
Removing backport flag since there's nothing to backport yet...

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links