# Project:Support desk

(Redirected from Project:Support)
vde   This page is for questions relating to the MediaWiki software.

Welcome to MediaWiki.org's Support desk, the central on-wiki place to ask MediaWiki questions!

The greater purpose of this page is to make our Manual and other available help so good that you do not have to come here to ask questions, or making them easier to find.

There are other ways for of communication as well (IRC, mailing lists etc.). Read more here.

## §Post a new question

1. To help us answer your questions, please always indicate which versions you are using:
• MediaWiki (reported by your wiki's Special:Version page)
• PHP (likewise)
• Database (likewise, e.g. MySQL 5.5)
2. Please include the URL of your wiki unless you absolutely can't. It's often a lot easier for us to identify the source of the problem if we can look for ourselves.
3. To start a new thread, click "Start a new discussion".

## §Archiving topics

Topics are automatically archived when they have been inactive for three weeks. If a question you have asked is approaching this limit and still has not been answered, please 'bump' it to prevent it being archived. However do not 'bump' for other reasons.

Start a new discussion

## Contents

Redirect Categories311:40, 28 February 2015
[RESOLVED] Mediawiki internal error: Another module has already been registered as oojs (ResourceLoader.php)200:57, 28 February 2015
[RESOLVED] Enable Anonymous File Upload (v. 1.24.1)322:38, 27 February 2015
[RESOLVED] Updating from 1.17 not working416:09, 27 February 2015
[RESOLVED] permission for editing text/creating page for normal users that will require authorization by editors413:36, 27 February 2015
Hilfe zur extension:eventcalendar 313:32, 27 February 2015
External link opens in new window on request but not always :-(012:56, 27 February 2015
Watchlist not sending emails310:50, 27 February 2015
Can't login. No error messages. 1009:50, 27 February 2015
Offline upgrade?209:05, 27 February 2015
Creating a custom search bar018:29, 26 February 2015
[RESOLVED] How to find a certain URL within wikitext?217:24, 26 February 2015
How to reenable the sitenotice315:02, 26 February 2015
Problem with Bureaucrat permissions412:51, 26 February 2015
Chart not showing the up-to date data in Pchart4mw111:04, 26 February 2015
find text for section {{Q2A:module=homepage}} 110:56, 26 February 2015
How to add a script excerpt to the header of each page to introduce MathJax (without SimpleMathJax extension)110:53, 26 February 2015
[RESOLVED] Line breaks in php522:22, 25 February 2015
[RESOLVED] Content Not Showing In Wiki2614:05, 25 February 2015
Show 'Last Updated by' and 'Last updated at' values in my theme413:42, 25 February 2015
 First page Previous page Next page Last page

## Redirect Categories

It is no problem to redirect a category. The problem is, that the pagename of the redirected category will not appear under the target category. Is there any way to solve this problem?

11:05, 28 February 2015

A category redirect only makes sense for cases, in which both, the redirect and its target, are semantically identical. In this case, you should in fact not use the category, which you want to redirect. Instead, use the actual target in your pages!

88.130.78.3711:17, 28 February 2015

I operate a Wiki in 3 languages in one, with given categories. At the moment the problem for English or French speaking users is, that they must use the German words for the categories. E.g. one category is Teerose, the English word is Tea and it is difficult for an English user to spell Teerose or other more complicated words.

11:27, 28 February 2015

If the users do not understand the category names, which I guess basically only are single words, in how far does it then help the users to have categories pointing to pages they don't understand? I think the problem is not the mixture of languages in category names, but that different languages are mixed at all. If you have different languages for the content, it is only logical to also have different languages for the categories.

88.130.78.3711:40, 28 February 2015

## [RESOLVED] Mediawiki internal error: Another module has already been registered as oojs (ResourceLoader.php)

I just tried to upgrade Mediawiki from 1.22 to 1.24.1.

Everything seemed to go smoothly till I tried loading the site and got an error about oojs already being registered. Did the requisite googling and didn't find anything that seemed to fit or provide options to fix. I've attached the output below. Things to look at?

MediaWiki internal error.

Original exception: [f164743a] /wiki/index.php?title=Main_Page Exception from line 279 of /usr/local/var/www/mediawiki-1.24.1/includes/resourceloader/ResourceLoader.php: ResourceLoader duplicate registration error. Another module has already been registered as oojs Backtrace:

2. 1 /usr/local/var/www/mediawiki-1.24.1/includes/OutputPage.php(2730): ResourceLoader->__construct(GlobalVarConfig)
3. 2 /usr/local/var/www/mediawiki-1.24.1/includes/OutputPage.php(526): OutputPage->getResourceLoader()
4. 3 /usr/local/var/www/mediawiki-1.24.1/includes/OutputPage.php(552): OutputPage->filterModules(array, string)
5. 4 /usr/local/var/www/mediawiki-1.24.1/includes/OutputPage.php(624): OutputPage->getModules(boolean, string, string)
6. 5 /usr/local/var/www/mediawiki-1.24.1/includes/OutputPage.php(3039): OutputPage->getModuleMessages(boolean, string)
7. 6 /usr/local/var/www/mediawiki-1.24.1/includes/OutputPage.php(3114): OutputPage->getScriptsForBottomQueue(boolean)
8. 7 /usr/local/var/www/mediawiki-1.24.1/includes/skins/Skin.php(618): OutputPage->getBottomScripts()
9. 8 /usr/local/var/www/mediawiki-1.24.1/includes/skins/SkinTemplate.php(490): Skin->bottomScripts()
10. 9 /usr/local/var/www/mediawiki-1.24.1/includes/skins/SkinTemplate.php(274): SkinTemplate->prepareQuickTemplate(OutputPage)
11. 10 /usr/local/var/www/mediawiki-1.24.1/includes/OutputPage.php(2226): SkinTemplate->outputPage()
12. 11 /usr/local/var/www/mediawiki-1.24.1/includes/MediaWiki.php(594): OutputPage->output()
13. 12 /usr/local/var/www/mediawiki-1.24.1/includes/MediaWiki.php(435): MediaWiki->main()
14. 13 /usr/local/var/www/mediawiki-1.24.1/index.php(46): MediaWiki->run()
15. 14 {main}

Exception caught inside exception handler: [23e4344c] /wiki/index.php?title=Main_Page Exception from line 279 of /usr/local/var/www/mediawiki-1.24.1/includes/resourceloader/ResourceLoader.php: ResourceLoader duplicate registration error. Another module has already been registered as oojs Backtrace:

2. 1 /usr/local/var/www/mediawiki-1.24.1/includes/OutputPage.php(2730): ResourceLoader->__construct(GlobalVarConfig)
3. 2 /usr/local/var/www/mediawiki-1.24.1/includes/OutputPage.php(526): OutputPage->getResourceLoader()
4. 3 /usr/local/var/www/mediawiki-1.24.1/includes/OutputPage.php(552): OutputPage->filterModules(array, string)
5. 4 /usr/local/var/www/mediawiki-1.24.1/includes/OutputPage.php(624): OutputPage->getModules(boolean, string, string)
6. 5 /usr/local/var/www/mediawiki-1.24.1/includes/OutputPage.php(3039): OutputPage->getModuleMessages(boolean, string)
7. 6 /usr/local/var/www/mediawiki-1.24.1/includes/OutputPage.php(3114): OutputPage->getScriptsForBottomQueue(boolean)
8. 7 /usr/local/var/www/mediawiki-1.24.1/includes/skins/Skin.php(618): OutputPage->getBottomScripts()
9. 8 /usr/local/var/www/mediawiki-1.24.1/includes/skins/SkinTemplate.php(490): Skin->bottomScripts()
10. 9 /usr/local/var/www/mediawiki-1.24.1/includes/skins/SkinTemplate.php(274): SkinTemplate->prepareQuickTemplate(OutputPage)
11. 10 /usr/local/var/www/mediawiki-1.24.1/includes/OutputPage.php(2226): SkinTemplate->outputPage()
12. 11 /usr/local/var/www/mediawiki-1.24.1/includes/exception/MWException.php(195): OutputPage->output()
13. 12 /usr/local/var/www/mediawiki-1.24.1/includes/exception/MWException.php(238): MWException->reportHTML()
14. 13 /usr/local/var/www/mediawiki-1.24.1/includes/exception/MWExceptionHandler.php(45): MWException->report()
15. 14 /usr/local/var/www/mediawiki-1.24.1/includes/exception/MWExceptionHandler.php(141): MWExceptionHandler::report(MWException)
16. 15 /usr/local/var/www/mediawiki-1.24.1/includes/MediaWiki.php(449): MWExceptionHandler::handle(MWException)
17. 16 /usr/local/var/www/mediawiki-1.24.1/index.php(46): MediaWiki->run()
18. 17 {main}
216.106.102.1216:53, 27 February 2015

I don't know of the exact internals, but this error means that the OOjs module has tried to be registered multiple times. I would guess that this can happen, if you use old extensions or an old skin, which are not properly updated for MediaWiki 1.24. Maybe you still have files from the old MediaWiki version in the way, which are now causing trouble. In this case updating them should solve the issue.

In order to investigate, which extension might cause this, you might try disabling all extensions and then enabling them one by one until you get the error again!

88.130.78.3722:52, 27 February 2015

Thanks, that was it. I need do do a serious cleanup of the extensions directory instead of just bulk copying during the backup. But, I'm up and running now.

Thanks again.

216.106.102.1200:56, 28 February 2015

## [RESOLVED] Enable Anonymous File Upload (v. 1.24.1)

Edited by 0 users.
Last edit: 16:20, 27 February 2015

I'm working on a script to convert our old wiki to WikiMedia and it would be really handy to enable anonymous file uploads for it. Is it possible to enable anonymous file uploads? I've found examples of how to restrict logged in users to upload files to only certain groups, but nothing to enable them.

204.209.209.13016:20, 27 February 2015

Set

$wgGroupPermissions['*']['upload'] = true;$wgGroupPermissions['*']['reupload'] = true;


in LocalSettings.php. If your wiki is publicly available, this will enable spammers to not only write about their junk, but to also upload photos of it. Just as a thought...

88.130.78.3716:37, 27 February 2015

Thanks! The wiki isn't publicly available and I plan on disabling anonymous uploads after the script has uploaded the documents from our old wiki.

204.209.209.13021:34, 27 February 2015

That's fine!

88.130.78.3722:37, 27 February 2015

## [RESOLVED] Updating from 1.17 not working

My version 1.17 installation recently went into a state where the content of the wiki does not appear, although everythin else does, including menus and the code for the content can be viewed by selecting edit, even if the same content is not displayed when browsing the wiki normally. It is not clear to me what caused this. I don't think I did anything so I suspect an upgrade of some software on the server by the hosting company, the php version or something like that. I am trying to fix this and any help would be greatly appreciated.

It was suggested online that this situation might be amended by upgrading the wiki, but I am having problems with the update process. I have backed everything up and added a sha1 column to table revisions as suggested in the documentation. I copied my old LocalSettings.php to a directory with version 1.24. However, when I run the update script on the server, "php maintenance/update.php", the script exits right away without producing any output. The update process has not been completed successfully as I get a database error if I try to swap the old/new directories and open the new version.

I also tried using the web update. On the second page of the wizard, it seems like the system is supposed to detect my existing wiki, but nothing comes up and I cannot continue.

Because of the lack of error messages, I am unsure what to do. Any ideas?

2A00:C88:4000:A00C:FC9B:3121:3D91:D6F312:30, 24 February 2015

Hi!

The symptoms that the content, although displayed in editing mode, does not show up in the normal pages, is usually caused by an upgrade of the PCRE package on the server. A MediaWiki upgrade will in fact fix this.

You should enable error reporting in PHP and activate error display in MediaWiki to get more information about what is going wrong. See how to debug for more information!

88.130.67.20012:41, 24 February 2015

Thanks! I turned on the error reporting and I am now getting the following output. There is indeed no "ScopedCallback.php" in "includes/libs". I should note that I just downloaded and extracted a fresh copy of the version 1.24.1 tar archive. Did I make some mistake in that process?

Warning: require(/home/linguist/public_html/wiki//includes/libs/ScopedCallback.php) [function.require]: failed to open stream: No such file or directory in /home/linguist/public_html/wikixx/includes/AutoLoader.php on line 1282

Fatal error: require() [function.require]: Failed opening required '/home/linguist/public_html/wiki//includes/libs/ScopedCallback.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/linguist/public_html/wikixx/includes/AutoLoader.php on line 1282

2A00:C88:4000:A00C:FC9B:3121:3D91:D6F313:00, 24 February 2015

MediaWiki 1.24.1 does contain a includes/libs/ScopedCallback.php file - the version I downloaded back in December 2014 did and the tarball offered for download right now does as well. Can you please double check, why that file is missing for you? Did all files from the new tarball get extracted correctly? This file should be there!

88.130.67.20015:04, 24 February 2015

Okay, I figured this out. The file was there, my mistake. The issue arose because I had the old wiki directory selected in the LocalSettings.php file and the file was not found under the old path. The issue went away when I edited the settings file. Thanks for the help!

89.160.129.20015:08, 27 February 2015

## [RESOLVED] permission for editing text/creating page for normal users that will require authorization by editors

the title might not be so clear i tried my best, but the idea is that when a user(contributor) wants to add text or create a page there will be an authorization stage that will require the editors to agree to the information that the user wants to add and if the editor doesnt authorize the text it wont add it

is this possible in anyway?

11:10, 25 February 2015

Extension:FlaggedRevs is for you.

15:37, 26 February 2015

Or use Extension:Approved Revs.

15:44, 26 February 2015

thank you so much!!!

15:56, 26 February 2015

one thing i cant seem to understand i dont see how do i set who can approve the pages and how to set user groups that needs approval on pages? cant find any explanation on it any where please help

84.95.206.22913:36, 27 February 2015

## Hilfe zur extension:eventcalendar

Hallo, ich versuche es einfachheitshalber zunächst mal auf deutsch: also, ich würde gerne die extension eventcalendar nutzen, komme aber einfach nicht mit der Einrichtung klar. Das SemanticBundle habe ich bereits installiert und in der Localsettings.php eingebunden. Aber wie binde ich nun den Kalender in meine seite ein und wie erschaffe ich neue Termine??? Würde mich riesig über eine einfache Erklärung freuen!!! Danke

92.225.81.22111:16, 26 February 2015
12:26, 26 February 2015

yes it is!! And I don´t understand how to make it work in my Wiki??? PLEAAAAAAAAAAAAAAAAAAAAAAAAASSSSSSSSSSSSEEEEEEEEEEEE Can you explain me??!!!

92.225.81.22115:10, 26 February 2015

> PLEAAAAAAAAAAAAAAAAAAAAAAAAASSSSSSSSSSSSEEEEEEEEEEEE

??? What is the intention to do that?

> yes it is!!

Then you should ask there :)

13:32, 27 February 2015

## External link opens in new window on request but not always :-(

Hello All,

I installed the LaunchExternal extension in my Wiki, and now any URL in a text opens in a new window, BUT the one to MediaWiki. How come ?

Example:

In this page http://didiermorandi.fr/AAT/inventaire/index.php/Table_des_mati%C3%A8res link to Forum de discussions et d'informations does open in a new window, but in page http://didiermorandi.fr/AAT/inventaire/index.php/Accueil (4th §), link to MediaWiki does not :-(

Config is

MediaWiki 1.24.1
PHP       5.5.11 (apache2handler)
MySQL     5.0.67-log



Thanks.

12:56, 27 February 2015

## Watchlist not sending emails

Hello,

I have been working with mediawiki these last few days trying to get notifications to work properly. To give some background Watchlist DID work back last year until sometime around april when it quit sending emails. The project was put off until now and I am tasked with getting notifications to work again.

Initially we were getting zero notifications period, now after adding $wgUsersNotifiedOnAllChanges = array( 'user1', 'user2' ); and disabling SELinux I am able to get notified on all changes. Unfortunately the watchlist still appears to be broken. Here is part of my LocalSettings.php$wgEnableEmail = true; $wgEnableUserEmail = true;$wgEmergencyContact = "wiki@company.net"; $wgPasswordSender = "wiki@company.net";$wgEnotifUserTalk = false; # UPO $wgEnotifWatchlist = true; # UPO$wgEmailAuthentication = false; $wgUsersNotifiedOnAllChanges = array( 'user1', 'user2' );$wgSMTP = array(

'host'     => "wh.company.net",
'IDHost'   => "wh.company.net",
'port'     => 25,
'auth'     => false,


);

I've tried changing $wgEmailAuthentication = false; and in both cases true or false I don't get any watchlist updates however the notify on all changes still works. Sorry for not being able to give more information, my big question is what other places might there be in mediawiki where a setting is preventing the sending of watchlist updates? Additionally is there any reason to think that my current version may be the problem? Product Version MediaWiki 1.21.2 PHP 5.3.3 (apache2handler) MySQL 5.1.73 Thanks for the help, Regards, Jacob 64.85.160.400:15, 19 February 2015 Did you check the apache logs, whether they contain something? There is also a new version of the SMW-Watchlist available via composer. 08:23, 19 February 2015 Yeah I have looked at the logs and no couldn't find an explanation in them. I think the best course of action will be installing SMW-Watchlist and see if that works better. Thanks for the help. 64.85.160.403:13, 27 February 2015 You could try to enable the debug log as explained in Manual:How to debug, and perform an action that should trigger the email, then see the debug log to any message related to the email function. You could also check the Manual:Job queue to see how many jobs are on the table. I don't remember if email notifications are handled by the job queue, but if they are and there's some problem on it, it could be also the problem. 10:50, 27 February 2015 ## Can't login. No error messages. Edited by author. Last edit: 00:24, 10 April 2013 I try to login and it just refreshes the login page with no error and not logged in. I can view the contents of my wiki but unable to edit since login doesn't work. Is there a folder/database permission which could have changed which would do this? Also, when installing a test wiki i get a blank screen when clicking the initial setup button. The PHP log says: PHP Warning: require(.../wiki/languages/Language.php): failed to open stream: Permission denied in ...wiki/includes/AutoLoader.php on line 1146 mediawiki 1.19.2 php 5.4 MySql 5.5.3 05:58, 9 April 2013 Try to do perform a search through the search bar and let us know if the search works, and if it fails see if the search terms appear already in the search bar of the search results page. 09:45, 10 April 2013 thanks for looking! search bar seems to work fine. However i notice that all the wikimarkup and html is included in the search results. edit: oh.. Just realised that is normal after googling it. btw my test wiki is 1.20.3 if that makes any difference. 12:02, 10 April 2013 Well, that's really strange. Something that may cause this is the loss of session information. Make sure PHP session configuration variables are set correctly to allow session storage. For example, upload a php file with this contents to the server: <?php session_start(); if (!isset($_SESSION['count'])) {
$_SESSION['count'] = 0; } else {$_SESSION['count']++;
}

print($_SESSION['count']);  Browse that page and it should print you a number increasing every time you reload the page. If not, something is wrongly configured in the php.ini. 20:18, 10 April 2013 The test worked: +1 each refresh. Not sure if this is relevant, but a web developer recently installed joomla in a different directory. Also they wiped my htaccess.txt file. I deactivated the htaccess.txt file in the joomla directory just in case with no improvement. 05:04, 11 April 2013 Check the value of Manual:Configuration settings#Cookies. If any of those variables are defined, try to comment them, since in general their default value is already OK. If your wiki is public a link to it may help. 09:31, 12 April 2013 ## Offline upgrade? One option appears to be missing from Manual:Upgrading and maybe it is for a good reason, but I'll have to ask first. If you don't have shell access to the server that hosts your relatively large site, you may still be able to download the files and database that belong to it. If that's the case, I would expect that you can replicate the site on your local desktop computer or whatever (e.g. using a stack that includes PHP, etc.) and do the upgrade from the command line; then, if the upgrade has completed successfully, you can upload the database and files to replace the old ones and the job is done. Would this imaginary scenario work, or did I just paint a rosy picture that underestimates the complexity of the process? Does it matter, for instance, that the local computer runs Windows, while the remote server is Unix-based, or that the solution stack of your local computer is not as full as the remote installation? If it does work though, it would be worth considering as an alternative to the web-based updater (which may not work) or the rather more expensive solution of migrating your site (which not everyone can afford) and so as a way out of an impasse. Cavila (MW 1.22, MySQL 5.5.37-0, Php 5.4.4-14 squeeze, SMW 1.9.2, SF 2.7)14:43, 26 February 2015 > If you don't have shell access [...] and the job is done. Yes, that basiclly is possible. What you are speaking about, technically is a move to your other, local PC. See Manual:Moving_a_wiki for more information on server moves! Then what you do is an upgrade as detailed on Upgrade and then another move back to the original server. I have not tested a Windows <-> Unix move myself, but I would expect the following: • Configured file system paths have to be adjusted (e.g. in LocalSettings.php, but possibly also at other places). • All caches have to be cleared. • If the domain name/URL of the server is different both times, that will have to be adjusted as well (e.g. in$wgServer).
• Additionally, the objectcache DB table has to be cleared - otherwise there will be a flood of "file not found" errors.
• It might be possible that you have to adjust some paths somewhere deep inside the DB; I do not know if and where, but that it would be e.g. is the reason for why you have to TRUNCATE the objectcache table.

Usually it won't be reasonable to go down all that way moving a wiki just to do an upgrade. The few bucks you save for not paying a more expensive hosting will easily be spent for the working time needed to do the server moves.

88.130.112.15116:09, 26 February 2015

Thanks for this!

By the sound of it, it is not unfeasible per se, but the move back and forth might be rather cumbersome and not entirely 'idiot-proof', with a number of issues that could easily become a right pain. Localsettings.php can easily be adjusted, but some of the other, database-related things you mention regarding 'objectcache' and others listed at Manual:Moving a wiki are well outside my 'comfort zone'.

On the other hand, the alternative is more than 'a few bucks' extra. I might give it a try and see how things work out (or not).

Cavila (MW 1.22, MySQL 5.5.37-0, Php 5.4.4-14 squeeze, SMW 1.9.2, SF 2.7)09:05, 27 February 2015

## Creating a custom search bar

Hi all. Is there any way to code a Search Bar that will search pages within a specific category?
I have pages categorized as "Photos" and I would like a search bar that would search through those pages rather than the whole Wiki.
Any help would be appreciated.

Product Version: MediaWiki 1.19.7
PHP 5.3.15 (cgi-fcgi)
MySQL 5.1.63-community-log

198.103.104.1118:29, 26 February 2015

## [RESOLVED] How to find a certain URL within wikitext?

How can I find certain URLs within my articles via the search?

I suppose that the search engine only finds URLs that are not included in [ ].

[1] for example finds the article. Whereas [2] doesn't find the URL - probably because it is included in [ ].

Any way to find an URL regardless of the surrounding wikitext?

11:26, 14 February 2015

Try insource:"URL" [1]

18:30, 14 February 2015

Thanks a lot!
Just figured out that this only works in MW 1.24 (see Help:CirrusSearch#insource:).
Another reason to upgrade :)

17:20, 26 February 2015

## How to reenable the sitenotice

I accidentally click the close button on a site, how can I enable it again?--一個正常人 (talk) 17:51, 25 February 2015 (UTC)

17:51, 25 February 2015

IIrc MediaWiki is somehow saving the state of this notice. Do you see it again, if you remove all cookies related to the according site?

If not, you can still view the page MediaWiki:Sitenotice inside the according wiki, which will contain the text of the site notice. See Manual:Interface/Sitenotice for more information on the pages, which are used for site notices.

88.130.65.22218:18, 25 February 2015

Each time when I need to see the text or find the link in the sitenotice, I need to view the page MediaWiki:Sitenotice, it's really inconvenient.--一個正常人 (talk) 13:12, 26 February 2015 (UTC)

13:12, 26 February 2015

Have you tried my other tip?

88.130.112.15115:02, 26 February 2015

## Problem with Bureaucrat permissions

Edited by 3 users.
Last edit: 13:44, 25 February 2015

Editing my original message to include new stuff.
I looked at several Manual: pages including the articles on:

MediaWiki version: 1.24.1
PHP Version: 5.5.21 (cgi-fcgi)
SQLite Version: 3.7.9 with full-text search support

I have a site set up that I'm using to test MediaWiki.
I have the newest stable version of MediaWiki set up, using a mysql database. (I think it's my sql. whatever the local one is where it doesn't do a host, all you need is db name and write access.)

It took me a while today to figure out how to use Lockdown and I got that working (wanted it so that sysop's couldn't read a certain namespace; there are other administrative groups that work exclusively in this namespace.)

I have the following code in my LocalSettings.php file, and I'm trying to make it so that the default bureaucrat group can only add people to the default groups, and not remove anyone from bureaucrat.
I don't want bureaucrat's to be able to add to this other group of 'exclusive administrators', which will be handled by another exclusive group, or stewards.

unset( $wgGroupsAddToSelf['bureaucrat'] ); unset($wgGroupsRemoveFromSelf['bureaucrat'] );
unset( $wgAddGroups['bureaucrat'] ); unset($wgRemoveGroups['bureaucrat'] );
$wgGroupsAddToSelf['bureaucrat'] = array( 'bot', 'administrator', 'bureaucrat', 'oversight', 'oversightadmin', 'developer', 'interfaceeditor' );$wgGroupsRemoveFromSelf['bureaucrat'] = true;
$wgAddGroups['bureaucrat'] = array( 'bot', 'administrator', 'bureaucrat', 'oversight', 'oversightadmin', 'developer', 'interfaceeditor' );$wgRemoveGroups['bureaucrat'] = array( 'bot', 'administrator', 'oversight', 'oversightadmin', 'developer', 'interfaceeditor' );


Edit: Feel free to reply, or link to the reply, on my non-existant talk page. Please create it :3
Edit 2: If needed, I can copy paste my entire LocalSettings.php file.

00:10, 25 February 2015

Okay, you explained what do you want to do and what have you done so far. But what problem have you encountered?

$wgGroupsRemoveFromSelf doesn't follow the usage described on the manual. 10:55, 25 February 2015 I want bureaucrats to be able to add themselves in some groups. According to the GroupsRemoveFromSelf#Changes in 1.14 article, it says I'm using that config properly to make it so bureaucrats to remove themselves from any groups. This is what I want. In the line above that, I want bureaucrats to only be able to add themselves to the groups 'bot' 'administrator' 'bureaucrat' 'oversight' 'oversightadmin' 'developer' and 'interfaceeditor' On my Special:UserRights page, users in bureaucrat can still add themselves to any group. Should 'administrator' be replaced with 'sysop' ? If so, any chance this is causing an issue for the entire line? Or is there something wrong with my 'unset' commands? I saw those somewhere, and they're close to the end of my LocalSettings.php file.. 20:21, 25 February 2015 > I want bureaucrats to be able to add themselves in some groups. This is possible with the default configuration. Is that not working? It should work. One note also because you mentioned the Lockdown extension: Note that MediaWiki is not made for access control! There will most likely alway be a way around whatever retriction you have set up. If you need per-page or per-usergroup permissions, then you should not use MediaWiki. Use a CMS instead! 88.130.65.22222:22, 25 February 2015 I don't need my site totally secure, I understand content posted on my site will be accessible by anyone who actually tries hard enough. I just don't want some areas easily accessible. The "adding themselves in some groups" isn't working. Even though I have the following code near the end of my LocalSettings.php file, bureaucrats can still add themselves to ALL groups (including those not listed in the array).$wgGroupsAddToSelf['bureaucrat'] = array( 'bot', 'administrator', 'bureaucrat', 'oversight', 'oversightadmin', 'developer', 'interfaceeditor' );

12:51, 26 February 2015

## Chart not showing the up-to date data in Pchart4mw

Mediawiki version 1.24

Creating a line chart with data from SQL Server Using ExternalData and ODBCDatabase. charts are working fine but while refreshing the page chart is not showing the up-to date data showing old data only.

while clicking the show preview button we can able to see the up-to date chart.

{{#get_db_data: db=mydb |from=User_Connections t |data=CaptureDate=t.CaptureDate,UserConnections=t.value}}

{{#pLines:ymin=0|ymax=500|axiscolor=888888|colorscheme=purpleblue|cubic|filled|angle=90|legend|plots|data= ,UserConnections {{#for_external_table: {{{CaptureDate}}},{{{UserConnections}}}

}} }}

and disable the below line in pChart4mw.php $wgPChart4mwCacheEnabled= true; kindly do the needful -- Ragu 09:51, 26 February 2015 11:04, 26 February 2015 ## find text for section {{Q2A:module=homepage}} I am working on a site for a client and on one of the pages Template:Q2A:module=homepage is embedded in the page and a block of text is rendered from it. I want to edit the content of that section but I can't find where the text is coming from. Template:Q2A:module=homepage does not exits. On other pages there are Template:Q2A:module=dogs and Template:Q2A:module=cats are embedded and also showing text. How can I debug this? What other options are there for the types of page you can put within {{ }} with this structure Q2A:module= Thanks 20:13, 25 February 2015 Below the edit area there's a section named "templates used on this page" (you may need to hit preview first if you're editing a section). It will give you links to the template. However, it could be that the wiki uses a custom extension and Q2A is a sort of parser function that gets the contents from an external source. In that case, you won't find it in the templates used on this page section. 10:56, 26 February 2015 ## How to add a script excerpt to the header of each page to introduce MathJax (without SimpleMathJax extension) Edited by another user. Last edit: 10:48, 26 February 2015 How to add a <script> excerpt to the header of each page to introduce MathJax (without SimpleMathJax extension) I've tried editing the MediaWiki:Common.js file, adding <script type="text/javascript" src="http://cdn.mathjax.org/mathjax/latest/MathJax.js"> </script>, as I would add to the header of a normal HTML document. This doesn't work, however, perhaps because the javascript isn't inserted verbatim (as far as I can tell, on inspection of the the source of pages afterwards). I've been going through the php files that seem relevant (OutputPage.php, Html.php, WebStart.php) and attempting to have them directly write this code snippet to the header, but I'm new to PHP and my dogged, misguided attempts garner me little success. I tried the SimpleMathJax extension initially, but including it in LocalSettings.php only crashed the site (though other extensions I've manually added work correctly). I'd rather use the MathJax formatting ($$...$$, \(...)\), so would be more grateful for suggestions on how to get MathJax into the header than mend the SimpleMathJax extension. Any help at all is highly appreciated, of course! 121.223.31.12610:55, 24 February 2015 Add this to MediaWiki:Common.js $(function() {
importScriptURI('http://cdn.mathjax.org/mathjax/latest/MathJax.js');
});

