I am happy to announce the availability of the first stable release of the new MediaWiki 1.23 release series.
MediaWiki 1.23 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-1.23 file for the full list of changes in this version.
This is a Long Term Support release (LTS) and will be supported until May 2017.
Our thanks to everyone who helped to improve MediaWiki by testing the release candidates and submitting bug reports.
== What's new? ==
* MediaWiki 1.23 includes all changes released in the smaller 1.23wmfX software deployments to Wikimedia sites.
=== Skin autodiscovery deprecated ===
Skin autodiscovery, the legacy skin installation mechanism used by MediaWiki since very early versions (around 2004), has been officially deprecated and will be removed in MediaWiki 1.25.
* MediaWiki 1.23 will emit warnings in production if a skin using the deprecated mechanism is found.
* See Manual:Skin autodiscovery for more information and a migration guide for site admins and skin developers.
=== Notifications ===
With 1.23, MediaWiki starts to behave more like a modern website as regards notifications, to keep the editors of your wiki engaged and always up to date about what interests them. This used to require several custom settings.
* (bug 45020) Make preferences "Add pages I create and files I upload to my watchlist" and "pages and files I edit" true by default.
* (bug 45022) Make preference "Email me when a page or file on my watchlist is changed" true by default.
* (bug 49719) Watch user page and user talk page by default.
This will allow your new users to immediately start benefiting from the watchlist and email notification features, without needing to first read all the docs to find out that they're as useful as they are.
=== Merged extensions ===
Merged into 1.23:
* ExpandTemplates (bug 28264).
* AssertEdit (bug 27841) - documented at API:Assert.
=== Interface ===
* (bug 42026) Add option to only show page creations in Special:Contributions (and API).
* Add new special page to list duplicate files, Special:ListDuplicatedFiles.
* (bug 60333) Add new special page listing tracking categories (Special:TrackingCategories).
=== Editing ===
* A new special page Special:Diff was added, allowing users to create internal links to revision comparison pages using syntax such as Special:Diff/12345, Special:Diff/12345/prev or Special:Diff/12345/98765.
=== Help pages ===
With 1.23, MediaWiki begins a process of consolidation of its help pages. Now, most are using the Translate extension and can be easily translated and updated in hundreds languages.
In the coming months, we'll focus on making more of the central help pages translatable and on linking them from the relevant MediaWiki interfaces for better discoverability. Please help: add your own translations; update existing pages and cover missing MediaWiki topics.
Traditionally, help pages have been scattered on countless wikis and poorly translated; most of those on mediawiki.org were migrated with the help of some Google Code-in students.
=== CSS refresh for Vector ===
* Various Vector CSS properties have been converted to LESS variables.
* The font size of <code>#bodyContent</code>/<code>.mw-body-content</code> has been increased to 0.875em.
* The line-height of <code>#bodyContent</code>/<code>.mw-body-content</code> has been increased to 1.6.
* The line-height of superscript (sup) and subscript (sub) are now set to 1.
* The default color for content text (but not the headers) is now #252525; (dark grey).
* All headers have updated sizes and margins.
* H1 and H2 headers now use a serif font.
* Body font is "sans-serif" as always.
For more information see Typography refresh.
=== Configuration ===
Add Config and GlobalConfig classes:
* Allows configuration options to be fetched from context.
* Only one implementation, GlobalConfig, is provided, which simply returns $GLOBALS[$name]. There can be more classes in the future, possibly a database-based one. For convinience the "wg" prefix is automatically added.
* This adds the $wgConfigClass global variable which is used to determine which implementation of Config to use by default.
* The ContextSource getConfig and setConfig methods were introduced.
Full release notes:
Platform is CentOS.
MW version 1.20.2
PHP 5.4.29 (apache2handler)
I want to upgrade (long overdue) to MW 1.22.7 .
Backed up the files and DB. did "php update.php" returns no errors.
I didn't upgrade the extensions because I have lots of them, and have found
this the hardest part of upgrades. (I guess I was hoping they would work).
Reloaded existing (old) LocalSettings.php
All the above done from command line.
Result: blank wiki. My thinking (funny how writing this out causes a better
thought process) is that my old extensions are causing the problem(s).
I think I should try to delete extensions from LocalSettings.php and see how
that improves the situation. I believe however I have extensions that possibly
have not been updated and I'll be missing some extension functions I was relying on.
Yet I'll be happy to have the ability to add new ones (a bit of work for sure).
My main objective is to get Semantic Wiki folded into the mix.
Any comments quite welcome, and thank you for any help in advance.
(PS. I'm able to revert to old setup due to careful backups of files. update.php update
for 1.22.7 doesn't seem to harm the reversion to 1.20.2).
Also, so much work has been done on 1.20.2 that I'm loathe to lose the
extensions that were part of that work, if they're out of date with 1.22.7 .
Rob Lingelbach http://rob.colorist.orghttp://colorist.org rob(a)colorist.org
I'm Giacomo and in the company I'm working for we're using Mediawiki
1.18.1 with the Semantic Bundle installed ( version 20120327, Semantic
Media Wiki version 1.7.1 ).
We recently tried to upgrade mediawiki to version 1.22 and Semantic
Media Wiki to version 1.9.1 and now we are facing a problem with a
the library is called Sgvizler (http://dev.data2000.no/sgvizler/) and
it's used to query a Sparql endpoint and visualize the results using the
visualization libraries (
As explained in the sgvizler documentation, inserting a div tag with the
correct attributes, the library will draw the requested charts; you just
need to import the sgvizler.js file and the script for the google api
Calling the sgvizler library from an html test page it works just fine,
while if we put the html code (see the attached file) inside a wiki page
(between <html>...</html> tags, setting $wgRawHtml=true in
LocalSettings.php) the browser freezes and stop responding ("script
stopped responding") (both Firefox and Chrome).
It should be noticed that the same wiki page with the same content is
correctly rendered in mediawiki 1.18.1, using the extension Widgets
(version 0.9.2); in mediawiki 1.22.7 we tried the library embedding it
in extesion Widgets version 0.9.2, 1.0 and 1.1, and also without using
Widgets (as depicted above).
libraries, since the sparql endpoint receives the query and the results
are sent back correctly.
Debugging, the execution seems to stop/loop on the Script:
Since the library is working just fine with mediawiki 1.18.1, could the
issue have something to do with resources/libraries loaded in mediawiki
1.22? I noticed that in the mw 1.22 source page there are these lines in
while in mw 1.18 we just have:
What are your suggestions to track down this problem?
Thank you in advance for any help you can provide.
I am not sure if this is the right place to post my problem - but it seems
to be the best place that I've found so far:
I am using MediaWiki 1.22.6 with PHP 5.4.4-14+deb7u9 (apache2handler) and
MySQL 5.5.37-0+wheezy1. Every time I try to use the extension
CrossReference, lets say with the following example:
Here is a reference to <xr id="fig:my-fig"/> ===
The preview of the created fragment looks fine but after saving the page, I
always get some identifiers instead of the HTML markup, e.g.
Here is a reference to UNIQe2677deae0027008-xr-00000005-QINU
And exactly the same behavior shows up when I use the extension Cite.
Thanks in advance
I am tasked with translating our wiki into a couple of languages. We
have several thousand pages, and just creating all of the sub-pages is a
I've looked at the various translate extensions, and they seem to be
either on the fly, or assisted manual.
Is anyone aware of a translation extension or script that would spider
through the wiki, using Google or MS to translate each page, and create
the appropriate language sub-pages?
I know that human proofreaders would have to go through each page after
that and fix/correct/rewrite the automatic translations, but at least
all of the subpages, with the appropriate images, templates, etc. would
be in place, making the job much, much simpler.
first of all, thanks for the help!
* Now that I got everything up and running I get this error
* "Notice: Uncommitted DB writes (transaction from
DatabaseBase::query (LCStore_DB::get)). in
C:\xampp\htdocs\Entwicklung\includes\db\Database.php on line 3944"
When I click on the log in button on the page it disappears for a while!
I´ll try to explain my problem a little more detailed. So I have my folder in htdocs/wiki @v1.15
Now I´ve downloaded the new version 1.22 and extracted the new files from 1.22 In my 1.15 folder and replaced all those (I have a backup) with the new ones. Now I tried to navigate to the folder in my Browser specified in the update.txt and on the forum. Now when I go to the update.php data I get the error:
"Fatal error: Cannot redeclare wfProfileIn() (previously declared in C:\xampp\htdocs\smartcards\includes\profiler\Profiler.php:33) in C:\xampp\htdocs\smartcards\includes\ProfilerStub.php on line 24"
The file specified in the wiki manual witch may causes errors isn't in my folder so I Can't delete it (StartProfiler.php)
I was trying to upgrade from v.1.15 to 1.22.
So I download the new MediaWiki archive and inserted the data in the
folder to the old 1.15 folder @htdocs/mediawiki
Now when trying to navigate in the browser to the url:
I will only get the error message : "Fatal error: Cannot redeclare
wfProfileIn() (previously declared in
C:\xampp\htdocs\smartcards\includes\ProfilerStub.php on line 24"
Can I get help here please?
Sorry for my English!
I hope someone can help out here.
I have setup MW 1.22.* successfully on a test server of my own but am
now having trouble going into "production" ...
I have a managed Linux server. Via the web panel, I have created a
database and a database user. On the command line, I have to connect to
the database via a form like :
mysql -u user -S /tmp/mysql5.sock -p database
I have to use the "socket" form (-S) or it fails to connect (access
denied). See :
I am trying to set up MW 1.22.7, running the initial setup
(mw-config/index.php) to set up the database I get an error :
1) Using database = localhost
ERROR = DB connection error: Access denied for user: 'dbuser@localhost'
(Using password: YES) (localhost).
2) Using database = localhost:/tmp/mysql5.sock
ERROR = DB connection error: Unknown MySQL server host
'localhost:/tmp/mysql5.sock' (1) (localhost:/tmp/mysql5.sock).
I refererred to this page for the 2nd format above :
"Note: If running MySQL using a different socket file (e.g. mysql on
using --socket=/tmp/mysocketfile), set the database host
to:"localhost:/tmp/mysocketfile". Sometimes sockets are called ports. If
have a port number for your database host, follow the same
I also see a resolved bug (with code I see I have in 1.22.7 (IP.php)) :
mysqli: Non-standard port handling broken (explicit parameter int $port
I tried the command line installer but got problems as well e.g.
> php5.5 maintenance/install.php wikiname admin --pass <pass> \
--dbname <database> --dbserver localhost:/tmp/mysql5.sock --dbuser
<dbuser> --dbpass <dbpass> \
Setting up database
DB connection error: Connection refused (localhost:/tmp/mysql5.sock).
Check the host, username and password and try again.
Does anyone know how I can get MW connected here?