SEQwiki:Configuration

From SEQwiki
Jump to: navigation, search

This page documents and describes the MediaWiki configuration used on this wiki

Registration

All registrations are controlled through the vBulletin forums (SEQanswers). Only users who are registered there can edit this wiki.

Installed extensions

For a full list of installed extensions, see Special:Version.

Some important extensions are described in more detail.

  • Semantic MediaWiki (including Semantic Forms and Semantic Drilldown).
  • DPL allow users to 'query' page metadata.

Requested extensions

To request an extension, add it to the following list, along with a quick description of why you think its needed:

InterWiki 
This is useful so that we can more easily link to other sites like Wikipedia, MediaWiki, Semantic-MediaWiki and others with links like w:this, mw:this, and smw:this, respectively. http://www.mediawiki.org/wiki/Extension:InterWiki
like 
this
like 
this

Configuration details

A list of the non-standard options set in 'AdditionalSettings.php' and why.

####these are for Short URLS
$wgArticlePath = "/wiki/$1";
$wgUsePathInfo = true;
####

#Dan demanded these ;) (the hostages have been released)
$wgEnableUploads = true;
$wgNamespacesWithSubpages[NS_MAIN] = true;
$wgEnableMWSuggest = true;

#change logo
$wgLogo = "http://seqanswers.com/w/seqa_logo.jpg";

#disable account creation (on the wiki) and anonymous editing
$wgGroupPermissions['*']['createaccount'] = false;
$wgGroupPermissions['*']['edit'] = false;

#Increase php memory so SMW doesn't die
ini_set( 'memory_limit', '128M' );

#for Semantic_Bundle
require_once( "$IP/extensions/semantic-bundle/SemanticBundleSettings.php" );
require_once( "$IP/extensions/semantic-bundle/SemanticBundle.php" );

# Extension PubMed
#$wgPubmedCache="/tmp/pubmedcache";
$wgPubmedLimit=0;
$wgPubmedPath="extensions/Pubmed";
$wgPubmedLayoutFile="layout_ext.def";
$wgPubmedLayoutLinks="PMID,WORLDCAT,EZB,DOI";
$wgPubmedProxyHost="";
$wgPubmedProxyPort="";
$wgPubmedProxyUser="";$wgPubmedProxyPass="";
require_once("$wgPubmedPath/Pubmed.php");

# For Tag cloud sizes 
$sdgFiltersSmallestFontSize=9; 
$sdgFiltersLargestFontSize=25; 

#for Asksql
$wgGroupPermissions['sysop' ]['asksql'] = true;
require_once('extensions/Asksql/Asksql.php');

#Dynamic Page List:
include("$IP/extensions/DynamicPageList/DynamicPageList2.php");

#
$wgPFEnableStringFunctions = true; 


Requested configuration

If you're used to looking after your own wiki, and something not quite right is driving you crazy, request the appropriate change to the site configuration here, along with a quick description of why you think its needed:

Requests

Disable the Cache please HAL: http://meta.wikimedia.org/wiki/MediaWiki_FAQ#How_do_I_completely_disable_caching.3F

This makes SMW/SF run better, and should have minimal impact on server performance on such a small wiki. As SMW/SF matures, this should become less of an issue, and caching can be re-enabled. If server performance is significantly impacted, we can undo this change.

With best wishes, --Dan 08:46, 16 December 2009 (UTC)

Configuration TODO

It would be really cool if each wiki page's talk page was managed by a thread in the vBulletin forums. The main difficulty in setting this up, I think, is ensuring the correct navigational experience for the user (i.e. embedding the forum thread in the wiki talk page).

The wiki could be tied to the forum in other ways, for example, somehow linking user pages in the wiki to user pages in the forum.