MediaWiki-l May 2013

mediawiki-l@lists.wikimedia.org

75 participants
61 discussions

Creating a fresh SQLite database for mediawiki
by Nick White 28 May '13

28 May '13

Hi, Is there a straightforward way to create a new sqlite database for mediawiki, all ready for me to import data from an XML dump into? I want this in order to easily populate fresh databases with data from my mediawiki site, for easy testing of new stuff. I expected a command like the following to work: sqlite3 db.sqlite < maintenance/tables.sql But there are lots of errors, starting with: Error: near line 53: near "AUTO_INCREMENT": syntax error Error: near line 130: no such table: main.user Error: near line 131: no such table: main.user Error: near line 132: near "(": syntax error I know I can create a new database using the install.php script, but that's overkill for me, and if possible I'd like to script the creation of an appropriate table structure that I can then import a database dump into. Does anybody have any suggestions? Why doesn't the above command work? Reading the code of how the install.php script works implies to me that it's roughly how the tables are set up. Is there some step I'm missing? Or should I go about this a different way entirely? Thanks in advance, Nick White

2 2

module in WikiEditor not added reliably.
by Jan Wort 28 May '13

28 May '13

Hello, I'd like to use custom dialogs and buttons in the WikiEditor (https://www.mediawiki.org/wiki/Extension:WikiEditor). The customization are done via code in the /index.php/MediaWiki:Common.js I'm having trouble that sometimes my custom module is not added. At the moment I use time-deferred check-function: window.setTimeout(checkModule,500) which than loads a function that checks if the module that defines the custom dialog has actually been loaded: var checkModule = function(){ if(!$.wikiEditor.modules.dialogs.modules.mytool){ $( '#wpTextbox1' ).wikiEditor( 'addModule', mytool()); //console.log("postLoad of module was needed!") } } This seems to work fairly well in the real world, but seems rather hacky code wise. The first attempt to add the module is done in a function which is executed on the jQuery 'wikiEditor-toolbar-doneInitialSections' event. (build-in-event in the current 1.21 Version of Wikieditor): $( '#wpTextbox1' ).on( 'wikiEditor-toolbar-doneInitialSections', customExtendEditor in the customExtendEditor function, the module is defined, and the Module is added (not always sucessfully): var mytool = function(){ return { dialogs:{ mytool:{ [etc.] $( '#wpTextbox1' ).wikiEditor( 'addModule', mytool()); a button is added via ` $('#wpTextbox1').wikiEditor( 'addToToolbar', { … ` but that never caused me problems itself so far. If you know a better, less hacky solution than the deferred check and re-addition, please let me know. Kind Regards, Jan PS.: full code (from my wiki's /index.php/MediaWiki:Common.js): http://jsfiddle.net/RAHCg/

1 0

adding custom licences to the upload wizard
by d_jan 28 May '13

28 May '13

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

4 3

Fwd: Query about 1.21.0 version
by Punit Varia 28 May '13

28 May '13

Hi, Is MediaWiki 1.21.0 is stable version ? After installing it shows 1.21.0rc5. -- * -------------------------------------------------------------------------------------------------------------------------------------------- * *Punit Varia * *Script Packaging Head* punit(a)softaculous.com <http://www.softaculous.com/><http://www.softaculous.com/> <http://www.softaculous.com/> Become our fan on Facebook <http://www.facebook.com/softaculous>and follow us on Twitter <https://twitter.com/softaculous>

3 2

(no subject)
by Robbie Wray 27 May '13

27 May '13

1 0

Contract code snippet: additions to head section for dummies
by Forest S 27 May '13

27 May '13

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

2 1

(no subject)
by abdellah el menaoui 27 May '13

27 May '13

1 0

MediaWiki 1.21.0 released
by Mark A. Hershberger 25 May '13

25 May '13

-----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.sig http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0.patch.gz.sig http://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-----

1 0

Re: [MediaWiki-l] Wiki spam. Stronger fightback.
by Henny Savenije 24 May '13

24 May '13

As for blocking IP's automatically. This is another good method which I also use. http://danielwebb.us/software/bot-trap/ You hide a small "invisible" image with a link which people won't see but bots do. Descent bots won't follow that link since you told them in robot.txt not to do so. Spammer bots will. Then they are trapped. Their IP is automatically added to .htaccess At 06:29 PM 5/24/2013 Friday -0400, you wrote: >We have two issues here, Blocking said IPs in a reliable simple >method. * Thought would be something like torblock that just >downloads the list on a daily/weekly/whatever schedule * can provide >the blocked users information on why they are blocked and appeal >process for valid users (ipblockexempt) Two: A method for reporting, >confirming and listing said sources. * The easiest method that I >know of would be a category based system with a bot/script that >compiles a complete listing of said pages in the category on a >regular basis. * Using a category system enables a more fulidic >process, reduces edit conflicts and provides several other options. >_______________________________________________ MediaWiki-l mailing >list MediaWiki-l(a)lists.wikimedia.org >https://lists.wikimedia.org/mailman/listinfo/mediawiki-l _ _ (o) (o) oOOO----(_)----OOOo--- Henny (Lee Hae Kang) ----------------------------- http://www.henny-savenije.pe.kr Portal to all my sites http://www.hendrick-hamel.henny-savenije.pe.kr (in English) Feel free to discover Korea with Hendrick Hamel (1653-1666) http://www.hendrick-hamel.henny-savenije.pe.kr/indexk2.htm In Korean http://www.hendrick-hamel.henny-savenije.pe.kr/Dutch In Dutch http://www.vos.henny-savenije.pe.kr Frits Vos Article about Witsen and Eibokken and his first Korean-Dutch dictionary http://www.cartography.henny-savenije.pe.kr (in English) Korea through Western Cartographic eyes http://www.hwasong.henny-savenije.pe.kr Hwasong the fortress in Suwon http://www.oldKorea.henny-savenije.pe.kr Old Korea in pictures http://www.british.henny-savenije.pe.kr A British encounter in Pusan (1797) http://www.genealogy.henny-savenije.pe.kr/ Genealogy http://www.henny-savenije.pe.kr/phorum Bulletin board for Korean studies

1 0

Fwd: [QA] First post (almost)
by Quim Gil 22 May '13

22 May '13

Hi, we have now a mailing list dedicated to software quality assurance: https://lists.wikimedia.org/mailman/listinfo/qa http://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

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

MediaWiki-l May 2013