Last modified: 2014-08-08 16:06:19 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 50039 - Proposed changes to default settings (DefaultSettings.php) (tracking)
Proposed changes to default settings (DefaultSettings.php) (tracking)
Status: NEW
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: tracking
Depends on: 33836 33837 40621 40622 42594 51941 54948 69301 30401 35785 45020 45022 50040
Blocks: tracking redesign-sp-prefs 58223
  Show dependency treegraph
 
Reported: 2013-06-23 08:49 UTC by Krinkle
Modified: 2014-08-08 16:06 UTC (History)
9 users (show)

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


Attachments

Description Krinkle 2013-06-23 08:49:47 UTC

    
Comment 1 MZMcBride 2013-06-23 16:39:04 UTC
This bug tracks proposed changes to default settings.
Comment 2 Matthew Flaschen 2013-12-12 01:19:03 UTC
My understanding is this is intended to refer to everything in DefaultSettings.php, not just preferences.

Is that correct?  If so, we should make one specifically for default preferences.
Comment 3 Nemo 2013-12-12 07:32:05 UTC
(In reply to comment #2)
> Is that correct?  If so, we should make one specifically for default
> preferences.

Why?
Comment 4 Matthew Flaschen 2013-12-12 23:47:36 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > Is that correct?  If so, we should make one specifically for default
> > preferences.

Default user preferences ($wgDefaultUserOptions) are a distinct subset of what's in DefaultSettings.php.  They're end-user focused and they appear in a particular area of the interface, unless they're hidden.

I think this will make it a little easier to organize the bug relationships.
Comment 5 Nemo 2013-12-13 06:39:48 UTC
(In reply to comment #4)
> Default user preferences ($wgDefaultUserOptions) are a distinct subset of
> what's in DefaultSettings.php.  They're end-user focused and they appear in a
> particular area of the interface, unless they're hidden.

Most of the blockers I see here are quite end-user focused, I don't understand the distinction. It's also not very easy to apply, for instance $wgEnotifMinorEdits is not $wgDefaultUserOptions but it makes one more preference available so I would have no idea where to put it with your proposal. Competing tracking bugs with unclear scope are a nightmare.

> I think this will make it a little easier to organize the bug relationships.

Like?
Comment 6 Matthew Flaschen 2013-12-13 20:19:10 UTC
(In reply to comment #5)tle easier to organize the bug relationships.
> 
> Like?

For instance, if this is intended for everything in DefaultSettings.php, it does not really make sense to block bug 58223 ("Improvements to the layout and contents of Special:Preferences") (since e.g. $wgIncludeLegacyJavaScript has nothing to do with Special:Preferences).

But it would make sense for a bug about default user preferences to block bug 58223.
Comment 7 Nemo 2013-12-13 20:35:11 UTC
I don't see any reason for bug 58223 to be added as dependency of this or any other preferences tracking bug (bug 58229 was closed).

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


Navigation
Links