Last modified: 2014-08-05 02:16:08 UTC
This was an interesting comment from WhatamIdoing on bug 67826, so I thought I'd split it out for its own discussion. > Changing default user preferences means overriding the choices of > registered editors who actually want the feature (including thousands of > editors who voluntarily opted-in before MediaViewer was made avaialble > by default). > > It's too bad that MediaWiki doesn't have a good one-click system for > changing prefs, like a "Click here to enable X" button or pop-up. It'd be > so much easier than telling hundreds of users "Go to Special:Preferences, > click to this tab, scroll halfway down, find this item, tick the box, scroll > all the way down, save the page."
Thanks for filing this. I should note that what would be most functional is a system that lets me post a link (meaning a wikilink or a URL) that represents the command. I want anyone to be able to do this, not just the devs. Something like: "Click [[Special:ChangePreferences/scary-code-name-for-pref |here]] to toggle the tickbox for that pref" (or whatever format is necessary) would be great.
I don't understand this bug. We have plenty of one-click preference change systems, which alter the preferences via WebAPI. As one prominent example, see [[mw:ULS]]. I recommend filing a separate bug for each preference you want one such control for, specifying if it can also supplant the Special:Preferences checkbox (cf. bug 32811; keep bug 31882 in mind). Unless requirements for this request to be considered fulfilled are clarified, I propose RESOLVED WORKSFORME.
(In reply to Nemo from comment #2) > I don't understand this bug. We have plenty of one-click preference change > systems, which alter the preferences via WebAPI. As one prominent example, > see [[mw:ULS]]. I think you have mis-understood this request; it's asking for a consistent, MW-provided system to do this that works the same way for all preferences, and which each feature can trivially provide, not specific ad-hoc hacks like ULS etc. use which mean users have to learn them each time.
(In reply to James Forrester from comment #3) > I think you have mis-understood this request; it's asking for a consistent, > MW-provided system to do this that works the same way for all preferences The WebAPI works for all preferences. Can you clarify the requirements, as you're so sure about them?
I think I can: Tell me the exact wikitext I need to type to tell an editor at the English Wikipedia's Help Desk these things: "Click HERE to disable MediaViewer" "Click HERE to opt into the Beta Feature VisualEditor" "Click HERE to set your default image size to 300 px" "Click HERE to set your gender to female" "Click HERE to turn on Twinkle" "Click HERE to turn off Navpops" "Click HERE to set your default image size to 300 px" "Click HERE to set your gender to female"
(In reply to WhatamIdoing from comment #5) > I think I can: > > Tell me the exact wikitext I need to type to tell an editor at the English > Wikipedia's Help Desk these things: > > "Click HERE to disable MediaViewer" Don't write "click here". http://www.w3.org/QA/Tips/noClickHere […] > "Click HERE to set your gender to female" whatever ajax appears should be clear on privacy implications (value is published) and what exactly it's used for. (software strings not stats, etc) also, remember a11y, aria, etc.
