Extension talk:Configure

From mediawiki.org


I'm currently evaluating your extension -- nice work!

I do have a couple of suggestions if you're interested:

  1. First, I think it would be extremely helpful if the configuration pages had links from each configuration setting to the appropriate help page on the MediaWiki.org site. For example, the configuration setting for $wgEmergencyContact would display $wgEmergencyContact as a link to Manual:$wgEmergencyContact instead of just displaying the name of the setting.
  2. The "Access" section is cluttered and hard to navigate -- perhaps the Group Permissions needs to be pulled out and handled differently to reduce the clutter on this page. Skizzers has written a nice extension specific to $wgGroupPermissions that looks promising -- you might want to look at that. The currently display of the different Group Permissions sections makes it difficult to differentiate between the groups -- breaking this up with a horizonal line between the groups might help with that.

--Hoggwild5 09:49, 19 May 2008 (UTC)Reply[reply]

For the first, this might be a good idea.
The cells should already display a border to distinguish the groups. The "Groups" section might be moved to its own tab to reduce a bit "Access" part.
This can be implemented in the next days. But remember that this extensions is still not finished, just wait :) (this is also for what you wrote on my talk page.)
iAlex 14:23, 19 May 2008 (UTC)Reply[reply]
I'll be on the lookout for revisions :) --Hoggwild5 16:37, 19 May 2008 (UTC)Reply[reply]

Strange messages after install?[edit]

Hi, After I enable the Configure extension I get the following error:

Warning: fopen(/messages-<my_dbname>) [function.fopen]: failed to open stream: Permission denied in /ril/www/mw1.12/w/includes/MessageCache.php on line 115

I've never seen such a directory before. What should the root directory be for this directory; "/messages-<my_dbname>"? // RIL-sv 08:50, 28 May 2008 (UTC)Reply[reply]

MediaWiki 1.12.0
PHP       5.1.2 (apache2handler)
MySQL     5.0.22-Debian_0ubuntu6.06.9-log
You need to set $wgLocalMessageCache in Special:Configure. Unfortunately, even if you set it to false in Special:Configure, it looks for a directory called "false". Another bug with Configure is that it seems to be breaking things such as diff3 and/or ImageMagick. Haven't tested the newest SVN revision yet though, but I suppose they're still present...iAlex, got a solution for these? :-) --Sayuri 11:01, 28 May 2008 (UTC)Reply[reply]
Should be fixed in r35477. iAlex 11:41, 28 May 2008 (UTC)Reply[reply]
RIL-sv: Now when I downloaded r35477, and assigned $wgLocalMessageCache (from inside the Configure) it works. =) RIL-sv 12:41, 28 May 2008 (UTC)Reply[reply]

Bug: Enabling Configure causes transclusion to stop working[edit]

Enabling the Configure extension causes transclusion to stop working (MW 1.12final). As soon as I disable the extension I get back to normal transclusion functionality. Let me point out that this extension is really really a candy extension, so I will really really wait for next (quick) update. :) // Rolf Lampa, RIL-sv 19:28, 28 May 2008 (UTC)Reply[reply]

Sorry, but i could not reproduce that bug, be sure that $wgEnableScaryTranscluding (section Interwiki) is set to true. iAlex 19:40, 28 May 2008 (UTC)Reply[reply]
Hm, puzzling. $wgEnableScaryTranscluding made no difference, since it controls interwiki (only?). I had a number of values stored in MAIN_NS articles, retrieving them with this syntax; {{:Settings/CompanyName}}, but that doesn't work when Configure is enabled. If you have any hints about how to debug this, then please advice. RIL-sv 20:50, 28 May 2008 (UTC)Reply[reply]
Oh sorry, i thought it was about interwiki transclusion. Should be fixed in r35518. iAlex 21:03, 28 May 2008 (UTC)Reply[reply]

Path for the config file[edit]

Hi, I intend to install this and saw that I can set the path for the config file ($wgConfigureFilesPath). is there someway I can point to a directory "below the root"; something like:

$wgConfigureFilesPath = "../wconfig";

But where do I put the $IP .... ???

The idea is to pointto a place where you cant see files etc. - say, as I understand it http://www.yoursite.com woud point to a directory http, on your server, and you can actuall make other directories on parallel to http. Say I have a structure:

..\http\                http://www.mysite.com
..\http\wiki            http://www.mysite.com\wiki      (my wiki installed ) 
..\http\test\           http://www.yoursite.com\test    (test for a new site) 
..\http\snitz\           http://www.yoursite.com\sintiz (a forum) 
..\scripts\             various scripts
You don't need to use $IP, this is just a way to do it. But it would be a good idea to use a absolute path, such as $wgConfigureFilesPath = dirname( dirname( $IP ) ) . '/wconfig'; if I understand your configuration correctly. iAlex 15:51, 14 July 2008 (UTC)Reply[reply]

