# Project:Support desk

(Redirected from Support desk)
vde   Welcome to MediaWiki.org's Support desk, where you can ask MediaWiki questions!

There are also other places where to ask: IRC, mailing lists, Q&A etc.

## Post a new question

• MediaWiki
• PHP
• Database
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".
Start a new discussion

## Contents

Preventing spam012:34, 29 July 2015
[RESOLVED] Login Problem2712:08, 29 July 2015
Mediawiki install123:45, 28 July 2015
Starting conversion of LiquidThreads to Flow at mediawiki.org521:58, 28 July 2015
deleting user accounts from user list221:56, 28 July 2015
ElasticSearch extension not supported for CirrusSearch Extension downloaded from latest WIKI version 1.25.1514:33, 28 July 2015
Can't enable skin Vector.php510:29, 28 July 2015
Boot108:38, 28 July 2015
Create users by the admin did not work503:00, 28 July 2015
HTML markup in search results022:55, 27 July 2015
Search result without image as first.010:50, 27 July 2015
Log has not be created for today107:04, 27 July 2015
Editing footer links107:00, 27 July 2015
delete watchlisttoken406:48, 27 July 2015
Memory Leak? Memory running out.316:37, 26 July 2015
No links in the mobile view1214:50, 26 July 2015
Single Sign On - LDAP Extension821:21, 25 July 2015
Open source exam and quiz banks: An idea for a new wiki221:15, 25 July 2015
Cannot edit Common.css (or any MediaWiki:* page)115:09, 25 July 2015
 First page Previous page Next page Last page

## Preventing spam

What can I do to prevent spam? Somebody flooded Speedypedia with hundreds of new users and spam pages, probably because I posted in this website (www.mediawiki.org) a link to Speedypedia. How can we prevent such spam? I think it can be a bot or many bots who created this spam.

12:34, 29 July 2015

Media Wiki: 1.16.0 PHP: 5.2.12 MySQL: 5.0.67-log

Hey, I installed the wiki on a local server and configured all settings, but when i wanted to log in with my admin account, i got this error message: "There seems to be a problem with your login session; this action has been canceled as a precaution against session hijacking. Go back to the previous page, reload that page and then try again" I tried it again and again, but the result was equal, the same problem when I try to register a new account.

217.229.148.16102:08, 5 September 2010

I get the same error as thread starter..anyone pls can help us? Im using 1.16 + wamp.

203.115.201.2503:10, 13 September 2010

I'm having the same problem on the new clean installation when trying login or create a new account - any solution for it?..

93.172.250.6913:33, 8 November 2010

Probably something is wrong with your sessions; most likely PHP is not able to write to your sessions directory. Check your php.ini for the sessions directory and if PHP can write to those files.

-- Bryan (talk|commons)20:18, 11 November 2010

I got the same problem since soon, but not for all the installations on the same server (same version). Apparently the cookies are not good. It seems to come from the repertory of installation...

Lamidesbetes18:19, 12 November 2010

The connection to the database seems also be examined in this problem !

Lamidesbetes18:20, 12 November 2010

Looks like this has to do with setting a DNS CNAME.. it's only happening in IE8 for me... anyone have a fix?

63.241.252.223:34, 8 December 2010

I have the exact same issue now, fresh install. Anyone going to help with this??

174.113.146.18601:21, 25 March 2011

I found this solution:

go in your LocalSettings.php and at the end add the following code of line :

session_save_path("tmp");

Create a folder "tmp" in your wiki installation directory. give rights 777 (permissions)

Which worked for me.... also, check to make sure your disk has space

66.201.56.15018:07, 31 March 2011

This worked perfectly for me on a new install. Thanks, you're the first person to actually give a usable answer to those that don't have access to the server's PHP.ini files that I could find.

71.107.97.16404:52, 20 May 2011

Eh?! Don't put it in web-accessible directories, or your user accounts will be easily hackable.

Max Semenik05:12, 20 May 2011

