Re: [MediaWiki-l] Free MediaWIki hosting sites
Orain will allow that, just let us know and we'll be happy to help out. FYI, we've nailed down the source of the outages, that should be long past. Date: Wed, 15 Jul 2015 11:41:46 +1000 From: brentonhorn...@gmail.com To: mediawiki-l@lists.wikimedia.org Subject: Re: [MediaWiki-l] Free MediaWIki hosting sites Thanks Frodo, these sites are the best I've come across so far but do any of them allow shell access? See I have a local wiki I would like to transfer to this online Wiki, via running `php maintenance/importDump.php` on the XML dump of my local wiki. I have tried importing via Special:Import but the dump is far too large for this to work. On 15 July 2015 at 07:17, Frodo Baggins frodobaggins...@gmail.com wrote: or GuHat - Frodo Baggins: Hobbit, Wikipedia editor (blackhat999 https://en.wikipedia.org/wiki/User:Blackhat999), Linux freak, and hacker extraordinaire. On Wed, Jul 1, 2015 at 10:56 AM, Frodo Baggins frodobaggins...@gmail.com wrote: Try x10 hosting if you want complete ctrl. - Frodo Baggins: Hobbit, Wikipedia editor (blackhat999 https://en.wikipedia.org/wiki/User:Blackhat999), Linux freak, and hacker extraordinaire. On Tue, Jun 30, 2015 at 2:59 PM, Frodo Baggins frodobaggins...@gmail.com wrote: I personally like Orain. One note though: they have had some outages lately. - Frodo Baggins: Hobbit, Wikipedia editor (blackhat999 https://en.wikipedia.org/wiki/User:Blackhat999), Linux freak, and hacker extraordinaire. On Tue, Jun 30, 2015 at 12:51 PM, Thomas Mulhall thomasmulhall...@yahoo.com wrote: Well there's heliohost ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l -- Thanks for your time, Brenton ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
[MediaWiki-l] How would I convert LQT namespaces to Flow pages on a localhost wiki
I have MW 1.25.1 and the matching Flow extension and am attempting to make Flow convert the LQT pages to Flow counterparts (all pages in the Talk namespace), but the instructions on the Flow extension page on MW.org don't seem to be very helpful and WMF specific. I could use some advice how to do this, I plan to deploy this on the Orain wikifarm as soon as is practicable, but I wanted to do some localhost testing first. ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] QuickLink extension not working with MediaWiki 1.24.1
I believe WikiEd has similar functionality that conflicts if certain features of WikEd are enabled. Try experimenting to find out what exactly might be the issue. Date: Thu, 5 Mar 2015 23:27:35 +1000 From: brentonhorn...@gmail.com To: mediawiki-l@lists.wikimedia.org Subject: Re: [MediaWiki-l] QuickLink extension not working with MediaWiki 1.24.1 Thanks, but it doesn't seem to be compatible with WikEd because when it is active it doesn't load, whereas when I disable it, it appears to work perfectly. Any ideas of how to overcome this problem? On 5/03/2015 7:50 PM, Arcane 21 wrote: The autocomplete script works far, far better, and can be enabled as a gadget or site script. Here's a gadget version you can snag from my wiki here: https://allthetropes.orain.org/wiki/Special:Gadgets/export/Auto_Complete Date: Thu, 5 Mar 2015 16:26:26 +1000 From: brentonhorn...@gmail.com To: mediawiki-l@lists.wikimedia.org Subject: [MediaWiki-l] QuickLink extension not working with MediaWiki 1.24.1 Hi, Extension:QuickLink (https://www.mediawiki.org/wiki/Extension:QuickLink) isn't working on MediaWiki 1.24.1 for me. When I type [[ brackets no link suggestions appear (in fact I don't see any evidence of it being installed besides its appearance on Special:Version, even though I downloaded the zip file, extracted its contents, moved them to the extensions/ directory and added |require_once(extensions/QuickLink/QuickLink.php)| to LocalSettings.php). This isn't surprising that QuickLink no longer works seeing how it was last edited 4 or so years ago. Any alternatives to this extension that suggest links after [[ is typed in source mode or any ways to get QuickLink to work for me will be gladly welcomed. Keep in mind I am using WikiEditor and WikEd and do not intend on removing them from my MediaWiki installation. Thanks for your time, Brenton ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] QuickLink extension not working with MediaWiki 1.24.1
The autocomplete script works far, far better, and can be enabled as a gadget or site script. Here's a gadget version you can snag from my wiki here: https://allthetropes.orain.org/wiki/Special:Gadgets/export/Auto_Complete Date: Thu, 5 Mar 2015 16:26:26 +1000 From: brentonhorn...@gmail.com To: mediawiki-l@lists.wikimedia.org Subject: [MediaWiki-l] QuickLink extension not working with MediaWiki 1.24.1 Hi, Extension:QuickLink (https://www.mediawiki.org/wiki/Extension:QuickLink) isn't working on MediaWiki 1.24.1 for me. When I type [[ brackets no link suggestions appear (in fact I don't see any evidence of it being installed besides its appearance on Special:Version, even though I downloaded the zip file, extracted its contents, moved them to the extensions/ directory and added |require_once(extensions/QuickLink/QuickLink.php)| to LocalSettings.php). This isn't surprising that QuickLink no longer works seeing how it was last edited 4 or so years ago. Any alternatives to this extension that suggest links after [[ is typed in source mode or any ways to get QuickLink to work for me will be gladly welcomed. Keep in mind I am using WikiEditor and WikEd and do not intend on removing them from my MediaWiki installation. Thanks for your time, Brenton ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Make an account set as a bot
You have to assign that account the bot user right. Date: Fri, 6 Mar 2015 15:39:42 +1000 From: brentonhorn...@gmail.com To: mediawiki-l@lists.wikimedia.org Subject: [MediaWiki-l] Make an account set as a bot Hi, I've got an account called MyFirstBot on my local wiki that is a bot and I'd like to know how to set it as a bot account. I created the account via my web browser so it is set, by default as a user account. Thanks for your time, Brenton ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Make an account set as a bot
Special:UserRightsManagement Date: Fri, 6 Mar 2015 16:09:08 +1000 From: brentonhorn...@gmail.com To: mediawiki-l@lists.wikimedia.org Subject: Re: [MediaWiki-l] Make an account set as a bot And how do I do this? On 6/03/2015 3:57 PM, Arcane 21 wrote: assign that account the bot user right. ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Enabling special character file names
There is an extremely hacky fix that is not recommend somewhere on Bugzilla/Phabricator, but otherwise, no. This issue does not affect Linux or Mac users, but is unsolvable on Windows aside from that hacky fix (which is a pain to set up and can corrupt the database if I recall right). Date: Sat, 14 Feb 2015 13:40:36 +1000 From: brentonhorn...@gmail.com To: mediawiki-l@lists.wikimedia.org Subject: Re: [MediaWiki-l] Enabling special character file names Yeah I'm running Windows. So I'm guessing there's no known way of overcoming this issue? On 14 February 2015 at 13:34, Arcane 21 arc...@live.com wrote: Small correction to previous message: Windows. From what I understand, Windows based systems have trouble parsing certain characters when MediaWiki is run on a WAMP stack due to the Windows settings for saving filenames. From: arc...@live.com To: mediawiki-l@lists.wikimedia.org Subject: RE: [MediaWiki-l] Enabling special character file names Date: Fri, 13 Feb 2015 21:32:58 -0600 Is your web stack on a Wnodws based system? If so, they have known issues with special character file names. Date: Sat, 14 Feb 2015 13:12:35 +1000 From: brentonhorn...@gmail.com To: mediawiki-l@lists.wikimedia.org Subject: [MediaWiki-l] Enabling special character file names Hi I'd like to allow special characters in file names on my Wiki. For example, currently I'd like some file names to include Greek letters like alpha and beta. In order to avoid being accused of using this list as my personal Google I am giving you the details of all my searches of Google and Wikimedia sites. I have checked https://phabricator.wikimedia.org/T3780 but I couldn't see any solutions to this problem. I was going to try https://phabricator.wikimedia.org/T3780#60419 but after I searched SpecialUpload.php I did not find anywhere in the file with if( $this-saveUploadedFile( in it, hence I couldn't even give it a try (granted that posted made almost 8 years ago). I also found https://www.mediawiki.org/wiki/FileBackend after searching for FileBackend, as it was a popular topic in this thread, in a MediaWiki search but I hadn't the foggiest how it applied to what I wanted. I also saw http://stackoverflow.com/questions/4138705/mediawiki-special-characters-in-file-name-issue but I haven't a clue what the accepted answer meant for me. Thanks for your time, Brenton ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Inkscape for SVG thumbnailing
If you just need quick and dirty clientside SVG rendering, try this extension: https://www.mediawiki.org/wiki/Extension:NativeSvgHandler Even if you don't have any other SVG renderer enabled, it pipes the output through your browser's SVG renderer as a middleman, which, unless you have a browser that belongs in a museum, will work fine 100% of the time. Date: Thu, 5 Feb 2015 05:04:16 +1000 From: brentonhorn...@gmail.com To: mediawiki-l@lists.wikimedia.org Subject: [MediaWiki-l] Inkscape for SVG thumbnailing Hi, I'd like to know how I can use Inkscape for SVG thumbnailing on my Windows 7 OS with a MediaWiki installation. Inkscape's files are located at C:\Program Files (x86)\Inkscape. My efforts to date (mostly based on Manual:$wgSVGConverters and other MediaWiki manual pages) have failed. Currently my LocalSettings.php file's SVG-related settings are: # Image Converter $wgSVGConverter = 'Inkscape'; $wgSVGConverters = array( 'Inkscape' = '$path/inkscape.exe -z -w $width -f $input -e $output', ); # Image converter path $wgSVGConverterPath = '/Program Files (x86)/Inkscape'; This gives the following error (which appears in the thumbnail's place): Error creating thumbnail: '' is not recognized as an internal or external command, operable program or batch file. The reason I'd like Inkscape as my SVG thumbnailer in particular is because I sometimes use SVGs that are only correctly rendered by Inkscape (I know that Wikia's thumbnailer (whatever it might be) frequently makes rendering errors with these SVGs, e.g., see http://health-and-medicine.wikia.com/wiki/File:Symptoms_of_Hodgkin_lymphoma.svg and all the black spots that appear in it. Thanks for your time, Brenton ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Jmol errors
Hello Brenton, I did some testing and found out the reason for the first error: It needs to the file type identified in LocalSettings.php with special configuration settings You can find more info here: https://www.mediawiki.org/wiki/Extension:Jmol#Managing_molecular_files Date: Wed, 4 Feb 2015 07:55:11 +1000 From: brentonhorn...@gmail.com To: mediawiki-l@lists.wikimedia.org Subject: [MediaWiki-l] Jmol errors Hi, I've installed the Jmol extension and I have noticed two major problems: 1. When uploading a pdb file at Special:Upload I receive the error: File extension .pdb does not match the detected MIME type of the file (text/plain). Other chemical file extensions produce similar errors, including .sdf, .cml, etc. Even though I have added: $wgFileExtensions = array( 'doc', 'docx', 'xls', 'xlsx', 'mpp', 'pdf', 'ppt', 'tiff', 'bmp', 'pptx', 'ps', 'odt', 'ods', 'odp', 'odg' , 'ogg', 'sdf', 'mol', 'pdb', 'xyz', 'mol2', 'svg', 'cml' ); to LocalSettings.php 2. Whenever I add jmolpdb/jmolpdb to an article (any article, even my sandbox, i.e., User:Fuse809/sandbox), jmolPdb/jmolPdb or other Jmol tags jmolFile/jmolFile and click Save page I'm left at a blank page with the URL of http://localhost:8080/mediawiki/index.php?title=PAGENAMEaction=submit (where PAGENAME is the page's name). Thanks for your time, Brenton ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Jmol extension
Brenton, pursuant to your wanting Jmol on your Orain wiki, I created an Orain repo for the Jmol extension, which you or anyone else can get to make it easier for localhost or independent use: https://github.com/Orain/Jmol Date: Wed, 4 Feb 2015 06:31:41 +1000 From: brentonhorn...@gmail.com To: mediawiki-l@lists.wikimedia.org Subject: Re: [MediaWiki-l] Jmol extension Nvm, I figured out I didn't download the files, just their web pages, rofl. On 4 February 2015 at 06:26, Brenton Horne brentonhorn...@gmail.com wrote: Hi I installed Jmol via following these instructions https://www.mediawiki.org/wiki/Extension:Jmol#Installing_Jmol_extension and the result was when I opened my MediaWiki extension I saw this page (and it didn't matter which page I went to) http://imgur.com/7OQAhEa. Any ideas of what I should do now? Thanks for your time, Brenton ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Places I can set up my own MediaWiki website
Hello, Brenton, I'm staff at the Orain wiki farm, which can be found here: https://meta.orain.org We allow a large degree of customization for your wiki at no cost to you (we are donation funded, there are no membership or subscription fees), so please, feel free to check us out. Date: Mon, 2 Feb 2015 22:41:18 +1000 From: brentonhorn...@gmail.com To: mediawiki-l@lists.wikimedia.org Subject: [MediaWiki-l] Places I can set up my own MediaWiki website Hi, I've installed MediaWiki on my PC and I was wondering how I could turn this installation into a website for free. Is this possible? I have created a Wiki with Wikia but they have far less customization than that allowed by MediaWiki software (e.g., the extensions they have are all constant across the Wikia family of sites and while you could request new ones from Wikia staff I have never seen a case where they actually installed a new extension based on these requests, even for one single Wiki) so hence why I'd like to know if I could set up my own fully-customizable Wiki based on my current MediaWiki installation. Thanks for your time, Brenton ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [Wikitech-l] Parsoid's progress
Given what I've seen so far, it might be best to aim for a gradual
reimplementation of Parsoid features to make most of them work without a need
for Parsoid, with the eventual goal of severing the need for Parsoid completely
if possible. At any rate, the less the parser has to outsource, the less
complicated things will be, correct?
Date: Tue, 20 Jan 2015 11:02:10 -0500
From: canan...@wikimedia.org
To: wikitech-l@lists.wikimedia.org
Subject: Re: [Wikitech-l] Parsoid's progress
I believe Subbu will follow up with a more complete response, but I'll note
that:
1) no plan survives first encounter with the enemy. Parsoid was going to
be simpler than the PHP parser, Parsoid was going to be written in PHP,
then C, then prototyped in JS for a later implementation in C, etc. It has
varied over time as we learned more about the problem. It is currently
written in node.js and probably is at least the same order of complexity as
the existing PHP parser. It is, however, built on slightly more solid
foundations, so its behavior is more regular than the PHP parser in many
places -- although I've been submitting patches to the core parser where
necessary to try to bring them closer together. (c.f.
https://gerrit.wikimedia.org/r/180982 for the most recent of these.) And,
of course, Parsoid emits well-formed HTML which can be round-tripped.
In many cases Parsoid could be greatly simplified if we didn't have to
maintain compatibility with various strange corner cases in the PHP parser.
2) Parsoid contains a partial implementation of the PHP expandtemplates
module. It was decided (I think wisely) that we didn't really gain
anything by trying to reimplement this on the Parsoid side, though, and it
was better to use the existing PHP code via api.php. The alternative would
be to basically reimplement quite a lot of mediawiki (lua embedding, the
various parser functions extensions, etc) in node.js. This *could* be done
-- there is no technical reason why it cannot -- but nobody thinks it's a
good idea to spend time on right now.
But the expandtemplates stuff basically works. As I said, it doesn't
contain all the crazy extensions that we use on the main WMF sites, but it
would be reasonable to turn it on for a smaller stock mediawiki instance.
In that sense it *could* be a full replacement for the Parser.
But note that even as a full parser replacement Parsoid depends on the PHP
API in a large number of ways: imageinfo, siteinfo, language information,
localized keywords for images, etc. The idea of independence is somewhat
vague.
--scott
On Mon, Jan 19, 2015 at 11:58 PM, MZMcBride z...@mzmcbride.com wrote:
Matthew Flaschen wrote:
On 01/19/2015 08:15 AM, MZMcBride wrote:
And from this question flows another: why is Parsoid
calling MediaWiki's api.php so regularly?
I think it uses it for some aspects of templates and hooks. I'm sure
the Parsoid team could explain further.
I've been discussing Parsoid a bit and there's apparently an important
distinction between the preprocessor(s) and the parser. Though in practice
I think parser is used pretty generically. Further notes follow.
I'm told in Parsoid, ref and {{!}} are special-cased, while most other
parser functions require using the expandtemplates module of MediaWiki's
api.php. As I understand it, calling out to api.php is intended to be a
permanent solution (I thought it might be a temporary shim).
If the goal was to just add more verbose markup to parser output, couldn't
we just have done that (in PHP)? Node.js was chosen over PHP due to
speed/performance considerations and concerns, from what I now understand.
The view that Parsoid is going to replace the PHP parser seems to be
overly simplistic and goes back to the distinction between the parser and
preprocessor. Full wikitext transformation seems to require a preprocessor.
MZMcBride
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
(http://cscott.net)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Parsoid's progress
If I might weigh in, I concur with MZMcBride. If Parsoid is absolutely needed regardless, that's one thing, but if a VE editing interface can be set up that doesn't need Parsoid, that would reduce dependence on third party software, make installation easier for all parties concerned, and not be as resource intensive, and since the optimization of resources is always a plus IMO, severing dependency on Parsoid and attempting to do it's current functions purely in house seems like a good plan to pursue. Date: Mon, 19 Jan 2015 11:15:54 -0500 From: z...@mzmcbride.com To: wikitech-l@lists.wikimedia.org Subject: [Wikitech-l] Parsoid's progress (Combining pieces of Jay's thread and pieces of the shared hosting thread.) Daniel Friesen wrote: Parsoid can do Parsoid DOM to WikiText conversions. So I believe the suggestion is that storage be switched entirely to the Parsoid DOM and WikiText in classic editing just becomes a method of editing the content that is stored as Parsoid DOM in the backend. Tim Starling wrote: Parsoid depends on the MediaWiki parser, it calls it via api.php. It's not a complete, standalone implementation of wikitext to HTML transformation. HTML storage would be a pretty simple feature, and would allow third-party users to use VE without Parsoid. It's not so simple to use Parsoid without the MediaWiki parser, especially if you want to support all existing extensions. So, as currently proposed, HTML storage is actually a way to reduce the dependency on services for non-WMF wikis, not to increase it. Based on recent comments from Gabriel and Subbu, my understanding is that there are no plans to drop the MediaWiki parser at the moment. Yeah... what is this all about? My understanding (and please correct me if I'm wrong) is that Parsoid is/was intended to be a standalone service capable of translating wikitext -- HTML. You seem to be stating that Parsoid is neither complete nor standalone. Why? Currently Parsoid is the largest client of the MediaWiki PHP parser, I'm told. If Parsoid is regularly calling and relying upon the MediaWiki PHP parser, what exactly is the point of Parsoid? How much parity is there between Parsoid without the use of the MediaWiki parser and the MediaWiki parser? That is, if you selected a random sample of pages from a Wikimedia wiki, how many of them could Parsoid correctly parse on its own? And from this question flows another: why is Parsoid calling MediaWiki's api.php so regularly? I'm also interested in Parsoid's development as it relates to the broader push for services. If Parsoid is going to be the model of future services development, I'd like a clearer evaluation of what kind of model it is. Again, please correct me if I'm wrong, mistaken, misinformed, etc., but from my place of limited knowledge, it sounds very unappealing to create large Node.js applications (services) that closely tie in and require(!) PHP counterparts. This seems like the opposite of moving toward a more flexible, modular architecture. From my perspective, it would seem to only saddle us with additional technical debt moving forward, as we double complexity indefinitely. MZMcBride ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Status of the Purge extension
I agree. Purging should either be integrated into the MW core or the extension needs to be made so anyone can use it whenever needed without needing JS. Date: Sun, 28 Dec 2014 09:38:26 -0800 From: jdlrob...@gmail.com To: wikitech-l@lists.wikimedia.org Subject: Re: [Wikitech-l] Status of the Purge extension On 28 Dec 2014 08:16, MZMcBride z...@mzmcbride.com wrote: Ricordisamoa wrote: It looks like the Purge extension https://www.mediawiki.org/wiki/Extension:Purge for MediaWiki could be very useful to replace many similar gadgets on Wikimedia sites. New users often need to purge the server cache, and don't know how to do it. A simple link is way more helpful than visit the history page and replace 'history' with 'purge', etc. Also, a server-side extension has much better i18n support and works without JavaScript. Is anyone interested in getting it in? Hi. Rather than trying find ways to institutionalize the purge action, I'd strongly prefer that we examine the purge action's current use-cases and find ways to obviate them. Purging should be an internal implementation detail and any time a user feels that manually purging a page is required, MediaWiki has failed the user. Well said. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[MediaWiki-l] How do I configure the PageTriage for my non WMF wiki
I wanted to install this extension for my non WMF wiki: https://www.mediawiki.org/wiki/Extension:PageTriage Got it working, but I have no idea how to configure it, and all I really need to do (for now) is configure it to have a filter for the main namespace (instead of Article like on Wikipedia). Any help in this regard would be appreciated. ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] How do I configure the PageTriage for my non WMF wiki
Okay, small update, figured out how this works (Article IS the main namespace), but I don't see the curation toolbar, how do I enable this? From: arc...@live.com To: mediawiki-l@lists.wikimedia.org Date: Tue, 23 Dec 2014 19:02:50 -0600 Subject: [MediaWiki-l] How do I configure the PageTriage for my non WMF wiki I wanted to install this extension for my non WMF wiki: https://www.mediawiki.org/wiki/Extension:PageTriage Got it working, but I have no idea how to configure it, and all I really need to do (for now) is configure it to have a filter for the main namespace (instead of Article like on Wikipedia). Any help in this regard would be appreciated. ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] How do I configure the PageTriage for my non WMF wiki
Thanks for the tips, Ryan. It would be nice to have the curation toolbar and other stuff working, but I got the pages feed working nicely, and that's more than sufficient at the moment. Again, thanks for the help, and have a Merry Christmas! :) Date: Tue, 23 Dec 2014 17:28:00 -0800 From: rkald...@wikimedia.org To: mediawiki-l@lists.wikimedia.org Subject: Re: [MediaWiki-l] How do I configure the PageTriage for my non WMF wiki The instructions at https://www.mediawiki.org/wiki/Extension:PageTriage#Installation should cover the installation process. Configuring PageTriage, however, is fairly janky and not for the faint of heart. In theory, you can configure most of it by overriding these two files: /modules/ext.pageTriage.defaultTagsOptions/ext.pageTriage.defaultTagOptions.js /modules/ext.pageTriage.defaultDeletionTagsOptions/ext.pageTriage.defaultDeletionTagsOptions.js ...with local Javascript code at... MediaWiki:PageTriageExternalTagOptions.js MediaWiki:PageTriageExternalDeletionTagsOptions.js That allows you to customize (almost) all of the tags and workflow options for your local wiki. I say 'almost' because some of the deletion processes on English Wikipedia were just too complicated to make configurable in a sensible way, so they ended up getting hard-coded into PageTriage. And since the development of PageTriage was killed right after it launched on enwiki (due to the fact that English Wikipedians still preferred using Special:NewPages), it was never properly finished to support other wikis :( Kaldari On Tue, Dec 23, 2014 at 5:02 PM, Arcane 21 arc...@live.com wrote: I wanted to install this extension for my non WMF wiki: https://www.mediawiki.org/wiki/Extension:PageTriage Got it working, but I have no idea how to configure it, and all I really need to do (for now) is configure it to have a filter for the main namespace (instead of Article like on Wikipedia). Any help in this regard would be appreciated. ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [Wikitech-l] [BREAKING CHANGE] Plans to move Cite configuration from wikitext messages to CSS styles
Thanks for the clarification. I think the idea (as you explained it) sounds great, hope you guys can get it working. :) From: jforres...@wikimedia.org Date: Tue, 16 Dec 2014 22:06:11 -0800 To: wikitech-l@lists.wikimedia.org Subject: Re: [Wikitech-l] [BREAKING CHANGE] Plans to move Cite configuration from wikitext messages to CSS styles On 16 December 2014 at 21:07, Arcane 21 arc...@live.com wrote: At the risk of sounding stupid, does this mean other wikis will need a Parsoid instance to use this extension, or is this simply being tested in a Parsoid environment and it's just using CSS instead of wikitext for rendering? If the former, not a fan of the idea at all. If the latter, awesome, sounds like a great idea. The latter; this has become a pressing need for faithful replication of expected styles for pages rendered using Parsoid, but we'll do this in both the regular Cite extension and the current re-implementation of it inside Parsoid. They will share the styling so that it will just work. I'm still confused on the exact details of how this will work, so I'd appreciate clarification. Right now we've not yet confirmed that we can entirely replicate all the features and configurations that people are using in Cite via the existing messages in the new CSS system. This is mostly a please help and/or tell us if we're crazy e-mail. :-) J. -- James D. Forrester Product Manager, Editing Wikimedia Foundation, Inc. jforres...@wikimedia.org | @jdforrester ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [BREAKING CHANGE] Plans to move Cite configuration from wikitext messages to CSS styles
At the risk of sounding stupid, does this mean other wikis will need a Parsoid instance to use this extension, or is this simply being tested in a Parsoid environment and it's just using CSS instead of wikitext for rendering? If the former, not a fan of the idea at all. If the latter, awesome, sounds like a great idea. I'm still confused on the exact details of how this will work, so I'd appreciate clarification. From: jforres...@wikimedia.org Date: Tue, 16 Dec 2014 18:10:46 -0800 To: wikitech-l@lists.wikimedia.org Subject: Re: [Wikitech-l] [BREAKING CHANGE] Plans to move Cite configuration from wikitext messages to CSS styles On 16 December 2014 at 04:45, Brad Jorsch (Anomie) bjor...@wikimedia.org wrote: On Tue, Dec 16, 2014 at 5:44 AM, Marc Ordinas i Llopis marc...@wikimedia.org wrote: Due to how MediaWiki's messages system works, changes to the display styles need to be copied into each of the ~300 display languages for users, else those users with different languages will see different reference styles on the same page. That sounds like bug T33216, which was fixed a while ago. Does this actually occur now? No, this is talking about the problem of changing the rendering styles needing to be done in each of the customised languages manually through the translation system (and being totally unlike what the translation system on TranslateWiki.net generally uses and is suited for). It was not meant to be referring to https://phabricator.wikimedia.org/T33216, which I believe is still fixed, yes. J. -- James D. Forrester Product Manager, Editing Wikimedia Foundation, Inc. jforres...@wikimedia.org | @jdforrester ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [MediaWiki-l] Off topic: Wiki spammer is using spoofed IP addresses???
Spammers might be using something similar to the IPfuck Firefox/Chrome extension, which fakes an IP address instead of allowing the real IP to be recorded, not sure how we can defend against that sort of thing at present. Date: Fri, 24 Oct 2014 16:25:42 -0400 From: phoenixoverr...@gmail.com To: alj62...@yahoo.com; mediawiki-l@lists.wikimedia.org Subject: Re: [MediaWiki-l] Off topic: Wiki spammer is using spoofed IP addresses??? The IP address belongs to CANTV Servicios which I have seen a LOT of spam from recently On Fri, Oct 24, 2014 at 3:25 PM, Al alj62...@yahoo.com wrote: I am surprised to see that a spammer is spoofing his IP address. I got some spam from 200.90.74.226 - 226 is out of range for IPs and so isn't even a valid IP address. I confirmed that the number is not a wiki username and the apache log shows the same IP. It appears maybe the spammer's script has a bug and not range-checking the generated numbers which made it obvious that the IP is spoofed; otherwise I would have never noticed. I thought IP spoofing was a fairly sophisticated tactic and didn't expect to see a common wiki spammer using it, or am I wrong? I'm also surprised apache even allowed the connection, much less the Amazon AWS firewall. Am I missing something? Al ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [Wikitech-l] MediaWiki Security and Maintenance Releases: 1.22.10 and 1.23.3
Mostly a few bugfixes. To: mediawiki-annou...@lists.wikimedia.org; mediawik...@lists.wikimedia.org; mediawiki-enterpr...@lists.wikimedia.org; wikitech-l@lists.wikimedia.org; gla...@hallowelt.biz Date: Thu, 28 Aug 2014 15:10:09 +0200 From: matma@gmail.com Subject: Re: [Wikitech-l] MediaWiki Security and Maintenance Releases: 1.22.10 and 1.23.3 There weren't actually any security patches in these releases, were there? -- Matma Rex ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [MediaWiki-l] AbuseFilter block duration - can it be made different for IPs?
Just a guess here, but couldn't you load a list of Tor exit nodes into a filter and have it deny an edit if those IPs hit certain keyword filters? From: dger...@gmail.com Date: Sun, 3 Aug 2014 23:05:51 +0100 To: mediawiki-l@lists.wikimedia.org Subject: [MediaWiki-l] AbuseFilter block duration - can it be made different for IPs? The default block duration for AbuseFilter is indefinite. $wgAbuseFilterBlockDuration can be set to alter this. My question is: can we make it different for IPs? The use case here is RationalWiki, which is currently getting a very tedious troll coming in from Tor. We don't actually want to switch off Tor and other proxies except in dire circumstances, but we would quite like the AbuseFilter (whose rules we have highly tuned) to block its positives for, say, a few days. (Usernames, they can stay indefinite.) Is there a way to do this - different behaviour for usernames and IPs? - d. ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [Wikitech-l] Deploying a centralized questionnaire to all pages of a specific Category.
You might wish to try this: https://www.mediawiki.org/wiki/Extension:Quiz Date: Sat, 2 Aug 2014 18:12:51 -0400 From: valing...@gmail.com To: wikitech-l@lists.wikimedia.org Subject: [Wikitech-l] Deploying a centralized questionnaire to all pages of a specific Category. Hello, I'm trying to find if there's a way (extension or built in functionality) to create a list of questions on a specific page then deploy this set of questions on say every page of a certain Category. Also, when the questions are deployed to a specific category, i'd need to give users a way to answer those questions (a simple textbox would be enough). It doesn't need to keep track of who answered what, only the most recent update would be the answer. Thanks ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [MediaWiki-l] Syntax highlight for wikitext?
https://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi https://www.mediawiki.org/wiki/Extension:CodeEditor There should be a gadget on MediaWiki.org you could import with this sort of functionality as well. From: diana...@gmail.com To: MediaWiki-l@lists.wikimedia.org Date: Sat, 5 Jul 2014 22:42:53 -0300 Subject: [MediaWiki-l] Syntax highlight for wikitext? Hello, Is there an extensions to enable some syntax highligh in the very article editor?! I'm not talking about hilite wikitext in demos but real hilite when entering article content. Thanks, Diana ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Syntax highlight for wikitext?
This should work: https://www.mediawiki.org/wiki/User:Remember_the_dot/Syntax_highlighter From: diana...@gmail.com To: mediawiki-l@lists.wikimedia.org Date: Sun, 6 Jul 2014 00:16:29 -0300 Subject: Re: [MediaWiki-l] Syntax highlight for wikitext? Thanks for your quick response Arcane 21, I'm looking for a extension that syntax highlight the wiki markup, i.g. ref, '''bold''', ''italics'' etc not for programming languages. - Original Message - From: Arcane 21 arc...@live.com To: mediawiki-l@lists.wikimedia.org Sent: Saturday, July 05, 2014 11:22 PM Subject: Re: [MediaWiki-l] Syntax highlight for wikitext? https://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi https://www.mediawiki.org/wiki/Extension:CodeEditor There should be a gadget on MediaWiki.org you could import with this sort of functionality as well. From: diana...@gmail.com To: MediaWiki-l@lists.wikimedia.org Date: Sat, 5 Jul 2014 22:42:53 -0300 Subject: [MediaWiki-l] Syntax highlight for wikitext? Hello, Is there an extensions to enable some syntax highligh in the very article editor?! I'm not talking about hilite wikitext in demos but real hilite when entering article content. Thanks, Diana ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Syntax highlight for wikitext?
I agree, Gryllida, it would be a nice core feature. From: gryll...@fastmail.fm To: mediawiki-l@lists.wikimedia.org Date: Sun, 6 Jul 2014 15:10:45 +1000 Subject: Re: [MediaWiki-l] Syntax highlight for wikitext? Diana and Arcane, The script you linked is nice without extra frills. Thank you. (WikEd gadget also highlights wiki markup, but it breaks some other things. It is available on all Wikimedia projects.) I would ideally like to see the markup highlight functionality in the core of MediaWiki some day, which may or may not have been considered before. On Sun, 6 Jul 2014, at 14:35, Diana K. C wrote: Wow this is great! Thanks a lot! - Original Message - From: Arcane 21 arc...@live.com To: mediawiki-l@lists.wikimedia.org Sent: Sunday, July 06, 2014 1:02 AM Subject: Re: [MediaWiki-l] Syntax highlight for wikitext? This should work: https://www.mediawiki.org/wiki/User:Remember_the_dot/Syntax_highlighter From: diana...@gmail.com To: mediawiki-l@lists.wikimedia.org Date: Sun, 6 Jul 2014 00:16:29 -0300 Subject: Re: [MediaWiki-l] Syntax highlight for wikitext? Thanks for your quick response Arcane 21, I'm looking for a extension that syntax highlight the wiki markup, i.g. ref, '''bold''', ''italics'' etc not for programming languages. - Original Message - From: Arcane 21 arc...@live.com To: mediawiki-l@lists.wikimedia.org Sent: Saturday, July 05, 2014 11:22 PM Subject: Re: [MediaWiki-l] Syntax highlight for wikitext? https://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi https://www.mediawiki.org/wiki/Extension:CodeEditor There should be a gadget on MediaWiki.org you could import with this sort of functionality as well. From: diana...@gmail.com To: MediaWiki-l@lists.wikimedia.org Date: Sat, 5 Jul 2014 22:42:53 -0300 Subject: [MediaWiki-l] Syntax highlight for wikitext? Hello, Is there an extensions to enable some syntax highligh in the very article editor?! I'm not talking about hilite wikitext in demos but real hilite when entering article content. Thanks, Diana Gryllida. ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [Wikitech-l] new terms of use/paid contributions - do they apply to mediawiki
In terms of applying the rule to things like articles written by someone for pay on behalf of someone else, that policy makes sense. As for code, I agree, that policy is counterproductive. To: wikitech-l@lists.wikimedia.org Date: Mon, 16 Jun 2014 22:42:05 +0200 From: matma@gmail.com Subject: Re: [Wikitech-l] new terms of use/paid contributions - do they apply to mediawiki I agree. The new policy would just introduce pointless bureaucracy. -- Matma Rex ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Preventing MW from adding a page to watchlist
This seems to be a MW bug. Ever since we updated our wiki to MW 1.23, this has been happening to lots of our users, myself included. Apparently, the option to add pages edited to the watchlist is checked by default, which probably needs to be disabled by default. Date: Tue, 10 Jun 2014 10:57:17 +0200 From: benap...@gmail.com To: wikitech-l@lists.wikimedia.org Subject: [Wikitech-l] Preventing MW from adding a page to watchlist There is no mention of this feature in https://www.mediawiki.org/wiki/API:Rollback but according to Helder in this bug report https://bugzilla.wikimedia.org/show_bug.cgi?id=66273 mediawiki insert every page to which a rollback api was used on to a users watchlist. Is there a way to disable it? ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Preventing MW from adding a page to watchlist
Thanks for the reminder. However, I think that not all those settings are not necessarily good, and here's why: * (bug 45020) Make preferences Add pages I create and files I upload to my watchlist and pages and files I edit true by default. This seems to be the default on Wikia, which I have also used, but not everyone wants to do thus. I personally only like to use a watchlist to keep track of select pages instead of every page I edit, so I find this default irritating. * (bug 45022) Make preference Email me when a page or file on my watchlist is changed true by default. This is a good idea. * (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. This is a good idea. In short, the first setting strikes me as bad, but I think the other two are good ideas. Date: Tue, 10 Jun 2014 13:22:26 + From: jer...@tuxmachine.com To: wikitech-l@lists.wikimedia.org Subject: Re: [Wikitech-l] Preventing MW from adding a page to watchlist On Jun 10, 2014 9:18 AM, MZMcBride z...@mzmcbride.com wrote: And sysadmins of larger wiki installations probably want to re-visit whether the user preferences defaults are appropriate for their communities. They also may wan to consider reading the release announcement emails… (e.g. http://lists.wikimedia.org/pipermail/mediawiki-announce/2014-June/000152.html ) -Jeremy ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] LiquidThreads - how do we kill it?
As someone who likes LQT (autosigning and visible threading are excellent features) and wishes Flow was basically that, but better, I personally would hope Flow would attempt to incorporate as many advantages of LQT and provide a way to convert LQT threads to Flow format as smoothly as possible if Flow is to be a true successor to LQT. Personally, I'm not as crazy about VisualEditor (I find the classic WikiEditor more comfortable for some reason), but I too see its appeal. From: dger...@gmail.com Date: Fri, 6 Jun 2014 20:48:03 +0100 To: wikitech-l@lists.wikimedia.org Subject: Re: [Wikitech-l] LiquidThreads - how do we kill it? On 6 June 2014 20:12, Martijn Hoekstra martijnhoeks...@gmail.com wrote: On Fri, Jun 6, 2014 at 11:27 AM, David Gerard dger...@gmail.com wrote: YMMV. Wikipedia is pretty much enculturated, but RationalWiki gets n00bs *all the time* who object to something on a page. You know what the most frequent reply involves? Please learn to sign your comments. If auto signatures are the best thing LQT/Flow brings, I have a bad feeling about it. That would be a distortion of my point :-) I have mostly found LQT annoying as a user, but I can see the attraction of a discussion where the threading is clearly visible, and I'm presuming extensive user testing will be done - typical mind fallacy is a serious hazard, and not one Wikimedia can afford.[1] This is why software changes on WMF wikis are ultimately up to WMF, not the wiki communities. (Of course, debacles like the introduction of VE show why caution is still sensible. And I say that as a huge fan and advocate of VE.) - d. [1] http://wiki.lesswrong.com/wiki/Typical_mind_fallacy What works for you or me cannot be presumed to work for the world. Geeks are regularly *shocked* at what ordinary people make of things. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] LiquidThreads - how do we kill it?
Going to have concur on this. Flow and VE would be great for attracting new users, but leaving the foundation of the community in the dust in favor of innovation strikes me as a bad idea. I support the idea of having the ability for the old methods of editing and talk pages to work when and where possible and for the transition to newer ideas to be as gentle as possible on those who might otherwise be alienated by the changes. Date: Sat, 7 Jun 2014 02:39:17 +0200 From: schneeschme...@googlemail.com To: wikitech-l@lists.wikimedia.org Subject: Re: [Wikitech-l] LiquidThreads - how do we kill it? 2014-06-06 22:28 GMT+02:00 S Page sp...@wikimedia.org: The tone of your message made me want to cry, quit my job, and punch the wall in frustration :( I am sorry, S, this is certainly not what I intended. I apologise for the tone of my last mail. But I appreciate you being open about your dislike and suspicion of Flow, and can only hope that over time Flow's growing feature set leads users to *want* it enabled on the talk pages they visit. The most important point about everything new the WMF is currently developing is that it really can frustrate and drive away even more old editors. The WMF only talks about new editors, but does not take into account that we need to keep the old ones in the first place. @Gerard: Losing old editors is the biggest cost of all those changes. This is why we have to keep these as small as possible and we have to avoid them wherever possible. There always has to be a switch for disabling everything new and to return to the old state. To give you some more background: Our community has suffered a lot of stress over the past years which results in frustration in many places. Many long-time editors have gone inactive because of that. Some of the stress is self-made, some came in from the German chapter, mostly last year (this will hopefully change now), and some of the stress comes from San Francisco. The latter stems mostly from new developments in technical terms. Remember that this is only a small community of only a few hundred regulars, and that we had to fight against visual editor, and when media viewer was announced the first question was whether it would still be possible to switch it off when it would not be beta any more. Many of us are exhausted and tired to fight against the Wikimedia bodies. That's why I interfere when there is talk about Flow. Both visual editor and flow have the potential of providing another and perhaps final blow to the still active old editor community. There is only one community. We don't have another one as substitutes to take over. If a wiki project is dead and broken once it will be broken forever. Regards, Jürgen. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [MediaWiki-l] Validating wiki text before saving
That's what I was looking for, thank you very much!
To: mediawiki-l@lists.wikimedia.org
Date: Mon, 19 May 2014 19:30:45 +1000
From: billinghu...@gmail.com
Subject: Re: [MediaWiki-l] Validating wiki text before saving
Sure. I would look to maybe give all the required templates the one
id=... as that makes the match for those easiest, otherwise you want to
use contains_any
contains_any is good for something like
!contains_any (user_groups, sysop, autopatrolled, ...)
At Commons, I did a simple one for main namespace that requires
gallery... just ensure that you test them for a while first, and if you
have enough people watching your RC, then tags are useful.
Best way that I learnt was just looking at different Special:AbuseFilter
and seeing what the competent were doing, and mimicking their components.
Here is a simple example of one such
article_namespace == 0 (new_wikitext regex
\[\[[Cc]ategory:\s?\d{1,4}\sworks\]\])
action = edit
!contains_any (user_groups, sysop)
You will want to do something for things being new pages.
Regards, Billinghurst
On Mon, 19 May 2014 00:19:59 -0500, Arcane 21 arc...@live.com wrote:
I was wondering if there was a way to make a filter for the following:
New pages must have one of a series of templates (any of the templates
will do, as long as at least one is present) and a category of some
sort.
This would only apply to users that are not autopatrolled, bots or
administrators.
We'd like to have something on our wiki to deter new editors that don't
follow the manual of style guidelines and so the filter would be to
encourage them to do so, with the hope and intention of encouraging good
editing.
I'm not very skilled in the use of AbuseFilter, so if someone could show
me an example filter that would fit the above (if possible), it would be
appreciated.
To: mediawiki-l@lists.wikimedia.org
Date: Mon, 19 May 2014 12:53:52 +1000
From: billinghu...@gmail.com
Subject: Re: [MediaWiki-l] Validating wiki text before saving
On Sun, 18 May 2014 19:37:25 -0400, Tom t...@hutch4.us wrote:
On May 16, 2014, at 10:01 PM, Max Semenik maxsem.w...@gmail.com
wrote:
https://www.mediawiki.org/wiki/Extension:AbuseFilter
The more I think about it the better I like using this extension as a
solution to Larry's question.
AbuseFilter is pretty flexible. There are already rules created and
being
used for missing Category(ies) from page edits. You can deny the save
or
warn and allow, plus tag the edit.
So all is needed is a filter to check all edits for a url with the
wiki's
domain name. A gentle reminder, you do not need to use this syntax
with
an
example of what to use. Or the hard road, not allowed please use
this.
Tom
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
An advantage of such an approach is that you can provide very specific,
direct and customised information and guidance. English Wikisource has
an
abuse filter that checks a namespace for specific template that is
required
to be present, and where it is not, then guidance is given on the
format,
and links to specific help pages.
https://en.wikisource.org/wiki/Special:AbuseFilter/1
In fact this was created as a filter before we even thought about its
use
in abuse settings.
Sometimes it would nice to be able to cascade filters, or exclude on
the
basis of a previous filter, however, that is not yet possible.
Regards, Billinghurst
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Validating wiki text before saving
I know even less about Semantic Forms than I do AbuseFilter, but given that you may be right, I'll have to look into that as well before we commit to anything. Thanks for the alternative suggestion. :) From: tharpena...@gmail.com Date: Mon, 19 May 2014 06:56:05 -0700 To: mediawiki-l@lists.wikimedia.org Subject: Re: [MediaWiki-l] Validating wiki text before saving Per my understanding the following needs to be done: 1.New pages must have certain templates. 2 This is to force users to follow a certain style guidelines. 3. Admin must have freedom to get around these restrictions if need be. Based on that, I think, the best solution would be to use Semantic Forms. A far easier solution then the AbuseFilter. Sent from my iPad On May 18, 2014, at 10:19 PM, Arcane 21 arc...@live.com wrote: I was wondering if there was a way to make a filter for the following: New pages must have one of a series of templates (any of the templates will do, as long as at least one is present) and a category of some sort. This would only apply to users that are not autopatrolled, bots or administrators. We'd like to have something on our wiki to deter new editors that don't follow the manual of style guidelines and so the filter would be to encourage them to do so, with the hope and intention of encouraging good editing. I'm not very skilled in the use of AbuseFilter, so if someone could show me an example filter that would fit the above (if possible), it would be appreciated. To: mediawiki-l@lists.wikimedia.org Date: Mon, 19 May 2014 12:53:52 +1000 From: billinghu...@gmail.com Subject: Re: [MediaWiki-l] Validating wiki text before saving On Sun, 18 May 2014 19:37:25 -0400, Tom t...@hutch4.us wrote: On May 16, 2014, at 10:01 PM, Max Semenik maxsem.w...@gmail.com wrote: https://www.mediawiki.org/wiki/Extension:AbuseFilter The more I think about it the better I like using this extension as a solution to Larry's question. AbuseFilter is pretty flexible. There are already rules created and being used for missing Category(ies) from page edits. You can deny the save or warn and allow, plus tag the edit. So all is needed is a filter to check all edits for a url with the wiki's domain name. A gentle reminder, you do not need to use this syntax with an example of what to use. Or the hard road, not allowed please use this. Tom ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l An advantage of such an approach is that you can provide very specific, direct and customised information and guidance. English Wikisource has an abuse filter that checks a namespace for specific template that is required to be present, and where it is not, then guidance is given on the format, and links to specific help pages. https://en.wikisource.org/wiki/Special:AbuseFilter/1 In fact this was created as a filter before we even thought about its use in abuse settings. Sometimes it would nice to be able to cascade filters, or exclude on the basis of a previous filter, however, that is not yet possible. Regards, Billinghurst ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
[MediaWiki-l] Is there a version of the Navigation Popups gadget that works on MW 1.23?
I tried importing the Wikipedia version of Navigation Popups gadget to my wiki (currently running MW 1.23 RC1) and it doesn't seem to work. Is there an earlier version that does work on MW 1.23? ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Validating wiki text before saving
I was wondering if there was a way to make a filter for the following: New pages must have one of a series of templates (any of the templates will do, as long as at least one is present) and a category of some sort. This would only apply to users that are not autopatrolled, bots or administrators. We'd like to have something on our wiki to deter new editors that don't follow the manual of style guidelines and so the filter would be to encourage them to do so, with the hope and intention of encouraging good editing. I'm not very skilled in the use of AbuseFilter, so if someone could show me an example filter that would fit the above (if possible), it would be appreciated. To: mediawiki-l@lists.wikimedia.org Date: Mon, 19 May 2014 12:53:52 +1000 From: billinghu...@gmail.com Subject: Re: [MediaWiki-l] Validating wiki text before saving On Sun, 18 May 2014 19:37:25 -0400, Tom t...@hutch4.us wrote: On May 16, 2014, at 10:01 PM, Max Semenik maxsem.w...@gmail.com wrote: https://www.mediawiki.org/wiki/Extension:AbuseFilter The more I think about it the better I like using this extension as a solution to Larry's question. AbuseFilter is pretty flexible. There are already rules created and being used for missing Category(ies) from page edits. You can deny the save or warn and allow, plus tag the edit. So all is needed is a filter to check all edits for a url with the wiki's domain name. A gentle reminder, you do not need to use this syntax with an example of what to use. Or the hard road, not allowed please use this. Tom ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l An advantage of such an approach is that you can provide very specific, direct and customised information and guidance. English Wikisource has an abuse filter that checks a namespace for specific template that is required to be present, and where it is not, then guidance is given on the format, and links to specific help pages. https://en.wikisource.org/wiki/Special:AbuseFilter/1 In fact this was created as a filter before we even thought about its use in abuse settings. Sometimes it would nice to be able to cascade filters, or exclude on the basis of a previous filter, however, that is not yet possible. Regards, Billinghurst ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Extension matrix not being updated
Awhile back, the bot that used to update that section died. From: aklap...@wikimedia.org To: mediawiki-l@lists.wikimedia.org Date: Thu, 1 May 2014 23:40:48 +0200 Subject: Re: [MediaWiki-l] Extension matrix not being updated On Thu, 2014-05-01 at 13:42 -0700, Chris Tharp wrote: So does anyone know why the Extension Matrix is not being updated? https://bugzilla.wikimedia.org/show_bug.cgi?id=61147 andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [Wikitech-l] Text-to-speech extension?
I'm not disabled myself, but I do see the benefits in such a venture, and assuming there is text-to-speech program with a MediaWiki friendly API (or at least can hook into MediaWiki fairly well) that could be used as a backend, I would think this would not only be possible, but a great idea. Date: Tue, 29 Apr 2014 02:49:51 +0200 From: ilias.k...@freemail.gr To: wikitech-l@lists.wikimedia.org Subject: [Wikitech-l] Text-to-speech extension? Hello, and thank you for your work, I was looking at the Librivox project today and I thought that it'd be great to have voice support in Mediawiki, to aid people with sight impairments or disabilities. So I was wondering whether there is a text-to-speech extension for Mediawiki, or if there could be some other means of offering wiki pages in audio form. Thanks for your time as well, Ilias K. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [MediaWiki-l] MediaWiki hooks and parameters
I recommend using the MW 1.22.4 tarball to base this on. The MW 1.22.3
extensions are the wrong branch and produce errors, assuming you're using the
Cite extension that was bundled with the 1.22.3 tarball..
From: amelia.irel...@gmod.org
Date: Thu, 13 Mar 2014 14:18:54 -0700
To: mediawiki-l@lists.wikimedia.org
Subject: [MediaWiki-l] MediaWiki hooks and parameters
Hello,
I'm having a little trouble getting a custom hook to perform the actions I
want
it to after upgrading from PHP 5.3 / MW 1.19.2 to PHP 5.4 / MW 1.22.3.
I am hacking an existing extension, ProcessCite, that integrates into the
Cite
extension by adding a custom hook to one of Cite's functions:
# from Cite_body.php
function stack( $str, $key = null, $group, $follow, $call ) {
# add the call to the CiteBeforeStackEntry hook
wfRunHooks( 'CiteBeforeStackEntry', array( $str, $call ) );
ProcessCite runs code that creates a value for $str based on the contents of
$call. Here are the relevant parts of ProcessCite:
# Declare the hook:
$wgHooks['CiteBeforeStackEntry'][] = 'wfProcessCite';
# the function itself
function wfProcessCite($str, $argv){
# process $argv and $str to create a new version of $str
# $argv remains unchanged, $str is set to new value
$str = new string;
return true;
}
Debug statements reveal that wfProcessCite is creating the correct value for
$str, but the value is not altered when wfProcessCite finishes. I am not
sure
if I am calling the hook in the wrong way, given that I want to alter the
value of $str.
The MW manual page on hooks (http://www.mediawiki.org/wiki/Manual:Hooks) is
somewhat confusing -- what is the difference between passing $someData to a
function versus passing a set of parameters?!
Any help would be appreciated!
Thank you,
Amelia.
--
Amelia Ireland
GMOD Community Support
Generic Model Organism Database project
http://gmod.org || @gmodproject
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
[MediaWiki-l] Getting a very strange error with Special:Gadgets on MW 1.22.3
Whenever I try to enter Special Gadgets on my localhost wiki, I get the
following messages:
[d6ed31cf] /allthetropes/index.php/Special:Gadgets Exception from line 376 of
C:\xampp\htdocs\allthetropes\includes\SpecialPage.php: Call to undefined method
SpecialGadgets::getPageTitle
Backtrace:
#0 C:\xampp\htdocs\allthetropes\extensions\Gadgets\SpecialGadgets.php(98):
SpecialPage-__call(string, array)
#1 C:\xampp\htdocs\allthetropes\extensions\Gadgets\SpecialGadgets.php(98):
SpecialGadgets-getPageTitle(string)
#2 C:\xampp\htdocs\allthetropes\extensions\Gadgets\SpecialGadgets.php(30):
SpecialGadgets-showMainForm()
#3 C:\xampp\htdocs\allthetropes\includes\SpecialPage.php(631):
SpecialGadgets-execute(NULL)
#4 C:\xampp\htdocs\allthetropes\includes\SpecialPageFactory.php(488):
SpecialPage-run(NULL)
#5 C:\xampp\htdocs\allthetropes\includes\Wiki.php(298):
SpecialPageFactory::executePath(Title, RequestContext)
#6 C:\xampp\htdocs\allthetropes\includes\Wiki.php(602):
MediaWiki-performRequest()
#7 C:\xampp\htdocs\allthetropes\includes\Wiki.php(467): MediaWiki-main()
#8 C:\xampp\htdocs\allthetropes\index.php(49): MediaWiki-run()
#9 {main}
Notice: Uncommitted DB writes (transaction from DatabaseBase::query
(User::loadFromDatabase)). in
C:\xampp\htdocs\allthetropes\includes\db\Database.php on line 3944
Gadgets themseves work fine, and I can manually edit the CSS/JS files for them
without a, I just can't access the special page for them at all and have no
idea why.
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Getting a very strange error with Special:Gadgets on MW 1.22.3
Thanks for clearing that up. To: mediawiki-l@lists.wikimedia.org Date: Wed, 12 Mar 2014 22:26:43 +0100 From: matma@gmail.com Subject: Re: [MediaWiki-l] Getting a very strange error with Special:Gadgets on MW 1.22.3 The 1.22.3 tarball is hopelessly broken beyond repair. Don't use it. https://bugzilla.wikimedia.org/show_bug.cgi?id=62101 -- Matma Rex ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [Wikitech-l] Preview of the proposal for MediaWiki Homepage
The picture at the top and most of the other icons need shrunk a little, and the page needs to fit more items together (it looks rather spaced out), but I do like the icon choices. It would also benefit from some more frames to separate the page sections IMO. Otherwise, looks great. :) From: monteirobr...@gmail.com Date: Mon, 24 Feb 2014 17:54:13 -0300 To: wikitech-l@lists.wikimedia.org Subject: [Wikitech-l] Preview of the proposal for MediaWiki Homepage Hello everyone, I would like to invite you to take a look the preview [1] of MediaWiki Homepage. Your opinion, contribution and help are very welcome. Thank you. Best regards, [1] https://www.mediawiki.org/wiki/MediaWiki/Homepage_redesign/Preview Brena Monteiro +55 27 98109 0123 @monteirobrena http://twitter.com/monteirobrena Reflexões Brenianas http://monteirobrena.wordpress.com ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Drop support for PHP 5.3
I support this. Adequate testing of 5.4 before abandonment of 5.3 would be a sensible prelude to any major decision concerning this matter. Date: Fri, 21 Feb 2014 16:37:24 -1000 From: canan...@wikimedia.org To: wikitech-l@lists.wikimedia.org Subject: Re: [Wikitech-l] Drop support for PHP 5.3 On Feb 18, 2014 8:11 AM, Faidon Liambotis fai...@wikimedia.org wrote: Last time we were discussing PHP 5.4 it was quite a while ago but I remember hearing that we'd need to do some porting work for our extensions. Is this still the case? If so, it seems the first step would be for WMF to ensure that it can run on 5.4 (and transition prod to 5.4?), before dropping support for 5.3. --scott ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Drop support for PHP 5.3
Being a firm believer in the LTS model, I support David's take on this issue. Besides, they tend to be tested and reliable and have a longer support window by default, so it makes sense to support them in turn. From: dger...@gmail.com Date: Fri, 21 Feb 2014 01:04:39 + To: wikitech-l@lists.wikimedia.org Subject: Re: [Wikitech-l] Drop support for PHP 5.3 On 21 February 2014 01:00, Techman224 techman...@techman224.ca wrote: Let me put this out there so there isn’t confusion. The regular 6 month releases of Ubuntu are the stable releases. A LTS release is released every two years on the same cycle as regular Ubuntu releases. A LTS release is certainly more stable than regular releases, but not calling regular releases stable is a bit misleading. For server purposes, I think we can stick to LTSes. Approximately nobody runs a non-LTS Ubuntu for their web hosting. (And even less now that non-LTSes are only getting a nine-month lifetime.) - d. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [MediaWiki-l] Need help rendering SVG files on my localhost wiki
Thanks for the link. It looks like ImageMagick is rather poor for viewing
certain SVG files, so I'm glad to know there are some alternatives I can use.
Again, thanks for the help.
Date: Thu, 23 Jan 2014 09:03:13 +0100
From: sigb...@wiwi.hu-berlin.de
To: mediawiki-l@lists.wikimedia.org
Subject: Re: [MediaWiki-l] Need help rendering SVG files on my localhost wiki
Hi, according to
http://www.mediawiki.org/wiki/Manual:Image_administration#SVG you might
need to change the rendering software.
Sigbert
Am 23.01.2014 02:08, schrieb Arcane 21:
SVG files render poorly on my localhost wiki, with the colors often blacked
out. I have ImageMagick installed to render graphic files, and everything
but SVG files renders well.
I'm running MediaWiki 1.22.1 on Windows 7 SP1 64bit with
PHP
5.4.19 (apache2handler)
MySQL
5.5.32
My LocalSettings:
## To enable image uploads, make sure the 'images' directory
## is writable, then set this to true:
$wgEnableUploads = true;
$wgUseImageMagick = true;
$wgImageMagickConvertCommand = C:\\Program Files
(x86)\\ImageMagick-6.8.7-Q16\\convert.exe;
$wgFileExtensions =
array('png','gif','jpg','jpeg','doc','xls','mpp','pdf','ppt','tiff','bmp','docx',
'xlsx', 'pptx','ps','odt','ods','odp','odg','svg');
Any help with resolving the issue would be appreciated.
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
[MediaWiki-l] Need help rendering SVG files on my localhost wiki
SVG files render poorly on my localhost wiki, with the colors often blacked
out. I have ImageMagick installed to render graphic files, and everything but
SVG files renders well.
I'm running MediaWiki 1.22.1 on Windows 7 SP1 64bit with
PHP
5.4.19 (apache2handler)
MySQL
5.5.32
My LocalSettings:
## To enable image uploads, make sure the 'images' directory
## is writable, then set this to true:
$wgEnableUploads = true;
$wgUseImageMagick = true;
$wgImageMagickConvertCommand = C:\\Program Files
(x86)\\ImageMagick-6.8.7-Q16\\convert.exe;
$wgFileExtensions =
array('png','gif','jpg','jpeg','doc','xls','mpp','pdf','ppt','tiff','bmp','docx',
'xlsx', 'pptx','ps','odt','ods','odp','odg','svg');
Any help with resolving the issue would be appreciated.
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [Wikitech-l] Revamping interwiki prefixes
If I might weigh in here, I don't see the harm in including all the WMF wikis onto the interwiki map. MediaWiki is intensely related to the WMF, so those links make logical sense and it does no harm to include them in my opinion. Date: Thu, 16 Jan 2014 22:40:37 -0500 From: nathanlarson3...@gmail.com To: wikitech-l@lists.wikimedia.org Subject: Re: [Wikitech-l] Revamping interwiki prefixes On Thu, Jan 16, 2014 at 7:35 PM, This, that and the other at.li...@live.com.au wrote: I can't say I care about people reading through the interwiki list. It's just that with the one interwiki map, we are projecting our internal interwikis, like strategy:, foundation:, sulutil:, wmch: onto external MediaWiki installations. No-one needs these prefixes except WMF wikis, and having these in the global map makes MediaWiki look too WMF-centric. It's a WMF-centric wikisphere, though. Even the name of the software reflects its connection to Wikimedia. If we're going to have a super-inclusive interwiki list, then most of those Wikimedia interwikis will fit right in, because they meet the criteria of having non-spammy recent changes and significant content in AllPages. If you're saying that having them around makes MediaWiki look too WMF-centric, it sounds like you are concerned about people reading through the interwiki list and getting a certain impression, because how else would they even know about the presence of those interwiki prefixes in the global map? I don't see the need for instruction creep here. I'm for an inclusive interwiki map. Inactive wikis (e.g. RecentChanges shows only sporadic non-spam edits) and non-established wikis (e.g. AllPages shows little content) should be excluded. So far, there have been no issues with using subjective criteria at meta:Talk:Interwiki map. I dunno about that. We have urbandict: but not dramatica: both of which are unreliable sources, but likely to be used on third-party wikis (at least the ones I edit). We have wikichristian: (~4,000http://www.wikichristian.org/index.php?title=Special:Statisticscontent pages) but not rationalwiki: ( ~6,000 http://rationalwiki.org/wiki/Special:Statistics content pages). The latter was rejectedhttps://meta.wikimedia.org/w/index.php?title=Talk%3AInterwiki_mapdiff=4573672oldid=4572621awhile ago. Application of the subjective criteria seems to be hit-or-miss. If we're going to have a hyper-inclusionist system of canonical interwiki prefixes https://www.mediawiki.org/wiki/Canonical_interwiki_prefixes, we might want to use WikiApiary and/or WikiIndex rather than MediaWiki.org as the venue. These wikis that already have a page for every wiki could add another field for interwiki prefix to those templates and manage the interwiki prefixes by editing pages. Thingles saidhttps://wikiapiary.com/w/index.php?title=User_talk%3AThinglesdiff=409395oldid=408940he'd be interested in WikiApiary's getting involved. The only downside is that WikiApiary doesn't have non-MediaWiki wikis. It soundedhttp://wikiindex.org/index.php?title=User_talk:Leucostictediff=prevoldid=144256as though Mark Dilley might be interested in WikiIndex's playing some role in this too. But even WikiIndex has the problem of only containing wikis; the table will have to have other websites as well. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] I'm back from Hacker School
Welcome back, Sumana! From: suma...@wikimedia.org Date: Fri, 3 Jan 2014 22:48:22 -0500 To: wikitech-l@lists.wikimedia.org Subject: [Wikitech-l] I'm back from Hacker School Hi! As of yesterday, I'm back after my three-month sabbatical at Hacker School. I'm in catchup mode so I haven't yet resubscribed to most lists, nor quite taken back over Engineering Community Team (Quim Gil is still in charge until sometime next week when I feel back up to speed). Thank you to WMF for the sabbatical program, thanks to my boss Rob Lanphier for his support, and thanks to my team. I was able to walk away worry-free for three great months because I knew that Andre Klapper, Quim Gil, and Guillaume Paumier had my back. :) Sumana Harihareswara Engineering Community Manager Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] PHP new version(s) 5.5.7 and other versions. (upgrade, if you can)
I've tried PHP 5.5.0, had to go back to PHP 4.4.9 due to issues with deleting and moving pages in MediaWiki. From: p858sn...@gmail.com Date: Mon, 16 Dec 2013 19:08:24 +1000 To: wikitech-l@lists.wikimedia.org Subject: Re: [Wikitech-l] PHP new version(s) 5.5.7 and other versions. (upgrade, if you can) Who? What? When? Where? Why? On Mon, Dec 16, 2013 at 5:05 PM, Thomas Gries m...@tgries.de wrote: PHP users are strongly advised to upgrade their PHP versions: PHP 4.0.6 - PHP 4.4.9 PHP 5.0.x PHP 5.1.x PHP 5.2.x PHP 5.3.0 - PHP 5.3.27 PHP 5.4.0 - PHP 5.4.22 PHP 5.5.0 - PHP 5.5.6 Vendor Status: Vendor has released PHP 5.5.7, PHP 5.4.23 and PHP 5.3.28|.|| If you compile PHP from its sources, then the following configure works well: | |./configure --prefix=/usr --datadir=/usr/share/php --mandir=/usr/share/man --bindir=/usr/bin --libdir=/usr/share --includedir=/usr/include --sysconfdir=/etc --with-libdir=lib64 --with-config-file-path=/etc --with-apxs2=/usr/sbin/apxs2-prefork --with-openssl --with-bz2 --with-zlib --with-curl --with-ldap --with-mysql --with-mysqli=mysqlnd --with-pdo-mysql --enable-mbstring --with-xsl --enable-calendar --with-gd --with-jpeg-dir=/usr/lib64 --with-png-dir=/usr/lib64 --with-iconv --with-pspell --with-gmp --with-mcrypt --enable-zip --enable-bcmath make make install | ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] PHP new version(s) 5.5.7 and other versions. (upgrade, if you can)
Thanks for the suggestion Tyler, I'll be sure to file a report. From: tylerro...@gmail.com Date: Mon, 16 Dec 2013 07:58:38 -0500 To: wikitech-l@lists.wikimedia.org Subject: Re: [Wikitech-l] PHP new version(s) 5.5.7 and other versions. (upgrade, if you can) On Mon, Dec 16, 2013 at 7:08 AM, Arcane 21 arc...@live.com wrote: I've tried PHP 5.5.0, had to go back to PHP 4.4.9 due to issues with deleting and moving pages in MediaWiki. Is there a bug filed for this. If not please do so. MediaWiki should be compatible with newer PHP versions. *-- * *Tyler Romeo* Stevens Institute of Technology, Class of 2016 Major in Computer Science ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] PHP new version(s) 5.5.7 and other versions. (upgrade, if you can)
I submitted a bug report describing the problem in more details on the Wikimedia Bugzilla, but short version is that when deleting or moving multiple pages at once, I experienced severe server lag and timeouts, and the job queue seemed to process the requests in PHP very slowly in PHP 5.5.0. I rolled back to 5.4, and it's working fine. More details can be found on the bug report I submitted on Bugzilla. Date: Mon, 16 Dec 2013 23:36:17 +0100 From: m...@tgries.de To: wikitech-l@lists.wikimedia.org Subject: Re: [Wikitech-l] PHP new version(s) 5.5.7 and other versions. (upgrade, if you can) Am 16.12.2013 13:08, schrieb Arcane 21: I've tried PHP 5.5.0, had to go back to PHP 4.4.9 due to issues with deleting and moving pages in MediaWiki. We need more details. Which version of MediaWiki do you use ? I never encountered any problems with the latest PHP versions 5.5.0...5.5.7 and latest MediaWiki core. If you compile PHP from its sources, then the following configure works well: ./configure --prefix=/usr --datadir=/usr/share/php --mandir=/usr/share/man --bindir=/usr/bin --libdir=/usr/share --includedir=/usr/include --sysconfdir=/etc --with-libdir=lib64 --with-config-file-path=/etc --with-apxs2=/usr/sbin/apxs2-prefork --with-openssl --with-bz2 --with-zlib --with-curl --with-ldap --with-mysql --with-mysqli=mysqlnd --with-pdo-mysql --enable-mbstring --with-xsl --enable-calendar --with-gd --with-jpeg-dir=/usr/lib64 --with-png-dir=/usr/lib64 --with-iconv --with-pspell --with-gmp --with-mcrypt --enable-zip --enable-bcmath make make install ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[MediaWiki-l] Notice to all MW users with Apache PHP 5.5
I have a localhost test wiki that was using Apache PHP 5.5, which I downgraded back to PHP 5.4. While 5.5 did deliver better response time for most things like page requests, I suffered severe lag and server timeouts when attempting to do multiple page moves and especially page deletions. On PHP 5.4, the response time is slightly slower for almost all operations, but I do not have the lag and timeout issues I experienced on 5.5. I do not know if this is common to all users of Apache PHP 5.5, so I do not know if this is a common issue, but I felt it wouldn't hurt to share with the rest of MediaWiki community. Also, if using the XAMPP stack, I recommend XAMPP 1.8.2 over 1.8.3 since the former has PHP 5.4 and the latter PHP 5.5 ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] SPAMMERS!!!!
Some additional tips. On my wiki, we use ConfirmEdit with Asirra (requires 5-10 edits to disable), which I find to be one of the more effective captchas to frustrate spammers. I also find it useful to check user all the user names that are obvious gibberish and determine which ones come from the same IP and IP ranges. Genrally, if you want to be sure you aren't punishing legitimate users, only block the IPs and IP ranges that have four or more obvious spammer usernames attached to them, as these are usually mass produced by a bot from zombie computers used to spam. Date: Tue, 26 Nov 2013 06:33:24 + From: stephdech...@gmail.com To: mediawiki-l@lists.wikimedia.org Subject: Re: [MediaWiki-l] SPAMMERS Why you need to delete those spammer accounts? I thought to ban them with their IP address is enough unless others from the same IP address want to contribute to your wiki. Actually at that time when my wiki was under spamming, I accidentally blocked two IP addresses, and suddenly.. No more spammers :D or at least not that more. I don't think your wiki would have so much people registering to manually, so that spamming must be done with a program which came from one or several IPs. Moreover, I tried to use ReCaptcha from Extension: ConfirmEdithttps://www.mediawiki.org/wiki/Extension:ConfirmEditto protect my wiki from spammers, but still failed. I was told that some of the spamming accounts are registered manually and then spammed automatically. Why not ask everyone with edits less than 3 or 5 to do ReCaptcha? User name blacklist can also help on stop others to spam... My wiki is in Chinese, and I set that none of the user with a username begins with [a..zA..z0..9] alphanumerical charater can register to my wiki. No spammers so far. After that, if you still decide to delete those spamming accounts with their pages, you might try Extension: UserMergehttps://www.mediawiki.org/wiki/Extension:UserMergeor even try to hack it to see if there's anyway to use it to delete a lot of users once. Or if some users did a lot of spamming work, you might also try Extension: Nuke https://www.mediawiki.org/wiki/Extension:Nuke. For more extensions to help you stop others spamming, why not have a look on how Wikipedia did? Spam prevention *Abuse Filter https://www.mediawiki.org/wiki/Extension:AbuseFilter *Applies automatic heuristics to edits Andrew Garrett, River Tarnell, Victor Vasiliev and Marius Hoch *AntiBot https://www.mediawiki.org/wiki/Extension:AntiBot *Simple framework for spambot checks and trigger payloads Tim Starling *AntiSpoof https://www.mediawiki.org/wiki/Extension:AntiSpoof *Blocks the creation of accounts with mixed-script, confusing and similar usernames Brion Vibber *AntiSpoof for CentralAuth https://www.mediawiki.org/wiki/Extension:AntiSpoof *Adds AntiSpoof technology to CentralAuth Sam Reed *ConfirmEdit https://www.mediawiki.org/wiki/Extension:ConfirmEdit (Version 1.2)*Provides CAPTCHA techniques to protect against spam and password-guessing Brion Vibber and others *SpamBlacklist https://www.mediawiki.org/wiki/Extension:SpamBlacklist *Regex-based anti-spam tool allowing to blacklist URLs in pages and email addresses for registered users Tim Starling, John Du Hart and Daniel Kinzler *Title Blacklist https://www.mediawiki.org/wiki/Extension:Title_Blacklist (Version 1.4.2)*Allows administrators to forbid creation of pages and user accounts per a blacklisthttp://en.wikipedia.org/wiki/MediaWiki:Titleblacklistand whitelist http://en.wikipedia.org/wiki/MediaWiki:Titlewhitelist Victor Vasiliev and Fran Rogers *TorBlock https://www.mediawiki.org/wiki/Extension:TorBlock *Allows tor exit nodes to be blocked from editing a wiki Andrew Garrett 2013/11/25 Jonathan Aquilina eagles051...@gmail.com Hi John, I am helping the document foundation with spam issues, and they report a drastic drop of registrations with questy which is really good. I am currently working on being able to have localized questions for the said project. I am not sure how to exactly answer your question though. My wiki though public does not accept registrations at all. I am the only one with an account. On Mon, Nov 25, 2013 at 10:16 PM, John W. Foster jfoster81...@gmail.com wrote: Wow. I am getting clobbered, or was. I shut down the new account system that was open to the public and set it to be by e-mail confirmation, then disabled e-mail for a while.. I then used the deletUnusedAccounts.php a couple of times and it deleted 17860 of the spammers. But they are a persistant lot and some of them actually did manage to get pages up and running, actually hundreds or maybe thousands of them. The challenge is How do I get rid of them?, doing it one at a time is useless. How to keep them at bay. I would appreciate any tips regarding this. expecially actual mediawiki settings that get rid of them. I
[MediaWiki-l] Suffering frequent problems with deleting multiple pages in MediaWiki
Whenever I try to delete multiple pages in MediaWiki on my localhost wiki, the first page deleted (if I'm deleting more than one at a time) go well, but the rest take a really long time before they are deleted. I get similar issues when opening lots of tabs to check out the contents of multiple pages, but its when trying to delete multiple pages does the problem get really bad. In fact, the problem is characterized by the pages taking really long to load and update every time it crops up. I suspect it's a problem with my PHP settings, but I'm not sure what I should change. I'm running MediaWiki 1.22wmf22 on Windows 7 with the following: MediaWiki 1.22wmf22 PHP 5.5.0 (apache2handler) MySQL 5.6.11 ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [Wikitech-l] Applying nofollow only to external links added in revisions that are still unpatrolled
I agree. While spammers are so pathetic they will do anything for page views, I have to admire (and detest) their ability to adapt in order to spread their nonsense. Anything that slows them down, even in the slightest degree, is something I support and recommend. Date: Mon, 18 Nov 2013 09:24:54 -0500 From: m...@uberbox.org To: wikitech-l@lists.wikimedia.org Subject: Re: [Wikitech-l] Applying nofollow only to external links added in revisions that are still unpatrolled On 11/18/2013 04:39 AM, Happy Melon wrote: I'm sure spam directed at, say, enwiki, would get very subtle very quickly if spammers thought there was a real chance of it being able to use enwiki's pagerank weight. Don't underestimate spammers' ability to learn and adapt. Also +1; pagerank is a valuable thing and Wikipedia has lots of it. Spammers would be quick to find ways to cheat, lie and manipulate their way into tapping into it. Right now, we are plagued with the spammers that are too desperate or stupid to care; if we turned nofollow off, they would all descend upon us like a plague of locusts. -- Marc ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Updating the RELEASE-NOTES format for 1.22 and 1.23
Seems like a reasonable approach to me. The old release notes were a little hard to follow, but your suggestion should make them more straightforward from now on. Date: Thu, 7 Nov 2013 22:21:52 -0500 From: m...@nichework.com To: wikitech-l@lists.wikimedia.org Subject: [Wikitech-l] Updating the RELEASE-NOTES format for 1.22 and 1.23 I've already posted to mediawiki-l to try and get input from end users on these proposed changes [1], but I'd like to see if we can't change the RELEASE-NOTES format for the time that we're working on 1.23. The main thing I've done is a bit of reordering and collection: * New features * Breaking changes (collected in a single section) * Configuration changes * Bug fixes * API changes * Language updates * Misc changes This is an effort to put the things users to know most about in a new release at the top of the file. This could even be done using git comments as others have suggested. Does this seem like a reasonable approach going forward? Thanks for any comments, Mark. [1] http://article.gmane.org/gmane.org.wikimedia.mediawiki/42443 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Officially supported MediaWiki hosting service?
I have a wiki there, and Orain is actually pretty decent as wiki farms go, though they could probably use more regular staff members. It is non profit for the forseeable future, though ads have been discussed only as in opt in option for those that want them. Date: Wed, 2 Oct 2013 21:33:35 -0400 From: m...@nichework.com To: wikitech-l@lists.wikimedia.org Subject: Re: [Wikitech-l] Officially supported MediaWiki hosting service? On 10/02/2013 07:17 PM, phoebe ayers wrote: I have needed such a thing for wikis for small non-profits/library associations that I've been involved with, where I didn't want to host it myself (because I didn't want to take personal responsibility for the site of an organization that I might not stay involved with, and because I don't really have the chops to deal with security and spam issues); but also did not have a good hosting option with a larger organization or library, which I find are often not very familiar with mediawiki (e.g. I've been trying to get our library systems dept. to install some basic extensions for our internal mediawiki for a couple years now). There's not a lot of money in that particular use case, unfortunately, but I imagine I'm not alone in that need either. Did you see the Orain wikifarm? https://meta.orain.org/ It seems to be targeted to the non-profit use case. Mark. -- Mark A. Hershberger NicheWork LLC 717-271-1084 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [MediaWiki-l] Fwd: [Wikitech-l] Officially supported MediaWiki hosting service?
Wikia allows anyone to create a wiki by simply following a simple form and filling in some basic information. Once that's done, you can start working on your new wiki. Their own rules allow the hosting of anything except adult content (i.e. - pornographic) like most other wiki services. They are completely ad supported, so there is no cost to host a wiki. They will install several extensions by request, including Semantic MediaWiki and several extensions (albeit somewhat older versions), but they only have Monobook as the other skin besides the Oasis skin, and they otherwise don't allow much in the way of customization, especially anything that might interfere with the placement of ads on a site wide basis. To: mediawiki-l@lists.wikimedia.org From: wjhon...@aol.com Date: Tue, 1 Oct 2013 20:31:46 -0400 Subject: Re: [MediaWiki-l] Fwd: [Wikitech-l] Officially supported MediaWiki hosting service? I was always under the impression that Wikia *approves* sites. You can't just have them host anything you want, they have to agree to it. Is that not the case? Also would you know what they charge? -Original Message- From: Ed Swing ed.sw...@sas.com To: MediaWiki announcements and site admin list mediawiki-l@lists.wikimedia.org Sent: Tue, Oct 1, 2013 5:21 pm Subject: Re: [MediaWiki-l] Fwd: [Wikitech-l] Officially supported MediaWiki hosting service? There is always Wikia. They're a few versions behind, but host a TON of wikis already. You can even have them enable various extensions (like Semantic Bundle). From: mediawiki-l-boun...@lists.wikimedia.org [mediawiki-l-boun...@lists.wikimedia.org] on behalf of Mlpearc [mlpe...@everythingfoodanddrink.org] Sent: Tuesday, October 01, 2013 7:13 PM To: MediaWiki announcements and site admin list Subject: Re: [MediaWiki-l] Fwd: [Wikitech-l] Officially supported MediaWiki hosting service? This would be interesting for my little farm, I have the time to put into it but not the needed know how to fix issues, install some extensions etc, but as Wjhonson states it would have to be adorable to those users. * Mlpearc* Founder Everything Food Drink.org everythingfoodanddrink.orghttp://www.everythingfoodanddrink.org/w/index.php/Main_Page Phone: 760-718-1290 On Tue, Oct 1, 2013 at 12:21 PM, Nikolas Everett never...@wikimedia.orgwrote: Atlassian sells a Confluence in the cloud at a per seat cost. VisualEditor would make MediaWiki a decent competitor from the perspective of the corporate types I've seen involved in such purchasing decisions. I'm not sure how much traction it'd have but there is something to say for MediaWiki being the wiki that everyone is used to. Nik On Tue, Oct 1, 2013 at 3:13 PM, Andre Polykanine an...@oire.org wrote: Hi everyone, Agreed with Brion completely. Such hosting would be an extremely useful thing, but it should have no ads (at least as a payed option), be able to redirect to a custom domain, and have all the things Brion mentioned. I would pay for it, I think. -- With best regards from Ukraine, Andre Skype: Francophile My blog: http://oire.org/menelion (mostly in Russian) Twitter: http://twitter.com/m_elensule Facebook: http://facebook.com/menelion ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] How to anonymise MW database?
I can't think of anything offhand. You might want to run a database search to make sure none of those values in those user fields is available elsewhere on the database in cleartext, but otherwise, you should be fine. To: mediawiki-l@lists.wikimedia.org From: a.niel...@shikadi.net Date: Sat, 28 Sep 2013 22:51:38 +1000 Subject: [MediaWiki-l] How to anonymise MW database? Hi all, Just as a safety net I'd like to publish copies of the databases powering my MediaWiki installations, so that if I lose all my data and backups, I might still be able to get something back (as well as reassuring my users that their contributions won't be lost forever!) I don't want to publish the raw database dump because it contains people's e-mail addresses and password hashes, but I'm thinking that perhaps if I take a copy of the database and erase the values in those tables, I might be able to export and publish the 'anonymised' copy. I'd rather not omit the user table entirely, because if I do ever need to restore the wiki from this copy I'll need it to associate the right account with each edit. Does anyone know which fields contain sensitive data that I should remove? I can see these obvious candidates: user.user_password user.user_newpassword user.user_email user.user_token user.user_email_token Are there any others that are potentially confidential and should not be made public? Many thanks, Adam. ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [Wikitech-l] Can we help Tor users make legitimate edits?
I like this idea. Not every Tor user is vandal or troll, and assuming that all of them are by default is not assuming good faith. Some people are just really paranoid about their internet anonymity or live in restrictive countries (both of which I sympathize with), so this idea would let them edit in good faith while filtering out vandal/troll edits. It would also be a good idea to apply this to certain IP ranges like government/office buildings for similar reasons. Date: Fri, 27 Sep 2013 19:40:53 -0400 From: suma...@wikimedia.org To: wikitech-l@lists.wikimedia.org; e...@dymaxion.org Subject: Re: [Wikitech-l] Can we help Tor users make legitimate edits? This is a quick followup to http://www.gossamer-threads.com/lists/wiki/wikitech/323006 and partly in keeping with the anti-vandalism discussion at http://www.gossamer-threads.com/lists/wiki/wikitech/392727 as well. On 12/27/2012 07:26 PM, Sumana Harihareswara wrote: TL;DR: A few ideas follow on how we could possibly help legit editors contribute from behind Tor proxies [snip] 4) Allow more users the IP block exemption, possibly even automatically after a certain number of unreverted edits, but with some kind of FlaggedRevs integration; Tor users can edit but their changes have to be reviewed before going live. We could combine this with (3); Nymble administrators or token-issuers could pledge to review edits coming from Tor. But that latter idea sounds like a lot of social infrastructure to set up and maintain. From talking to Eleanor Saitta: could we do FlaggedRevs by IP space, and/or by the intersection of IPs and topic space? Basically, let people edit from Tor IPs (and/or whitelist or blacklist categories) as long as those go through a FlaggedRevs-type process? And we could also do FlaggedRevs on specific IP ranges, like blocks that are known to be certain government office buildings. -- Sumana Harihareswara Engineering Community Manager Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Advance notice: I'm taking a sabbatical October-December
Good luck and have fun, Sumana! :) Date: Fri, 27 Sep 2013 20:31:37 -0400 From: suma...@wikimedia.org To: wikitech-l@lists.wikimedia.org Subject: Re: [Wikitech-l] Advance notice: I'm taking a sabbatical October-December Well, off I go. I'm about to unsubscribe from this list for the first time in years. Looking forward to returning in January with MORE POWERS. -Sumana P.S. I'm sure you can find my personal email address if you need to. :) On 09/04/2013 09:47 PM, Sumana Harihareswara wrote: Thanks, Oren! If I am able to work on pywikipediabot or other Wikimedia tech and I blog about it, I'll syndicate to http://en.planet.wikimedia.org . I may cross-post additional thoughts to http://geekfeminism.org/ . If people want a summary IRC office hour/video tech talk after I come back, I could do that too. -Sumana On 08/31/2013 07:57 AM, Oren Bochman wrote: Congratulations - I hope you get co make many new bugs and even do some cool coding outside the wmf! I'm wandering if you'll update us about this unique experience as time allows? On Wednesday, August 28, 2013, Sumana Harihareswara wrote: I've been accepted to Hacker School https://www.hackerschool.com, a writers' retreat for programmers in New York City. I will therefore be taking an unpaid personal leave of absence from the Wikimedia Foundation via our sabbatical program. My last workday before my leave will be Friday, September 27. I plan to be on leave all of October, November, and December, returning to WMF in January. During my absence, Quim Gil will be the temporary head of the Engineering Community Team. Thank you, Quim! I'll spend much of September turning over responsibilities to him. Over the next month I'll be saying no to a lot of requests so I can ensure I take care of all my commitments by September 27th, when I'll be turning off my wikimedia.org email. If there's anything else I can do to minimize inconvenience, please let me know. And -- I have to say this -- oh my gosh I'm so excited to be going to Hacker School in just a month! Going from advanced beginner to confident programmer! Learning face-to-face with other coders, 30-45% of them women, all teaching each other! Thank you, WMF, for the sabbatical program, and thanks to my team for supporting me on this. I couldn't do this without you. -- Sumana Harihareswara Engineering Community Manager Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Can we help Tor users make legitimate edits?
Hmm, I can see your point. Flagged Revs would be as much of hindrances on regular users as it would be on Tor users. I still think it should be permissable for Tor editors to submit legitimate edits in some way, but your points about the AGF policy and the purpose of Flagged Revs are duly noted. Date: Fri, 27 Sep 2013 21:05:29 -0400 From: risker...@gmail.com To: wikitech-l@lists.wikimedia.org Subject: Re: [Wikitech-l] Can we help Tor users make legitimate edits? On 27 September 2013 19:40, Sumana Harihareswara suma...@wikimedia.orgwrote: This is a quick followup to http://www.gossamer-threads.com/lists/wiki/wikitech/323006 and partly in keeping with the anti-vandalism discussion at http://www.gossamer-threads.com/lists/wiki/wikitech/392727 as well. On 12/27/2012 07:26 PM, Sumana Harihareswara wrote: TL;DR: A few ideas follow on how we could possibly help legit editors contribute from behind Tor proxies [snip] 4) Allow more users the IP block exemption, possibly even automatically after a certain number of unreverted edits, but with some kind of FlaggedRevs integration; Tor users can edit but their changes have to be reviewed before going live. We could combine this with (3); Nymble administrators or token-issuers could pledge to review edits coming from Tor. But that latter idea sounds like a lot of social infrastructure to set up and maintain. From talking to Eleanor Saitta: could we do FlaggedRevs by IP space, and/or by the intersection of IPs and topic space? Basically, let people edit from Tor IPs (and/or whitelist or blacklist categories) as long as those go through a FlaggedRevs-type process? And we could also do FlaggedRevs on specific IP ranges, like blocks that are known to be certain government office buildings. I think perhaps there's a real disconnect between what Flagged Revisions does and its purpose, as well as how widespread its use is. FR is not used on 95% of Wikimedia projects. It is attached to specific pages (or entire namespaces); it is not attached to either anonymous (IP) or registered users. You're looking for some other type of software, some form of user right if it is to be attached to specific users (either anonymous or registered) that woulddo what, exactly? Require that a project's editors review every single edit from those IPs but not block them, no matter how much junk they put in a project? And again, any such use would be specific to each project. I would be very disturbed if the WMF was to take it upon itself to start telling projects they have to accept edits from IPs and ranges they've had extremely poor experience with. AGF is not a suicide pact. Risker/Anne ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Improving anti-vandalism tools (twinkle, huggle etc) - suspicious edits queue
That idea sounds like something already that could be done by the Flagged Revs extension. Given that many of those suspicious edits could be extremely subtle, like minor changes to mathematical equations and statistics, articles with lots of potential for those types of subtle vandal edits would probably be better handled by having them approved with Flagged Revs and allowing trusted editors (like members of a particular Wiki Project based in those fields) to review the edits. I doubt Twinkle or Huggle would be ideal for such vandalism, as it would be easy to mistake legitimate edits for vandal edits, and automated vandal detection/reversion processes would generally have a poor margin of error for such subtle vandalism. Date: Thu, 26 Sep 2013 15:06:47 +0200 From: benap...@gmail.com To: wikitech-l@lists.wikimedia.org Subject: [Wikitech-l] Improving anti-vandalism tools (twinkle, huggle etc) - suspicious edits queue Hi, I noticed that there is a high amount of suspicious edits that may be vandalism but were never reverted because people who were dealing with vandals (using some automated tool) in that moment weren't able to decide if it was vandalism or wasn't. For example some smart changes to statistical data, dates, football scores, changes that look weird but aren't clearly vandalism etc. These edits should be reviewed by expert on the topic, but in this moment, they aren't collected anywhere. I think we should create a new service (on tool labs?) that would allow these tools to insert such edits to queue (or database) of suspicious edits for later review by experts, this categorized database / queue could be browsed by people who are experts on given topics and got reviewed / reverted by them. The database would need to be periodically scanned and all changes that were reverted would need to be removed from it. The people who reviewed the edits could also flag them as ok. This way we could improve the efficiency of anti-vandalism tools by the amount of edits which are ignored or skipped these days. Some suggestions or ideas how to implement such a feature? ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] A message for all everyone on the Wikitech mailing list
Sumana Harihareswara recently provided me assistance with some code I wanted to write and invited me to join the wikitech mailing list, and she also suggested I share my response to her with the rest of the list subscribers, which I have reproduced (with some mild alterations) below: Thanks for the mailing list link, Sumana, just submitted a subscription request. As for those links you provided, I have bookmarked them and will be studying them extensively, your assistance is greatly appreciated :) As for my wiki (https://mediawikitesters.orain.org/wiki/Main_Page), I like to test gadgets, user scripts, and extensions, and the wiki is basically for me and anyone else who is interested to display useful code, test it in a live environment, and hopefully swap notes with each other on how to improve it it. The wiki is still rather new, but anyone interested is welcome. As for the gadgets section of my wiki, I find gadgets to be incredibly useful and am trying to compile as many gadgets as I can that can be used by anyone with MediaWiki that I find universally useful and adaptable to any wiki, as I prefer code that works out of the box and is compatible as possible, especially with the more recent versions of MediaWiki, and my goal is to make it available to anyone for any wiki. Most are from WMF projects or have been adapted from them to be useful on any wiki. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[MediaWiki-l] Are there any good resources for writing scripts and gadgets
I'm currently trying to adapt several gadgets that are meant for wikis using the Monobook/Vector skins to the Monaco skin, and so far, I've managed to successfully port over the UTC Clock gadget and Sandbox page gadget to Monaco, but aside from those I've been having trouble since, frankly, my knowledge of Javascript/JQuery is slim and I'm not familiar with all the variables used in writing user scripts. I've fairly decent with CSS style sheets, but I still need help with Javascript, so does anyone know of some good resources I could look into, preferably tailored for writing scripts on MediaWiki? Also, if anyone wants to see what I have done so far (and have released publicly), the wiki I have been testing my live gadget/user script code on is here: https://mediawikitesters.orain.org/wiki/Main_Page ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
[MediaWiki-l] Have released a modified version of the Monaco skin
I have just finished making a fork of Daniel Friesen (Dantman's) port of the Monaco skin for anyone who likes using the skin but has found it has display errors when used with certain extensions (like WikiEditor), especially on the latest versions of MediaWiki. This forked version has several edits to make it more compatible with more recent versions of MediaWiki, mostly CSS tweaks and a compatibility patch for users of the WikiEditor extension. I'm not very experienced with GitHub, but I have tested the project linked below and it works fine for me, so I would like to share my fork with the MediaWiki community: https://github.com/Arcane21/monaco-port I hope it was not inappropriate to use this mailing list to share this, so if it was, I apologize, but I thought this might benefit the MediaWiki community, and I hope it proves useful. ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Mediawiki as an Enterprise wiki
I'm not sure how much help this is, but it should be possible to section off certain levels of the wiki for certain user groups (you could possibly make a user group for every individual user if you needed to) What you would do, for sections with info so sensitive that only one or two people should have access is simply to restrict everything, even the ability to read the page (including the page source) in any way, to just those user groups you specify. This would effectively secure that information to just those parties alone, though this would require manually toggling settings for each user group, which would be extremely tedious yet doable. That security hassle aside, MediaWiki is probably the best option you have for handling such a large amount of content, and while I'm no expert on wiki security, it is probably the most well featured wiki when it comes to additional security options and extensions you can install and configure, and I would highly recommend using it. In fact, I found an extension that should serve your security needs well in blocking even page sources from being viewable (for your needs, this would be essential) https://www.mediawiki.org/wiki/Extension:ProtectSource You also want this extension, just to close loopholes in the above extension, such as the Special:Import/Export special pages: https://www.mediawiki.org/wiki/Extension:DisableSpecialPages I'm not sure what else you need at the moment, but you should check out all the page permission and security extensions on MediaWiki.org, not to mention all the page permission documentation available to determine how feasible the level of security you desire is: https://www.mediawiki.org/wiki/Permissions Hope that helps. From: pierre.labrec...@live.ca To: mediawiki-l@lists.wikimedia.org Date: Fri, 9 Aug 2013 23:10:05 -0400 Subject: [MediaWiki-l] Mediawiki as an Enterprise wiki Hello, (sorry for my poor English.) This is probably a recurring question. I work for an IT company of around 80 000 employees and we would like to build an enterprise wiki, where we will put all our technical documentation (how to, troubleshooting, scripting, etc.). 80 000 employees, but this wiki will be for 1000 of them. It may generate a minimum of 200 000/300 000 pages + images + etc. You have to know that in some of our documentation, we have usernames and passwords, or maybe firewall configuration, etc. for different customers. Of course, I know that Mediawiki cannot provide a per page/category security (at a read level): my understanding is that Mediawiki is Read all pages or Access denied to all pages. nothing in between. So we cannot restrict view of some documents to a specific group. Fine. So let's say that it's not a problem and that all our technicians will be able to read all the technical documents, of all our customers. Someone told me that we just don't have to put some confidential informations in our wiki documents (no user/password/confidential config/etc.). Fine. But where ? If we don't put them in the wiki pages, it means that the users will have to go in the wiki for the basic informations, then go on another tool to have the confidential info. Now, my question: how do you manage this ? I really love Mediawiki and would like to implement it in our business, but I haven't enough information on how this can be implemented in the reality of a business. And no: no budget to buy something like Confluence. I have try Dokuwiki, XWiki, Tiki, MoinMoin, many others. I love Dokuwiki too, but wasn't sure enough it was a strong tool to be able to manage that amount of pages/images/. Anyway, I always come back to MediaWiki. I don't know why. Best regards, Pierre ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] MySQL 5.6.x
I have. So far, I'd call it an upgrade, since most of my database retrieval calls have been going a lot faster since I made the switch. MariaDB gives a similar performance boost in my experience, but since I run a localhost install on a XAMPP stack, it can be a real hassle making the switch from MySQL to MariaDB. However, moving up from your current MySQL to MySQL 5.6 shouldn't be an issue and you should get a performance boost out of it. I can't tell what this would me for a live site, but so far, it works well for me, and you could probably drop in replace the newer version of MySQL over your older version with little difficulty. Date: Thu, 1 Aug 2013 00:35:58 -0400 From: k...@riseup.net To: mediawiki-l@lists.wikimedia.org Subject: [MediaWiki-l] MySQL 5.6.x -BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Hi, Has anyone tested MediaWiki with MySQL 5.6.x? I'm aware that Wikimedia now uses MariaDB, but I'm currently stuck with MySQL on Amazon RDS and was wondering whether I should upgrade from 5.5.31 to 5.6.12. - -Kudu. -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) iQIcBAEBCQAGBQJR+eWtAAoJEMG+LL161/I7vZYP/jLOcF48u2oVyipIi06KYvrD GFpPErKysFkRK8WRcINMsT4yvWpcy9vaJII42Hix0I6sFZuDRDhCdGGfuAAKKFeH LahsZBTWUENja73OdsSnGUlUcCXS88+TfPz3X4u3ZMcf564lkt1uzKveJ5Odl/7u OKxoFmSffL77G19PuX8PnmjTqdjgAGU457fQCeDkGlA0TvY0KJWPB7TCEj8aXz52 RAgbzcNrNtNiYP+9ngaBsRRIV1ILWgG03u3FP09GqLVTB4Dw7UiAWgCdPp4CWa3O /Icik7QiDN2mUbT6OwCFCfdTkrDZaxJDYGIOLwNs8uI1ssTV+BMMfdgm4zgraCGO dB1w2qSHbpmPVq2NsvSfVR7885m0CyWvCQQDkWyzJazOAoca6BO9TLpqrV56J2+B qpzh5jTHfFg7msuWiVAXtZSM+T3YsKoQdtk+NSnF+3pg/e/Xjv3XGGdr3ba7rfLg VUbT/bCP5aRZeB8IaOlXhEV/GlU8c/SmPVyDeP0AmfbR2fEY9vNhwupHYCeVOeo5 N9UNTZWnOetxeYRK5u1MKTFTvgvOdF5K6gZChAKsog3s/fuHxLAWTPWEpCpl9WzS rX79ELOHU0RU5bT/XJBWYuoobM4aDSLdmAV7kv+Di2nUMNlNtfv9QwbnJ31zl57a mXTjVOhyWy7CDtIMHcLv =3rd6 -END PGP SIGNATURE- ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Extremely strange parsing error discovered
Actually, I do. Just turned it off, that fixed the problem. Date: Mon, 3 Jun 2013 12:12:06 +0200 From: d.j.hartman+wmf...@gmail.com To: mediawiki-l@lists.wikimedia.org Subject: Re: [MediaWiki-l] Extremely strange parsing error discovered You wouldn't have Adblock installed per chance ? DJ On Mon, Jun 3, 2013 at 6:40 AM, Arcane 21 arc...@live.com wrote: I just discovered an extremely strange error when parsing the following: ==Advertisements== All one will get when trying to create that section heading will be a blank heading (though any table of contents will show the proper heading. I'm not sure what causes it, and I have verified it exists on MW 1.19, 1.20, and 1.21. ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Fwd: Query about 1.21.0 version
It received an official release on MediaWiki.org, so it should be. The version number is probably an artifact from the final release candidate that wasn't altered before release. Date: Mon, 27 May 2013 12:24:59 +0530 From: pu...@softaculous.com To: mediawiki-l@lists.wikimedia.org Subject: [MediaWiki-l] Fwd: Query about 1.21.0 version Hi, Is MediaWiki 1.21.0 is stable version ? After installing it shows 1.21.0rc5. -- * * *Punit Varia * *Script Packaging Head* pu...@softaculous.com http://www.softaculous.com/http://www.softaculous.com/ http://www.softaculous.com/ Become our fan on Facebook http://www.facebook.com/softaculousand follow us on Twitter https://twitter.com/softaculous ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Wiki spam. Stronger fightback.
That sounds like a good idea, John. Also, to elaborate on my early proposed idea for this master spam IP list, I'm a fan of having an invitation only wiki website where vetted users can submit known spammer IPs and IP ranges to a community IP list that can be imported into any MediaWiki wiki. I'm not sure how this proposed wiki would be structured (i.e. - whether it would be a regular wiki, using Semantic MediaWiki, etc.), but I would be interested in a wiki dedicated to fighting wiki spam where vetted users can create IP blacklists for spammers, swap information on known spammers and ways to combat them, and in the interests of security, it may be necessary to restrict page viewing to confirmed members only. Past that, I don't have too many more ideas I can submit for this brainstorming session, but some form of master anti-spammer IP list in some usable form sounds like a great idea in any event. Date: Fri, 24 May 2013 17:48:02 -0400 From: phoenixoverr...@gmail.com To: alj62...@yahoo.com; mediawiki-l@lists.wikimedia.org Subject: Re: [MediaWiki-l] Wiki spam. Stronger fightback. One thing that might work (wouldnt be 100%) would be a method for identifying IP ranges of know abuse where legit collateral is minimal and keeping a database of these and auto-blocking them. These IPs are typically those of: * known web-hosting services * Proxy Services * data-center providers * similar cases where risk of legit end user usage is minimal. I know working with anti-spam efforts that there are several know ISP's that 99% of their traffic is spam. If something like this is implemented it could reduce spam by as much as 80% or more. On Fri, May 24, 2013 at 5:19 PM, Al Johnson alj62...@yahoo.com wrote: More brainstorming ideas about this... A centralized DB would require a site requiring heavy use since it would be hit for each edit submission from every participating site. An alternative would be a subscriber model where the global list (or updates) is downloaded periodically by subscribers. How long to block an IP? I'm not an expert in this area, but what if the IP is blocked for an extended period of time, such as ONE YEAR. If that IP ends up being reissued to a legitimate ISP customer and he gets blocked, that will alert that user that his ISP is either participating in spamming or is tolerating spammers user of their IPs which is affecting regular customers. This may sound harsh, but this could force ISPs to address the problem with their spammer customers. And, there is still a workaround for the legit user who can usually just reboot their modem to get a new IP address. Just thinking out load... al From: Al Johnson alj62...@yahoo.com To: MediaWiki announcements and site admin list mediawiki-l@lists.wikimedia.org Sent: Friday, May 24, 2013 2:41 PM Subject: Re: [MediaWiki-l] Wiki spam. Stronger fightback. Maybe mediawiki sites can unite to keep a global list of these IP's and block them as soon as they are submitted. Each mediawiki site can auto-submit a spammer IP as soon as it's discovered to the global list. What are the problems with this idea? Al ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
[MediaWiki-l] Had an error upgrading from MW 1.2.05
When MW 1.20.6 came out, I decided to upgrade to it from 1.20.5, and I decided to run the web updater afterwards. All I got was a blank screen no matter what I tried, so I reverted back to 1.20.5 and everything was normal again. I'm not sure what happened, but I thought I'd let everyone on the mailing list know that there might be a problem with the newest security release. P.S. - Not really related to the above, but still MediaWiki related: Does anyone know what happened to the MediaWiki Users forum? It's been down for awhile, apparently due to database issues, and I was wondering if anyone here has more information on what happened. ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Was wondering if I could make a story generator in MediaWiki?
That actually looks like a great idea for what I'd like to do, since I'm still
trying to figure out Semantic Forms, and this looks like a good alternative for
stock MediaWiki.
As for that template, it's pretty much what I had in mind for this story
generator idea, so thank you for the help, Matma.
However, I'd wondering if I could implement the template in the below manner
somehow:
I'd like to provide a page with the instruction on how to use the
silly story generator, then an input box (I have the InputBox extension)
when the template can be added, and the result can be shown on another
page or window.
Either that, or transcluded into a section below the Inputbox which can be
cleared off and purged for reuse.
I'm
not averse to installing any extensions if I have to to make this work
(I assume I'd probably need the Labeled Section Transclusion Extension
or something similar for the above idea)
To: mediawiki-l@lists.wikimedia.org
Date: Wed, 13 Mar 2013 17:57:06 +0100
From: matma@gmail.com
Subject: Re: [MediaWiki-l] Was wondering if I could make a story generator
in MediaWiki?
The best you could do with vanilla MW is to create a template with the story
text, and call the template with appropriate variables. E.g.:
Template:Story:
One day while I was {{{1}}} in the {{{2}}} a {{{3}}} fell through the roof.
Any page:
{{story|sleeping|kitchen|dog}}
For something more user-friendly, you could probably use the Semantic
MediaWiki extension; I'm not sure if there's anything more specific that
could let you achieve this.
--
Matma Rex
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Is it possible to use different logos for different skins?
Thanks guys, this was exactly the information I needed.
From: dev...@gmail.com
Date: Tue, 19 Feb 2013 14:53:32 +0900
To: mediawiki-l@lists.wikimedia.org
Subject: Re: [MediaWiki-l] Is it possible to use different logos for
different skins?
Ah, not modern skin not has logo, so you can add that line to
MediaWiki:Monobook.css
2013/2/19 devunt dev...@gmail.com:
You can add this code in each skin's css file (ex:
MediaWiki:Vector.css, MediaWiki:Modern.css)
#p-logo a { background-image:
url('http://www.example.com/w/logo_you_want.png') !important; }
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Fwd: Bootstrap based theme for Mediawiki
I tried in on my wiki (I have MW 1.19.3), and I had problems with the drop down menus and some of the tab items showing up right. From: innocentkil...@gmail.com Date: Sun, 10 Feb 2013 08:04:44 -0500 To: alj62...@yahoo.com; mediawiki-l@lists.wikimedia.org Subject: Re: [MediaWiki-l] Fwd: Bootstrap based theme for Mediawiki On Sun, Feb 10, 2013 at 6:54 AM, Al Johnson alj62...@yahoo.com wrote: Has anyone tried out this skin? The nav bar drop-downs (Toolbox, Page, user, etc.) don't drop down. I reported it to the developer, but am wondering if it works for anyone else. I tried it out like Thursday. Everything WFM (other than the Echo notifications being placed kinda funny) -Chad ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
[MediaWiki-l] How does one enable the animated star for the MediaWiki watchlist on the Vector skin?
I wanted enable the animated star icon for the watchlist on my wiki with the Vector skin (like it works on Wikipedia and RationalWiki), but I have no idea how to enable it. I looked over MediaWiki.org over and over again and I couldn't find any information how to enable that feature. If anyone knows how to enable that feature, your help would be appreciated. ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] How does one enable the animated star for the MediaWiki watchlist on the Vector skin?
I have Vector installed (the extension and skin). I just don't know how to activate the animated star for the watchlist feature. Subject: Re: [MediaWiki-l] How does one enable the animated star for the MediaWiki watchlist on the Vector skin? From: thehelpfulonew...@gmail.com Date: Sun, 27 Jan 2013 03:28:59 + To: arc...@live.com; mediawiki-l@lists.wikimedia.org The first thing that comes to mind is https://www.mediawiki.org/wiki/Extension:Vector which is installed on all of our wikis. Perhaps give that a try? Thehelpfulonehttps://meta.wikimedia.org/wiki/User:Thehelpfulone On 27 Jan 2013, at 01:59, Arcane 21 arc...@live.com wrote: I wanted enable the animated star icon for the watchlist on my wiki with the Vector skin (like it works on Wikipedia and RationalWiki), but I have no idea how to enable it. I looked over MediaWiki.org over and over again and I couldn't find any information how to enable that feature. If anyone knows how to enable that feature, your help would be appreciated. ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
[MediaWiki-l] Requesting help and advice on making a custom Vector skin
My question is simple: How do I (A) clone the Vector skin and (B) make it so my customized Vector skin can have custom background and text colors. I tried using this skin initially: https://code.google.com/p/darkvector/ Unfortunately, it has graphical errors in my version of MediaWiki (currently 1.19.3), so I decided it would be better to take my own version of Vector, clone under a different name (currently DarkVector is the name I'm using), then I planned to make my own version of darkvector (I was going to change the colors slightly, but I like the version on google code) Unfortunately, I'm only really good at editing CSS. I tried editing my clone .php files, but I either (A) keep screwing up the layout (and the sidebar disappears) or (B) I get it looking right but all of my edits to the screen.css to change the colors have no effect. I'm not sure I know what I doing, so if someone could walk me through what I'd like to do or could provided me pointers on what I might be getting wrong, I would appreciate the assistance. ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Requesting help and advice on making a custom Vector skin
Ah, I get your point. Thanks for the suggestion, and that link has a pretty easy to follow tutorial, so I'll try that. Much appreciated. To: mediawiki-l@lists.wikimedia.org From: dan...@nadir-seen-fire.com Date: Thu, 17 Jan 2013 16:56:59 -0800 Subject: Re: [MediaWiki-l] Requesting help and advice on making a custom Vector skin On Thu, 17 Jan 2013 16:51:32 -0800, Arcane 21 arc...@live.com wrote: My question is simple: How do I (A) clone the Vector skin and (B) make it so my customized Vector skin can have custom background and text colors. I tried using this skin initially: https://code.google.com/p/darkvector/ Unfortunately, it has graphical errors in my version of MediaWiki (currently 1.19.3), so I decided it would be better to take my own version of Vector, clone under a different name (currently DarkVector is the name I'm using), then I planned to make my own version of darkvector (I was going to change the colors slightly, but I like the version on google code) Unfortunately, I'm only really good at editing CSS. I tried editing my clone .php files, but I either (A) keep screwing up the layout (and the sidebar disappears) or (B) I get it looking right but all of my edits to the screen.css to change the colors have no effect. I'm not sure I know what I doing, so if someone could walk me through what I'd like to do or could provided me pointers on what I might be getting wrong, I would appreciate the assistance. You don't want to clone vector. Rather you want to create a skin that's based on it. See http://blog.redwerks.org/2012/02/28/mediawiki-subskin-tutorial/ -- ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/] ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Requesting help and advice on making a custom Vector skin
I followed the instructions on that tutorial, and I have my Dark Vector subskin set up as the tutorial specified, but I'm having two problems 1. Simple Search (as enabled by $wgVectorUseSimpleSearch = true; in LocalSettings.php) doesn't seem to work properly. When removed from my LocalSettings.php file, the skin looks normal, but I'd like to have that feature on my derivative skin. 2. I tried editing the CSS to change the background and text color, and it seems to have no effect. I'm not sure what I'm doing wrong, but I was trying to make the non content areas black, the text either blue or black, and the content area gray, and even though I copied the CSS that controls the colors from the Vector screen.css and modified it accordingly, there seems to be no changes. Any help would be appreciated. From: arc...@live.com To: dan...@nadir-seen-fire.com; mediawiki-l@lists.wikimedia.org Date: Thu, 17 Jan 2013 19:14:46 -0600 Subject: Re: [MediaWiki-l] Requesting help and advice on making a custom Vector skin Ah, I get your point. Thanks for the suggestion, and that link has a pretty easy to follow tutorial, so I'll try that. Much appreciated. To: mediawiki-l@lists.wikimedia.org From: dan...@nadir-seen-fire.com Date: Thu, 17 Jan 2013 16:56:59 -0800 Subject: Re: [MediaWiki-l] Requesting help and advice on making a custom Vector skin On Thu, 17 Jan 2013 16:51:32 -0800, Arcane 21 arc...@live.com wrote: My question is simple: How do I (A) clone the Vector skin and (B) make it so my customized Vector skin can have custom background and text colors. I tried using this skin initially: https://code.google.com/p/darkvector/ Unfortunately, it has graphical errors in my version of MediaWiki (currently 1.19.3), so I decided it would be better to take my own version of Vector, clone under a different name (currently DarkVector is the name I'm using), then I planned to make my own version of darkvector (I was going to change the colors slightly, but I like the version on google code) Unfortunately, I'm only really good at editing CSS. I tried editing my clone .php files, but I either (A) keep screwing up the layout (and the sidebar disappears) or (B) I get it looking right but all of my edits to the screen.css to change the colors have no effect. I'm not sure I know what I doing, so if someone could walk me through what I'd like to do or could provided me pointers on what I might be getting wrong, I would appreciate the assistance. You don't want to clone vector. Rather you want to create a skin that's based on it. See http://blog.redwerks.org/2012/02/28/mediawiki-subskin-tutorial/ -- ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/] ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Requesting help and advice on making a custom Vector skin
I managed to figure out what I needed to do by following this manual: https://www.mediawiki.org/wiki/Manual:Skinning/Vector From: arc...@live.com To: mediawiki-l@lists.wikimedia.org; dan...@nadir-seen-fire.com Date: Thu, 17 Jan 2013 21:07:51 -0600 Subject: Re: [MediaWiki-l] Requesting help and advice on making a custom Vector skin I followed the instructions on that tutorial, and I have my Dark Vector subskin set up as the tutorial specified, but I'm having two problems 1. Simple Search (as enabled by $wgVectorUseSimpleSearch = true; in LocalSettings.php) doesn't seem to work properly. When removed from my LocalSettings.php file, the skin looks normal, but I'd like to have that feature on my derivative skin. 2. I tried editing the CSS to change the background and text color, and it seems to have no effect. I'm not sure what I'm doing wrong, but I was trying to make the non content areas black, the text either blue or black, and the content area gray, and even though I copied the CSS that controls the colors from the Vector screen.css and modified it accordingly, there seems to be no changes. Any help would be appreciated. From: arc...@live.com To: dan...@nadir-seen-fire.com; mediawiki-l@lists.wikimedia.org Date: Thu, 17 Jan 2013 19:14:46 -0600 Subject: Re: [MediaWiki-l] Requesting help and advice on making a custom Vector skin Ah, I get your point. Thanks for the suggestion, and that link has a pretty easy to follow tutorial, so I'll try that. Much appreciated. To: mediawiki-l@lists.wikimedia.org From: dan...@nadir-seen-fire.com Date: Thu, 17 Jan 2013 16:56:59 -0800 Subject: Re: [MediaWiki-l] Requesting help and advice on making a custom Vector skin On Thu, 17 Jan 2013 16:51:32 -0800, Arcane 21 arc...@live.com wrote: My question is simple: How do I (A) clone the Vector skin and (B) make it so my customized Vector skin can have custom background and text colors. I tried using this skin initially: https://code.google.com/p/darkvector/ Unfortunately, it has graphical errors in my version of MediaWiki (currently 1.19.3), so I decided it would be better to take my own version of Vector, clone under a different name (currently DarkVector is the name I'm using), then I planned to make my own version of darkvector (I was going to change the colors slightly, but I like the version on google code) Unfortunately, I'm only really good at editing CSS. I tried editing my clone .php files, but I either (A) keep screwing up the layout (and the sidebar disappears) or (B) I get it looking right but all of my edits to the screen.css to change the colors have no effect. I'm not sure I know what I doing, so if someone could walk me through what I'd like to do or could provided me pointers on what I might be getting wrong, I would appreciate the assistance. You don't want to clone vector. Rather you want to create a skin that's based on it. See http://blog.redwerks.org/2012/02/28/mediawiki-subskin-tutorial/ -- ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/] ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Considering a move to Mediawiki
I'm not sure about highlighting items, but the search engine of MediaWiki is quite good, especially if you install the Lucene search extension and associated software, and you cane even set up the search to work with external search engines if you or the user prefers for faster/more efficient searching. Searches also start with the most relevant results and progress downward towards the least relevant results by default. Items can be tagged/grouped into categories and subcategories very easily in MediaWiki, and reversed the same way. Content and menus can be very easily accessed, especially depending on the modifications you make to the skin, sidebar, redirects, and navigation templates. As for adding new entries, that is rather easy to do, and you can customize how edits are made and entered using both extensions and by editing the configuration files that govern user rights. As for option/support for importing FosWiki data, I'm afraid I don't have much knowledge if that is possible, you may wish to look around to see if any scripts have been made for this type of conversion. From: agenere...@hotmail.com To: mediawiki-l@lists.wikimedia.org Date: Thu, 29 Nov 2012 14:26:21 -0800 Subject: [MediaWiki-l] Considering a move to Mediawiki Hello, My name is Anthony and I'm looking at possible replacement for my organization's current document management system: Foswiki. I've looked at a number of different comparison charts and spoke to a few vendors, but have hadtrouble actually getting a good sense for what might work for us. Here are a few things that our users are looking to find, in the new system: * Have search results return page headings or other recognizable entity title. * Be able to group or un-group search results by web/category/areas * Search results show context of search term or at least show highlighted search term in a section of the result. * Search results focus page on the results not fill the page with fluff * Search results are ranked. Not all hits should be treated equally. * Tool is easy to navigate through contents/menus to appropriate page * Adding new entries is intuitive and easy to accomplish. * Editing existing entries is intuitive and easy to accomplish. ** Provide options/support for importing existing (FOS Wiki) data. Anyone out there who knows Mediawiki well enough to speak to the question of how it addresses the above, please let me know your thoughts. Thank you, -Anthony ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] wiki format
If you want to create a wiki with these features in MediaWiki, I suggest checking out the Extensions available for MediaWiki on mediawiki.org and picking what is needed for your setup. There are several wiki extensions for lists and flowcharts, and stock MediaWiki already has some of those features you mentioned already included, but given the sheer amount available you may have to do some experimenting to find what you need. Since you don't mind having either a localhost or public web setup but aren't sure what you need at the moment, I would stick with a localhost setup and experiment with extensions until you find what you need, and on a localhost setup you would have total freedom to add and remove changes at will until you find the right combination of extensions to make the wiki you are hoping to create. Also, if you don't feel the need or don't wish to wish your wiki public, a localhost setup would be best for your purposes, especially if you will putting potentially sensitive information for your own personal use on the wiki. A localhost wiki will also be only edited by yourself and you will have total control over what information is added, if that is a concern. Date: Tue, 6 Nov 2012 03:58:41 +0200 From: chembio...@yahoo.com To: mediawiki-l@lists.wikimedia.org Subject: [MediaWiki-l] wiki format hello! I want to create a wiki (either local or web) my main goal is to be able to organize alot of data very nicely and to edit it easily (not looking for ability to be edited by others etc) however, I want to be able to do these: 1) create and edit rich text (wiki can already do that) 2) create and edit flowcharts, diagrams, etc of as many as possible types (can it do it?) 3) create tables, sortable, filterable, searchable, etc (can it do it?) please advise if it can and how to do it! thanks! ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Is there an autocategorization ability for bullet point items in MediaWiki?
Thanks Tom, that helps quite a bit, but how would I make a more generalized
template that I could use on any page?
I'm trying to make it so I can use it to autocategorize entire lists of bullet
pointed items at a time, mostly for convenience, and I'd like to be adaptable
to any page.
From: t...@hutch4.us
Date: Tue, 30 Oct 2012 09:39:52 -0400
To: mediawiki-l@lists.wikimedia.org
Subject: Re: [MediaWiki-l] Is there an autocategorization ability for bullet
point items in MediaWiki?
DPL needs a parameter or heading to transclude page info.
Just use a template
{{bullet|snow|hail|sleet}}
Have the template bullet list
*[[{{{1|}}}]]
*[[{{{2|}}}]]
etc
But I would integrate into an if call
{{#if:{{{1|}}}|*[[{{{1|}}}]]|}}
To automate categorization you based on page name you need to pass the page
name you use the template on.
{{bullet|snow|hail|sleet|page={{PAGENAME
Now you can add categorization splicing together {{{page|}}} and the listing
of parameter numbers in the if call.
Limitations, you'd have to allow for 10 or whatever # would be you max if
parameters and have a statement for each checking value.
Probably better to use the Arrays extension and use a comma to separate the
values. Then call with a #arrays print call.
{{bullet|snow,sleet,hail|page={{PAGENAME
Tom
On Oct 30, 2012, at 9:01 AM, Arcane 21 arc...@live.com wrote:
Tried Dynamic Page List 2.01 (Third Party)
It doesn't seem to work with text in bulletpoints, as I wanted to use it
autocategorize all items between the DPL parser tags in a Category with
same name as the article the bullet pointed items are on.
I.E. - All items in a bulletpointed list (that link to other article pages)
would be autocategorized in a category with the same name as the article
the bullet pointed items are in.
If someone could spell put how I might be able to use DPL parser code for
this purpose (an example of how this would look when typed out would be
quite helpful), it would be appreciated.
If this is the wrong extension or DPL cannot do this, I'm open to
alternatives.
From: leo_wallen...@hotmail.com
To: mediawiki-l@lists.wikimedia.org; arc...@live.com
Subject: RE: [MediaWiki-l] Is there an autocategorization ability for
bullet point items in MediaWiki?
Date: Tue, 30 Oct 2012 12:27:51 +
You should have a look at Semantic MediaWiki, Dynamic Pagelist, or similar
extensions!
/Leo
___Leonard wallentinleo_wallen...@hotmail.com@leo_wallentin+46
(0) 735 - 933 543
From: arc...@live.com
To: mediawiki-l@lists.wikimedia.org
Date: Tue, 30 Oct 2012 07:17:48 -0500
Subject: Re: [MediaWiki-l] Is there an autocategorization ability for
bullet point items in MediaWiki?
Sorry. My last post got slightly garbled...still new to using this mailing
list, so here's my message again:
I was curious if there is a way to take a bullet pointed list of internal
wiki links to other articles (whether they contain content or not) on a
single page and have them automatically categorized to the category to
same name as the article page.
For example, I have the article page Snow, and I want to add a list of
subtopics on the article page Snow to the category Snow, with
subtopics being:
(bulletpoint one)Flurries (bulletpoint two) Hail (bulletpoint three) Sleet
My question is if there is a template, extension, or wiki parser
expressions I should use to make all items on a bullet pointed list be
autocategorized in the category with the same name as the article page.
If anyone has any ideas or knows what I need, any assistance would be
greatly appreciated.
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Is there an autocategorization ability for bullet point items in MediaWiki?
Thanks, that clears up my remaining questions. I think I can handle it from
here.
Appreciate the help.
From: t...@hutch4.us
Date: Tue, 30 Oct 2012 10:09:37 -0400
To: mediawiki-l@lists.wikimedia.org
Subject: Re: [MediaWiki-l] Is there an autocategorization ability for bullet
point items in MediaWiki?
{{bullet}} would be the template and you have to build the template to what
you need. I would really recommend Arrays.
{{bullet|Ford,GM,Chyrsler,Audi|page={{PAGENAME
{{PAGENAME}} is a magic word and pulls in the current PAGENAME you use the
template call on.
PAGENAME in this example could be Auto manufacturers. Or Names of Auto
manufactures.
Tom
On Oct 30, 2012, at 9:55 AM, Arcane 21 arc...@live.com wrote:
Thanks Tom, that helps quite a bit, but how would I make a more generalized
template that I could use on any page?
I'm trying to make it so I can use it to autocategorize entire lists of
bullet pointed items at a time, mostly for convenience, and I'd like to be
adaptable to any page.
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Getting Cite to work
I just tried it and seems work fine for me. Try this in your sandbox: refexample/ref ==Notes== references/ If it worked right, you'll see a small [1], a Notes section header, and the reference will have a small blue citation link pointing up with the word example next to it. Date: Tue, 30 Oct 2012 10:28:35 -0400 From: st...@clemson.edu To: MediaWiki-l@lists.wikimedia.org Subject: [MediaWiki-l] Getting Cite to work I installed the svn Cite files and added the require_once command in the LocalSettings.php file. I tried a simple reference in Sandbox, but nothing seemed to happen. The ref tags are still there and references / is empty. What do I need to do? -- D. E. (Steve) Stevenson (Almost emeritus) Associate Professor Director, Institute for Modeling and Simulation Applications. Clemson University steve at clemson dot edu Anyone who has ever looked into the glazed eyes of a soldier dying on the battlefield will think hard before starting a war. -Otto von Bismarck, statesman (1815-1898) ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
