Hi,
I am upgrading my 1.10.0 installation to 1.11.0 and the update.php
script is stuck (~20 min.) at:
Deleting old default messages (this may take a long time!)...
I can check the site in the mean time and it appears as if the upgrade
has gone ahead (Special:Version shows 1.11.0). The site is extremely
slow, probably due to the server load by the script.
Any suggestions what I should do? Kill it and re-run?
Thanks,
Andi
An automated run of parserTests.php showed the following failures:
This is MediaWiki version 1.12alpha (r25977).
Reading tests from "maintenance/parserTests.txt"...
Reading tests from "extensions/Cite/citeParserTests.txt"...
Reading tests from "extensions/Poem/poemParserTests.txt"...
Reading tests from "extensions/LabeledSectionTransclusion/lstParserTests.txt"...
17 still FAILING test(s) :(
* URL-encoding in URL functions (single parameter) [Has never passed]
* URL-encoding in URL functions (multiple parameters) [Has never passed]
* Table security: embedded pipes (http://lists.wikimedia.org/mailman/htdig/wikitech-l/2006-April/022293.html) [Has never passed]
* Link containing double-single-quotes '' (bug 4598) [Has never passed]
* message transform: <noinclude> in transcluded template (bug 4926) [Has never passed]
* message transform: <onlyinclude> in transcluded template (bug 4926) [Has never passed]
* BUG 1887, part 2: A <math> with a thumbnail- math enabled [Has never passed]
* HTML bullet list, unclosed tags (bug 5497) [Has never passed]
* HTML ordered list, unclosed tags (bug 5497) [Has never passed]
* HTML nested bullet list, open tags (bug 5497) [Has never passed]
* HTML nested ordered list, open tags (bug 5497) [Has never passed]
* Inline HTML vs wiki block nesting [Has never passed]
* Mixing markup for italics and bold [Has never passed]
* dt/dd/dl test [Has never passed]
* Images with the "|" character in the comment [Has never passed]
* Parents of subpages, two levels up, without trailing slash or name. [Has never passed]
* Parents of subpages, two levels up, with lots of extra trailing slashes. [Has never passed]
Passed 527 of 544 tests (96.88%)... 17 tests failed!
Hi all,
I am thinking of trying to integrate xTableHeaderFixed[1] into
MediaWiki, perhaps as an extension or perhaps integrated into
monobook.js. It is a piece of JavaScript that freezes table headers.
So when you scroll down so a big table's header is offscreen but the
table body is onscreen, you will still see the header float at the top
of your screen. It is very cool; try the demo[1] and see.
xTableHeaderFixed seems to work in basically all modern browsers[2].
Would the xTableHeaderFixed be a useful addition to MediaWiki's
functionality? Would it be likely that it would be adopted on
enwikipedia once I make this contribution?
Cheers,
Jason Spiro
maintainer of vimpulse.el for Emacs
^ [1]. see http://www.cross-browser.com/x/examples/xthf.html for info and demo
^ [2]. http://www.sitepoint.com/forums/showpost.php?p=3261254&postcount=54
--
Jason Spiro: Linux consultant, web developer, corporate trainer.
No job too big or too small, whether two hours or two months.
Contact me for info; to see my resume, send email with subject line "resume".
+1 (613) 668-6096 / Email: info(a)jspiro.com / MSN: jasonspiro(a)hotmail.com
Hey guys -- someone posted a question / objection to Wikinvest's terms of
service a while back. I'm one of the cofounders of Wikinvest, but as I'm not
subscribed to Wikitech-l, I didn't hear about it until now. Anyway, I wanted
to address Mark Clements' concerns (full text below for those who don't
remember). To answer some (and apologize for others!):
1) The modifications Wikinvest made to MediaWiki are not GPL (this isn't a
requirement of the GPL license) -- although, we're interested in giving back
to the community. It was so helpful to have this great platform (MediaWiki)
for us to build on and we'd love to contribute some of the stuff we've built
on top of it back. There's a bunch of stuff we've built on top of the
platform -- anyone have any suggestions for what we be useful to others? Of
the stuff we've built, what do you guys want and think would be useful to
the project?
2) The fact that we didn't have clear, visible attribution to MediaWiki and
the community that built it is really not cool on our part -- I apologize
for that. I can only say that it was not an attempt to "hide" our use of
MediaWiki, it was more an "oh my god we're working 18-hour days 7 days a
week for launch" and we didn't understand the attribution requirements /
forgot to properly give credit. Thanks for pointing it out, my apologies
again, and there's now a big button on every page on our site that specifies
we are "powered by MediaWiki" and gives credit where it's due.
3) Our help content was borrowed from Wikipedia -- I unfortunately didn't
quite understand the requirements on how the attribution should work. The
attribution now links to the original Wikipedia content, the article history
(to credit all the contributors), the GFDL license on Wikipedia, and also
specifies that all our help content is GFDL'd, which I think covers all the
requirements but let me know if I'm still messing it up.
Anyway, hopefully I've got all this right now, and I hope there are no hard
feelings. If you have any other suggestions for the site (and if any of you
guys are interested in potentially joining us) please let me know...
Parker
--------------------
Mark Clements <gmane at kennel17.co.uk
<wikitech-l%40lists.wikimedia.org?Subject=%5BWikitech-l%5D%20Wikinvest%20is%20looking%20for%20world%20class%20developers%0A%09whoare%20passionate%20about%20wikis%20and%20want%20to%20extend%20mediawiki&In-Reply-To=>>
wrote:
Point 8 in the terms of service[1] includes the line (emphasis mine): "You
may not modify, reproduce, distribute, create derivative works of, publicly
display or in any way exploit, any of the content, SOFTWARE, and/or
materials available on Wikinvest, in whole or in part, except as expressly
provided in Nvest's policies and procedures made available via Wikinvest."
Isn't this a violation of the GPL for MediaWiki. Or perhaps it is referring
to some other software (in which case clarification is probably required)?
In addition I found no mention that the site was powered by MediaWiki and
that the software, including any modifications you have made, is available
under the GPL. I am unsure whether this is a requirement, though - perhaps
someone can clarify that.
Finally, there is a lot of help content that has been copied from Wikipedia,
and aside from a 'thank you' on the contents page[2] there is no
attribution. These pages need a clear link to the source article, and to the
full GFDL text. Also, it should be noted that all edits made to these pages
are also (by definition) licensed under the GFDL. If it would make things
easier, there are some public domain help pages being developed at
mediawiki.org [3], which aren't quite as good or as thorough, but which may
be used without attribution. - Mark Clements (HappyDog)
[1] http://www.wikinvest.com/site/Terms_of_Service [2]
http://www.wikinvest.com/help/Contents [3]
http://www.mediawiki.org/wiki/Help:Contents
--
www.wikinvest.com
Two days ago the disk filled up on one of our servers, Bacon,
(http://ganglia.wikimedia.org/pmtpa/graph.php?c=Miscellaneous&h=bacon.wikime…).
The full disk resulted in some thumbnails failing to render.
The root problem was resolved, but some of the failed thumbnails
remained failed. They could be resolved by purging the image page, or
by simply waiting for the cache to expire for them. The technical
team considered the matter closed.
Sometime today awareness of broken thumbs on English Wikipedia rocketed up.
Rather than successfully flagging the tech team's attention, a series
of inaccurate sitenotices were placed on English Wikipedia and on
several other language Wikipedias. The English notice in particular
was displayed to the general public.
The notices claimed that the issue was being worked on. This was not
correct. The notice most likely caused people to not report the
problems they were seeing.
None of the active tech team were aware of any ongoing issue. It was
understood that some images would fail to display until their cache
expired but this was not believed to be an issue significant enough in
scale to justify any action.
When I happened to browse over to enwp as a reader I saw the notice.
I asked ST47 to remove the notice. I got a hold of our resident
caching god, Mark Bergsma, and went ahead and mass-purged all the
thumbnails.
Sometime after that point the incorrect notice was restored on English
Wikipedia and revised several times, and in its last version it
attempted to give bad directions on how to purge images. It is
generally inadvisable to instruct the general public to purge pages on
a wide scale for a number of reasons.
All in all this issue was handled poorly all around. On the tech side
a status report should have gone out after the fix, and on the
Wikipedia admins side no claim should ever be made that a problem is
being worked on unless you are darn sure that it is the case.
There are also some issues related to how we communicate with the
public, but I'll leave it to someone else to complain about that.
My biggest fear is that had there been a second issue it may have
persisted for days with the techs unaware of the problem. I've seen
some prior examples of over eagerness to claim something is being
worked on in the past in our user communities. It frightens me for
this reason.
Hopefully future events will be handled better and this message will
increase awareness of the potential issues involved.
Thanks for your time.
On 07/09/2007, brion(a)svn.wikimedia.org <brion(a)svn.wikimedia.org> wrote:
> Revision: 25635
> Author: brion
> Date: 2007-09-07 13:30:28 +0000 (Fri, 07 Sep 2007)
>
> Log Message:
> -----------
> Revert 25602 and 25604 schema changes for now.
> Please don't commit schema changes to trunk until you've cleared them with me and Tim -- remember trunk is meant to be ready-to-run live at all times.
> They force operational work before we can update the software again, and it's a big pain in the ass to deal with them unexpectedly.
Does this mean you and Tim will actually be available to review/clear
things? You've both previously had a high workload, which meant that
absolutely nothing could get done.
Rob Church
An automated run of parserTests.php showed the following failures:
This is MediaWiki version 1.12alpha (r25949).
Reading tests from "maintenance/parserTests.txt"...
Reading tests from "extensions/Cite/citeParserTests.txt"...
Reading tests from "extensions/Poem/poemParserTests.txt"...
Reading tests from "extensions/LabeledSectionTransclusion/lstParserTests.txt"...
17 still FAILING test(s) :(
* URL-encoding in URL functions (single parameter) [Has never passed]
* URL-encoding in URL functions (multiple parameters) [Has never passed]
* Table security: embedded pipes (http://lists.wikimedia.org/mailman/htdig/wikitech-l/2006-April/022293.html) [Has never passed]
* Link containing double-single-quotes '' (bug 4598) [Has never passed]
* message transform: <noinclude> in transcluded template (bug 4926) [Has never passed]
* message transform: <onlyinclude> in transcluded template (bug 4926) [Has never passed]
* BUG 1887, part 2: A <math> with a thumbnail- math enabled [Has never passed]
* HTML bullet list, unclosed tags (bug 5497) [Has never passed]
* HTML ordered list, unclosed tags (bug 5497) [Has never passed]
* HTML nested bullet list, open tags (bug 5497) [Has never passed]
* HTML nested ordered list, open tags (bug 5497) [Has never passed]
* Inline HTML vs wiki block nesting [Has never passed]
* Mixing markup for italics and bold [Has never passed]
* dt/dd/dl test [Has never passed]
* Images with the "|" character in the comment [Has never passed]
* Parents of subpages, two levels up, without trailing slash or name. [Has never passed]
* Parents of subpages, two levels up, with lots of extra trailing slashes. [Has never passed]
Passed 527 of 544 tests (96.88%)... 17 tests failed!
config/index.php wasn't detecting eAccelerator (svn,ea svn,5.2.3) until
I changed
$conf->eaccel = function_exists( 'eaccelerator_get' );
to
$conf->eaccel = function_exists( 'eaccelerator_info' );
Is it possible to change it on svn as well?
--alnokta