Sugestion - trouble[edit]

"If an admin changed the settings in a way that the wiki can't work anymore, you can simply drop the conf-now.ser file you'll find in $wgConfigureFilesPath directory. Then it will fall back to the default configuration that is in LocalSettings.php. It's why it's important to keep that file."

It would be nice if you preserve the "last working version of conf-now.ser" - perhaps on demmand, by date or some version count. Thus it would be possibel to "back-down" the changes made. Asset (And how do you add date/time here??)

Old versions (included the current version) are kept in the same directory as conf-now.ser. If you broke something, you can drop conf-now.ser, then go to Special:Configure and edit a version show at the top of the page (if possible not the broken one ;). iAlex 15:55, 14 July 2008 (UTC)Reply[reply]


How do you uninstall this? I tried taking it off localsettings.php but my wiki gets screwed up. -- 23:34, 28 September 2008 (UTC)Reply[reply]

If you remove the extension from LocalSettings.php, then any change you made in Special:Configure or Special:Extensions will be lost. You can use the writePHP.php maintenance script to write the settings as they were defined in the extension and put them in LocalSettings.php. iAlex 17:38, 29 September 2008 (UTC)Reply[reply]
I am on a shared host so I cannot run the script. What can I do?-- 02:45, 3 October 2008 (UTC)Reply[reply]
There isn't currently a web interface for this maintenance script. An idea would be to install MediaWiki and this extension on your local computer, then copy the configuration files (conf-*.ser) and run this script on your local computer. iAlex 07:42, 4 October 2008 (UTC)Reply[reply]

Assigning rights[edit]

  • How do I give myself "configure-all" right so I can access the Special:Configure Groups section? I tried without success adding the following to LocalSettings.php:
$wgConfigureEditRestrictions['wgGroupPermissions'] = array( 'configure-all' );
  • I assume this is where I can change $wgGroupPermissions options?
  • Special:Configure tells me the "Access" requires 'configure-all' right, but I find that I can already view and edit it. -- 23:15, 14 October 2008 (UTC)Reply[reply]
To grant yourself the 'configure-all' right, put
$wgGroupPermissions['bureaucrat']['configure-all'] = true;
in LocalSettings.php. iAlex 06:38, 15 October 2008 (UTC)Reply[reply]
Thanks for that. I copied that line exactly, and I still find that I can not display the "Group" section, receiving the message "You are not allowed to edit group settings". Other entries in my LocalSettings.php file, such as accessing extensions, seem to work fine. Any suggestions? -- 08:45, 15 October 2008 (UTC)Reply[reply]
Be sure that you put it after calling efConfigureSetup(), otherwise it'll be override if you already saved a configuration. iAlex 11:37, 15 October 2008 (UTC)Reply[reply]
Fantastic! Obvious when you know how. And what an incredible number of new options! Thanks. -- 13:52, 15 October 2008 (UTC)Reply[reply]

Old configuration versions[edit]

If I don't want older configuration versions, can I just delete the files conf-2008*.ser -- 13:54, 15 October 2008 (UTC)Reply[reply]

Yes. iAlex 14:10, 15 October 2008 (UTC)Reply[reply]

"No old version of the configuration available"[edit]

Hi, I have Installed this extention but dont get any of the options, all i get is a message with "No old version of the configuration available"... Any ideas? Im running the latest version of mediawiki Prom3th3an 12:11, 11 November 2008 (UTC)Reply[reply]

Problem with $wgConfigureEditableSettings = array();[edit]

Interner Fehler

Value for $wgDBtype setting is not in permitted (given: , permitted: MySQL, PostreSQL)


  1. 0 extensions/Configure/SpecialConfigure.php(23): ConfigurationPage->importFromRequest()
  2. 1 extensions/Configure/Configure.page.php(107): SpecialConfigure->doSubmit()
  3. 2 includes/SpecialPage.php(559): ConfigurationPage->execute(NULL)
  4. 3 includes/Wiki.php(229): SpecialPage::executePath(Object(Title))
  5. 4 includes/Wiki.php(59): MediaWiki->initializeSpecialCases(Object(Title), Object(OutputPage), Object(WebRequest))
  6. 5 index.php(116): MediaWiki->initialize(Object(Title), NULL, Object(OutputPage), Object(User), Object(WebRequest))
  7. 6 {main}

Hello This program is good and in normal use, all is right. But if I want to include "$wgConfigureEditableSettings = array();", the script answers the message above. Now, I include the variable $wgDBtype but nothing changes.

Can you help me?


my LocalSettings.php

$wgDBtype = "MySQL"; $wgUserrightsInterwikiDelimiter = '@'; require_once( "$IP/extensions/Configure/Configure.php" ); efConfigureSetup(); $wgConfigureEditableSettings = array(); $wgConfigureWikis = true;

