Extension:CMS-WIKI-like

The goal
The goal is the create a CMS that it can be is easily used by anyone, Compared to a classic CMS (content management system) where the editor interface is really different to the site, making it not so evident where to start.

I think that wiki system (mediawiki? Bouncingmolar)) resolved this problem, but the problem for an associations site is that we don't have edit buttons on all pages especially the main page. To solve this, I created this extension (my first implementation: La Margelle, my church ;-) ).

Another problem I have is to create a member area, to solve that the white list read is too restrictive, so I introduced a list of regular expressions (in future it can be replaced by name space but this creates some technical problems).

History

 * 28 04 2006 : add blacklist ($wgRegexpBlackGroupPermissions).

Features

 * Create standard pages.
 * Create member area.
 * Create wiki area.

What
A MediaWiki extension used to manage dynamically the $wgGroupPermissions and the $wgDisabledActions.

[[Category:]]==Install== To install the extension : it is great that youcan do on in a group. That you are to continue on, an continue on the cating on keep it all going strong.
 * copy the source to a file named CMS-WIKI-like.php.
 * copy this file in the extensions directory.
 * add include_once('extensions/CMS-WIKI-like.php'); after the $wgGroupPermissions.
 * edit MediaWiki:Nosuchaction to Prohibited action.
 * edit MediaWiki:Nosuchactiontext to You don't have access of this action be sure that you are login.
 * in the LocalSettings.php replace $wgGroupPermissions by $wgRegexpGroupPermissions, the false value to array and the true one by array('.*').
 * replace the $wgRegexpWhitelistRead = array(...); by $wgRegexpGroupPermissions['*']['read'] = array(...);

Quick start
To use it you just edit or add attribute to $wgRegexpGroupPermissions[group][action or permission] = array of regexp to allow it, if other ignore it => all access.

A user manage access is viewmenu, is is used to view the menu. we can specify css classes to hide by using the $wgMenuClass' default value is  '.editsection, #p-cactions, #p-tb' ''. then you need to add in the html header part of the skin :

Example
A configuration example : The result is that we have a wiki part, Main Page, a restricted access part, only sysop can create accounts.

Licence
GNU General Public License (GPL)

Author: user:sbrunner