Dear MediaWiki Hackers ,
WikiMedia Israel is pleased to announce a second Hackathon in Tel Aviv.
If anyone is staying in Israel or Visiting for Xmas consider joining us at a
developer conference and will be held in the hackaton format - (less
lectures and more coding, adding features and fixing pesky bugs. )
On the hour, every hour we will host lightning talk in a subject related to
wiki technology or research. (lightning talks are about 5 minutes long) Some
of the slots are currently open - so let us know if you have some
interesting updates ?
Schedule:
10:00 - Start and Registration.
10:30 - Opening Words and Setting up teams.
>From this point on we will code in teams with short breaks for meals and
brief lightning talks (5 minutes)
12:00 - Lightning talk on MediaWiki Eco system.
13:00 - Lightning talk on Google summer of code.
14:00 - Lunch
15:00 - Lightning talk on translation, internationalization and
localization.
16:00 - Lightning talk on (Suggest a subject) .
17:00 - Lightning talk on (Suggest a subject).
At this point we suggest you prepare a demo on what you have developed or
learned.
18:00 - Lightning talk on (Suggest a subject).
19:00 - Dinner.
19:30 - Demos.
22:00 - Closing.
http://www.meetup.com/MediaWiki-TLV/ English registration
http://www.wikimedia.org.il/events/hackathon-2013/ Hebrew registration
Any questions can be directed to me at
OrenBochman(a)gmail.com
---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com
Hey all,
Several MediaWiki extensions, such as Maps and Semantic MediaWiki, are now
installable via Composer. Lately I've been getting quite a few questions
from developers on how to have their extensions support this awesome
dependency manager, and decided to write down the most important points
that are not obviously evident in the Composer documentation down.
http://www.bn2vs.com/blog/2013/11/24/introduction-to-composer-for-mediawiki…
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil. ~=[,,_,,]:3
--
Hello guys,
I'm starting some conversations here in Brazil about the GLAM and other
touristic ideas under the Brazilian Education Program.
So, we are very interested to use the QRCodes linking to wikipedia
articles, so we are evaluating QRpedia.
Since the QRpedia is running as an external project in an external domain,
it is reliable and stable to use in that kind of project?
There are any plans to have that "service" running officially on Wikimedia's
servers?
There are any way to have it running on the http://tools.wmflabs.org/server ?
Best regards
--
*Rodrigo PadulaEducation Program Coordinator - Brazil**Consultant for the
Brazilian Catalyst Program at Wikimedia Foundation*
*+55 21 9326 0558Blog: http://www.rodrigopadula.com
<http://www.rodrigopadula.com>Twitter: @rodrigopadula*
Hey all,
I'm currently working on the new Capiunto MediaWiki extension[1], which
adds infobox functionality to Scribunto (and the MediaWiki parser in
general).
The Capiunto extension uses the HtmlBuilder Lua module[2] originally
from enwiki to create the Infobox html. The HtmlBuilder provides general
support for creating html in an easy and flexible way (maybe comparable
to jQuery in JavaScript). Because of this and because it doesn't really
fit into Capiunto we consider adding it directly to Scribunto. That way
one could access its functionality directly as (maybe) mw.html.
Prior to adding it to Scribunto I will review, document and write unit
tests for the module.
I hope you agree that this module is nice to have and that it fits into
Scribunto best.
Cheers,
Marius
1 https://www.mediawiki.org/wiki/Extension:Capiunto
2 https://en.wikipedia.org/wiki/Module:HtmlBuilder
Hi all,
We at ShoutWiki (http://www.shoutwiki.com/) updated from MediaWiki 1.21 to
MediaWiki 1.22 earlier today. The upgrade went mostly smoothly, save for
some smaller issues, but afterwards we ran into one major issue: user
preferences are not being saved.
When a user updates their preferences via [[Special:Preferences]], the
special page claims that the changes were saved correctly, but this is not
the case. It seems that the only entries saved to user_properties are
'variant' and 'watchlisttoken'.
Setting a preference via eval.php seems to work:
> $u = User::newFromName( 'Jack Phoenix' ); $u->setOption( 'signature',
'set via a CLI script' ); $u->saveSettings(); $dbw = wfGetDB( DB_MASTER );
$dbw->commit(); echo $u->getOption( 'signature' );
set via a CLI script
> $u = User::newFromName( 'Jack Phoenix' ); echo $u->getOption( 'signature'
);
set via a CLI script
...but this is an optical illusion. Visiting any wiki page seems to reset
the preferences to their defaults.
We've diffed /includes/specials/SpecialPreferences.php,
/includes/Preferences.php and /includes/User.php but nothing overly
suspicious has come up.
ShoutWiki uses quite many extensions (see, for example,
http://www.shoutwiki.com/wiki/Special:Version), some of which are yet to be
released, but as far as I'm able to see, none of these mess with the
preferences stuff. Unlike the defaults in /includes/DefaultSettings.php,
the user_properties table is _not_ shared on ShoutWiki. Our essential
configuration files are also published online at
http://www.shoutwiki.com/conf/ .
Needless to say that this bug doesn't seem to manifest itself at least on
my local development setup, only on production.
Anyone got any clues as to what might be causing this and how to fix it? If
we're not able to fix this soon, we're forced to roll back the 1.22 change,
because our users are rather fond of their preferences, obviously.
Thanks and regards,
--
Jack Phoenix
MediaWiki developer
i glad the new v1.22 is come out,but after upgrade,my code is not function
any more,what happen in here
$authUrl = "xxxx datamarket.accesscontrol.windows.net/v2/OAuth2-13/
";
$options = array();
$options['method'] = 'POST';
$options['timeout'] = $this->config['timeout'];
$options['postData'] = array(
'grant_type' => "client_credentials",
'scope' => "http://api.microsofttranslator.com",
'client_id' => $clientID,
'client_secret' => $clientSecret
);
$options['postData'] = $params;
$req = MWHttpRequest::factory($authUrl, $options);
$status = $req->execute();
after upgrade mw 1.22
i got this error
[error] PHP Warning: curl_setopt_array() [<a
href='function.curl-setopt-array'>function.curl-setopt-array</a>]: Array
keys must be CURLOPT constants or equivalent integer values in ...
Dear all,
I am happy to announce the availability of the first stable release of the new MediaWiki 1.22 release series.
MediaWiki 1.22 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.22 file for the full list of changes
in this version.
Our thanks to everyone who helped to improve MediaWiki by testing the release candidates and submitting bug reports.
== What's new? ==
MediaWiki 1.22 includes all changes released in the smaller 1.22wmfX software deployments to Wikimedia sites.
=== Anti-spam and countervandalism improvements ===
We're improving countervandalism and anti-spam features:
* The patrolling system has been improved to make the "mark as patrolled" link available on any patrollable page or revision, without having to go to Special:RecentChanges or Special:NewPages. It is no longer necessary to look up the "rcid" URI parameter from these special pages. (Bug 15936)
* Extension:SimpleAntiSpam, a small but harmless shield against the simplest forms of spambots, has been merged into core.
===Editing improvements===
* When comparing revisions in the history or when previewing changes while editing, "(No difference)" is now shown in place of a diff when the revisions are identical. (Bug 14431)
* After a successful edit, the confirmation message "Your edit was saved." is now shown. Formerly a separate extension (Extension:PostEdit), this feature is now part of the core software. (Bug 48276)
===Upgrades to Vector and other skins===
The old Vector extension has been merged into core, and the extension has been discontinued. The new version includes several improvements to both the Vector skin and cross-skin features. (Bug 45051) If you were previously using the Vector extension, you must uninstall it (the extension, not the skin) before upgrading to 1.22.
All skins:
* Section edit links are now displayed next to their respective headings rather than along the opposite side of the page. (Bug 41729)
* Lists of templates and categories used on the page, displayed below the edit form, are now collapsible. The area with license information, edit summary, and related functionality below the edit field has received a minor graphical lift. (Bug 43689)
* An "edit warning" is now displayed when the user attempts to leave the edit page with unsaved changes, on browsers supporting dialogs.
* Vector skin only:
** Navigation menu subsections are now collapsible.
** Page tabs can now dynamically fold into a dropdown menu when the browser window isn't wide enough to fit them.
===Support for Composer===
The Composer PHP dependency manager can now be used to install some extensions. It solves many common problems, including finding where to download an extension, resolving all of its dependencies and libraries, and selecting the right versions. Most MediaWiki extensions do not currently support Composer, but this is expected to change.
==Upgrade notices for MediaWiki administrators==
As with every release, there are some routine maintenance and upgrade tasks that go beyond the primary installation process.
===PHP JSON extension now required===
Though the minimum PHP version is still 5.3.2, MediaWiki now requires either the native JSON extension or the pecl-json-c fork. Most servers already have this PHP extension installed and enabled. However, if you administer your own server, and the MediaWiki installer says you don't have this extension:
* If you compiled PHP yourself with the --disable-all configure option, you may have to recompile with --enable-json.
* On Red Hat or CentOS, check for the line extension=json.so in /etc/php.ini or /etc/php.d/json.ini.
* Ubuntu 13.10, Fedora 19, and other recent Linux distributions package pecl-json-c separately, under names such as php5-json (Ubuntu universe) and php-pecl-jsonc (Fedora). They no longer include the original JSON extension because of licensing concerns.
=== Several ancient skins removed ===
On April 1, 2013, several ancient skins were removed from core (not an April Fools' joke): Chick, Classic, MySkin, Nostalgia and Simple.
Nostalgia was the phase I/UseModWiki-like skin, and Classic was the main skin before the introduction of the default MonoBook in MediaWiki 1.3 on May 22, 2004. Dating back to February 2002 both skins existed over a year before MediaWiki got its name.
=== Blank system messages must be deleted ===
Blanking a system message (editing it on wiki to remove all content) will no longer restore the default value for the message, but instead make it show as an empty string in the interface (fixing Bug 14176, "Add ability to disable MediaWiki messages"). If you have blank messages on your wiki (check Special:AllMessages), you must delete them unless you want them to display as empty.
===Protection rights usage has changed===
A new setting ($wgCascadingRestrictionLevels) was added for enabling cascading protection for protection levels other than "Allow only administrators" (Bug 47617). Shortly afterward, the way the "editprotected" and "autoconfirmed" rights work was changed. In particular, the "autoconfirmed" right is now only used for rate limiting, not page protection. If your wiki has custom user groups with the "autoconfirmed" right, you may need to grant those groups the new "editsemiprotected" right when you upgrade.
===Special:Disambiguations has been removed===
Special:Disambiguations, a page that listed "Pages linking to disambiguation pages", has been removed (Bug 35981). If your wiki used this feature, consider using Extension:Disambiguator. Switching to the new extension is easy and generally only requires a small change to a single template.
=== Bundled extensions ===
Newly bundled for 1.22:
* SimpleAntiSpam
Full release notes:
https://git.wikimedia.org/blob/mediawiki%2Fcore.git/1.22.0/RELEASE-NOTES-1.…https://www.mediawiki.org/wiki/Release_notes/1.22
**********************************************************************
Download:
http://download.wikimedia.org/mediawiki/1.22/mediawiki-1.22.0.tar.gz
GPG signatures:
http://download.wikimedia.org/mediawiki/1.22/mediawiki-1.22.0.tar.gz.sig
Public keys:
https://www.mediawiki.org/keys/keys.html
----
Markus (mglaser)
Hey,
A while back I created a properly segregated interface for turning message
keys into messages. Since I've seen someone create almost the exact same
thing, and now ended up needing such an interface in another project as
well, I decided to put this into its own little library.
https://github.com/JeroenDeDauw/i18n
At this time, only msgText is exposed in the general interface, as this is
the only thing I've needed so far. This can easily be extended for other
use cases though. Just released version 0.1 of this library, which is fully
tested, and is installable via Composer.
Hope this is of use to some people, and of great amusement to those who do
not understand interface segregation and IoC.
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil. ~=[,,_,,]:3
--