We wish to restrict anonymous views to our mediawiki installation. Every unauthorized user is to be redirected to a particular page. This page may not be a wiki page.
Can we do this using LocalSettings.php?
If not, do we have any extension/hook for the very purpose?
Thanks in advance
mediawiki-l-bounces@lists.wikimedia.org schrieb am 10.01.2008 10:55:35:
We wish to restrict anonymous views to our mediawiki installation. Every unauthorized user is to be redirected to a particular page. This page may not be a wiki page.
Can we do this using LocalSettings.php?
$wgGroupPermissions['*' ]['read'] = false; $wgGroupPermissions['user' ]['read'] = true;
prevents anonymous users from reading. You can exclude some pages using a whitelist:
$wgWhitelistRead = array('Spezial:RequestAccount','Special:RequestAccount','Hauptseite');
If not, do we have any extension/hook for the very purpose?
HTH, Arnd
We are including mediawiki application into one existing site. for this we made one wrapper to check the authenticity of the user from existing site, We want to allow only two types of users;- 1. which are present into the mediawiki database 2. which are authentic according to our wrapper but new to mediawiki database
problem is, if someone directly gives mediawiki path to the browser then he can easily click " create account" and login into mediawiki.
How we prevent this anonymous user to login into mediawiki.
On 1/10/08, amuenzeb@rockwellcollins.com <amuenzeb@rockwellcollins.com > wrote:
mediawiki-l-bounces@lists.wikimedia.org schrieb am 10.01.2008 10:55:35:
We wish to restrict anonymous views to our mediawiki installation. Every unauthorized user is to be redirected to a particular page. This page may not be a wiki page.
Can we do this using LocalSettings.php?
$wgGroupPermissions['*' ]['read'] = false; $wgGroupPermissions['user' ]['read'] = true;
prevents anonymous users from reading. You can exclude some pages using a whitelist:
$wgWhitelistRead = array('Spezial:RequestAccount','Special:RequestAccount','Hauptseite');
If not, do we have any extension/hook for the very purpose?
HTH, Arnd _______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
mediawiki-l-bounces@lists.wikimedia.org schrieb am 10.01.2008 13:45:50:
We are including mediawiki application into one existing site. for this we made one wrapper to check the authenticity of the user from existing site, We want to allow only two types of users;-
- which are present into the mediawiki database
- which are authentic according to our wrapper but new to mediawiki
database
problem is, if someone directly gives mediawiki path to the browser then
he
can easily click " create account" and login into mediawiki.
How we prevent this anonymous user to login into mediawiki.
You can prevent access to the create-account page using the following command in LocalSettings.php
$wgGroupPermissions['*' ]['createaccount'] = false;
However, this effectivly prevents everybody from creating new accounts. If you want members of some group in the wiki to still be able to create accounts (substitutional for new users of course) you must explicitly enable them. For instance:
$wgGroupPermissions['sysop']['createaccount'] = true;
If you want anonymous user to be able to request accounts rather than instantly create them, you should take a look at the ConfirmAccount extension:
http://www.mediawiki.org/wiki/Extension:ConfirmAccount
HTH, Arnd
On 1/10/08, amuenzeb@rockwellcollins.com <amuenzeb@rockwellcollins.com > wrote:
mediawiki-l-bounces@lists.wikimedia.org schrieb am 10.01.2008
10:55:35:
We wish to restrict anonymous views to our mediawiki installation.
Every
unauthorized user is to be redirected to a particular page. This
page
may not be a wiki page.
Can we do this using LocalSettings.php?
$wgGroupPermissions['*' ]['read'] = false; $wgGroupPermissions['user' ]['read'] = true;
prevents anonymous users from reading. You can exclude some pages
using a
whitelist:
$wgWhitelistRead = array('Spezial:RequestAccount','Special:RequestAccount','Hauptseite');
If not, do we have any extension/hook for the very purpose?
HTH, Arnd _______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Hello,
My question is (MW 1.11) How to get a more light DATA with WP by eliminating a ton of version of revision that WP keeps in the tables ?
To day I can no more export by phpMyAdmin, I do not know how to obtain a file XML ( on a mutualized server = pb of rights for running maintenance/dumpexport.php) -> So I think that I can relieve simply my DATED by eliminating that tons of "histories", today useless, ... but how can it be done?
Thank a lot you for the help = I need to backup/reinject my distant site/data at home (on localhost)
How to get a more light DATA with WP by eliminating a ton of version of revision that WP keeps in the tables ?
Well, there's /maintenance/deleteOldRevisions.php, but I don't know if anyone's been keeping it up-to-date with changes to the rest of the code (some of the maintenance scripts are quite out-of-date, I believe). You could back everything up and try it and see what happens.
TD> Well, there's /maintenance/..., but I don't know if anyone's been TD> keeping it up-to-date with changes to the rest of the code (some TD> of the maintenance scripts are quite out-of-date, I believe). You TD> could back everything up and try it and see what happens.
But things might look cool but a month later you find out you have now embedded some wrinkle into your database, who knows. That's the problem with the maintenance directory. Programs are left lying there like old cigarette butts in an ashtray. Actually more like old medicine in an open cabinet where we kids are near. http://bugzilla.wikimedia.org/show_bug.cgi?id=12384 I mean it's not like we found the code on some 3rd party sidewalk. It it right there in the official distribution. Often they bear hints inside them that they are just what we want to do some job. The authors must have some inner urge to share them with us, otherwise they wouldn't be in the maintenance directory in the standard distribution. The must be eager for bug reports about what happens when we run them, which me might, upon guessing what the program will due despite lack of documentation, comments, etc.
On 11/01/2008, jidanni@jidanni.org jidanni@jidanni.org wrote:
TD> Well, there's /maintenance/..., but I don't know if anyone's been TD> keeping it up-to-date with changes to the rest of the code (some TD> of the maintenance scripts are quite out-of-date, I believe). You TD> could back everything up and try it and see what happens.
But things might look cool but a month later you find out you have now embedded some wrinkle into your database, who knows. That's the problem with the maintenance directory. Programs are left lying there like old cigarette butts in an ashtray. Actually more like old medicine in an open cabinet where we kids are near. http://bugzilla.wikimedia.org/show_bug.cgi?id=12384 I mean it's not like we found the code on some 3rd party sidewalk. It it right there in the official distribution. Often they bear hints inside them that they are just what we want to do some job. The authors must have some inner urge to share them with us, otherwise they wouldn't be in the maintenance directory in the standard distribution. The must be eager for bug reports about what happens when we run them, which me might, upon guessing what the program will due despite lack of documentation, comments, etc.
Yeah, a bit more discipline with regards to maintenance scripts would be good. At the very least, a comment at the top of each one saying what versions of MW it will reliably work with.
I think this solution can work, can you suggest that how to make group for particular users. as i understood that in given example you mention the group name "sysop".
On 1/10/08, amuenzeb@rockwellcollins.com amuenzeb@rockwellcollins.com wrote:
mediawiki-l-bounces@lists.wikimedia.org schrieb am 10.01.2008 13:45:50:
We are including mediawiki application into one existing site. for this we made one wrapper to check the authenticity of the user from existing site, We want to allow only two types of users;-
- which are present into the mediawiki database
- which are authentic according to our wrapper but new to mediawiki
database
problem is, if someone directly gives mediawiki path to the browser then
he
can easily click " create account" and login into mediawiki.
How we prevent this anonymous user to login into mediawiki.
You can prevent access to the create-account page using the following command in LocalSettings.php
$wgGroupPermissions['*' ]['createaccount'] = false;
However, this effectivly prevents everybody from creating new accounts. If you want members of some group in the wiki to still be able to create accounts (substitutional for new users of course) you must explicitly enable them. For instance:
$wgGroupPermissions['sysop']['createaccount'] = true;
If you want anonymous user to be able to request accounts rather than instantly create them, you should take a look at the ConfirmAccount extension:
http://www.mediawiki.org/wiki/Extension:ConfirmAccount
HTH, Arnd
On 1/10/08, amuenzeb@rockwellcollins.com <amuenzeb@rockwellcollins.com > wrote:
mediawiki-l-bounces@lists.wikimedia.org schrieb am 10.01.2008
10:55:35:
We wish to restrict anonymous views to our mediawiki installation.
Every
unauthorized user is to be redirected to a particular page. This
page
may not be a wiki page.
Can we do this using LocalSettings.php?
$wgGroupPermissions['*' ]['read'] = false; $wgGroupPermissions['user' ]['read'] = true;
prevents anonymous users from reading. You can exclude some pages
using a
whitelist:
$wgWhitelistRead = array('Spezial:RequestAccount','Special:RequestAccount','Hauptseite');
If not, do we have any extension/hook for the very purpose?
HTH, Arnd _______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
mediawiki-l-bounces@lists.wikimedia.org schrieb am 11.01.2008 06:44:19:
I think this solution can work, can you suggest that how to make group for particular users. as i understood that in given example you mention the group name
"sysop".
To learn more about user- and group-rights you may want to start here:
http://www.mediawiki.org/wiki/Help:User_rights
HTH, Arnd
mediawiki-l@lists.wikimedia.org