Template talk:SettingSummary

See also Project_talk:Forum.

Auto categorization
Based on Template:Extension, I've attempted to add some automatic categorization based on the "section" parameter but it needs support for comma-delimited sections and a way to pick out (parse) root words like "path", "database", "log", etc for inclusion in appropriate categories. I'm not the best parser function template scripter (whatever) so if anyone else would like to try it, go for it. -Eep² 16:12, 31 July 2007 (UTC)

How about Category:MediaWiki configuration settings available currently?
Adding such a category for all settings marked as still in use would probably help with finding settings that are marked that way incorrectly. Any objections? --Tbleher 12:28, 10 April 2008 (UTC)


 * Not if you can do it based on the current info being passed into the extension - in fact, we should have a 'Settings avilable in MediaWiki 1.x' category for all versions of MediaWiki, if possible. However, I'm not sure we can do that very easily.  Current list is do-able by just checking whether version_max is set, and is a good first step. --HappyDog 21:59, 31 July 2008 (UTC)


 * Just to clarify - the "Not" at the start of the above meant "No objections", and wasn't me making an objection... :-) --HappyDog 22:00, 31 July 2008 (UTC)

Add a location and default choice
Can someone add a location and default choice, so a person can easily find out where each one of these files are located at, and if the setting is already there by default? Rumpsenate 06:58, 17 July 2009 (UTC)
 * I agree, it is really hard for new users to know where this coding is found. I tried this here before: and gave up because of the complexity of the template. Adamtheclown 16:39, 13 February 2011 (UTC)

Extensions
This template supposes that configuration pages are created only for core features: is it allowed to create pages like Manual:$wgCheckUserForceSummary? If it's considered desirable to create such pages, we could perhaps make the section parameter check if there's an extension with that name and if so make a link to it and add the page to a category of configs for that extension, which could then be used on the extension page by Template:Extension to create an automatic list of configs with DynamicPageList or whatever (additional to manually filled lists in the body of the page). Nemo 08:28, 15 May 2011 (UTC)