Hi there,
CentOS 6.4 x86_64, php 5.3.3, PostgreSQL 9.3.1, mediawiki 1.21.3.
When trying to delete a file that was previously imported, I get:
(translated from french, original message below)
A query syntax error in the database happened. That can be a bug in
software. The last query executed by the database was:
(SQL query hidden)
from function « Revision::fetchFromConds ». The database send back
error « « 0A000 : ERROR: FOR UPDATE can't be applied on the possibly
NULL side of an extern join ».
That is in french:
Une erreur de syntaxe de la requête dans la base de données est
survenue. Ceci peut indiquer un bogue dans le logiciel. La dernière
requête traitée par la base de données était :
(Requête SQL cachée)
depuis la fonction « Revision::fetchFromConds ». La base de données a
renvoyé l'erreur « 0A000 : ERREUR: FOR UPDATE ne peut être appliqué
sur le côté possiblement NULL d'une jointure externe ».
PostgreSQL log gives:
SELECT /* Revision::fetchFromConds Low */
rev_id,rev_page,rev_text_id,rev_timestamp,rev_comment,rev_user_text,rev_user,rev_minor_edit,rev_deleted,rev_len,rev_parent_id,rev_sha1,rev_content_format,rev_content_model,page_namespace,page_title,page_id,page_latest,page_is_redirect,page_len,user_name FROM "revision" INNER JOIN "page" ON ((page_id = rev_page)) LEFT JOIN "mwuser" ON ((rev_user != 0) AND (user_id = rev_user)) WHERE page_id = '722' AND rev_id = '4584' LIMIT 1 FOR
UPDATE
I'll be glad to try some patch.
Keep up the good work,
Laurent.
Dear all,
Thanks to the feedback from Wikimedia developers, version 2.0-beta2 of the Memento time travel extension for Mediawiki is now available for testing and feedback. The extension can be downloaded via [1]. Information on the extension is available at [2]. A demonstration wiki equipped with the extension is available at [3].
The extension is fully compliant with the Memento specification [4], soon to be released as an RFC. The effort is generously funded by the Andrew W. Mellon Foundation and is a collaboration between Old Dominion University and the Los Alamos National Laboratory.
The Memento protocol extends HTTP to support content negotiation with time, allowing one to view past versions of web pages. This document [5] provides insight into the added value that the protocol brings to MediaWiki. The 1-minute screencam [6] and the 10-minute screencam [7] show Memento at work in the Web at large. The latter pays significant attention to temporal navigation in Wikipedia, and hence illustrates that the Memento Team considers time travel in MediaWiki platforms a major use case of the protocol.
The Memento protocol is not yet natively supported by browsers but a fully functional extension for Chrome is available [8]. The Memento Team hopes that adoption by MediaWiki platforms, in addition to the existing adoption by major web archives [9] and support by the International Internet Preservation Consortium [10], may lead browser manufacturers to consider implementation.
The Memento team is appreciative of all of the feedback from the Wikimedia team and is eager to get additional input on the extension in order to guide its further development to a state that fully meets the MediaWiki community's needs. Feedback on all issues is greatly appreciated as we work to improve the code base.
Shawn M. Jones on behalf of the Memento Team
http://www.cs.odu.edu/~sjone/
[1] https://github.com/hariharshankar/mediawiki/releases/tag/2.0-beta2
[2] https://www.mediawiki.org/wiki/Extension:Memento
[3] http://ws-dl-05.cs.odu.edu/demo-302-recommended-relations/
[4] http://www.mementoweb.org/guide/rfc/ID/
[5] http://www.mementoweb.org/wikipedia/
[6] http://www.youtube.com/watch?v=0_70lQPOOIg
[7] http://www.youtube.com/watch?v=WtZHKeFwjzk
[8] http://bit.ly/memento-for-chrome
[9] http://mementoweb.org/depot/
[10] http://netpreserve.org
I am getting this message on some of my mediawiki site pages:
Error: Module:Navbar:25: bad argument #1 to 'sub' (string expected, got
nil)
I figure this is another Lua issue caused by using Wikipedia templates &
Scribunto. Any tips??
I finally got Scribunto to quit crapping out on my uploads by disabling
the extra settings as shown below:
require_once( "$IP/extensions/Scribunto/Scribunto.php" );
$wgScribuntoDefaultEngine = 'luastandalone';
# $wgScribuntoUseGeSHi = true;
# $wgScribuntoUseCodeEditor = true;
$wgScribuntoEngineConf['luastandalone']['luaPath'] = '/usr/bin/lua5.1';
$wgScribuntoEngineConf['luastandalone']['errorFile'] =
'/var/log/luaerror.log';
I don't know if its actually working since I don't know how to
test/check it.
Thanks!
John
I've written an SQL query to extract some data from our wikidb as follows:
select
page_title,
u.user_name,
u.user_email,
rev_timestamp,
c.cl_to
from page p
join revision r
on p.page_id = r.rev_page
join user u
on r.rev_user = u.user_id
left join categorylinks c
on p.page_id = c.cl_from
where page_latest = r.rev_id
into outfile "/tmp/report.txt";
I need to obtain the full page URI, not just the Page Title. I can't seem
to find that stored in the wikidb. Am I just missing it or is it always
dynamically generated?
Thanks
Bill
Dear all,
today I realize that the table objectcache has 457217 Entrys with 1,1 GiB in size.
But I have disabled caching!
my text table has 47356 Entries with 354,7 MiB
all the entrys in objectcache have within the column “exptime” the Value “2038-01-19 03:14:07”
in localsettings I have these settings:
## Shared memory settings
$wgMainCacheType = CACHE_NONE;
$wgMemCachedServers = array();
## CACHE DEAKTIVIEREN, DIE UNTEREN 3 ZEILEN WIEDER LÖSCHEN WENN DER SERVER IN DIE KNIE GEHT
$wgMessageCacheType = CACHE_NONE;
$wgParserCacheType = CACHE_NONE;
$wgCachePages = false;
I think there is something wrong with my wiki, isn’t it?
Can I truncate this table and has someone an idea what's going wrong?
MediaWiki 1.19.0
PHP 5.3.27 (cgi-fcgi)
MySQL 5.1.42-community
Best regards
Thomas Ramm
I am using the collections extension
http://www.mediawiki.org/wiki/Extension:Collection to create PDFs of
selections of our wiki.
Is anyone aware of a way to create these pdfs off-line using a cron job?
I'd like to run a midnight snapshot of the selections for the reviewers.
I thought "I should probably upgrade our intranet wikis from 1.19.7 to 1.19.9".
I go to http://dumps.wikimedia.org/mediawiki/1.19/ ... and I see only
the patch from 1.19.8 to 1.19.9, not the one from 1.19.7 to 1.19.8?
Was there any reason the previous patches were removed? I'd rather not
just blat my installation with the new one, or try to work out the
patch by hand ...
- d.
Sorry for the empty mail before this, dont know what happened. Mail text
_now_ attached.
-----
Dear MediaWiki community,
I'm trying to install a MediaWiki instance. Although I never worked with
MediaWiki before, I feel quite comfortable with server issues (*nix) and
PHP.
I'd like to have mail support in the MW instance. Unfortunately I cannot
rely on sendmail (or even mini_sendmail) binary in my installation for
several reasons - both requiring a shell binary.
It seems, it's possible to replace original PHP's mail() command by an
alternate mailer program.
a) Is includes/UserMailer.php the main and only spot where mail
functionality code can be spotted?
b) I read about hooks in mailer class code (line 288 of
https://doc.wikimedia.org/mediawiki-core/master/php/html/UserMailer_8php_so…):
$ret = wfRunHooks( 'AlternateUserMailer', array( $headers, $to, $from,
$subject, $body ) );
Is this hook meant to replace the original mail program?
c) Did anyone replace original mailing code by PHPMailer yet?
d) Or is it easier to just use PEAR::Mail instead of PHPMailer (there
seemed to be some code about PEAR in it)?
Thank you for reading,
Matthias