10:53, 26 February 2015

## [RESOLVED] Line breaks in php

Hi how can I do line breaks in php because I am trying to do line breaks for global in github.com/paladox/Metrolook/blob/test/MetrolookTemplate.php

151.229.250.23312:14, 21 February 2015

The question is unrelated to MediaWiki. See http://php.net/manual/

13:04, 22 February 2015

I tried searching on google and none show you how to do it.

86.135.166.20413:33, 22 February 2015

Ok.

10:13, 23 February 2015

Really? Example:

function wtf( $really ) { global$wgWTFOne, $wgWTFTwo,$wgWTFThree;
global $wgWTFFour,$wgWTFFive, $wgWTFSix; }  -> function wtf($really ) {
global $wgWTFOne,$wgWTFTwo, $wgWTFThree,$wgWTFFour, $wgWTFFive,$wgWTFSix;
}


(sorry for my terms)

17:28, 23 February 2015

Thankyou.

151.229.250.23320:16, 25 February 2015

## [RESOLVED] Content Not Showing In Wiki

I have an old version of Mediawiki (1.16.4) which I use for local history research. When I tried to access it today, none of the content would display. Regardless of which page I navigate to, the Mediawiki code can be seen in edit mode but does not render when I exit that mode. Any suggestions, please?

15:02, 21 November 2014

Hi!

This most likely is this problem: Manual:Errors_and_symptoms#All_pages_have_no_content.2C_but_when_editing_a_page_the_wiki_text_is_there.

Most likely a MediaWiki upgrade should solve it!

88.130.80.15215:32, 21 November 2014

Thanks. The reason I'm still using 1.16.4 is my lack of knowledge regarding upgrading. Is it 'easy'? Which version can I move too with minimal hassle? How do I protect the wiki text during upgrade? There are around 2.5m words, hundreds of images and thousands of hours invested in the project so far.

15:41, 21 November 2014

Just seen reference to upgrading to a minimum of 1.22.1 but I'd welcome advice on queries posted previously. I'm a bit out of my depth!

15:46, 21 November 2014

Upgrading is not really difficult. When you do it for the first time, you will need some time to do it, but it should be feasible.

Some notes:

Make sure you have a working backup: All files of the MediaWiki installation and the database!

Your wiki text, images and so on will all stay as they are during upgrade; anyway, I can only repeat that: Make sure, that your backup is working! Try extracting it and see, if a wiki, which you have set up from the backup, works!

Finally: Which versions of PHP and of MySQL are you using? The page Special:Version in your wiki will tell...

88.130.80.15218:22, 21 November 2014

In Special:Version, it is like all the other pages, blank wiki page template with no content. However, my server cPanel shows that it is using PHP version 5.4.35 and MySQL version 5.5.40-cll.

