Page MenuHomePhabricator
Create Task
Maniphest T62748

BetaFeatures: "Automatically enable ..." not working
Closed, ResolvedPublic
Actions

Description

The "Automatically enable all new beta features" box isn't working.

When the BetaFeatures product was first released, there were 4 items available.[1] The additional item "Nearby Pages" has been added since then, but was not automatically enabled in our preferences.

  1. https://blog.wikimedia.org/2013/11/07/introducing-beta-features/

Filing on behalf of this thread: https://www.mediawiki.org/wiki/Talk:About_Beta_Features#.22Automatically_enable_all_new_beta_features.22_not_working_.28.3F.29

Version: unspecified
Severity: major
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=60747

Details

Reference
bz60748

Related Objects

Event Timeline

• bzimport raised the priority of this task from to High.Nov 22 2014, 3:04 AM
• bzimport added a project: BetaFeatures.
• bzimport set Reference to bz60748.
Quiddity created this task.Feb 2 2014, 8:02 PM
Quiddity added a comment.Feb 5 2014, 10:11 PM

Confirmed - the "New search" BetaFeature was recently added to the options at Enwiki, but not enabled for me, despite having "Automatically enable..." checked.

Quiddity added a comment.Feb 15 2014, 7:19 PM

Setting priority and upgrading importance. HTH.

gerritbot added a comment.Mar 4 2014, 6:00 AM

Change 116721 had a related patch set uploaded by Legoktm:
Fix typo when getting auto-enroll preference setting

https://gerrit.wikimedia.org/r/116721

Legoktm added a comment.Mar 4 2014, 6:02 AM

Patch fixes the typo which was making this not work.

However, the current code will only enable the new betafeatures when the user visits Special:Preferences, or whenever the 'GetPreferences' hook is run (API's action=options I think). Is that acceptable from a UX point of view?

Jdforrester-WMF added a comment.Mar 19 2014, 1:36 AM

(In reply to Kunal Mehta (Legoktm) from comment #4)

Patch fixes the typo which was making this not work.

Yay. Marking as FIXED.

However, the current code will only enable the new betafeatures when the
user visits Special:Preferences, or whenever the 'GetPreferences' hook is
run (API's action=options I think). Is that acceptable from a UX point of
view?

No. Created bug 62815 for that, which is distinct from this issue.

Legoktm added a comment.Mar 19 2014, 5:01 AM

(In reply to James Forrester from comment #5)

(In reply to Kunal Mehta (Legoktm) from comment #4)

Patch fixes the typo which was making this not work.

Yay. Marking as FIXED.

Patch hasn't been merged yet :/

gerritbot added a comment.Mar 20 2014, 1:52 AM

Change 116721 merged by jenkins-bot:
Fix typo when getting auto-enroll preference setting

https://gerrit.wikimedia.org/r/116721

Jdforrester-WMF added a comment.Mar 20 2014, 1:54 AM

(In reply to Kunal Mehta (Legoktm) from comment #6)

(In reply to James Forrester from comment #5)

(In reply to Kunal Mehta (Legoktm) from comment #4)

Patch fixes the typo which was making this not work.

Yay. Marking as FIXED.

Patch hasn't been merged yet :/

Sorry, thought I'd +2'ed but apparently not.

Quiddity mentioned this in T64815: BetaFeatures: "Automatically enable ..." should actually automatically enable, not require visiting Special:Preferences.Jun 14 2015, 7:12 PM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL