Difference between revisions of "MediaWiki Configuration"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (CodeSyntaxHighlight MediaWiki Extension (done))
 
(15 intermediate revisions by 5 users not shown)
Line 1: Line 1:
This pages have been automatically generated by twiki2mediawiki. Please
+
== Page Review (done) ==
review all of them, as there will be broken markup and broken links.
+
  
Please review your page and move the link from the "Converted Pages" to "Reviewed Pages". To move your page to a new name you have to login. If you would like to see a page removed add a link to the [[Twiki2mediawiki_TODO_list#remove.28d.29|remove(d)]] section.
+
All Main_ prefixed pages and links have been reviewed and corrected.
 
+
== Page Review ==
+
 
+
In some of the SVG* pages the links have to be changed to avoid the Main_ prefix.
+
 
+
* [[Main SVGCoordinateSystems]]
+
* [[Main SVGEllipticArcs]]
+
* [[Main SVGFilterSourceCode]]
+
* [[Main SVGGroupOpacity]]
+
* [[Main SVGHEAD]]
+
* [[Main SVGImportFilter]]
+
* [[Main SVGImportTodo]]
+
* [[Main SVGPathSemantics]]
+
* [[Main SVGSupportedFeatures]]
+
* [[Main SVGUnsupportedFeatures]]
+
* [[Main SVGUserExperiences]]
+
 
+
These pages are of dubious usefulness, completeness & relevance and should prolly be removed:
+
* [[WebOOoBanners]]
+
* [[OOoES]]
+
  
 
== Managing Rights (done) ==
 
== Managing Rights (done) ==
Line 75: Line 54:
 
We might want to keep one playground though.
 
We might want to keep one playground though.
  
== CodeSyntaxHighlight MediaWiki Extension ==
+
== CodeSyntaxHighlight MediaWiki Extension (done) ==
 +
 
 +
===OBSOLETE - this has been replaced with a new version of the Syntax Highlighter, and it has new MediaWiki syntax.  See [[Wiki maintenance/Extensions|Extensions]]===
 +
 
 
Code Syntax highlighting using GeShi
 
Code Syntax highlighting using GeShi
 
http://qbnz.com/highlighter/
 
http://qbnz.com/highlighter/
Line 91: Line 73:
 
ooodata/www/mwiki/extensions/CodeSyntaxHighlight/geshi
 
ooodata/www/mwiki/extensions/CodeSyntaxHighlight/geshi
 
and look like (initial comments removed):
 
and look like (initial comments removed):
<code>[php]
+
<source lang="php">
 
$language_data = array (
 
$language_data = array (
 
'LANG_NAME' => 'C',
 
'LANG_NAME' => 'C',
Line 181: Line 163:
 
)
 
)
 
);
 
);
</code>
+
</source>
  
 
I found this link useful for working out color codes:
 
I found this link useful for working out color codes:
Line 187: Line 169:
  
 
[[User:Iannz]]
 
[[User:Iannz]]
 +
 +
Could we add the uno idl language file I wrote ? The file is attached to one of my
 +
