Now that Sam has announced the 1.18 Release Candidate, we'd like to make
sure that we've created a tarball that will work.
Please give 1.18RC1 a try and add your experience to
<http://www.mediawiki.org/wiki/MediaWiki_roadmap/1.18/Upgrade_reports>.
I just upgraded one of the wikis I maintain from 1.15 and recorded my
experience. Of course, as Sam writes in his announcement, you should
probably not do this on a production wiki "unless you are both very
brave and very confident in your MediaWiki administration skills." So,
maybe you'll want to try it in a test installation.
That said, let us know of your successes!
Of course, we'd like to know about failures, too, and that page is an
appropriate place to report them (in addition to bugzilla), but we
really need to know if this release is as good as we think it is.
Thanks,
Mark.
I'm happy to announce the availability of the first release candidate of
the new MediaWiki 1.18 release series.
Please try it out and let us know what you think. Don't run it on
any wikis that you really care about, unless you are both very
brave and very confident in your MediaWiki administration skills.
MediaWiki 1.18 is a large release that contains many new
features and bug fixes. This is a summary of the major changes of
interest to users. You can consult the RELEASE-NOTES file for the
full list of changes in this version.
*********************************************************************
What's new?
*********************************************************************
MediaWiki 1.18 brings the usual host of various bugfixes and new
features.
jQuery 1.6.4 is now included as standard, along with numerous
more jQuery plugins.
Breaking changes:
* action=watch / action=unwatch now requires a token
As of 1.18, some extensions are now being bundled with the released tarball.
The following extensions are bundled with MediaWiki as of 1.18. All are
currently in use
on Wikimedia sites.
* ConfirmEdit - Various CAPTCHA techniques to try to prevent spambots and
other automated tools from editing your wiki.
* Gadgets - A system to allow users to enable or disable JavaScript or
CSS tools made available to users site-wide.
* Nuke - A special page allowing administrators to mass-delete content
added by a spammer or vandal.
* ParserFunctions - Additional parser functions (like #if and #switch to
supplement the "magic words" present in MediaWiki.
* Renameuser - A special page which allows authorized users to rename
user accounts.
* Vector - Enhancements to the Vector skin.
* WikiEditor - An improved and customizable editing toolbar developed
along the Vector skin.
Major features
- --------------
Better gender support
-- ---------------------
Until version 1.17, MediaWiki used neutral nouns to address and identify
users on their user page.
In English, this was not an issue since "User" matches both genders, but in
some languages the
neutral gender is always masculine; for example, this would cause
French-speaking female
Wikipedia users to be referred to as "Utilisateur" (male user) instead of
"Utilisatrice" (female user).
With version 1.18, user pages reflect the user's gender, if they have
specified it in their preferences.
More gender support (for instance in logs and user lists) will be available
in MediaWiki 1.19.
Improved file metadata support
-- -----------------------------
MediaWiki now detects the camera orientation from Exif metadata, and
rotates the picture
preview accordingly. The original file remains unchanged.
The overall metadata support in MediaWiki has been greatly extended.
Previously, MediaWiki could only
extract limited Exif metadata, and showed a subset of it on file
description pages. Since 1.18, MediaWiki
can extract IPTC and XMP metadata from uploaded files, and more Exif
information. This includes an
embedded description, author information, GPS coordinates, or copyright
statement.
Improved directionality support
-- -------------------------------
A lot of work has been done to fix directionality bugs (Left-To-Right,
Right-To-Left). Most notably bug 6100 is
fixed, which allows to display an RTL interface on an LTR wiki properly (and
vice versa). This was developed
under $wgBetterDirectionality, which is now no longer used because the
improvements are merged
with the core code.
A positive consequence is that the page content on wikis with multiple
scripts is aligned according to the
direction of the selected variant. For example, on a Kazakh language wiki,
selecting the Arabic script
variant will align the text as RTL, while selecting the Latin or Cyrillic
variant will align it as LTR.
Easily find where to customize interface messages
-- ---------------------------------------------
MediaWiki allows you to customize the user interface by editing pages in the
MediaWiki namespace.
However, even though they can be viewed at Special:AllMessages] the sheer
number of these messages
makes it difficult to find which one needs to be customized. In MediaWiki
1.18, a new pseudo-language
is introduced (qqx) to help people find such messages, by displaying the
messages' key instead of the
actual messages. All one has to do is append ?uselang=qqx to the page's
index.php/
URL (see
https://www.mediawiki.org/w/index.php?title=MediaWiki_1.18&uselang=qqx as an
example).
New plugin for collapsible elements
-- -----------------------------------
The new jQuery.makeCollapsible allows you to create collapsible tables,
lists and so on,
by adding the class mw-collapsible to the elements.
See the manual for details:
https://www.mediawiki.org/wiki/Manual:Collapsible_elements
Protocol-relative URLs
-- ----------------------
MediaWiki now supports protocol- relative URLs in links, interwiki targets
and $wgServer.
Protocol-relative URLs look like //example.com/wiki/Foo ; the browser will
recognize this
as http://example.com/wiki/Foo when following a link from an HTTP page, and
https://example.com/wiki/Foo when following a link from an HTTPS page.
This way, protocol-relative URLs enable a wiki to support HTTP and HTTPS
while serving
the same HTML for both, which means the parser cache doesn't have to be
split.
More personalisable styles and scripts
-- --------------------------------------
MediaWiki now automatically loads javascript and stylesheets more specific
to each user.
There is a separate CSS and JS file for each usergroup
(MediaWiki:Group-sysop.css,
MediaWiki:Group-autoconfirmed.js, etc), and also a CSS file for users
viewing without
JavaScript (MediaWiki:Noscript.css).
Other changes
-- -------------
$wgEnableDublinCoreRdf and $wgEnableCreativeCommonsRdf no longer
work in core, and the functionality has been moved to the relevant
extensions.
See http://www.mediawiki.org/wiki/Extension:DublinCoreRdf and
http://www.mediawiki.org/wiki/Extension:CreativeCoreRdf as appropriate
Math
- ----
$wgUseTeX has been superseded by the Math extension. To re-enable
math conversion after upgrading, obtain the Math extension from SVN or from
http://www.mediawiki.org/wiki/Extension:Math and add to LocalSettings.php:
require_once "$IP/extensions/Math/Math.php";
Language support
- ----------------
As with every release, MediaWiki 1.18 brings improved support for
languages in MediaWiki, with improved translation and features for
the many supported languages.
New languages:
* Angika (anp)
* Brahui (brh)
* Central Dusun (dtp)
* Jamaican Creole English (jam)
* Khowar (khw)
* Liv (liv)
* Kichwa (qug)
API
- ---
API bug fixes and new features have been added to 1.18, providing
more options for input and output.
* API modules were added to access QueryPage based special
pages, to Compare pages, Revert files, and to be able to access
other special pages such as Special:UnwatchedPages,
Special:MimeSearch and Special:ActiveUsers
* The output of the generated help page has been improved
The API contains a breaking changes against previous releases:
* action=watch now requires POST and token.
Other
- -----
Our thanks go to everyone who helped to improve MediaWiki
by testing the beta release and submitting bug reports and patches.
Release notes
- -------------
Complete release notes are at
http://www.mediawiki.org/wiki/Release_notes/1.18
**********************************************************************
Download:
http://download.wikimedia.org/mediawiki/1.18/mediawiki-1.18.0rc1.tar.gz
Patch to previous version (1.18.0beta1), without interface text:
http://download.wikimedia.org/mediawiki/1.18/mediawiki-1.18.0rc1.patch.gz
Interface text changes:
http://download.wikimedia.org/mediawiki/1.18/mediawiki-i18n-1.18.0rc1.patch.
gz
GPG signatures:
http://download.wikimedia.org/mediawiki/1.18/mediawiki-1.18.0rc1.tar.gz.sighttp://download.wikimedia.org/mediawiki/1.18/mediawiki-1.18.0rc1.patch.gz.si
g
http://download.wikimedia.org/mediawiki/1.18/mediawiki-i18n-1.18.0rc1.patch.
gz.sig
Public keys:
https://secure.wikimedia.org/keys.html
Some of our Windows 7 computers (running IE8) are unable to log into MediaWiki 1.17.0 at my company. The wiki login page complains that cookies need to be enabled (but they are). Anybody else seen & solved this?
It's only Windows 7 with IE8.
Thanks,
DanB
Forwarding this to mediawiki-l since this will probably have wider
interest than just wikitech-l. The Wikitech discussion can be seen
here:
http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/56572
Antoine Musso <hashar+wmf(a)free.fr> writes:
> Hello,
>
> PHP 5.2.6 and earlier have a bugs that prevents us from appending text
> to php://stdout . See [PHP 45303].
>
> We need to open php:// file descriptors in append mode (a) when running
> the web installer or we have a nice error caused by the output buffer
> being reset [BUG 31822] fixed by [r101644].
>
> By bumping our PHP version requirement to 5.2.7 we no more have that
> buffer reset issue. Maintenance scripts will throw a warning though [BUG
> 32325] [BUG 32263].
>
> Debian stable provides PHP 5.3.3.
> I am pretty sure Mac OS X 10.6 provide a PHP version after 5.2.6.
>
> 1.17 bumped requirement to PHP 5.2.3
> Can we bump it again for 1.18 ?
>
>
> References:
> [PHP 45303] https://bugs.php.net/bug.php?id=45303
> [BUG 31822] https://bugzilla.wikimedia.org/show_bug.cgi?id=31822
> [r101644] https://www.mediawiki.org/wiki/Special:Code/MediaWiki/101644
> [BUG 32325] https://bugzilla.wikimedia.org/show_bug.cgi?id=32325
> [BUG 32263] https://bugzilla.wikimedia.org/show_bug.cgi?id=32263
--
Mark A. Hershberger
Bugmeister
Wikimedia Foundation
mhershberger(a)wikimedia.org
717.271.1084
We have been experiencing problems with MW 1.16.2 related to logged in
users on client machines where the IP address changes. I have looked over
the Bugzilla reports but could not find anything obviously related.
If a user with a laptop logs into the wiki, puts the laptop to sleep,
moves to a different location and then attempts to continue processing,
the logs show his changes mapped to an IP address (or on one of our wikis
as anonymous), rather than his user name. A simple thought experiment
suggests the cookie presented to the wiki after the laptop move has a
different IP address than the request message. This confuses MW, giving
the user all his permissions (since he is logged in), but not properly
identifying the user's name in the logs.
Has anyone else observed this and if so, are there ways to address this
issue?
--
-- Dan Nessett
Just to remind you:
* India hackathon (18–20 November, Mumbai, India) — Alolita Sharma,
Siebrand Mazeland, Sumana Harihareswara and the local India team are
preparing for this event, which will focus on language, mobile and
offline support for MediaWiki content. You can register to request a
free invitation; approximately 100-125 attendees are expected.
https://www.mediawiki.org/wiki/India_Hackathon_2011
* Brighton hackathon (19–20 November, Brighton, England) — Free
registration is open for the general MediaWiki hackathon planned by
Lewis Cawte. You can register online. WMF engineers Antoine Musso, Roan
Kattouw, and Sam Reed plan to attend.
https://www.mediawiki.org/wiki/Brighton_Hackathon_2011
--
Sumana Harihareswara
Volunteer Development Coordinator
Wikimedia Foundation
---------- Forwarded message ----------
From: Nicholas Washington <washington367(a)gmail.com>
Date: 2011/11/10
Subject: HELP
To: mediawiki-l-owner(a)lists.wikimedia.org
*Hi, I just recently got on board with MediaWiki and am looking forward to
utilizing its functionality for use with a story I am in the process of
writing.
Upon installation, I noticed I am unable to access my wiki main page, nor
am I able to edit it because of a DATABASE ERROR. After temporarily adding
the function: $wgShowSQLErrors =true; It reads precisely as follows:*
*DATABASE ERROR*
A database query syntax error has occurred. This may indicate a bug in the
software.
The last attempted database query was:
SELECT log_type,log_action,log_user,
log_namespace,log_title,log_params,log_comment,
log_id,log_deleted,log_timestamp,user_name,user_editcount,
ts_tags FROM `logging` FORCE INDEX (page_time,user_time) INNER JOIN `user`
ON
((user_id=log_user)) LEFT JOIN `tag_summary` ON ((ts_log_id=log_id))
WHERE (log_action != 'revision') AND (log_type != 'suppress') AND log_type
IN ('delete','move')
AND log_namespace = '0' AND log_title = 'Main_Page' AND ((log_deleted & 9)
!= 9) AND
(user_id = log_user) ORDER BY log_timestamp DESC LIMIT 11
from within function "IndexPager::reallyDoQuery (LogPager)".
Database returned error "1176: Key 'user_time' doesn't exist in table
'logging' (localhost)".
*To be perfectly honest I have no idea what this means. I've attempted to
re-install mediawiki only to arrive at the same dead end. From what I can
tell, something seems to be missing, but I'm no tech guru or anything. Any
help on this matter would be much appreciated!*
Thanks, Nick.
--
Kind regards,
Huib Laurens
WickedWay.nl
Webhosting the wicked way.
Hi,
I'm looking for a hook that is called when the text of an article is
parsed because of a cache miss.
On IRC I was told to use one of the hooks called by Parser::parse, but I
am not sure that's the solution:
* Parse is also called on cached pages, e.g. to render the 'This page
has been accessed xxx times.' message.
* There seems to be no elegant way to recognize if the text to parse is
the actual Article content.
Currently I hook into ParserBeforeTidy, use a static variable to ensure
the method is executed only once and create a Revision object to get at
the article text. The method is always run regardless of whether there
was a cache miss or not.
There should be an easier and more elegant way to do this, right?
Cheers,
Stephan
Howdy,
I just found that the extension Multilang is broken and does not display anything. :-(
I wanted to create some small templates with it that get autotranslated, so
{{composer}} would yield in “Komponist”, “композитор” or just “composer”, depending on the selected language. Is there any other way to do this?
How is it done on commons.wikimedia.org?
Thanks,
Thomas
--
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
FYI: The WorkingWiki extension [1] can be used to plug in any number of
math systems into a MW wiki, including Sage, Octave, Mathematica, etc.
For instance, one you install WW and add a simple makefile rule of the form
> %.sage.out : %.sage
> (command-line operation here)
you can write the following in the wiki page:
<source-file filename="example.sage" display="example.sage.out">
1+2+3
</source-file>
and the number 6 will appear in the output wiki page. You can
alternatively have it produce a %.sage.html or %.sage.wikitext file to
customize the output, and you can set a default display rule so you
don't have to write the display= attribute.
At McMaster we primarily use it with R programs, but also with python,
maxima, and other things.
lw
[1] http://lalashan.mcmaster.ca/theobio/projects/index.php/WorkingWiki
On 11/09/2011 12:41 AM, mediawiki-l-request(a)lists.wikimedia.org wrote:
> Date: Tue, 8 Nov 2011 18:15:45 -0800 (PST)
> From: badon<fastgoldfish(a)gmail.com>
> Subject: Re: [Mediawiki-l] Wikipedia Feature Suggestions (Inline
> Calculations)
> To:mediawiki-l@lists.wikimedia.org
> Message-ID:<32808226.post(a)talk.nabble.com>
> Content-Type: text/plain; charset=us-ascii
>
>
> That is one of the neatest ideas I have heard in a while. If you make an
> extension, please consider making it general enough that many different math
> systems can be plugged into it. My vote is for mathematica, but there are
> many, many others - including a few free and open source packages. Here's a
> good starting point for finding them all:
>
> http://en.wikipedia.org/wiki/Mathematical_software
>
>
>
>
> John W. Foster-2 wrote:
>> >
>> > On Mon, 2011-11-07 at 22:36 -0800, badon wrote:
>>> >> There is this extension, which seems to be designed to do what you're
>>> >> asking
>>> >> for:
>>> >>
>>> >> http://www.mediawiki.org/wiki/Extension:CalcII
>>> >>
>>> >> However, it is quite old and probably in need of updating. Nonetheless,
>>> >> you
>>> >> can give it a try to see if it works for you. Also, if you're inclined to
>>> >> do
>>> >> so, you could get involved in updating and maintaining the extension. I
>>> >> agree, it would be a very nice thing to have for MediaWiki.
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> Jeff Brubaker wrote:
>>>> >> >
>>>> >> > Hi,
>>>> >> > I'm a mechanical engineer and I've been trying online calculations.
>>>> >> > I'd like the ability to integrate calculators directly into wikipedia.
>>>> >> > I think this live attribute would be a great asset to engineers. I put
>>>> >> > an example up at
>>>> >> > http://www.novanumeric.com/wiki/index.php/Quadratic_Formula I did that
>>>> >> > using an iframe though. Is there a better to implement this?
>>>> >> >
>>>> >> > Regards,
>>>> >> > Jeff Brubaker
>>>> >> >
>>>> >> > _______________________________________________
>>>> >> > MediaWiki-l mailing list
>>>> >> > MediaWiki-l(a)lists.wikimedia.org
>>>> >> > https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>>>> >> >
>>>> >> >
>>> >>
>> >
>> > -------------------------
>> > I too would have an interest in something like this as well. I have a
>> > site that we are building that is for folks interested in cutting edge
>> > physics. This might provide an interesting tool for us as well. Perhaps
>> > something that would link into a real mathematics system even.
>> > I,m going to look into this also.
>> > Thanks for the link& the idea.
>> > frosty
>> >
>> >
>> > _______________________________________________
>> > MediaWiki-l mailing list
>> > MediaWiki-l(a)lists.wikimedia.org
>> > https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>> >
>> >
> -- View this message in context:
> http://old.nabble.com/Wikipedia-Feature-Suggestions-%28Inline-Calculations%…
> Sent from the WikiMedia General mailing list archive at Nabble.com.