This worked for me. I had this problem with MW 1.18.1 after I upgraded my hosting with godaddy and they changed my ip and dedicated ip. Mediawiki kept asking for cookies to be enabled (they were enabled) on all types of browsers and platforms including the iphone. Problem solved for now, even though I'd like to know if it will come back after an upgrade.

Mark21:13, 2 March 2012

what is meant by give rights 777?

83.244.233.13513:43, 27 June 2013

Same problem, can't even register or login as admin. Enough space is present.

83.142.211.13020:38, 21 September 2011

Looks like it was caused by using $wgMainCacheType two times in LocalSettings.php, now it's solved. Beznogim23:05, 1 October 2011 Hi also have the same problem where the IP address work perfectly yet the hostname fails. Would love some kind of explanation? 195.43.48.14009:56, 13 January 2012 The problem i'm experiencing just seems to be Internet Explorer only. Firefox and chrome are un-affected either by the hostname or IP address. Although I can login using IE6/IE8 with the IP address, Example: http://180.10.66.4/mediawiki The problem occurs using the hostname. Example: http://myserver/mediawiki If I goto the login page a 'sess_xxxx' in the /tmp folder is created. If I attempt to login, or just refresh the login page this seems to set brand new a sess_xxxx everytime. I have checked the apache logs and the client IP address is always the same regardless if i used the hostname of IP address. Its not a permission issue. I have also tried the following which was suggested with no success.$wgUseSquid = true;

Some suggestion would be greatly appreciated.

