Category:MediaWiki - Revision history

Admin: /* Permissions */

2019-03-30T19:27:45Z

Permissions

← Older revision		Revision as of 19:27, 30 March 2019
Line 4:		Line 4:

	=Permissions=		=Permissions=

			==Setting Permissions for LocalSettings.php file==

			your mediawiki instance is configured using a localsettings.php file. this file usually contains sensitive info like DB password or MW secret key. what permissions should be set for this file?

			If the owner of the file is the same as the web server user, set permissions to 600.

			If the owner of the file is different from the web server user, set permissions to 640.

			MW manual page on LocalSettings.php: https://www.mediawiki.org/wiki/Manual:LocalSettings.php

			{{Quote\|
			The webserver user must have access to this file. If this is the same account, who is the owner of the file, then you can set permissions to 600. Sometimes, the webserver user is not the file owner, but they are in the owner's UNIX user group. In this case, permissions of 640 should be fine. For improved security you should narrow permissions down as far as possible.
			}}

	==Changing Images Folder Permissions==		==Changing Images Folder Permissions==

Admin: /* Math */

2019-03-09T21:25:25Z

Math

← Older revision		Revision as of 21:25, 9 March 2019
Line 93:		Line 93:

	==Math==		==Math==

			Also see [[MathTest]] for how to WRITE math formulas.

	I was having a lot of trouble getting the MediaWiki Math extension to work. I kept seeing the following error:		I was having a lot of trouble getting the MediaWiki Math extension to work. I kept seeing the following error:

Admin: /* Changing Namespace Permissions */

2017-05-01T01:30:17Z

Changing Namespace Permissions

