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
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;
'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
Thanks for your time!
Assistant Technical Librarian / Assistant IT Officer
American Philosophical Society
105 South Fifth Street
Philadelphia, PA 19106-3386
Tel. (215) 599-4299
*For technical support, please use helpdesk(a)amphilsoc.org
Main Library number: (215)440-3400
APS website: http://www.amphilsoc.org
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
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-
with 1.14+ there will be a link target
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 ?
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
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?