Replies in-line
> Message: 2
> Date: Sat, 3 Nov 2007 13:27:28 +0000
> From: "Thomas Dalton" <thomas.dalton(a)gmail.com>
> Subject: Re: [Mediawiki-l] how to create a bureaucrats group which in
> turn gives access to other people to make edits.
> To: "MediaWiki announcements and site admin list"
> <mediawiki-l(a)lists.wikimedia.org>
> Message-ID:
> <a4359dff0711030627p6164f3dapf6c5cb6ef3c4544d(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On 03/11/2007, shirish <shirishag75(a)gmail.com> wrote:
> > Hi all,
> > I'm making/playing with a wiki site where I want to make a
> > "user group" who in turn will give access to other people to do
> > edits/submissions stuff like that. No anonymous editing is done.
> > Right now I've done
> >
> > # Prevent new user registrations except by sysops
> > $wgGroupPermissions['*']['createaccount'] = false;
> >
> > This is done in LocalSettings.php
> >
> > which basically prevents anybody from doing any edits except a single
> > user. I am using MySQL as my database. I saw this which might have
> > the goods which I need
> > http://www.mediawiki.org/wiki/Manual:%24wgGroupPermissions but unable
> > to make sense of it.
>
> Do you actually want to restrict account creation, or just editing?
> It's often easier to let people create their own accounts, and then
> just have someone give them permission to edit. To do that, try
> something like:
>
> $wgGroupPermissions['*']['read'] = true; # Allow anons to read
> $wgGroupPermissions['*']['createaccount'] = true; # Allow anons to
> create accounts
> $wgGroupPermissions['*']['edit'] = false; # Stop anon edits
> $wgGroupPermissions['user']['edit'] = false; # Stop accounts without
> permission editing
> $wgGroupPermissions['editor']['edit'] = true; # Create a new user
> group for people with permission to edit
> $wgGroupPermissions['sysop']['userrights'] = true; # let sysop change
> user permissions
>
> $wgAddGroups['sysop'] = array( 'editor' ); # Allow sysops to grant
> edit permissions on Special:Userrights
> $wgRemoveGroups['sysop'] = array( 'editor'); # Allow sysops to remove
> those permissions
>
> Hope that helps. You may want to fine tune a few bits (who can create
> pages, create talk pages, etc).
Hi Thomas,
You really made my day. I'm guessing these are things if I
talk 'editor' as the usergroup which explicitly has been given
permissions in addition to what you have outlined.
$wgGroupPermissions['editor' ]['createpage'] = true; #Give
createpage permissions only to usergroup
$wgGroupPermissions['editor' ]['createtalk'] = true; #Give
talkpage create permissions only to usergroup
Another query which occured to me, although it may be totally
foolish, what do people think of having only 1 sysop or should there
be more than 1 sysop? On what factors should this be done? For e.g.
do wikipedia & memoryalpha.org (both high-visited sites having large
scale vandalism as well as big user-bases so really not my cup of tea
but still just to know what people think)
Also for creating a usergroup called 'editor' for e.g. . Now does that
usergroup needs to be created in mysql or not? As told before totally
a baby/noob in these matters.
Lastly, Thomas thank you for using/sharing your valuable time & insight .
Regards,
--
Shirish Agarwal
This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/
065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17
Hi,
I have a wiki at http://bibliowiki.com.pt that has been experiencing for
the past week severe (and increasing) parsing problems. It started out
last saturday as an occasional and apparently random glitch that seemed
to turn off the handling of template syntax, wereas tables instead of
showing the values turned up full of {{}} thingies with the variable
names inside.
This wiki had been transferred in mid September from my previous host
(which didn't have PHP5) to my current one (which has), and therefore
its version was pretty outdated: 1.6.X. It was working fine till last
saturday, though, so as I have been pretty pressed with time, I kept
postponing the update. When the trouble started, though, I was told a
few times (in #mediawiki, for instance) that the version of mediawiki
might be the culprit, so I finally updated a couple of days ago. The
update went fine, and, apart from the issue, the wiki is working now
properly in version 1.11.0 (PHP is 5.2.2 and MySQL 4.1.22-standard-log,
by the way).
The issue, however, remains, and seems to me to be getting worse. When
it struck only sometimes a few days ago, now it seems to be striking
almost constantly, and any sequence of clicks in "Página aleatória"
(portuguese version of "Random article") will almost certainly be
showing broken tables. Also, other variables, such as the {{SITENAME}}
one that exists in the login page, also started to show up instead of
their values from time to time. As an example, the stats page I have
opened right now, reads exactly as follows:
>>>Há actualmente um total de {{PLURAL:11 251|*11 251* página|*11 251*
páginas}} na base de dados. Isto inclui páginas de "discussão", páginas
sobre o projecto ({{SITENAME}}), páginas de rascunho, redireccionamentos
e outras que provavelmente não são qualificadas como páginas de
conteúdo. Excluindo estas, há {{PLURAL:8 62[[:Predefinição:*8
622*]]icheiro foi carregado|ficheiros foram carregados}}.<<<
Sometimes, adding "?action=purge" to the end of the page's URL helps,
but that's perhaps only 40% of the times.
The thing gets stranger still. My content is mostly within tables (it's
a database; I chose the wiki approach because of its greater openness to
unexpected details compared to the predefined and closed nature of
traditional databases... and my data does show a naughty tendency to
turn up surprises), and these tables are defined in simple templates,
only with the template name and their variables. One would expect that
if the software failed to recognize the variables, it *totally* failed
to recognize them, right? Wrong: typically, the first variable in the
template is properly shown, sometimes the second one also gets shown,
and only the rest is garbled.
*And* it comes and goes. A few minutes ago, I had the result I'm quoting
above in the statistics page; just now, a sequence of random pages
showed them all perfectly fine. I'm totally lost as to what might be
causing this, and, which is worse, the guys at the host are too, and not
even the three or four devs I talked to in #mediawiki were able to come
up with an answer.
Please help...
Jorge Candeias
--
_____________________________________________________________________
http://ficcao.com.pthttp://lampadamagica.blogspot.com
When syntax highlighting is applied to Bash code, keywords within
comments are still highlighted. This can be seen in this page:
http://en.wikipedia.org/wiki/Bash_syntax_and_semantics
Not a big deal, only cosmetic problem.
HI Guys - Please advice for the best approach on how to plan for Disaster
Recovery? We have another wiki server on separate datacenter.
Here is our requirements:
- DR Database should have same content on the Production so we could just
swing the DNS alias to the DR server.
- How to replicate the database, content and images?
- How frequent is the replication?
- How to back-up the whole wiki?
Any advice will be highly appreciated.
Regards'
zham
Hello all,
I intend to develop[*] a very simplified variant of the "stable version"
concept: If the editing user has no authorization, replace any sensitive
portions with a non-sensitive substitute - e.g. "{{Approved}}" becomes
"{{Approval Candidate}}".
[*] see "Re-inventing the wheel?" below
The following simple flowchart probably illustrates my idea better than
a verbose description would:
+--------------+
| save request |
+--------------+
|
V
/--------------------------------\ No
| article text contains $cue [1] |-------------------------------------+
\--------------------------------/ |
| |
Yes | |
V |
/------------------------\ No +------------------------------+ |
| user is authorized [2] |------->| replace $cue with $subst [1] | |
\------------------------/ +------------------------------+ |
| | |
Yes | | |
V | |
+--------------+ | |
| save article |<--------------------------------+---------------------+
+--------------+
[1] $cue and $subst are strings, read from an external TXT file
(in future version, these variables might be arrays of strings)
[2] authorization is handled via user rights (e.g. Bureaucrats, or
custom group "Editors"; might be read from an external TXT file)
Theoretically, this could all be very simple (maybe 10-20 LoC).
However, there are a few concerns:
#1 Re-inventing the wheel?
I'm probably not the first person to think of this on-save substitution.
However, I couldn't find an extension to build upon (which might be due
to a lack of unique keywords to search for).
#2 Preventing false positives
How can I prevent unparsed occurrences of $cue from being substituted?
For example, [[Template:Approval]] might contain usage notes with the
template call wrapped in PRE tags - this obviously should not be replaced.
Here's some very preliminary (pseudo-)code I quickly threw together -
maybe could help me fill in the blanks:
---------------
<?php
$wgHooks['ArticleSave'][] = 'wfCheckApprovalAuthorization';
function wfCheckApprovalAuthorization(&$article, &$user, &$text,
&$summary, $minor, $watch, $sectionanchor, &$flags) {
$cue = "foo"; // to be read from external TXT file
$subst = "bar"; // to be read from external TXT file
$auth = "editors"; // to be read from external TXT file
if( $text == $cue ) { // check for "contains", not "equals"
if( in_array( $auth, $user->$permissions ) ) { // nonsense?
str_ireplace( $cue, $subst, $text ); // nonsense?
}
}
}
?>
---------------
Sorry this message turned out to be so verbose.
For whoever has read this far, I'd greatly appreciate any feedback!
-- F.
-----Original Message-----
From: mediawiki-l-bounces(a)lists.wikimedia.org
[mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of Jack Eapen
C
Sent: Wednesday, July 18, 2007 6:28 PM
To: MediaWiki announcements and site admin list
Subject: Re: [Mediawiki-l] internal link in a new window
Go to includes/Linker.php. there's a function
getInternalLinkAttributes()
Add the target="_blannk" attribute to that function.
Similarly you can do for external links and interwiki links. (see the
functions just above that).
But it seems opening links in new windows is against the w3c standards?
:(
Regards,
Jack
----------------------------------------------------------------
"If you can find something everyone agrees on, it's wrong"
-----Original Message-----
From: mediawiki-l-bounces(a)lists.wikimedia.org
[mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of empirium
Sent: Wednesday, July 18, 2007 6:24 PM
To: mediawiki-l(a)lists.wikimedia.org
Subject: [Mediawiki-l] internal link in a new window
it is possible in mediawiki open internal link in a new window?
thanks in advance
luk
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
This electronic mail (including any attachment thereto) may be
confidential and privileged and is intended only for the individual or
entity named above. Any unauthorized use, printing, copying, disclosure
or dissemination of this communication may be subject to legal
restriction or sanction. Accordingly, if you are not the intended
recipient, please notify the sender by replying to this email
immediately and delete this email (and any attachment thereto) from your
computer system...Thank You
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
This electronic mail (including any attachment thereto) may be confidential and privileged and is intended only for the individual or entity named above. Any unauthorized use, printing, copying, disclosure or dissemination of this communication may be subject to legal restriction or sanction. Accordingly, if you are not the intended recipient, please notify the sender by replying to this email immediately and delete this email (and any attachment thereto) from your computer system...Thank You
Hi,
In certain articles, I have section headings of level 3and 4. I want to
include only level 3 in TOC. How I can exclude level 4 headings?
Based on http://en.wikipedia.org/wiki/Help:Section#Limiting_the_TOC I
tried the {{TOClevel|level=3}} after creating the template TOClevel.
But still the TOC has all section headings. Wht am I missing? My MW is
1.11
Regards,
Jack Eapen C
SunTec Knowledge Centre
This electronic mail (including any attachment thereto) may be confidential and privileged and is intended only for the individual or entity named above. Any unauthorized use, printing, copying, disclosure or dissemination of this communication may be subject to legal restriction or sanction. Accordingly, if you are not the intended recipient, please notify the sender by replying to this email immediately and delete this email (and any attachment thereto) from your computer system...Thank You
Referencing
http://www.mediawiki.org/wiki/Manual:Wiki_family#Scenario_2:_Quick_set-up,
as I understand it, I make my installation, then for each sub-wiki, as
it were, I merely create a copy of the LocalSettings.php file for each
wiki as appropriate, in the root directory - so if the code base is
in /opt/www/wiki, all of the LocalSettings.php copies land here for
each subwiki, with one single LocalSettings.php controlling the whole
show. Is this correct, or did I misread something?
-Dennis Carr
> Earlier: "... Referencing
http://www.mediawiki.org/wiki/Manual:Wiki_family#Scenario_2:_Quick_set-u
p
> as I understand it, I make my installation,
> then for each sub-wiki, as it were, I merely
> create a copy of the LocalSettings.php file
> for each wiki as appropriate, in the root
> directory - so if the code base is in
> /opt/www/wiki, all of the LocalSettings.php
> copies land here for each subwiki, with one
> single LocalSettings.php controlling the
> whole show. Is this correct, or did I
> misread something?
Peter Blaise responds: Yeah, you got it wrong.
LocalSettings.php moves from a yourwiki\config subdirectory
under each wiki to the root of each wiki, not to the root of your web,
and so each wiki is a subdirectory of your web share. This is how mine
go on Windows, your pattern may vary:
X:\www\apache2\htdocs\wiki1\config (deleted)
X:\www\apache2\htdocs\wiki1\ (contains moved LocalSettings.php from
above)
X:\www\apache2\htdocs\wiki2\config (deleted)
X:\www\apache2\htdocs\wiki2\ (contains moved LocalSettings.php from
above)
X:\www\apache2\htdocs\wiki3\config (deleted)
X:\www\apache2\htdocs\wiki3\config (contains moved LocalSettings.php
from above)
X:\www\apache2\htdocs\wiki4\config (deleted)
X:\www\apache2\htdocs\wiki4\config (contains moved LocalSettings.php
from above)
X:\www\apache2\htdocs\wiki5\config (deleted)
X:\www\apache2\htdocs\wiki5\config (contains moved LocalSettings.php
from above)
... and so on, all using common:
X:\www\apache2
X:\www\mysql5
X:\www\php5
X:\www\apache2\htdocs\phpmyadmin
X:\www\apache2\htdocs\temp
I wish there was a way to share extensions - do I just have to
try creative calling in LocalSettings.php? Perhaps have them all refer
to:
X:\www\apache2\htdocs\mediawiki\extensions
Has anyone tried this? Right now, I have copies of any
extensions I'd like to use, duplicated in each wiki. That makes them
independent and portable, backup wise, and I suppose the extensions
aren't really large, space wise. But I have to remember to update each.
However, it does allow me to experiment in one wiki and get it right
before cloning to the others. If they all depended on the same source
all the time, I'd have to experiment in yet another playground, like:
X:\www\apache2\htdocs\mediawiki\test-extensions
... then move any success to the real live common area.
The beauty of keeping each separate is that I can rubber stamp
any success from one to the others, and even leave one "old" and not
updated if stability is happy making. Hey, if it ain't broke, don't fix
it. I'm impressed with some of the antique wikis running out there -
some as old as 18 months or older! =8^o
Anyway, LocalSettings.php stays in the root of each of your
WIKIs, not the root of your WEB!
Hello list,
for the moment Mediawiki/Wikipedia shows a petition for donation at the
top of each page before the page name.
I want to do the same (showing text/images) for all and/or some special
page.
Any hints how to implement this?
Thanks for your advise.
Wolfgang