← Older revision		Revision as of 01:30, 1 May 2017
Line 46:		Line 46:
	Look for the piece of code that looks like this:		Look for the piece of code that looks like this:

	<~~source lang="php"~~>		<pre>
	if( $wgUser->isAllowed( 'read' ) ) {		if( $wgUser->isAllowed( 'read' ) ) {
	return true;		return true;
	} else {		} else {
	global $wgWhitelistRead;		global $wgWhitelistRead;
	</~~source~~>		</pre>

	This piece of code checks if a user has global "read" permissions, and if so, it proceeds to load the page.		This piece of code checks if a user has global "read" permissions, and if so, it proceeds to load the page.
Line 59:		Line 59:
	Add a check for the new "read_secret" permission:		Add a check for the new "read_secret" permission:

	<~~source lang="php"~~>		<pre>
	if( $this->getNamespace() == 100 ) {		if( $this->getNamespace() == 100 ) {
	//this is "Secret" namespace		//this is "Secret" namespace
Line 68:		Line 68:
	} else {		} else {
	global $wgWhitelistRead;		global $wgWhitelistRead;
	</~~source~~>		</pre>

	===Step 3: Create a group with the new permission===		===Step 3: Create a group with the new permission===
Line 74:		Line 74:
	The next step is to create a MediaWiki group that will have the just-created permission, "read_secret". I'll name this group something really creative like "secret":		The next step is to create a MediaWiki group that will have the just-created permission, "read_secret". I'll name this group something really creative like "secret":

	<~~source lang="php"~~>		<pre>
	$wgGroupPermissions['secret']['read_secret'] = true;		$wgGroupPermissions['secret']['read_secret'] = true;
	</~~source~~>		</pre>

	===Step 4: Add users to new group===		===Step 4: Add users to new group===

Admin: /* Step 1: Select Protected Namespace */

2017-05-01T01:29:50Z

Step 1: Select Protected Namespace

← Older revision		Revision as of 01:29, 1 May 2017
Line 34:		Line 34:
	Add the new namespace to <code>LocalSettings.php</code> with the following code:		Add the new namespace to <code>LocalSettings.php</code> with the following code:

	<~~source lang="php"~~>		<pre>
	$wgExtraNamespaces = array( 100 => "Secret");		$wgExtraNamespaces = array( 100 => "Secret");
	</~~source~~>		</pre>

	If you want to create more namespaces, you can number them 101, 102, 103, etc., or really, whatever you feel like. (Just keep the numbers big so they don't interfere with existing namespaces.)		If you want to create more namespaces, you can number them 101, 102, 103, etc., or really, whatever you feel like. (Just keep the numbers big so they don't interfere with existing namespaces.)

Admin: /* Changing Namespace Permissions */

2017-05-01T01:29:33Z

Changing Namespace Permissions

← Older revision		Revision as of 01:29, 1 May 2017
Line 4:		Line 4:

	=Permissions=		=Permissions=

			==Changing Images Folder Permissions==

			After a recent upgrade to the latest MediaWiki, I was encountering an issue trying to upload files. I saw this error message when attempting to upload an image:

			<pre>
			MediaWiki: Could not open lock file for <temporary path to image file>
			</pre>

			The problem was permissions on the <code>images/</code> directory in the MediaWiki installation. This problem was easy to solve: make the www user the owner of the images folder.

			<pre>
			$ cd /path/to/mediawiki/installation/
			$ chown -R www:www images/
			</pre>

			That solved the problem.

	==Changing Namespace Permissions==		==Changing Namespace Permissions==

Admin: /* Math */

2016-08-14T17:09:01Z

Math

← Older revision		Revision as of 17:09, 14 August 2016
Line 85:		Line 85:
	Here's how I resolved it:		Here's how I resolved it:

	'''Step 1: Install all the ~~crap~~ you need'''		'''Step 1: Install all the stuff you need'''

	<pre>		<pre>

Admin: /* Errors about MIME types */

2016-08-14T17:08:00Z

Errors about MIME types

← Older revision		Revision as of 17:08, 14 August 2016
Line 233:		Line 233:
	==Errors about MIME types==		==Errors about MIME types==

	{{mbox\|		{{mbox\|text=
	The short version:		The short version:

Admin: /* Errors about MIME types */

2016-08-14T17:07:49Z

Errors about MIME types

← Older revision		Revision as of 17:07, 14 August 2016
Line 232:		Line 232:

	==Errors about MIME types==		==Errors about MIME types==

			{{mbox\|
			The short version:

			Modifying <code>includes/mime.types</code> should fix the issue.
			}}

	When trying to upload an unusual file format/type, I saw an error message (regardless of whether I had checked "Ignore all warnings" checkbox or not) that said:		When trying to upload an unusual file format/type, I saw an error message (regardless of whether I had checked "Ignore all warnings" checkbox or not) that said:
Line 255:		Line 261:
	chemical/x-mdl-stlfile stl		chemical/x-mdl-stlfile stl
	</pre>		</pre>

			Modifying <code>includes/mime.types</code> fixed the issue.

	=Debugging=		=Debugging=

Admin: /* Errors */

2016-08-14T17:07:02Z

Errors

@@ Line 215: / Line 215: @@
 =Errors=
 I got some errors after transitioning to nginx+Apache instead of Apache alone, whenever I tried uploading an image I would see this:
@@ Line 229: / Line 231: @@
 </pre>
 =Debugging=

Admin: /* Bots */

2016-06-11T17:40:44Z

Bots

← Older revision		Revision as of 17:40, 11 June 2016
Line 256:		Line 256:
	=Bots=		=Bots=

	Mediawiki has an API: https://www.mediawiki.org/wiki/API:Client_code		Mediawiki has an API: https://www.mediawiki.org/wiki/API:Client_code

	~~This enables~~ interfacing with ~~an MW wiki using~~ Python ~~code, which enables you to write~~ bots.		pywikibot is a Python library providing bindings for interfacing with mediawiki, enabling Python bots: https://github.com/wikimedia/pywikibot-core

	Project idea: use the API to extract data about the wiki, make some simple graphs, plot it		pattern is a more powerful and more general text-mining library for the web, which has some functionality specific to mediawiki built in: https://github.com/clips/pattern

			Project idea: use the API to extract data about the wiki, make some simple graphs, plot it.

	[[Category:PHP]]		[[Category:PHP]]
	[[Category:MediaWiki]]		[[Category:MediaWiki]]