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
Hello,
We've been working for a while on a product called
omCollab<http://mike2.openmethodology.org/wiki/OmCollab>,
which is a collaboration solution that uses mediawiki and a number of mw
extensions as well as other technologies for collaboration. The whole
approach is free and open source. You can get the code from here:
http://mike2.openmethodology.org/wiki/Installing_omCollab
Our goal is to provide an integrated product that meets the requirements for
enterprise collaboration and will support our key initiative at
www.openmethodology.org and the concept of an integrated
framework<http://mike2.openmethodology.org/wiki/MIKE2:Integrated_Content_Repository>for
information development.
We're continuing to build on the approach: recent work that we'll move to
the trunk soon includes mediawiki/open office integration and
mediawiki/phpBB integration.
A couple questions for this group:
1. Do you think its a good idea?
2. Do you have any recommendations on open source assets we might want to
bundle into omCollab?
- The planned roadmap is here:
http://mike2.openmethodology.org/wiki/OmCollab_roadmap
- You can add bugs/feature requests here:
http://waterloo.openmethodology.org/trac/omcollab/
3. Does anyone want to help?
Thanks
Sean
Hello all,
Watchlist notification is not working on my mediawiki instance.
Just upgraded to 1.13.3, but confirmed that this did not cause the
problem, because my backup 1.12.0 installation also refuses to generate
watchlist notifications. I compared configurations and they are
identical (except for the spelling change/correction in
"$wgUsersNotifiedOnAllChanges").
pear is installed and working (I know this because
"$wgUsersNotifiedOnAllChanges" works fine).
My smtp server is also functioning.
The relevant LocalSettings.php code is as follows (the brackets are, of
course, filled with the appropriate username, password, email addresses,
host, & domain):
$wgEnableEmail = true;
$wgEnableUserEmail = true;
$wgUserEmailUseReplyTo = false;
$wgPasswordReminderResendTime = 24;
$wgSMTP= array(
'host' => "[host]",
'IDHost' => "[domain of host]",
'port' => 25,
'auth' => true,
'username' => "[username]",
'password' => "[password]");
$wgUsersNotifiedOnAllChanges = array('[username]');
$wgRCShowWatchingUsers = true;
$wgPageShowWatchingUsers = true;
$wgShowUpdatedMarker = true;
$wgEmergencyContact = "[emailaddress]";
$wgPasswordSender = "[emailaddress]";
$wgEnotifFromEditor = true;
$wgEnotifMinorEdits = true;
$wgEnotifRevealEditorAddress = true;
Are there other configurations that watchlist notifications depend on
that I could check? Is my php syntax off somewhere that's obvious to
someone with more php knowledge than me? Could someone refer me to the
appropriate documentation?
Thanks for your time!
--
Cheers,
Christopher Curry
Assistant Technical Librarian / Assistant IT Officer
American Philosophical Society
105 South Fifth Street
Philadelphia, PA 19106-3386
Tel. (215) 599-4299
ccurry(a)amphilsoc.org <mailto:ccurry@amphilsoc.org>
*For technical support, please use helpdesk(a)amphilsoc.org
<mailto:helpdesk@amphilsoc.org>*
Main Library number: (215)440-3400
APS website: http://www.amphilsoc.org
Hello-
I have a use case which I am having trouble figuring out how to implement:
mediawiki pages are auto generated by a bot which creates a 'base
page' containing details about some analysis results.
I'd like the auto generated results to appear on an editable page(say
as a block of text, or a table) that allows users to add information
to the same base page that the auto generated information is stored
on.... but not allow changes to the auto-generated content.
It is important that the auto generated content is displayed with the
user additions/content.
I feel like I've read how to do this someplace, but in digging around
in the docs have not had luck finding out how.
Thank you in advance-
John
Hi,
with 1.14+ there will be a link target
[[image:ImgFile.jpg|link=elsewhere]]
a) 1.14 in WP is alpha and not recommended for other running wikis?!
b) is there a planned date for releasing 1.14.0 ?
c) is it possible and reasonable to implement it previously into 1.13.x ?
Uwe (Baumbach)
U.Baumbach(a)web.de
_______________________________________________________________________
Sensationsangebot verlängert: WEB.DE FreeDSL - Telefonanschluss + DSL
für nur 16,37 Euro/mtl.!* http://dsl.web.de/?ac=OM.AD.AD008K15039B7069a
I receive "Error in my_thread_global_end(): 1 threads didn't exit." at the end of many pages. I only started receiving this after I upgraded from MediaWiki 1.9.2 to MediaWiki 1.13.2. Everything seems to work fine. Except I have a memory error with the dumpHTML extension. We also never received the memory error until after the upgrade. I am wondering if it could be related.
I have been reading php and mysql sites about this error; they seem to blame each other. We are using PHP 5.2.1 and MySQL 5.0.22
Thanks,
Mary Beebe
We are trying to use the dumpHTML extension. With a large wiki, it is giving us memory errors. In the middle of processing pages we receive:
Fatal error: Out of memory (allocated 2036072448) (tried to allocate 3168 Bytes) in ...Hooks.php.
It is not always the same page. We have a PHP memory limit of 1000M. Has anyone had any trouble with dumpHTML.
We have always used the old dumpHTML within maintenance in MediaWiki version 1.9.2. We have no trouble with the same wiki in a non-updated version on the same server.
Has anyone had any trouble with this extension?
Thanks,
Mary Beebe
Hello,
A question about http://download.wikimedia.org/*/latest. Is it
possible to reconstruct a snapshot for a given day from
pages-meta-history?
Thanks,
Illes