Problem after installation[edit]

I installed the extension, and it is shown on the Special:Version page. But when I try to access the Specialpages, I get an error message. On Sepcial:Extensions and Special:Configure I get

Fatal error: Call to undefined method WebConfiguration::loadFullData() in G:\XAMPP\xampp\htdocs\wiki\extensions\Configure\Configure.obj.php on line 251

and on Special:ViewConfig I get

Fatal error: Call to undefined method OutputPage::addScriptClass() in G:\XAMPP\xampp\htdocs\wiki\extensions\Configure\Configure.page.php on line 902

What can I do to fix this?

--Yandrak4ever 12:39, 25 October 2009 (UTC)Reply[reply]

I use MW1.19 G:\xampp\htdocs\wiki\extensions\Configure\Configure.obj.php on line 31

30 public function initialise( $useCache = true ) {

31 parent::initialise();

That is is wrong? --DarkSide666 (talk) 12:55, 19 June 2012 (UTC)Reply[reply]

I'm getting the first error message, but not the second. When I go to :ViewConfig, it just shows:



This looks like an exciting extension to have! I hope a fix is found soon.


Extra Namespaces - can't set group permissions of custom namespaces[edit]

Hi. This is a fantastic extension :)
I have a question though. I have setup custom namespaces called Client1, Client2 etc. However, these do not then show up in the namespaces list in the Namespace protection section. So I can't set any permissions on these extra namespaces. Am I doing something wrong?
Thanks! [Mitchelln] 11:05 31st March 2010

Conflict with extension:ConfirmAccount[edit]

When using extensions configure (R 68345) and ConfirmAccount (R 68345) in conjunction with MW 1.16.0beta3 a conflict occurs that spells out an error like ConfirmAccount extension requires $wgEnableEmail set to true. The error is given out as a plain message. Although both in LocalSettings.php and in Special:Configure the variable $wgEnableEmail = true; has been set.

I guess either of them is not taken correctly taken into account during run time. Hence my question: if a variable has been customized in both settings, which is ultimately taken into account? --Stoettner 09:47, 21 June 2010 (UTC)Reply[reply]

Can't download trunk version[edit]

When I try to download the trunk from Special:ExtensionDistributor/Configure I get an error...

The error should be fixed. – Nikerabbit 19:48, 16 July 2010 (UTC)Reply[reply]
  • Me too! I get this error:
svn: Working copy '/mnt/upload6/private/ExtensionDistributor/mw-snapshot/trunk/extensions' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)

--Ejcaputo 07:33, 19 July 2010 (UTC)Reply[reply]

I managed to get it to work by using svn directly (under Windows 7 with cygwin installed):

C:\web\www\wiki\extensions>svn checkout http://svn.wikimedia.org/svnroot/mediawiki/trunk/extensions/Configure/

--Ejcaputo 16:17, 21 July 2010 (UTC)Reply[reply]

Configure screws up wiki after making a change and saving the wiki[edit]

I'm probably installing this wrong, but...

When I install it, it shows up in Special:Version and the extension seems to work fine. But when I change a setting and save the configuration, the wiki becomes a bit screwed up.

Images stop working, the changes we made to the sidebar disappear, and under the search bar, the search button changes to a link that says "Advanced search". There are probably other changes, but I haven't found them. However, the extension does make the specified change to the wiki. It's as if Configure is forgetting much of the settings, which is probably what's happening.

While it may seem that it could be quickly fixed after some searching, what it does is a bit distressing.

The changes were reverted after I removed the conf-* files from the directory "serialized".

This is on a 1.16.0beta1, the LocalSettings.php file was previously (and still is) used to make configuration changes, and I placed the following lines almost at the bottom, right above Maintenance Shell:

require_once( "$IP/extensions/Configure/Configure.php" );
$wgConfigureEditableSettings = array();

Anyone know why this happens? It would be nice to be able to use the extension, for other administrators who don't have access to LocalSettings.php. 21:19, 21 July 2010 (UTC)Reply[reply]

Missing SVN Version tags[edit]