[SOLVED: My issue was caused by having an 'underscore' in the hostname example http://my_server - IE looks though it doesn't handle the underscore in the hostname as well as FF or Chrome does. Hope this helps anyone else using Mediawiki within their local intranet]

195.43.48.13813:48, 2 February 2012

had this error and the problem is that the facility lacked a standard memcached adding correct configuration

$wgSessionsInMemcached = true; # optional 200.153.233.25001:10, 20 March 2012 ... a little more resolved. This can also be a symptom of being short on disk space. 17:44, 23 August 2013 hi please upgrade to 1.19.0 or higher please 86.176.186.7719:12, 24 August 2013 Nothing would please me more (at least regarding mediawiki), but I require WYSIWYG working on a Semantic Form for my users, so I'm stuck with what I've got. Anyone similarly stuck can heed the diskspace problem as a possible reason for this problem. 19:37, 24 August 2013 I have the same issue right now. I am able to login as the administrator but any new account is not able to login. jjohnson19:13, 8 July 2015 Edited by 0 users. Last edit: 12:05, 29 July 2015 jjohnson: try this. Worked for me https://www.mediawiki.org/wiki/Thread:Project:Support_desk/Session_Hijacking_error_after_Update_1.19.14 satpatruni12:05, 29 July 2015 ## Mediawiki install I am trying to install this on CentOS 6.6. I install the software and it won't let me do the actual setup. I've tried many things suggested on the internet. When I try to run the update script, I get the following error: Function: DatabaseBase::sourceFile( /var/www/html/mediawiki-1.25.1/maintenance/interwiki.sql ) Error: 1054 Unknown column 'iw_api' in 'field list' (localhost) 64.239.147.13022:53, 28 July 2015 How are you doing the install? The recommended method is to use the tarball from releases.wikimedia.org, extract it and to go through installation - I usually do that with the webbrowser. When you now try again, before you start, please make sure that the database, which you are using, is actually empty. Should there be parts of the previous attempts (like some tables with some columns), remove them. The presence of such tables while you in fact want to do a new installation might confuse MediaWiki. 88.130.74.14723:45, 28 July 2015 ## Starting conversion of LiquidThreads to Flow at mediawiki.org LiquidThreads (LQT) has not been well-supported in a long time. Flow is in active development, and more real-world use-cases will help focus attention on the higher-priority features that are needed. To that end, LQT pages at mediawiki.org will start being converted to Flow in the next couple of weeks. This page, as the most active on mediawiki.org will be the last to be converted. Please see details, and an emphatic request for feedback, at Topic:Sdoatsbslsafx6lw. Much thanks. 07:28, 17 March 2015 Edited by 2 users. Last edit: 12:53, 5 June 2015 ## See also 11:43, 18 March 2015 Update: All pages except for this one, and VisualEditor/Feedback (which will be converted tonight), have been converted to Flow. This final page will be converted during the Wednesday workday. Thanks again to everyone who submitted bug reports, suggestions, constructive criticism, and feature requests. You might be interested to see the slides from the recent Wikimania presentation, File:User(s) Talk(ing) - Wikimania 2015.pdf, or to signup as a user research volunteer via http://wikimedia.org/research (they're currently doing some Flow research, but they cover many other aspects of the site in other months). As always, your comments and suggestions are welcome, encouraged, and needed, at Talk:Flow. 19:08, 28 July 2015 Thanks for the update! Keeping fingers crossed... :-) 88.130.74.14721:58, 28 July 2015 ## deleting user accounts from user list running MediaWiki 1.24.1 Three questions: 1.Is it possible to delete user accounts after creating an account, especially if you have sent a random password and cant acquire the password? 2.Is it possible to change the password after creating the account if you have sent a randomly generated password to their email address? 3.Also, if you've selected to send a user a random password to their email when creating the account is it possible to resend this account verification email to them if they accidentally deleted it. 18:39, 27 July 2015 "1.Is it possible to delete user accounts after creating an account, especially if you have sent a random password and cant acquire the password?" For help with Q1, you can try this Extension:UserMerge 21:06, 28 July 2015 2.Is it possible to change the password after creating the account if you have sent a randomly generated password to their email address? Yes, the user himself can simply log in with the random password; afterwards he can change it as he likes. Should the question be, if someone else can change the password, e.g. an admin, because the user for some reason cannot log in: The maintenance script changePassword.php can do that. 88.130.74.14721:55, 28 July 2015 ## ElasticSearch extension not supported for CirrusSearch Extension downloaded from latest WIKI version 1.25.1 Hi, I have upgraded WIKI for latest stable version 1.25.1. As MWSearch is obsolete extension so I have tried install CirrusSearch with ElasticSearch extention. But unfortunately I found below error message : " Warning: Invalid argument supplied for foreach() in /data/www/html/wikinew/extensions/Elastica/ElasticaConnection.php on line 78 Warning: Search backend error during fetching elasticsearch version after 2. Param host does not exist [Called from CirrusSearch\ElasticsearchIntermediary::failure in /data/www/html/wikinew/extensions/CirrusSearch/includes/ElasticsearchIntermediary.php at line 98] in /data/www/html/wikinew/includes/debug/MWDebug.php on line 300  content index...  Fetching Elasticsearch version...unable to determine, aborting.PHP Notice: Undefined index: version in /data/www/html/wikinew/extensions/CirrusSearch/includes/Maintenance/ConfigUtils.php on line 53  Notice: Undefined index: version in /data/www/html/wikinew/extensions/CirrusSearch/includes/Maintenance/ConfigUtils.php on line 53 ...Not supported! Only Elasticsearch 1.x is supported. Your version: . " Please help to resolve the above issue. Thanks in Adv. Sanjay 15:07, 15 July 2015 It seems you haven't a running Elasticsearch server, or you haven't configured it in the configuration variable$wgCirrusSearchServers.

11:10, 16 July 2015

Hi, I configured ElasticSearch Server name in variable $wgCirrusSearchServers. But when I run the script updateSearchIndexConfig.php under /extensions/CirrusSearch/maintenance and I got below Error/Warning message. content index... 1. PHP Warning: Invalid argument supplied for foreach() in /data/www/html/wikinew/extensions/Elastica/ElasticaConnection.php on line 78 2. Warning: Invalid argument supplied for foreach() in /data/www/html/wikinew/extensions/Elastica/ElasticaConnection.php on line 78 Fetching Elasticsearch version...unable to determine, aborting.PHP Notice: Undefined index: version in /data/www/html/wikinew/extensions/CirrusSearch/includes/Maintenance/ConfigUtils.php on line 53 3. Notice: Undefined index: version in /data/www/html/wikinew/extensions/CirrusSearch/includes/Maintenance/ConfigUtils.php on line 53 4. ...Not supported! 5. Only Elasticsearch 1.x is supported. Your version: . Please suggest for the solution since it says Only Elasticsearch 1.x is supported. Info: I have used 'CirrusSearch-REL1_25-ace4f80.tar.gz' & 'Elastica-REL1_25-eb56a6d.tar.gz' Thank You ! 12:22, 16 July 2015 After I configured in the configuration variable$wgCirrusSearchServers = array( 'elasticsearch0', 'elasticsearch1' );

Will you please let me know what a ElasticSearch Server is? Is it the same server where I hosted MediaWIKI 1.25.1 with the extensions 'CirrusSearch-REL1_25-ace4f80.tar.gz' & 'Elastica-REL1_25-eb56a6d.tar.gz' ?

Still I get the below Err Notice after running script 'updateSearchIndexConfig.php'

content index...

1. Fetching Elasticsearch version...unable to determine, aborting.PHP Notice: Undefined index: version in /data/www/html/wikinew/extensions/CirrusSearch/includes/Maintenance/ConfigUtils.php on line 53
2. Notice: Undefined index: version in /data/www/html/wikinew/extensions/CirrusSearch/includes/Maintenance/ConfigUtils.php on line 53
3. ...Not supported!
4. Only Elasticsearch 1.x is supported. Your version: .

Thank you !

13:49, 16 July 2015

You need to install elasticsearch on a server, it's a search service. You need to install it manually using the shell, it's normally not pre-installed. If it isn't installed, you can't use CirrusSearch (CirrusSearch itself doesn't work without elasticsearch).

06:02, 17 July 2015

I have successfully installed elasticsearch as a service using shell and I can able to access the service through the default port 9200 or by using curl.

Below is the set of configuration on my 'LocalSettings.php'

1. require_once( "$IP/extensions/Elastica/Elastica.php" ); 2. require_once( "$IP/extensions/CirrusSearch/CirrusSearch.php" );
3. #$wgDisableSearchUpdate = true; 4.$wgCirrusSearchServers = array( 'example.domain.com' );
5. $wgSearchType = 'CirrusSearch'; Still I have the below error while searching full text " ### An error has occurred while searching: We could not complete your search due to a temporary problem. Please try again later." Kindly provide a fix to the above ERROR ! Thanks in Adv. Sanjay 14:28, 28 July 2015 ## Can't enable skin Vector.php Hello, I've just installed MW 1.24.2 and tried to display the main page. Unfortunately there is an error saying: \mediawiki\skins\Vector/SkinVector.php): failed to open stream: No such file or directory in ...\mediawiki\includes\AutoLoader.php on line 1282 I checked in the LocalSettings.php if there is a problem with the path, but the default skin is set for "vector" and require_once "$IP/skins/Vector/Vector.php"; seems to be alright as well. The path of SkinVector.php seems to be correct and I couldn't find any typos or similar in the directory. I tried to download the skin separately and paste it into the skins directory, but then it says its only compatible with MW1.25+. I realized the error shows up with every skin I try to enable.

Any hints what might be the problem? I'm actually still thinking of a path problem, but I just don't know where to look after it.

MediaWiki: 1.24.2 PHP: 5.6.3 Database: MySQL 5.6.17

14:10, 27 July 2015

When you install MediaWiki, have you then taken a checkout from the Git versioning system? Doing so would be a way I could imagine you get this error.

In contrast, for normal end users, the recommended installation method is to use a tarball from here: http://releases.wikimedia.org/mediawiki/1.25/mediawiki-1.25.1.tar.gz. 1.25 btw. is the newest version - but a 1.24.2 tarball is available as well, if you want that. These tarballs contain everything you need, also the Vector skin in the correct version. :-)

88.130.109.19515:24, 27 July 2015

Hello and thank you for the reply! The reason why I don't use the 1.25 version is that I simply couldn't get the installation running - instead of getting the index.php to start from I always got a blank page, even tough I meet the requirements.

In the meantime I could fix the problem with the vector skin. In Vector.php on line 36 I replaced "$GLOBALS['wgAutoloadClasses']['SkinVector'] = __DIR__ . '/SkinVector.php';" with "$GLOBALS['wgAutoloadClasses']['SkinVector'] = 'skins/Vector/SkinVector.php';" and it seems to work fine now. :)

07:03, 28 July 2015

Regarding blank pages: Have you checked phab:T44205 (and maybe Manual:Errors_and_symptoms#You_see_a_Blank_Page)?

08:42, 28 July 2015

Yes I have checked the errors and symptoms of a blank page, but none of them seems to work for me. Because I have a blank page before the install I don't have a LocalSettings to modify, nor I have access to the php.ini since I'm on a hosted server. Regarding the DOM-XML problem I have checked with the phpInfo, but DOM-XML support is enabled as well as the other requirements.

09:56, 28 July 2015

Your change in Vector.php looks strange: __DIR__ is defined since PHP 5.3 at least. If you have PHP 5.6, this change should not be needed and if you have an old PHP version, you should get a different error ("Use of undefined constant __DIR__...").

For the blank page, you should check the error log or have your host tell you, what after such error is inside.

88.130.74.14710:28, 28 July 2015

## Boot

Hello.

I want to use some boot.

Where should I start?

I want to use boot f.e. to change categories on pages.

17:25, 27 July 2015

Which boot?

08:38, 28 July 2015

## Create users by the admin did not work

Hi, When creating a rather restricted Wiki (MediaWiki 1.25.1), I set:

$wgGroupPermissions['*']['createaccount'] = false;$wgGroupPermissions['*']['edit'] = false;

$wgMFShowRedLinksAnon = true;  That's it. 15:53, 23 July 2015 Thank you, it worked! what are these options? @Fried, the red link only didn't appear in the mobile view, not in the desktop view. 16:16, 23 July 2015 Redlinks are deactivated in mobile for performance reason and because the mobile editor wasn't a really good function to welcome users (especially newcomers). So we deactivated them and added these two options to activate them, e.g. if third party wikis want to use them. The first one is for logged in users (if set to true, logged in users always see redlinks, but logged out users doesn't) and the second one is for logged out users. Btw.: In the next release (1.26), redlinks will be enabled by default with a Click-to-action banner, if the user really wants to create a new page or not (redlinks are well known in the editing community, but a new user maybe doesn't know what it is, and the mobile editor doesn't have the nce warnings, like on desktop). 18:52, 23 July 2015 I have another problem - in the mobile view, if I search for an article which doesn't exist yet, I don't have a link to create this article (I only get this link in the desktop view). Is it also a feature we have to enable? 16:54, 23 July 2015 No, that is disabled by design. The mobile editor is a plain wikitext editor, which is a worse experience for newcomers. So, the eitor isn't really suitable for creating pages, too and we've disabled the create link for search. If you really want to enable it, you could do the following: .mw-search-createlink { display: inherit !important; }  • Save and reload the search page (maybe you have to clear your browser cache and maybe any other existing cache layers, depends on your setup) 18:49, 23 July 2015 OK, thank you! I'll try. 05:20, 24 July 2015 Thank you, it worked! 12:49, 24 July 2015 I have another question about Speedypedia. In Speedypedia one has to login or register to edit or create articles. When a user is not logged in in the mobile view, if he clicks on the "Edit" of any page he receives the message: "This page is protected to prevent vandalism." But the page is not protected, logged in users can edit it. I want the user to see the message "Would you like to edit this page? Login or register to edit articles.", unless the page is really protected (which is not the case in the page I tested). In the desktop view it's fine, if I'm not logged in I can view source, or create account or log in. But in the mobile view I receive this message if I try to edit the page. 12:55, 24 July 2015 Yeah, the problem is, that we never tested MobileFrontend with wikis, where you have to register to edit :) MF (=MobileFrontend) show this error message, whenever the page can not be edited by the current user, there is no configuration to handle this. Would you like to file a task in Phabricator for it? (Please note, that you're using REL1_25, so the WMF team(s) can decide what to do, normally we don't support other branches as master :)). 17:32, 24 July 2015 Task created, https://phabricator.wikimedia.org/T106943?workflow=create I don't understand what you mean REL1_25? If you want to know my version of MediaWiki, go to http://en.speedypedia.info/Special:Version (MediaWiki 1.25.1). 13:25, 25 July 2015 REL1_25 is the 1.25.X release branch in our git repository, it reflects the latest release of MediaWiki 1.25 :) 14:50, 26 July 2015 ## Single Sign On - LDAP Extension HELLO! Need some help here. Appreciate the help from all subject matter experts. So right now, I am trying to implement auto login to my mediawiki site. Currently, users are able to login to mediawiki using their windows account and password. Next, I would like to implement the auto-login function (without them entering their credentials). Below is my code. require_once( "$IP/extensions/LdapAuthentication/LdapAuthentication.php" );
require_once( "$IP/extensions/LdapAuthentication/LdapAutoAuthentication.php" ); //$wgAuth = new LdapAuthenticationPlugin(); #Commented out for autologin
$wgLDAPAutoAuthDomain = "MYDOMAIN"; //uncomment for auto login$wgDiff3 = "";

# Authenticate against Active Directory
$wgLDAPDomainNames = array( "MYDOMAIN" );$wgLDAPServerNames = array( "MYDOMAIN" => "MYDOMAINSERVER" );
$wgLDAPSearchStrings = array( "MYDOMAIN" => "USER-NAME@MYDOMAIN" );$wgLDAPEncryptionType = array( "MYDOMAIN" => "clear" );
$wgLDAPUseLocal = false;$wgMinimalPasswordLength = 1;

$wgLDAPBaseDNs = array( 'MYDOMAIN' => 'cn=Users,dc=domain,dc=com' );$wgLDAPSearchAttributes = array(
'MYDOMAIN' => 'sAMAccountName' );

$wgLDAPGroupUseFullDN = array( "MYDOMAIN"=>true );$wgLDAPBaseDNs = array( 'MYDOMAIN' => 'dc=MYDOMAIN,dc=example,dc=com' );
$wgLDAPSearchAttributes = array( 'MYDOMAIN' => 'sAMAccountName' );$wgLDAPGroupsUseMemberOf = array( "MYDOMAIN" => true );

//The objectclass of the groups we want to search for
$wgLDAPGroupObjectclass = array( "MYDOMAIN"=>"group" ); //The attribute used for group members$wgLDAPGroupAttribute = array( "MYDOMAIN"=>"member" );

//The naming attribute of the group
$wgLDAPGroupNameAttribute = array( "MYDOMAIN"=>"cn" );$userid = $_SERVER['REMOTE_USER'];$wgLDAPAutoAuthUsername = $userid; AutoAuthSetup();  Once I implemented the above, the domain name in my dropdownlist become empty and the username and password I entered denies my entry into the site although it is correct. Why is this happening? Please assist! Greatly appreciated it! THANKS ALL SO MUCH! Just to add on ,the server that I'm running is Apache 2.2 175.156.223.20916:17, 16 July 2015 You will have to install and configure kerberos for apache. Once you do that, you can use the [Extension:Auth_remoteuser Auth_remoteuser] extension to handle authentication. MarkAHershberger(talk)21:49, 18 July 2015 Hi Mark, I really appreciated your response! May I further clarify with you by installing and configuring kerbors for apache. Do you mean this website? (https://www.mediawiki.org/wiki/Extension:LDAP_Authentication/Kerberos_Configuration_Examples#Apache_configuration)? Or I have to install the mod_auth_kerb ? Another issue is so this LDAP extension can be used together with https://www.mediawiki.org/wiki/Extension:Auth_remoteuser to perform single sign on? Please advise. Thanks so much! mod_auth_kerb shouldn't be needed with IIS. That is what I would try first on Windows. MarkAHershberger(talk)21:21, 25 July 2015 Or are you advising me to use Auth_remoteuser extension instead of LDAP extension? Thanks! If you just need SSO authentication, then you should use Auth_remoteuser. MarkAHershberger(talk)21:18, 25 July 2015 I've tried to install and configure mod_auth_kerb on my Apache Server. But I am using Windows and the information I googled tends to be more towards Linux. Any help please? Thanks! 203.120.42.15101:06, 20 July 2015 If you are using IIS, SSO should already work, right? And then you would need something like Auth_remoteuser to get the logged in user. MarkAHershberger(talk)21:20, 25 July 2015 ## Open source exam and quiz banks: An idea for a new wiki I am a college professor of physics who is concerned about the high cost of education. In the technical fields (math and science) there in more than enough information on the internet-at-large for a self-learner to acquire more than 50% of a four year college degree. Although the wikis (e.g. Wikipedia and Wikiversity) are still underdeveloped compared to the internet-at-large, we are approaching the point where this knowledge will also be available in a convenient form that is open source. What is missing is a means by which a self-learner can easily document expertise in these subjects. Test banks are proprietary and carefully guarded by the publishers of textbooks. Wikiversity:Quizbank represents my effort to fill this need. The idea is to post these questions publicly and use software to first store the questions on a personal computer, and then to create wikitext that can be uploaded to a wiki and printed out as pdf files. I have already done that with a Matlab code that randomly selects questions and renders them in wikitext with pagebreaks such that all the multiple choice options are on the same page as the question. I am not a computer programmer and my software is hard to use. Here are some challenges that need to be addressed in the future, if this idea is to take off: 1. The Matlab software that retrieves and randomly selects questions from a copy of the quizbank that resides on a personal computer creates textfiles that must be uploaded to a wiki and then rendered as wikitext that can be printed. At the moment this is a public action. We need to arrange for these exams to be written and printed out in secret. I am able to do this because I am a Wikiversity custodian who can hide edits soon after they are made. And I make my exams many months in advance, and have only a small number of students. It is highly unlikely they would monitor my efforts and attempt to capture an exam as I write it. (Also, why cheat if the questions are already available?) 2. Teachers need to write test questions differently. One issue is the reluctance of students to ready anything. I tried to write tests based on Wikipedia articles, but found that all but the most dedicated students preferred to simply study the testbank. 1. One remedy is to select two or three questions from each exam and ask students to explain them in a short paragrah. ** Another remedy is to include written passages as part of the question. A large number of questions would be associated with that passage. As students prepare for the exams by reading the passage, they might find it easier to understand the passage than to attempt to memorize all the answers. 2. Another remedy is to require that students propose questions. The grading of such efforts is quite useful for any instructor who is a contributor to this bank. A related homework exercise for students is to verify that questions written for a specific Wikipedia article are still valid after the article has undergone a series of edits. 3. Another relatively trivial challenge is making the open source exam bank compatible with the conventional "secret" banks already available. The expectation is that colleges and universities would use the open source testbank as only a portion of the grade assessment and certification. There will always be room for those "secret" questions that only the instructor knows about. There is no great rush to solve these problems. I am still struggling to get a small version of the quizbank prepared for the four courses that I teach. Serious work needs to be performed after I have established that this is a good way to teach. But if anybody has any suggestions, please let me know. I am only vaguely aware of what sort of extensions can be written because I am not really a programmer. 16:00, 22 July 2015 Hi Guy, for that you write that you are not a programmer, you obviously have already made up big part of the software needed. You are writing much, but you do not have clear questions (yet) - so let me give you some thoughts: You say that certain questions (and their answers obviously) need to be secret. Hiding a revision from view is one way to do that, and it might not even be the worst. If you set up an own wiki for that stuff, kind of your own one, then you could fully control what is going on there. E.g. you could take people's read access away from certain pages. However, MediaWiki is not made for that and you cannot regard that as "secure". There will most likely always be a way around such limitation. Making the complete wiki private would however be possible (and secure if you ask me). If I understand correctly you or some co-workers will prepare tests. This should also continue that way - you do not want a computer algorithm to randomly pick questions for you. The Matlab software creates text files, which you are uploading to the wiki. Since I guess you know (or can control) the exact format, in which questions and answers are presented in these files, it should be rather easy to process them further. But if I understand you correctly, your software is already able to produce wikitext out of them. 88.130.105.13218:03, 22 July 2015 Thanks for responding. Let me give you two explanations and ask you a question: The explanations: 1. I chose a program that randomly selects from the quizbank because that was easier to write. It works OK for the time being. 2. The "secret" question bank I refer to are those proprietary banks that professors keep on their hard drives. These questions will always play a role in grade assessment. My question is about "secret" exams from a "public" (open source) question bank that need to be rendered by first uploading to Wikiversity, and then printing out as a pdf file. At the moment this is a "public" act that anybody can see. I don't need to do this now, but someday a larger open source organization (such as openStax College) might want to create tests "off-wiki", meaning that it is not necessary to go through Wikiversity or Wikipedia to render the wikitext into a pdf file. The solution would be to maintain a wikitext server with access that is by invitation only. I need to know if this feasible. I have noticed that two by-invitation-only wikis are at UC Davis with Chemwiki and the OpenStax College textbooks (affiliated with Rice University). These environments are much different than wikimedia "wikitext" syntax, using mathjax for equations, for example. Someday (maybe in a decade or so) I would like to see it possible for professors to render exams in wikitext in a way that nobody can see it until the day of the test. The wikitext would be created on personal computers, and ultimately rendered as pdf for paper-copy printout. If such "private" rendering of wikitext is feasible, I will continue to write exam questions on Wikiversity with the understanding that the technology will eventually catch up. On the other hand, if Wikimedia is adamantly against supporting any wiki that permits "secret" or "private" rendering of wikitext, and if a private server cannot be created that renders equivalent Wikipedia-style wikitext, then I need to think about working with the syntax used by OpenStax College or Chemwiki. I have contacted both organizations, and they are both giving me moral support. But neither organization seems to have the resources to create the software I hope will happen sometime in the future. Let me put the question simply with a hypothetical scenario: Suppose I were not an individual, but a consortium of dozens of professors who need a way to render wikitext in a fashion that nobody can see it until the day of the test. Would Wikimedia (or somebody else) be able to provide that support? I believe the answer is yes. 01:10, 23 July 2015 Suppose I were not an individual, but a consortium of dozens of professors who need a way to render wikitext in a fashion that nobody can see it until the day of the test. Would Wikimedia (or somebody else) be able to provide that support? It would be a SMOP, yes. You can set up your own copy of Wikiversity and and individual like myself or someone on the list of people on professional development and consulting would be able to help you. MarkAHershberger(talk)21:15, 25 July 2015 ## Cannot edit Common.css (or any MediaWiki:* page) I have a wiki up and running (www.makehumancommunity.org/wiki if you're interested). As far as I know everything works as expected, and as the admin I'm able to use all special pages and edit all common pages. Except the ones in the MediaWiki namespace. Specifically, I can't edit MediaWiki:Common.css. As soon as I navigate to that page, the interface looks as if I'm not logged in: The "log out" link changes to "log in", there is no edit tab etc. Now, I'm pretty sure I caused this, either with the phpbb authentication plugin or with the plain url settings in apache, the latter which look like this:  RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^/?wiki(/[^/]*)?$ /home/joepal/mediawiki/index.php [L]
RewriteRule ^/?wiki(/Special.*)?$/home/joepal/mediawiki/index.php [L] RewriteRule ^/?wiki(/MediaWiki.*)?$ /home/joepal/mediawiki/index.php [L]
Alias /wiki /home/joepal/mediawiki


... but, can anyone suggest where/how to start debug this?

14:28, 25 July 2015

Your RewriteRules look strange; they will do funny things and they are not standard. The alias directive will only work if used inside a server config or virtual host file - it will not work in .htaccess.