I have two questions about user rights:
1. For blocking read access to the wiki:
$wgGroupPermissions['*']['read'] = false;
I frequently see people recommend a $wgWhitelistRead array like this:
$wgWhitelistRead = array(
'Main Page',
'Special:Userlogin',
'-'
);
What does the '-' entry mean?
2. Is the documentation on $wgAddGroups outdated, as stated here,
under "Obsolete instructions for 1.13?":
http://www.mediawiki.org/wiki/Manual_talk:%24wgAddGroups
Thanks,
DanB
This is to announce a new release of UserRightsList.
http://www.mediawiki.org/wiki/Extension:UserRightsList
This extension provides an alternative to the standard User rights
management special page.
• Bureaucrats can view users as a list instead of searching for a
specific user name
• Users with account creation privileges can view limited rights for
other users they created, if user creation logging is enabled
• The user list can be filtered by group membership, username (with %
wildcards), and/or date ranges for user_registration (by month).
This version mainly converts the database interaction to use $dbr-
>select instead of $dbr->query, so I hope it will solve various
database problems that have been reported. I also added MIT license
info (so DanTMan can add this to svn) and a Russian translation
submitted at Mediawiki.org.
I've tested it on 1.12.0. Hope it's useful to others.
=====================================
Jim Hu
Associate Professor
Dept. of Biochemistry and Biophysics
2128 TAMU
Texas A&M Univ.
College Station, TX 77843-2128
979-862-4054
Hi,
After installing the latest MediaWiki (1.12) on a RHE/Apache2.0/PHP5 and
imported the wikipedia database I found that many of the pages shows a
message like:
The database did not find the text of a page that it should have found,
named "Province of Pennsylvania".
..still, the page exists in history. Maybe you can give me a clue where to
look for fixing that. Please.
thanks
Alex
Hi all,
I am pleased to announce a new release of my Mediawiki-Extension
Wiki2LaTeX, which provides LaTeX and PDF export capabilities to any
server which runs Mediawiki and a LaTeX-Distribution (like MikTex or
TeX-Live).
This release features better quotes-support, better support for
ParserFunctions and further customization of the whole parsing-process.
More information can be found on the Extension Page:
http://www.mediawiki.org/wiki/Extension:Wiki2LaTeX
Downloads and Issue Tracker on the google code page:
http://code.google.com/p/wiki2latex/
I hope this extension can be of use to those seeking for PDF-Export of
Mediawiki articles. Any comments and suggestions are welcome.
bye
Hans-Georg Kluge
Just wondering...
Would it be worth denormalizing categorylinks a bit so that
CategoryPage.php doesn't have to join categorylinks and page? I'm
thinking that having page_title and page_namespace duplicated there
would help performance. In particular, I'm wondering if getting rid
of the join would speed things up enough to make some of the things
we're doing with our modified category page extensions tolerable on
other sites (i.e. get real counts for how many subcategories, find the
subcategories even when they don't sort within the limit etc.) and
faster on ours.
I know that it violates all kinds of sacred db design principles and
is therefore probably a bad idea. Is this a job for (materialized)
views?
=====================================
Jim Hu
Associate Professor
Dept. of Biochemistry and Biophysics
2128 TAMU
Texas A&M Univ.
College Station, TX 77843-2128
979-862-4054
Guys,
I need help.
Is it possible to set each user to authenticate first before viewing and
editing pages instead of authenticating before editing pages? I don't want
to use htaccess at this moment if mediawiki has this feature. I'm using
mediawiki-1.10 with AD/LDAP authentication.
Thank you!
Welcome to mediawiki-l. This mailing list exists for discussion and questions
about the MediaWiki software[0]. Important MediaWiki-related announcements
(such as new versions) are also posted to this list.
Other resources.
If you only wish to receive announcements, you should subscribe to
mediawiki-announce[1] instead.
MediaWiki development discussion, and all Wikimedia technical questions, should
be directed to the wikitech-l[2] mailing list.
Several other MediaWiki-related lists exist:
- mediawiki-api[5] for API discussions,
- mediawiki-enterprise[6] for discussion of MediaWiki in the enterprise,
- mediawiki-cvs[7] for notification of commits to the Subversion repository,
- mediawiki-i18n[8] for discussion of MediaWiki internationalisation support,
- wikibugs-l[9] for notification of changes to the bug tracker.
List administrivia (unsubscribing, list archives).
To unsubscribe from this mailing list, visit [12]. Archives of previous postings
can be found at [3].
This list is also gatewayed to the Gmane NNTP server[4], which you can use to
read and post to the list.
Posting to the list.
Before posting to this list, please read the MediaWiki FAQ[10]. Many common
questions are answered here. You may also search the list archives to see if
your question has been asked before.
Please try to ask your question in a way that enables people to answer you.
Provide all relevant details, explain your problem clearly, etc. You may
wish to read [13], which explains how to ask questions well.
To post to the list, send mail to <mediawiki-l(a)lists.wikimedia.org>. This is a
public list, so you should not include confidential information in mails you
send.
When replying to an existing thread, use the "Reply" or "Followup" feature of
your mail client, so that clients that understand threading can sort your
message properly. When quoting other messages, please use the "inline" quoting
style[11], for clarity.
When creating a new thread, do not reply to an existing message and change the
subject. This will confuse peoples' mail readers, and will result in fewer
people reading your mail. Instead, compose a new message for your post.
Messages posted to the list have the "Reply-To" header set to the mailing list,
which means that by default, replies will go to the entire list. If you are
posting a reply which is only interesting to the original poster, and not the
list in general, you should change the reply to only go to that person. This
avoids cluttering the list with irrelevant traffic.
About this message.
This message is posted to the list once per week by <river(a)wikimedia.org>.
Please contact me if you have any questions or concerns about this mailing.
References.
[0] http://www.mediawiki.org/
[1] http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
[2] http://lists.wikimedia.org/mailman/listinfo/wikitech-l
[3] http://lists.wikimedia.org/pipermail/mediawiki-l/
[4] http://dir.gmane.org/gmane.org.wikimedia.mediawiki
[5] http://lists.wikimedia.org/mailman/listinfo/mediawiki-api
[6] http://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise
[7] http://lists.wikimedia.org/mailman/listinfo/mediawiki-cvs
[8] http://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
[9] http://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[10] http://www.mediawiki.org/wiki/FAQ
[11] http://en.wikipedia.org/wiki/Posting_style#Inline_replying
[12] http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
[13] http://www.catb.org/~esr/faqs/smart-questions.html
Hi all,
MediaWiki is a great project and a growing niche. As it becomes even
more popular, there will be increasing demand for experts in the
field.
I am compiling a contact list of MediaWiki experts who may be
interested in opportunities under the right circumstances. I am not a
recruiter - I'm a regular developer who sometimes gets asked for
referrals when I'm not personally available.
If you'd like to be on my shortlist of go-to experts, please contact
me off-list at: wilson.jim.r(a)gmail.com
Please be prepared to show your expertise by /any/ of the following:
* Committer status or patches accepted
* Bugs reported which were either resolved or are still open (that
is, /real/ bugs)
* Commit access to another open source project based on MediaWiki
* Extensions you've authored or significantly modified
* Links to any public wikis you administer
* Articles / blog entries written about MediaWiki concepts or development
* Significant contributions to documentation (mediawiki.org or
meta.wikimedia.org)
* Speaking engagements or user groups at which you've presented
* Other? (I'm sure I didn't think of everything)
I'll be happy to answer any questions, and I look forward to hearing from you!
-- Jim R. Wilson (jimbojw)
In our wiki, we have many toolbar buttons on the edit page, so we want to split them into multiple lines at designated spots. My hacked solution is below -- is there a better way?
To implement this, I hacked function mwInsertEditButton in skins/common/wikibits.js, so an imageFile value of "<br>" causes a real <br> to be inserted into the toolbar. I added this code as the first lines of mwInsertEditButton :
if (item.imageFile == '<br>') {
parent.appendChild(document.createElement("br"));
return true;
}
Is there a better way to accomplish this task without modifying core code?
Thanks,
DanB
Hello.
I recently installed a mediawiki and am trying to set it up to render svg
images. My linux host has the GD Library version 2.0.34. The documentation
at the wiki says to enable
$wgUseImageMagick<http://www.mediawiki.org/wiki/Manual:%24wgUseImageMagick>to
enable ImageMagick but what about the other libraries? What do I have
to
do to enable MediaWiki to display thumbnails of svg images?
thanks in advance,
Jubei