Last modified: 2010-05-15 15:28:54 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 704 - LocalSettings.sample is misleading, obsolete
LocalSettings.sample is misleading, obsolete
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
1.3.x
All All
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-10-12 22:21 UTC by Brion Vibber
Modified: 2010-05-15 15:28 UTC (History)
0 users

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


Attachments

Description Brion Vibber 2004-10-12 22:21:43 UTC
Much of LocalSettings.sample is incorrect, obsolete, misleading, or downright
dangerous. It leads people astray when they try to do manual installs instead of
using the installer, and desperately needs to be updated.
Comment 1 JeLuF 2004-10-12 22:25:25 UTC
Should it be deleted instead? 
- Users don't need to generate LocalSettings.php from the sample
  any more, the config script generates a LocalSettings.php
- Duplicating data (DefaultSettings.php and LocalSettings.sample)
  is error-prone.
Comment 2 Brion Vibber 2004-10-12 22:27:26 UTC
Nothing should be duplicated between DefaultSettings.php and
LocalSettings.sample. There would, however, be duplication between the
generation code in config/index.php and LocalSettings.sample.
Comment 3 Brion Vibber 2004-10-13 20:14:53 UTC
I've gone ahead and removed it.

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


Navigation
Links