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 Subverion 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.
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
I just tried to use the ini_set function,
to change the value of a variable in php.ini
for the execution of mediawiki.
MW ignored the new value however
and kept using the one from php.ini.
Is there something to know about
using ini_set() in LocalSettings.php?
Is its effect delayed but an amount
of time? Does something triggers
its effect at some point but not immediately?
Manu
Hi everybody,
I just finished hacking the mantainance/importImages.php script,
and it can now handle (seemingly safely) pre-existing files.
Removing the existence check as I suggested in a previous
email was working, but it was fairly unsafe: the file was overwritten
and no archive version was created. This resulted in the impossibility
to view, delete or revert to earlier version - not quite ideal.
I seem to have been able to fix those problems and it appears
to be doing the right thing, plus I've added a feature that
a) creates two "accepted" and "rejected" directories
b) moves the original files in one of those directories
depending if it has been successfully uploaded or not.
The latter feature is useful for a scheduled import, so
that as the script gets called every 15 minutes or so,
it doesn't upload images that had been uploaded 15
minutes earlier and haven't been manually removed
from the source directory.
The question is, if I want to make it publicly available
(I have to ask permissions to the company first), what's
the best way to do so? And how do I get it double
checked - testing and code?
Thanks for your help!
Manu
Hi fellow wikiholics,
I'm new to the mailing list. I realized today that when you click Edit
on a page you can see all the templates used on the page.
What's anoying is that this only works with "page edit" and not when you
just click to edit a section. Which means you have to do at least 2 more
clicks after realizing that a template is being used and you'd like to
edit the template.
Is there anyway around this problem? I want to see my page templates no
matter what edit I click on. And I'd like to not have to hack any php if
possible.
Joe
The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
Hello,
I followed the instruction and installed the flash.php extension. I
also added a line like this in my page: <swf width="400"
height="90">http://testwww. . . /4wiki.swf</swf>, but I am getting this
error:
Warning: Cannot modify header information - headers already sent by
(output started at
/var/www/apache2-default/wiki/extensions/flash.php:105) in
/var/www/apache2-default/wiki/includes/WebResponse.php on line 10
I am using this extension available at
http://www.mediawiki.org/wiki/Extension:Flash_Extension :
<?php
// MediaWiki Swf Extension Ver 0.1
// Set up MediaWiki to react to the "<swf>" tag
// Original file by Brigitte Jellinek
// Modified by Daniel Mustieles
Can this problem be fixed? If yes, how?
Thanks for your help in advance!
Sheau-Hwang Chang
Bridgewater State College
To All:
Is there a way to display the login page when a user accesses your wiki. For
example, when somebody goes to http://yourwiki.com they are forwarded to the
main page (http://yourwiki.com/index.php/Main_Page). Is there a way to
display the page http://yourwiki.com/index.php?title=Special:Userlogin
instead of the main page? I want my users to login first before seeing
anything.
Thanks.
-----------------------------------
Jason Spirko
Systems Administrator
Xoran Technologies
....................................................................................
This message (including any attachments) contains confidential and proprietary
information intended only for the addressee. If you are not the intended recipient,
please notify the sender immediately by responding to this e-mail, and delete
this message and attachments from your system. If you have any questions
about this e-mail please notify the sender immediately. Any unauthorized
disclosure, copying, distribution or reliance on the contents of this information
is strictly prohibited and may constitute a violation of law.
Hey all,
I'm trying to use MediaWiki in a pretty non-standard way, and I'm hoping
someone can give me a definitely answer about what works / wont work:
The site is a collection of a few different open-source document, chat,
and database tools. As such, it has it's own PHP code that drives the
site, and includes MediaWiki and other systems to generate parts of
pages where required.
As a simple example, I'm trying to do something like this:
function renderWiki($title)
{
$_R = $_REQUEST; $_G = $_GET; $_P = $_POST;
$_REQUEST = array(); $_POST = array();
$_GET = array( 'action' => 'render', 'title' => $title );
chdir('wiki');
ob_start();
require('index.php'); // run MediaWiki here
$output = ob_get_contents();
ob_end_clean();
$_REQUEST = $_R; $_GET = $_G; $_POST = $_P;
chdir('..');
return($output);
}
The first result I get is something like this:
require(/includes/WebRequest.php) [function.require
<http://drmvt.anjero.com/function.require>]: failed to open stream: No
such file or directory in
*/storage/websites/test/docs/includes/AutoLoader.php* on line *362
*I played around a bit, and found out that by making $IP global, either
in my function or in LocalSettings, I'd get a bit further, but then hit
this error:
*Fatal error*: Call to a member function incr() on a non-object in
*/storage/websites/drmvt/docs/includes/GlobalFunctions.php* on line *1679
*My hypothesis is that MediaWiki relies on many variables being in the
global scope, due to their being defined outside of any MW functions
(for example, anything defined by LocalSettings). Since I'm running MW
from inside my own function, variables not explicitly defined as global
inherit my function's variable scope. Thus later references to those
same variables, in subroutines where they are explicitly made global,
actually reference a different (and empty) variable scope.
1) Does this theory sound correct?
2) Assuming I need to use functions in my site's framework, what's the
best way to make this work?
Thanks,
Andy
Sorry, I'm somewhat of a noob. But why not just make them log in at
the main page URL, like we did in this wiki:
http://nutmeg.conncoll.edu/bio/index.php/Main_Page
afaik, there is no way they can go to another page unless they log in.
This would be controlled by
$wgGroupPermissions['*']['read'] = false;
in LocalSettings or DefaultSettings
http://www.mediawiki.org/wiki/Manual:%24wgGroupPermissions
Frank Fulchiero
Digital Media Specialist
Connecticut College
> From: "Jason Spirko" <jspirko(a)xorantech.com>
> Subject: Re: [Mediawiki-l] Use Special:UserLogin as Main Page
>
> We are using MediaWiki for our company wiki, when a employee goes
> to our
> wiki they are taken to the main page and then they are able to
> navigate
> through the site. I want the employees to login *before* they are
> directed
> to the main page (or any page for that matter).
>
> I use namespace protection throughout the site and to make it
> simpler for
> the employees it would be easier if they logged in first (every
> employee has
> an account w/permission to edit various namespaces). Some employees
> are
> confused by the login "errors" they receive when they want to edit
> a page.
> After I explain that its not an error and that they need to login
> to edit
> pages they understand. But I'm just trying to curb these panic
> attacks by
> making them login before they are even allowed to access the site.
You may also wish to try
http://www.mediawiki.org/wiki/Extension:Simple_Security
Regards,
Jack
----------------------------------------------------------------
"The absence of alternatives clears the mind marvelously"
-----Original Message-----
From: mediawiki-l-bounces(a)lists.wikimedia.org
[mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of Getzke,
John
Sent: Wednesday, August 01, 2007 2:00 AM
To: mediawiki-l(a)lists.wikimedia.org
Subject: [Mediawiki-l] AuthorRestriction Extension
I know this is a touchy subject for some, but has anyone had luck with
this restriction Extension:
http://www.mediawiki.org/wiki/Extension:AuthorRestriction
<http://www.mediawiki.org/wiki/Extension:AuthorRestriction> ?
I can see that it blocks users from reading pages, but does it also
block users from writing as well? If there are any positive reviews for
this extension I would like to hear it, or even better... bad reveiws.
Thanks,
John Getzke
_______________________________________________
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