[http://blogs.nuxeo.com/sections/blogs/cedric_bosdonnat/2006_08_20_uno-idl-syntax-highlighting-in-php blog articles].
 +
 +
[[User:Cedricbosdo]]
 +
 +
 +
Since we don't seem to have a distinct help page for that: just a list of programming languages with wiki syntax highlighting enabled, obtained with '''<nowiki><code>[langlist]</code></nowiki>'''.
 +
 +
<code>[langlist]</code>
 +
 +
To use syntax highlighting enclose piece of (C++) code in
 +
 +
<pre>
 +
<nowiki>
 +
<code>[cpp]
 +
... code goes here ...
 +
</code>
 +
</nowiki>
 +
</pre>
 +
 +
== Subpages (done) ==
 +
 +
On [[User:Kr|Kay]]'s suggestion the [http://meta.wikimedia.org/wiki/Help:Link#Subpage_feature subpage mechanism] has been enabled in [http://meta.wikimedia.org/wiki/LocalSettings.php#Enabling_subpages Localsettings.php] for the main namespace.
 +
 +
This eases the generation of hierarchical structures where appropriate. Subpages allow to place pages as children into other pages and to address other pages relative (e.g. ../../bla).
 +
Details can be found in the
 +
[http://meta.wikimedia.org/wiki/Help:Link#Subpage_feature mediawiki help]
 +
 +
There is also an RFE for listening all the subpages for a particular page:
 +
in [http://bugzilla.wikimedia.org/show_bug.cgi?id=233 MediaZilla] (bug tracking system for mediawiki).
 +
 +
--[[User:St|stx12]] 12:48, 11 May 2006 (CEST)
 +
 +
== New User Nofification ==
 +
 +
Admins are notified about creation of new user accounts via email.
 +
[http://meta.wikimedia.org/wiki/New_User_Email_Notification]
 +
 +
== AntiSPAM Measures ==
 +
 +
* Edit only if logged in (s. [[MediaWiki_Configuration#Managing_Rights_.28done.29|Managing Rights]])
 +
* Edit only if email if confirmed ($wgEmailConfirmToEdit)
 +
* SpamRegex prohibits <code>style=display:none</code> ($wgSpamRegex)
 +
 +
[[Category:Website]]

Latest revision as of 12:13, 17 June 2008

Page Review (done)

All Main_ prefixed pages and links have been reviewed and corrected.

Managing Rights (done)

  • sysop via db

http://meta.wikimedia.org/wiki/Setting_user_rights_in_MediaWiki#Granting_rights_to_users

It seems neccessary to require users to login to edit.
This avoids defacement and makes authors feel more responsible for the content.

Special Pages to take care of:

Help Content (done)

Help:Contents with links to
http://meta.wikimedia.org/wiki/MediaWiki_FAQ
http://meta.wikimedia.org/wiki/MediaWiki_User%27s_Guide

Help:Editing with links to
http://meta.wikimedia.org/wiki/Help:Editing
http://meta.wikimedia.org/wiki/Help:Contents#For_editors

Copyrights (done)

Project:Copyrights

Navigation Box (done)

See http://meta.wikimedia.org/wiki/MediaWiki_FAQ#In_version_1.5
MediaWiki:Sidebar

InterWiki Links

http://meta.wikimedia.org/wiki/Help:Guide_for_system_administrators_for_setting_up_interwiki_linking#add_your_own_custom

User:Haui configured issue InterWiki links for TWiki. A test page is at [Sandbox_BernhardHaumacherSandbox]. That would be handy here too.

Custom Namespaces

http://meta.wikimedia.org/wiki/Help:Namespace#Custom_namespaces http://meta.wikimedia.org/wiki/Help:Custom_namespaces

Cleanup Test Installations

mediawiki2, mediawiki, backups of httpd.conf, ... can be purged.

We might want to keep one playground though.

CodeSyntaxHighlight MediaWiki Extension (done)

OBSOLETE - this has been replaced with a new version of the Syntax Highlighter, and it has new MediaWiki syntax. See Extensions

Code Syntax highlighting using GeShi http://qbnz.com/highlighter/ Has been added as per http://mercury.it.swin.edu.au/swinbrain/index.php/CodeSyntaxHighlight_MediaWiki_Extension

Haven't updated help page yet.

The default color codes for Geishi could be improved.

I have changed the colors for oobas, but am not sure what colors to assign for C. I haven't managed to mimick the BASIC IDE as I don't understand why keywords like "for" are blue but "msgbox" is green.

For those that have access to the server the files are in: ooodata/www/mwiki/extensions/CodeSyntaxHighlight/geshi and look like (initial comments removed):

$language_data = array (
	'LANG_NAME' => 'C',
	'COMMENT_SINGLE' => array(1 => '//', 2 => '#'),
	'COMMENT_MULTI' => array('/*' => '*/'),
	'CASE_KEYWORDS' => GESHI_CAPS_NO_CHANGE,
	'QUOTEMARKS' => array("'", '"'),
	'ESCAPE_CHAR' => '\\',
	'KEYWORDS' => array(
		1 => array(
			'if', 'return', 'while', 'case', 'continue', 'default',
			'do', 'else', 'for', 'switch', 'goto'
			),
		2 => array(
			'null', 'false', 'break', 'true', 'function', 'enum', 'extern', 'inline'
			),
		3 => array(
			'printf', 'cout'
			),
		4 => array(
			'auto', 'char', 'const', 'double',  'float', 'int', 'long',
			'register', 'short', 'signed', 'sizeof', 'static', 'string', 'struct',
			'typedef', 'union', 'unsigned', 'void', 'volatile', 'wchar_t'
			),
		),
	'SYMBOLS' => array(
		'(', ')', '{', '}', '[', ']', '=', '+', '-', '*', '/', '!', '%', '^', '&', ':'
		),
	'CASE_SENSITIVE' => array(
		GESHI_COMMENTS => true,
		1 => false,
		2 => false,
		3 => false,
		4 => false,
		),
	'STYLES' => array(
		'KEYWORDS' => array(
			1 => 'color: #b1b100;',
			2 => 'color: #000000; font-weight: bold;',
			3 => 'color: #000066;',
			4 => 'color: #993333;'
			),
		'COMMENTS' => array(
			1 => 'color: #808080; font-style: italic;',
			2 => 'color: #339933;',
			'MULTI' => 'color: #808080; font-style: italic;'
			),
		'ESCAPE_CHAR' => array(
			0 => 'color: #000099; font-weight: bold;'
			),
		'BRACKETS' => array(
			0 => 'color: #66cc66;'
			),
		'STRINGS' => array(
			0 => 'color: #ff0000;'
			),
		'NUMBERS' => array(
			0 => 'color: #cc66cc;'
			),
		'METHODS' => array(
			1 => 'color: #202020;',
			2 => 'color: #202020;'
			),
		'SYMBOLS' => array(
			0 => 'color: #66cc66;'
			),
		'REGEXPS' => array(
			),
		'SCRIPT' => array(
			)
		),
	'URLS' => array(
		1 => '',
		2 => '',
		3 => 'http://www.opengroup.org/onlinepubs/009695399/functions/{FNAME}.html',
		4 => ''
		),
	'OOLANG' => true,
	'OBJECT_SPLITTERS' => array(
		1 => '.',
		2 => '::'
		),
	'REGEXPS' => array(
		),
	'STRICT_MODE_APPLIES' => GESHI_NEVER,
	'SCRIPT_DELIMITERS' => array(
		),
	'HIGHLIGHT_STRICT_BLOCK' => array(
		)
);

I found this link useful for working out color codes: http://www.htmlgoodies.com/tutorials/colors/article.php/3478961

User:Iannz

Could we add the uno idl language file I wrote ? The file is attached to one of my blog articles.

User:Cedricbosdo


Since we don't seem to have a distinct help page for that: just a list of programming languages with wiki syntax highlighting enabled, obtained with <code>[langlist]</code>.

[langlist]

To use syntax highlighting enclose piece of (C++) code in


<code>[cpp]
... code goes here ...
</code>

Subpages (done)

On Kay's suggestion the subpage mechanism has been enabled in Localsettings.php for the main namespace.

This eases the generation of hierarchical structures where appropriate. Subpages allow to place pages as children into other pages and to address other pages relative (e.g. ../../bla). Details can be found in the mediawiki help

There is also an RFE for listening all the subpages for a particular page: in MediaZilla (bug tracking system for mediawiki).

--stx12 12:48, 11 May 2006 (CEST)

New User Nofification

Admins are notified about creation of new user accounts via email. [1]

AntiSPAM Measures

  • Edit only if logged in (s. Managing Rights)
  • Edit only if email if confirmed ($wgEmailConfirmToEdit)
  • SpamRegex prohibits style=display:none ($wgSpamRegex)
Personal tools