Hi,
I was trying to export some entries using the special:export utility and
although I unchecked the box, to get all the revisions, the xml output file
includes only the last revision. Is there something I am missing or is this
utility partially disabled?
Thanks.
SM
Hello everyone,
I am trying to setup a dictionary using MediaWiki and I was wondering what the
best way is to go about setting it up as a multiple language dictionary (i.e.
each definition has translations in 4 other languages). I have heard about the
Ultimate Wikitionary which would be perfect, but I have to set something up
temporarily until that has been developed. From what I understand from
Wikimedia MetaWiki pages, the way to do it is to have separate installations
for each language and using InterWiki links to make definitions link to their
corresponding translations.
My questions are: am I correct about a multiple install being the recommended
way to setup a multilanguage wiki?
Is it okay to do it using multiple installations on the same server? Or is it
necessary to have a domain name for each installation?
Any help or suggestions would be much appreciated, thank you,
Andrew.
I've set up an indexing update daemon for the Lucene search indexes,
which accepts updates sent from a MediaWiki extension hook over XML-RPC.
One of the main reasons for doing it this way is that the page text
storage changes in MediaWiki 1.5 would make it much harder for a
separate app to get the text by poking directly at the database. Another
of course is that it'll just be easier to push out updates and to handle
page deletions.
Some quick notes:
http://meta.wikimedia.org/wiki/User:Brion_VIBBER/MWDaemon#Updater_daemon
Right now it's just running, indexing new updates. I'll re-pull old
pages and copy out the indexes later today, and set up the regular
pause-and-copy job.
The maintenance script 'luceneUpdate.php' can be used to poke the daemon
for status, to flush indexes, and to stop/start the update applier
thread for queued updates.
If this somehow breaks the site overnight, somebody check for the
include of MWSearchUpdateHook.php in CommonSettings and take it out.
The daemon's log file is in /usr/local/mwsearch/MWUpdater.log on maurus.
-- brion vibber (brion @ pobox.com)
>(however, using the old URLs would likely redirect to the newer style,
> were it implemented.)
It would be best if the redirects were 301 redirects too, I'm not sure
how the Squid servers are set up, but it's pretty easy doing this in
Squid (http://wiki.ehow.com/Implement-Redirects-in-Squid).
This will have an interesting effect on Google Page Rank too. Right
now the current main page has a PR of 9, unless someone at Google
speeds up the process, there'll probably be a delay in transferring
the PR from the old URL to the new URLs, so for awhile the main page
(and all the others) might appear to have a PR of 0, if it matters.
Travis
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
MediaWiki 1.5 beta 3 is a preview release of the new 1.5 release
series, with a security update over beta 2.
Incorrect escaping of a parameter in the page move template could
be used to inject JavaScript code by getting a victim to visit a
maliciously constructed URL. Users of vulnerable releases are
recommended to upgrade to this release.
Vulnerable versions:
* 1.5 preview series: n <= 1.5beta2 vulnerable, fixed in 1.5beta3
* 1.4 stable series: 1.4beta6 <= n <= 1.4.5 vulnerable, fixed in 1.4.6
* 1.3 legacy series: not vulnerable
This release also includes several bug fixes and localization updates.
See the changelog in the release notes for a detailed list.
Release notes:
http://sourceforge.net/project/shownotes.php?release_id=340291
Download:
http://prdownloads.sourceforge.net/wikipedia/mediawiki-1.5beta3.tar.gz?down…
MD5 checksum: ee2abd543d1f23bdb67da87d902cbb09
Before asking for help, try the FAQ:
http://meta.wikimedia.org/wiki/MediaWiki_FAQ
Low-traffic release announcements mailing list:
http://mail.wikipedia.org/mailman/listinfo/mediawiki-announce
Wiki admin help mailing list:
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
Bug report system:
http://bugzilla.wikimedia.org/
Play "stump the developers" live on IRC:
#mediawiki on irc.freenode.net
- -- brion vibber (brion @ pobox.com)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCzNsdwRnhpk1wk44RAkrLAKCZa9XjYcdjbyFdDU+K9MXr3yJHYgCghN1v
QZ22oXJi+jdm1Db2hB2mHR4=
=wTY+
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
MediaWiki 1.4.6 is a bug fix and security update release.
Incorrect escaping of a parameter in the page move template could
be used to inject JavaScript code by getting a victim to visit a
maliciously constructed URL. Users of vulnerable releases are
recommended to upgrade to this release.
Vulnerable versions:
* 1.5 preview series: n <= 1.5beta2 vulnerable, fixed in 1.5beta3
* 1.4 stable series: 1.4beta6 <= n <= 1.4.5 vulnerable, fixed in 1.4.6
* 1.3 legacy series: not vulnerable
This release also includes fixes for some rare bug annoying HTTP errors,
a PHP 4.1.2 breakage bug, and works around some template limitations
introduced in 1.4.5. See the changelog in the release notes for a
detailed list of bugs fixed.
Release notes:
http://sourceforge.net/project/shownotes.php?release_id=340290
Download:
http://prdownloads.sourceforge.net/wikipedia/mediawiki-1.4.6.tar.gz?download
MD5 checksum: f4f82bd486756c279f0c1977b290ce3b
Before asking for help, try the FAQ:
http://meta.wikimedia.org/wiki/MediaWiki_FAQ
Low-traffic release announcements mailing list:
http://mail.wikipedia.org/mailman/listinfo/mediawiki-announce
Wiki admin help mailing list:
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
Bug report system:
http://bugzilla.wikimedia.org/
Play "stump the developers" live on IRC:
#mediawiki on irc.freenode.net
- -- brion vibber (brion @ pobox.com)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCzNsWwRnhpk1wk44RAk3LAJ4/DBDT4Vu6YPIYwYntImUJ/AXBRACfWCsm
PCtY9QynW6h4RnSSShcCSvQ=
=u2ZE
-----END PGP SIGNATURE-----
> does anyone have comments on or object to this change?
Instead of having some name->ip mapping in future distributed
datacenter deployments we'd have to deal with url-based redirection,
what would involve external redirectors or internal hacks.
We should keep it as simple as possible for a while :)
Until we really know what we're doing.
Domas
Forwarding from OTRS in the hope someone on this list has more of an idea
about these problems than the board do.
Angela
---- Forwarded message from Daniël----
> Hello Angela, Jimbo & Florence,
>
> With the upgrade to MediaWiki 1.5 the Dutch Wikipedia was converted to
> UTF-8. This has caused that people using Mac OS 9 are now unable to edit
> the Wiki, because:
>
> * Netscape 4.5 is unsupported
> * Internet Explorer 5 doesn't support Unicode and vandalises pages
>
> Opera 6 seems to support Unicode, is reported to be extremely unstable
> on
> Mac OS9.
>
> I'm not a MacOS user, so perhaps I have forget a browser that runs on
> OS9,
> but this currently looks like an unsolvable problem.
>
> Do you have any experience with this?
TicketID=36280
I meant the page content, mainly - articles content. I got how can I
change the content of static parts like header and footer (by editing
skin scripts). But now the actual problem is how to change the content
of dynamic parts of content (best of all articles of Wikipedia).
Rowan Collins wrote:
>On 05/07/05, Nicolay A. Vasiliev <nvasiliev(a)whiteriversoft.com> wrote:
>
>
>>>presuming you are hoping to modify that output in
>>>some way, there may be an earlier stage of processing which your
>>>modification would conceptually fit into more neatly.
>>>
>>>
>>>
>>You're right - I try to do this. So, I'd like to know where is this point.
>>
>>
>
>What I meant was, what is it you are trying to modify? The HTTP
>headers? Some element of the skin? Some element of the page content
>itself? The "behaviour" of certain content? Any of these things
>*could* be done by altering the final output, but in each case there
>would be a better place to make your change - the code isn't
>brilliantly organised, but it at least attempts to organise the
>process into conceptual stages. If you describe what you're trying to
>achieve, I or someone else may be able to point you to the best part
>of the code to modify.
>
>
>