Although you're making it sound like a 'small' job, I would prefer that the upgrade be carried out by someone who knows what they are doing. Is there anyone on here who would consider taking on the task for a few bob?

My prime concern is for the wiki content which is very 'valuable'. I simply cannot risk it.

20:18, 21 November 2014

On the subject of upgrading, I have access to Softaculous in my server's cPanel. Would you recommend using a Softaculous script to uggrade from MediaWiki 1.16.4 to either 1.19.21 or 1.23.6 both options being available to me. I ask because I am aware that there have been some issues with using Softaculous to update various packages.

21:00, 21 November 2014

Well, 1.16 is not supported anymore and has security bugs. You should upgrade to one of the supported versions.

As a last resort, apply the patch provided in bug 58640 in your code.

18:28, 21 November 2014

The bug fix seems to relate to MediaWiki 1.22.0 and not 1.16.4 which I've been using?

20:19, 21 November 2014

## Show 'Last Updated by' and 'Last updated at' values in my theme

Hi, I am developing a new theme for mediawiki. I want to show the values of 'Last Updated by' and 'Last updated at' values in my theme. I could not find any doc related to these. Can you please help me to find this?

18:41, 24 February 2015

https://en.wikipedia.org/wiki/Help:Magic_words , Revision data.

19:51, 24 February 2015

20:19, 24 February 2015

If you develope a skin you can use BaseTemplate::getFooterLinks() to get an array of footer links including ['info']['lastmod'], or, if you just need the last modified data, you can use \$this->data[ 'lastmod' ];.

13:10, 25 February 2015

Doesn't Vector show these dates? At least one of them? Just take the code from there!

88.130.65.22213:42, 25 February 2015

 First page Previous page Next page Last page