The Extension doesnt have version tags (like in http://svn.wikimedia.org/viewvc/mediawiki/tags/extensions/SemanticMediaWiki/ ) in SVN ... it would be great for version management at installations to have these tags .. would it be possible to set a tag at the last release revision and provide tags in the future? --RScheiber 22:10, 14 September 2010 (UTC)Reply[reply]

The configuration could not be saved[edit]

The changes I made in the special page cannot be saved. It gives me the above error. Bennylin 09:22, 22 November 2010 (UTC)Reply[reply]

Nvm. Got it. Changed the owner of /serialized/conf-now.php. Bennylin 09:27, 22 November 2010 (UTC)Reply[reply]

Read current Localsettings?[edit]

Should this extension read my current security settings? I change dozens of rights in LocalSettings but when I go to the special page for Configure none of my LocalSettings seem to be in effect. I can't imagine this extension not reading a wikis LocalSettings but I don't see where to make that happen. Do I need to run an sql file to set up any tables? Or some update file to pre-load my current settings?

Does this extension overwrite my LocalSettings.php? Or just ignore it and use unknown special files instead? ~ 05:13, 23 March 2011 (UTC)

Settings you change via the web interface are stored in files or database depending on your configuration (see Extension:Configure#Handler comparison). If you use files, modifications are applied when you call efConfigureSetup();. This mean you can enforce the value of some settings by setting them after that call. If you use the database to store your settings, modifications are applied after executing LocalSettings.php unless you set $wgConfigureAllowDeferSetup to false in which case it's the same as with files. iAlex 11:54, 23 March 2011 (UTC)Reply[reply]
  • That helps clarify things a lot more. I can picture the flow now. Thanks. To be even clearer though, this extension DOES NOT read LocalSettings at all right? I'll need to get all my LocalSettings input into Configure manually. If I want to be certain my current security is maintained I will call efConfigure last (set for using files) until I am sure all my settings are entered. Perhaps some note on the extension page warning people (thicker people like me at least) that their current LocalSettings are not read by Configure and could be over written thereby removing existing security settings? Or something better phrased. Thanks again for the quick reply. ~ 14:45, 23 March 2011 (UTC)


Love this extension! Downloaded for 1.16.

Trying to save settings results in exception thrown immediately. 'Value not valid for setting' message, on settings I never changed (and have never set). Examined code, noticedt this happens for settings that are bound to an array of values. Fix for this issue:


if ( !array_key_exists( $val, $type ) ) {

Change to:

if ( strlen($val) && !array_key_exists( $val, $type ) ) {

Only checks if the value of the setting is in the array of valid values if the setting is set in the first place. 05:22, 4 May 2011 (UTC)

Boolean with default true questoin[edit]

If a setting has a default of true, and I want to set it to false, how is this done in the configure extension? 05:40, 4 May 2011 (UTC)

Automated reading of LocalSettings.php[edit]

Unless you are installing a new MW server, installing this extension is complicated since it overwrites many of the settings of LocalSettings.php in unexpected ways. I would prefer to see a third option for *all* settings: unset or default or as set by LocalSettings.php

Some indication of whether a variable has been set in LocalSettings.php would be desirable at a minimum.

$wgHashedSharedUploadDirectory was turned off by this extension which caused all of my images to disappear. Luckily, I had some familiarity of where to search to find how to get this setting back to normal. Most users will just uninstall. 05:57, 4 May 2011 (UTC)

Relative paths[edit]

The files in the serialized directory should not use the full path to store its data. It should use the variable $IP or something. If the installation is moved, this will cause the wiki to break. --17:52, 13 May 2011 (UTC)

Using the Extension[edit]

Hi I'm just curious, I have installed it, added the two lines of code in PHP local settings, and I am able to see the Configure extensions page. Basically I can see my installed Extensions - out of 3, I have Admin Links and Vote, Forums does not show up.

I'm wondering how I can use this, as when I click or uncheck the check box use this extension for vote, it always shows the extension anyway in special pages and I can use it regardless of the user account but obviously not as an anonymous user. Even for an admin user account, or a basic tester account I create, if I tick or untick use this extension, it still shows and appears to make no difference. Am I missing something here? I don't exactly understand how and why this occurs. I was under the impression if you deselect Use this Extension, it would not show up in the special pages at all? as if it's not even installed.

Can someone please shed a bit of light on this for me. Much appreciated, TV

Problem after upgrade to 1.18[edit]

The extension isn't working after upgrading to MW 1.18. The problem is a white screen without any error. after removing the lines:

require_once( "$IP/extensions/Configure/Configure.php" ); efConfigureSetup();

the site is working properly.

Reinstalling the extension didn't solve the problem.

Please read Manual:How to debug#PHP errors and enable error reporting to see the error you have; I cannot help you otherwise. iAlex 16:06, 15 January 2012 (UTC)Reply[reply]


Why is this page flagged so edits to this page require approval? A change in this page is stuck on review! --Captaincollect1970 (talk) 09:31, 29 May 2012 (UTC)Reply[reply]

How do I change $wgFavIcon?[edit]

I found where to change the site logo - but I don't see anywhere to change the favicon.

Changing settings in Group Permissions isn't working, no matter what I change it resets to default. I have called efConfigureSetup() after everything in LocalSettings nothing happens. I have tried t his also with no changes to LocalSettings other than adding Configure extension.


I marked it as such because of the supported MediaWiki version section in the infobox. 00:14, 8 February 2017 (UTC)Reply[reply]

Yeah, I also believe that this assessment is realistic. Cheers --[[kgh]] (talk) 08:40, 8 February 2017 (UTC)Reply[reply]