Hello,
I'm using the upload wizard extension
(https://www.mediawiki.org/wiki/Extension:UploadWizard). I would like to
add a custom licence to the choice of licences here. I would be very
grateful if someone could help me along and/or could provide an example
configuration.
I tried the following:
- Installing the extension (good start...)
- Config like described on
https://www.mediawiki.org/wiki/Extension:UploadWizard ("Enabling uploads
and thumbnails ")
...now the fun part, yet unsuccesful;
- LocalSettings.php: added
$wgUploadWizardConfig['licenses']['myown'] = array( 'msg' =>
'mwe-upwiz-license-myown' );
$wgUploadWizardConfig['licensesOwnWork']['licenses'][] = 'myown';
- created a wikipage at "Mediawiki:mwe-upwiz-license-myown" containing
some licence-text
I got the following:
the only output is that I get to see in the interface of the wizard are
text at the place where actually the licence choice should be that
resembles the name of the wikipage with the licence, framed by single
brackets: e.g. "[mwe-upwiz-license-myown-explain]"
Is there somebody who could help along and provide explanation or and
example of how to add a custom licence here?
Cheers,
Jan
Hello, all.
I've always been a big fan of Mediawiki and of free software in general,
but one thing I struggle with in extending the wiki I work on is adding
adding code to the the head of the HTML. ResourceLoader may be terrific
from a performance perspective, but it is an absolute nightmare for this
small scale developer. I'm a self-taught programmer, and my eyes just glaze
over when I look at the documentation. Yet it is something that I often
need to do, for Google Analytics, Google Custom Search, to make a custom
media player (that does what I want it to do), etc.
I'm looking for a short snippet of code - just something that I can paste
into LocalSettings.php that will take the contents of specific variable and
paste it into the head of every HTML page on the wiki. That's it.
I bet it could be done in 10 lines of code and it would be so helpful for
our site. Yet I'm sure it would take me 5 very frustrating hours for me to
figure it out, as I find some of the documentation quite opaque. Would
anyone be willing to program this? I'm happy to pay consulting fees. If you
want to give it away for free after, more power to you.
Forest
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm happy to announce the availability of the first stable release
of the new MediaWiki 1.21 release series.
MediaWiki 1.21 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.21 file for the full list of changes
in this version.
Our thanks go to everyone who helped to improve MediaWiki by testing
the beta release and submitting bug reports.
== What's new? ==
MediaWiki 1.21 includes all changes released in the smaller, bi-weekly
"1.21wmfX" software deployments to Wikimedia sites.
=== Clearer email notifications ===
Bug 14901 ? Email notification mistakes log action for new page
creation, the third most reported open MediaWiki bug, has been
fixed. Consequently, notifications now state clearly what action was
performed on the watched pages in case they are created, deleted,
restored, moved or changed.
There are still some known issues. If you customised MediaWiki:Enotif
body on your wiki, you have to delete or update it; see also full
documentation.
=== Skin ===
The CologneBlue skin has been refactored to make it relevant again,
more compatible with existing scripts, and more similar in structure
to Vector and Monobook, reusing a lot of existing code.
The only major difference for end-users should be a slight reordering
of the sidebar menu (the "Context" submenu was removed and its
contents merged into other ones). If you were, however, depending on
the exact HTML it used to produce, you'll need to review your tools.
=== ContentHandler ===
As part of the Wikidata initiative, 1.21 adopts an extensible
framework ("ContentHandler") so that pages can contain something other
than wikitext.
Right now, built-in content types are limited to
wikitext - wikitext, as usual
javascript - user-provided JavaScript code
css - user-provided CSS code
text - plain text
Extension developers can create additional content
types. Extension:EventLogging uses ContentHandler to implement a
namespace for JSON schemas, and may be used as a reference. Other
extensions, such as Scribunto, also make use of the new functionality.
ContentHandler affects diff rendering, handing of CSS and JavaScript
pages, import/export, and the API.
=== Support for high DPI displays ===
MediaWiki now tries to deliver higher-res images to high pixel density
screens such as Apple Retina Displays (see gerrit change 24115 for
details). This is a work-in-progress, so normal-resolution images may
still appear in some places and in some browser
versions. Administrators may need to watch out for higher load on
their image scaling software.
=== Ajax patrolling ===
(bug 7851) The features users have waited for longest: one-click Ajax
patrolling. With this new feature, users can mark revisions or pages
as having been "patrolled" with a single click while staying on the
current page.
=== Internationalization ===
(bug 24156) The general logging framework was made completely
localisable at last. The logging for each action (whether in core or
extensions) might still need to be updated to use the new system,
though.
(bug 40367) MediaWiki:Contributions now reflects the gender of the
user.
=== New accounts ===
(bug 22457) It's now easier to create accounts for other users by
sending a temporary password via e-mail: Special:CreateAccount now
shows a checkbox for logged-in users to use this feature, rather than
a button.
Account API: bots and other scripts can now use the API to create user
accounts, rather than attempting to pseudo-submit the HTML form.
=== Account creation welcome ===
The MediaWiki:welcomecreation message was split up into
MediaWiki:welcomeuser and MediaWiki:welcomecreation-msg so users no
longer see "Login successful" when creating their accounts (bug
42215). If you customized the former message and want to preserve your
customization, you'll have to modify the new messages accordingly.
=== More wikitext now supported in JavaScript messages ===
The jqueryMsg parser now supports wikilinks and int: transclusion. For
more details, see Manual:Messages API.
=== Using semantic headings for the navigation menu ===
The previous scheme of using (varying per skin) <h4>, <h5> and/or <h6>
tags (with nothing apart from the main <h1> above them in the
hierarchy) was change to consistently using a <h2> above the entire
navigation and <h3>s as portlet headings in all skins.
The <h2> is hidden for normal browsers, but accessible for
screen-readers or text browsers.
While this change is minor, it might require similarly minor updates
in any customized CSS or JS (or in screen scrapers).
=== Extended collation support ===
UCA-based category collations for 68 languages based in Latin, Greek
and Cyrillic alphabets are now supported. You can use them by setting
$wgCategoryCollation = 'uca-<langcode>', where <langcode> is the
appropriate language code.
=== Bundled extensions ===
Newly bundled for 1.21 (bug 43815):
Cite
ImageMap
Interwiki
Title Blacklist
SpamBlacklist
Poem
InputBox
LocalisationUpdate
SyntaxHighlight GeSHi
Full release notes:
https://www.mediawiki.org/wiki/Release_notes/1.21
**********************************************************************
Download:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0.tar.gz
Patch to previous version (1.20.0), without interface text:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0.patch.gz
Interface text changes:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-i18n-1.21.0.patch.gz
GPG signatures:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-core-1.21.0.tar.gz.s…http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0.tar.gz.sighttp://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0.patch.gz.sighttp://download.wikimedia.org/mediawiki/1.21/mediawiki-i18n-1.21.0.patch.gz…
Public keys:
https://secure.wikimedia.org/keys.html
- --
http://hexmode.com/
Imagination does not breed insanity. Exactly what does breed insanity
is reason. Poets do not go mad; but chess-players do.
-- G.K. Chesterson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iD8DBQFRoNaqc17xCi38v/URAgClAJ9YnIT5CLqfbFolRyoG8W7UOF+l6QCfSu5H
p79h+WXqEqs9MgYl1t+ES94=
=shHJ
-----END PGP SIGNATURE-----
Hi, we have now a mailing list dedicated to software quality assurance:
https://lists.wikimedia.org/mailman/listinfo/qahttp://lists.wikimedia.org/pipermail/qa/
Testing is a good activity for new contributors, improving the quality
of the software used by MediaWiki sysadmins and users. No prior
experience in testing / QA is required.
See the rationale and background below.
-------- Original Message --------
Subject: First post (almost)
Date: Wed, 22 May 2013 15:14:15 -0700
From: Quim Gil <qgil(a)wikimedia.org>
Organization: Wikimedia Foundation
To: qa(a)lists.wikimedia.org
Welcome to the QA list!
This mailing list is an umbrella to host people and discussions focusing
on software quality assurance in all its aspects: exploratory testing,
browser automation testing, unit testing, continuous integration, the
beta cluster, bug management and community QA activities.
We hope this list becomes useful to integrate and retain people
primarily interested in testing / QA. We are seeing many people
interested in testing from different angles. Some people are current
developers willing to learn and discuss more about this topic, best
practices, etc. Some are people new to the community that see testing /
QA as a way to contribute in technical tasks other than development.
This specialized list follows the good results offered by precedents
like the Analytics, Design of Editor Engagement lists. wikitech-l
subscribers will still receive the deep & wide QA related announcements.
No teams comfortable with the status quo will be encouraged to change
their current communication practices because of this list.
There is a bit more background at
https://bugzilla.wikimedia.org/show_bug.cgi?id=48057
Now, who's next?
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hi everyone,
I am trying to restore the revision table from Wikipedia dumps. I
understand that the file that I need is probably enwiki-XX-pages-
logging.xml.gz
I've downloaded the file and I am using the 1.16 version of mwdumper from
https://integration.wikimedia.org/ci/job/MWDumper-package/org.wikimedia$mwd…
When I execute the following I get this error:
java -server -jar mwdumper.jar --format=sql:1.5
enwiki-20130503-pages-logging.xml.gz | gzip -vc >
enwiki-latest-pages-articles.sql.gz
Exception in thread "main" java.lang.IllegalArgumentException: Unexpected
<id> outside a <page>, <revision>, or <contributor>
at
org.mediawiki.importer.XmlDumpReader.readId(XmlDumpReader.java:329)
at
org.mediawiki.importer.XmlDumpReader.endElement(XmlDumpReader.java:204)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:392)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:195)
at
org.mediawiki.importer.XmlDumpReader.readDump(XmlDumpReader.java:88)
at org.mediawiki.dumper.Dumper.main(Dumper.java:142)
0.0%
Mwdumper works well with other 7z xml files but not for this one. I tried a
couple of different xml page-logging files and even from a different
language wikipedias.
Anyone knows what this error is and why it occurs on this specific file?
PS: I've also tried to build mwdumper:
git clone https://gerrit.wikimedia.org/r/p/mediawiki/tools/mwdumper.git
mwdumper
However I couldn't use make or ant since there was not build.xml or
makefile in the git.
I appreciate any help you can give me with this.
Hello,
Let me start off by introducing myself. My name is Jason Lewis and I'm a
developer and (some kind of) designer from Australia. I play a role in the
community side of things for a PHP framework called Laravel.
Over the last few days I've developed a skin for the Laravel community wiki
that fits in with the overall theme of the other community sites. The idea
was to make it blend, but to also keep some sort of wiki "feel" to it. On
the surface it looks very fresh but at its core it is still very much Media
Wiki. You can check the skin out here: http://wiki.laravel.io
The purpose of this thread is to give you an overview of how I went about
skinning Media Wiki from the point of view of someone who has never
attempted it before. I've used Media Wiki in the past but never done
anything besides changing the default logo.* *During the process of
skinning I used the following tutorial as a reference for some of the
inner-workings of Media Wiki:
http://www.mediawiki.org/wiki/Manual:Skinning/Tutorial
*The Design
*
Before I even started looking at how to skin Media Wiki I drafted up a
design with just standard HTML/CSS. I used the Wikipedia site as a
reference here for some of the required elements but also referred to the
linked tutorial above as it mentions some design considerations. During
this designing stage I didn't used my own markup and gave my classes my own
names. I didn't think of the Media Wiki class names or IDs, that would come
later. Once I was happy with my design I begun the skinning process.
*The Skinning
*
This wasn't as hard as I was imagining it to be. There aren't a lot of
quality resources out there that go through skinning Media Wiki. Most just
say copy "MonoBook" and change it to fit your needs. I don't like that.
That, to me, feels very hacky. It was good to see the tutorial linked above
actually go through the setup procedure and the required files. What's even
better about this tutorial is that everything seemed separated. There were
a few tutorials that I briefly skimmed over that seemed to do everything in
the actual "skin" file.
I essentially copied the first part of that tutorial word-for-word, as I
had no idea how Media Wiki handled it all.
Once I got to the meat of my skin I only focused on the main elements. The
first part was the navigation bar. The only dynamically generated part of
that navigation bar is the "Toolbox" and the user section ("request
account", "login", then the actual user navigation). Everything else uses
static links and text. This was my first hurdle. How do I make a link with
Media Wiki? Luckily I got some help in the #mediawiki IRC. The "Linker" and
"Title" classes were what I was after. Here's an example.
<?php echo Linker::link(Title::newFromText('Laracon')); ?>
Next up I need to get the logged in user. I can't remember where but I
managed to stumble upon the $wgUser global variable (shudders). Using this
variable I could check if the user was logged in, if so output the users
menu, or if not show the login or register links.
After the navigation bar I went straight to the content and got that all
sorted. Once I had both these main sections completed I moved on to other
sections, like the "new talk" notifications and search box. There were a
few things I had to adjust slightly, such as the "action links" that appear
above a page ("edit", "discussion", etc). But for the most part it was
pretty easy.
The last little hurdle I had to jump was pulling the table of contents from
the page and sticking it to the left so that it scrolls with you.
Originally I wanted to somehow pull it on the server side and do it that
way. After a little trial and error and trawling through the API (plus some
tips from the IRC guys, thanks!) I decided to just use a jQuery approach.
Using jQuery I just pull the ToC out, and insert it before the main content
then use CSS for the rest.
That pretty much covers my experience and case study. The source of the
skin is available on GitHub for those interested:
https://github.com/jasonlewis/laravel-io-wiki-skin
Thanks for reading. I'd be happy to answer any further questions.
Jason