Wikipedia talk:AutoWikiBrowser/Feature requests/Archive 11

Archive 5

←

Archive 9

Archive 10

Archive 11

Archive 12

Interface amendments II

Status	This feature is partially implemented
Description	We can save space by replacing group boxes with a separator (see Microsoft guidelines) in the following tabs 'Options', 'More...', 'Disambig', 'Skip', and 'Bots'. In the case of 'Disambig', I suggest the groups shouldn't exist at all, the labels should go directly on the widget. Lightmouse (talk) 09:05, 11 June 2011 (UTC)
Added in revision

Thus:

•  Done Please replace the three Options tab group boxes (Automatic changes, Find and replace, Regex typo fixing) with three separator lines
• Please replace the three More... tab group boxes with three separator lines
• Please delete the Disambig tab group box 'Link to disambiguate' and move the label to the field
• Please delete the Disambig tab group box 'Variants' and move the label to the field
• Please replace the three Skip tab group boxes with three separator lines
• Please replace the three Bots tab group boxes with three separator lines

Lightmouse (talk) 12:09, 25 June 2011 (UTC)

rev 9471 for the options tab. -- Magioladitis (talk) 06:52, 9 September 2013 (UTC)

Stopping during processing

Status	Feature added in next release
Description	It would be nice if AWB stopped when you hit the 'stop' button. Currently you have to wait until it's between articles, and when the WP servers are bogged down, that can take quite a while. When it's stuck on a particularly long article in pre-parse mode, it's often quicker to stop AWB and search the article by hand, or at least it would be if you could stop AWB. — kwami (talk) 07:19, 1 March 2014 (UTC)
Added in revision	rev 10495

rev 10490 to rev 10495. Run main processing on background thread, so AWB can be stopped in the middle (background processing continues but AWB is available for use). Rjwilmsi 12:17, 19 November 2014 (UTC)

Shortcut

Status	Feature added in next release
Description	Adding a shortcut key (like alt-q) to the pre-parsing mode. (t) Josve05a (c) 19:06, 1 November 2013 (UTC)
Added in revision	rev 10497

rev 10497 Add Control+Shift+E as keyboard shortcut for pre-parse mode. Rjwilmsi 16:44, 19 November 2014 (UTC)

Populating PLACE OF BIRTH to Persondata

Status	This feature is not going to be implemented
Description	If the lead of an article about a person contains "(born November 10, 1980 in [[Los Angeles, California]])", AWB will add "November 10, 1980" to the Persondata DATE OF BIRTH= parameter. Could it also populate the PLACE OF BIRTH= parameter with [[Los Angeles, California]]? GoingBatty (talk) 02:16, 11 November 2010 (UTC)
Added in revision

I don't think this should be implemented. WP:MOSBIO says that the dates should be in the lead, but generally not places of birth and death. "Birth and death places should be mentioned in the body if known, and in the lead if they are relevant to the person's notability." This feature would bless and encourage those who go against the guideline. Chris the speller ^yack 19:02, 22 September 2012 (UTC)

I didn't see it that way, Chris, but you bring up an excellent point. I know there are hundreds of thousands of articles with Persondata templates without the SHORT DESCRIPTION= parameter, so I'm presuming there are also a large number where the PLACE OF BIRTH= is missing, and that populating the template would be a good thing. However, if this feature was implemented, it would be documented on WP:AWB/GF, which may lead people to believe that the place of birth should be in the lead. Any thoughts on how to populate this field without encouraging behavior that goes against the MOS? GoingBatty (talk) 13:16, 23 September 2012 (UTC)

I agree that populating the template would be a good thing, but not if it makes WP look sloppy to the average user. My own experience with Persondata is that it gets populated when I move places of birth and death from the lead to the body of the article and do other light overhauls of an article. Another way to populate this field is to scrape an infobox; I don't know whether this is already being done. Chris the speller ^yack 14:47, 23 September 2012 (UTC)

On Persondata's talk page, persondata is now officially depreciated. -- Magioladitis (talk) 07:24, 23 November 2014 (UTC)

Alerts for incomplete Persondata templates

Status	This feature is not going to be implemented
Description	Could you please add alerts when Persondata does not contain values in either the |NAME= or |SHORT DESCRIPTION= parameter? Encouraging AWB users to populate these fields will hopefully reduce the number of articles in the maintenance categories Category:Persondata templates without name parameter and Category:Persondata templates without short description parameter. GoingBatty (talk) 20:51, 24 February 2013 (UTC)
Added in revision

I use "Skip if no alerts". If we add more alerts this would imply less pages to skip. -- Magioladitis (talk) 21:04, 24 February 2013 (UTC)

For some tasks, users may want to "Skip if no alerts". For other tasks, users may want to be alerted to lots of things they can fix before clicking Save. GoingBatty (talk) 21:36, 24 February 2013 (UTC)

True but these pages are populated by tracking categories anyway. -- Magioladitis (talk) 21:57, 24 February 2013 (UTC)

I would like this change. When I'm fixing typos I won't see the tracking categories, and won't normally bother to scroll to the end just to see if the persondata is complete. -- John of Reading (talk) 08:46, 25 February 2013 (UTC)

I think this is going to be moot. There is already talk of bots on Wikidata getting information from persondata. (Mangus and Sk!d were involved) I have a feeling persondata will become obsolete when that happens. Maybe hold off on this request until stage 2 (or whatever the next rollout is called) is pushed to English Wikipedia? Hopefully will get a better idea where Wikidata is headed at that point. I think this entry on Wikidata shows where are now and the end of persondata. Bgwhite (talk) 10:19, 25 February 2013 (UTC)

Interesting, thanks for that link. -- John of Reading (talk) 10:59, 25 February 2013 (UTC)

First tracking category has 0 items now. -- Magioladitis (talk) 17:17, 9 August 2014 (UTC)

On Persondata's talk page, persondata is now officially depreciated. -- Magioladitis (talk) 07:21, 23 November 2014 (UTC)

Image file previewing

Status	This feature is not going to be implemented
Description	Allow previewing of image files instead of just a preview of the image description page. Image file preview may also include information about the file itself, e.g. file type & size, resolution, file duplicates, etc. Spebi (talk) 07:08, 24 August 2010 (UTC)
Added in revision

Is this something that AWB is capable of? Would it be better suited as a plugin or other? It's a feature that could really come in handy on my wiki. Could someone give me an indication as to whether or not it is possible? Spebi (talk) 09:50, 29 August 2010 (UTC)

I second this, please show us how!

Peteparker (talk) 00:59, 30 September 2013 (UTC)

Rjwilmsi this would mean that in File namespace we provide different (or extra) page statistics. -- Magioladitis (talk) 08:05, 8 October 2014 (UTC)

Removal of redundant commas within any infobox

Status	This feature is not going to be implemented
Description	Within an infobox, to remove a comma when followed by <br> (and its other versions) so that a "," does not appear at the end of each item in an infobox list. See the examples below for examples of what this should do. Skier Dude (talk 05:38, 5 December 2010 (UTC)
Added in revision

For example: a list like
|starring = [[Tom Sizemore]],<br />[[Richard Jenkins]],<br />[[Ving Rhames]],<br />[[Colm Feore]]

Example with commas
Starring	Tom Sizemore, Richard Jenkins, Ving Rhames, Colm Feore

becomes
|starring = [[Tom Sizemore]]<br />[[Richard Jenkins]]<br />[[Ving Rhames]]<br />[[Colm Feore]]

Example without commas
Starring	Tom Sizemore Richard Jenkins Ving Rhames Colm Feore

Skier Dude this is better as a WP:BOTREQ. So we can see who can do it and how. -- Magioladitis (talk) 18:18, 12 August 2014 (UTC)

Allow use of CirrusSearch back end for "Wiki search (text)" and/or "Wiki search (title)"

Status	This feature is not going to be implemented
Description	On the WP Special:Search page, the new CirrusSearch back end can be selected by appending &srbackend=CirrusSearch to the URL. The new search has a very useful feature called "Phrase search and proximity" that allows searching for terms that are separated by a specified number of words. The usefulness of this technique has been discussed at WT:AWB/T#signed a contact. Perhaps AWB could add a new source type to the drop-down list under "Make list", perhaps called ""Wiki search (text – CirrusSearch)" or something to that effect. If it just entails adding that single parameter to whatever gets passed to the WP server, this would greatly increase AWB's effectiveness for very little change of code. Chris the speller yack 20:21, 20 January 2014 (UTC)
Added in revision

@Chris the speller: I agree that the new CirrusSearch should be very helpful (although I agree that case sensitive searching would be a nice addition). Will CirrusSearch be replacing the current search engine, or will we have two types of searches going forward? Thanks! GoingBatty (talk) 20:49, 20 January 2014 (UTC)

@GoingBatty: mw:Search says "Our current project is to replace our legacy lsearchd system with a new system based on Elasticsearch (using a new extension called CirrusSearch). This project started in June 2013, with the migration slated to last until early 2014." That schedule seems rather optimistic. I get the feeling that it will probably be many months before CirrusSearch hits prime time; it hasn't even been offered in a beta version yet on en.wikipedia. I estimate that the index is about 70% built and will take a few more days to finish. Allowing AWB users to try CirrusSearch now will soften the learning curve for AWB users that will hit suddenly when they think it's time to yank the plug on the search that is now in production, and lots of productive WP cleanup can be done in the meantime; why wait? I asked about case-sensitive search on the talk page for CirrusSearch help, but haven't gotten a rise out of anybody there. Chris the speller ^yack 21:21, 20 January 2014 (UTC)

@Chris the speller: what is the status of this one? -- Magioladitis (talk) 07:38, 25 July 2014 (UTC)

@Magioladitis: It appears that we still have more time. WP:VPT#Tech News: 2014-30 says that they have hit some performance snags and have backed off using this as the primary search for the Spanish Wikipedia, and delayed its rollout for other languages. The index is complete, and I frequently use CirrusSearch to find certain kinds of phrases, but then have to scrape the screen to create a list for AWB. The previous target date for en.wikipedia was August 25; they are supposed to set a new schedule within a week. Chris the speller ^yack 14:54, 25 July 2014 (UTC)

There is nothing to be done by our side. It will be done anyway and it will be automatically inherited by AWB as long as it comes live. No worth implementing it independently. 6 months ago it may worth to do it but now... -- Magioladitis (talk) 17:25, 9 August 2014 (UTC)

@Chris the speller: It should work by now. Please confirm. -- Magioladitis (talk) 23:08, 9 September 2014 (UTC)

@Magioladitis: I assume you mean that I should try AWB 5.5.4.0, and that's what I did. I didn't see any difference in Wiki search (text); is there a switch to flip? One surprise was that the search kept hits from these namespaces: Main, User, Wikipedia, File, Template, Category (and all the talk pages for those). I usually filter for just Main/article, and never saw a new release change the filter before. Chris the speller ^yack 02:20, 10 September 2014 (UTC)

@Magioladitis: Now on 5.5.5.0 and still no capability to use CirrusSearch back end. We need this more than before, as LuceneSearch's index has not been updated for 11 days. Please advise. Chris the speller ^yack 21:08, 22 September 2014 (UTC)

@Reedy:? Any ideas? -- Magioladitis (talk) 21:11, 22 September 2014 (UTC)

'wmgUseCirrus' => array(
	'default' => true,
	'dewiki' => false,
	'enwiki' => false,
	'frwiki' => false,
	'zhwiki' => false,
),

And then from https://es.wikipedia.org/w/api.php

  srbackend           - Which search backend to use, if not the default
                        One value: CirrusSearch, LuceneSearch
                        Default: CirrusSearch

AWB doesn't set a srbackend parameter, so it should be using CirrusSearch (as it's the default). If it actually isn't, it would seemingly be a MediaWiki/MediaWiki API bug. Reedy (talk) 13:41, 23 September 2014 (UTC)

I know that "AWB doesn't set a srbackend parameter". That's exactly why I made this request over 8 months ago, so AWB could set it to use a back end that can produce useful results. Is there still any question about what I was asking for in January and am still asking for now? Chris the speller ^yack 16:20, 23 September 2014 (UTC)

I'm poking around about this on the MediaWiki side. Can you provide an example of something that should work? Ie it definitely does when using Cirrus, but doesn't using the (out of date) Lucene indexes? Reedy (talk) 13:49, 23 September 2014 (UTC)

Here is a query that only works with Cirrus. I tried it in a browser without cookies and it went to Cirrus and spat out results. Of course on dewiki, enwiki, frwiki, and zhwiki it wouldn't because it'd still go to lsearchd. And because the search is in Spanish.NEverett (WMF) (talk) 14:46, 23 September 2014 (UTC)

Please notice that this request was made over 8 months ago, long before CirrusSearch was the default back end for search on any Wikipedia. Perhaps when Magioladitis posted "It should work by now. Please confirm" he meant that I should test it on a Wikipedia that had CirrusSearch as default. I use en.wikipedia (99.999%) and so was confused by the claim that it should work. Now we're in a pickle because AWB can't make much use of the LuceneSearch index on en.wikipedia, which stopped updating almost 2 weeks ago, and it can't use CirrusSearch, because we have no way to specify that. I thought that by giving 8 months' notice we could be prepared for this day, but now it appears that I was too optimistic. AWB is not ready, and CirrusSearch hasn't addressed the shortcomings in finding hyphenation that were pointed out several months ago as feedback and then reinforced in bug reports. Can we do anything to improve this mess? Chris the speller ^yack 16:07, 23 September 2014 (UTC)

@Magioladitis: Now that CirrusSearch is the default search on all Wikipedias, it probably makes sense to mark this suggestion as "This feature is not going to be implemented". Chris the speller ^yack 05:21, 11 December 2014 (UTC)

Chris the speller done. -- Magioladitis (talk) 09:39, 11 December 2014 (UTC)

Make <br>→<br /> a fix item

Status	This feature is not going to be implemented
Description	I use syntax highlighting when editing, which I like a lot. In this environment, when it detects an HTML tag, it will highlight that snippit pink (by default), which is great. What I don't like is when, in infoboxes or whatever, there is a <br> tag that turns the entire rest of the article text pink because it never sees a closing tag. So I would really appreciate it if one of the filters AWB uses flagged every <br> tag for replacement with a <br /> tag so this issue could gradually get weeded out. Thanks! Deadbeef 10:27, 19 November 2014 (UTC)
Added in revision

Despite <br> without closing tag being invalid XML, <br> and <br/> are both valid forms of the line break in HTML.^[1] This means it's technically a bug in the syntax highlighter. I do prefer <br/> though. SiBr₄ (talk) 10:42, 19 November 2014 (UTC)

Marked as "no". Both are valid. -- Magioladitis (talk) 11:08, 19 November 2014 (UTC)

Correct. The break element is vastly overused in article content. Where used to improperly create lists, {{plainlist}} or similar should be used. Where used to format lyrics, poems and the like, <poem> should be used. --  Gadget850 ^talk 18:54, 25 November 2014 (UTC)

Only restrict Bots on CheckPage

Status	Feature added in next release
Description	It seems the current CheckPage format currently doesn't allow restriction of ONLY bot features (i.e. auto saving). On our wiki, we would like to allow all users to use AWB but restrict bot usage to a whitelist. Hylian King ZW (talk) 02:55, 26 May 2014 (UTC)
Added in revision	rev 10496

@Hylian King ZW: New checkpage option: <!--All users enabled user mode--> will enable all users for user mode, and enable bots only when in <!--enabledbots--> section. Rjwilmsi 13:50, 19 November 2014 (UTC)

Threading

Status	Feature added in next release
Description	Run "sort A-Z" and "remove duplicates" on seperate threads to prevent the user interface locking up Check that the listmaker buttons and menu items (which remain enabled when a background thread is running) don't cause an error if they fire when a thread is active; if they do, disable them, or implement a queuing system. --kingboyk 15:40, 9 April 2007 (UTC) The parser will have to be multi threaded as well as the IE component thing. The program will have two threads. One thread displays the result of the computation and the other thread will be working on the next item in the list. This will waste less of the user's time wasting for the page to load. Throttling will need to built in so that the program will slow down if it loads to many pages in a minute. —Dispenser 18:55, 3 June 2007 (UTC)
Added in revision

The "keep sorted" should only run when new items are added to the list. Rich Farmbrough, 04:24, 7 July 2009 (UTC).

Bump this because with large lists the sorting of the already sorted list can make it very hard to get enough attention from AWB to turn the sorting off. Also by sorting the list when an item is added we can use a fast insertion sort, only doing a big sort when the menu item is checked. The same logic could then handle "Remove duplicates", which in some circumstances one has to unclick and click repeatedly. Rich Farmbrough, 15:19, 22 August 2009 (UTC).

Marking as added. We now have faster list sorting and filtering with use of .NET 3.5 List.Distinct() and List.RemoveAll() with predicates. Rjwilmsi 12:06, 19 November 2014 (UTC)

Expand FixSyntax to correct "http:// http://"

Status	Feature added in next release
Description	AWB's FixSyntax general fix already fixes external links starting with "http://http://" (no space). Would it be possible to please expand this fix to also correct "http:// http://" (with a space)? See Shark finning for an example. Thanks! GoingBatty (talk) 16:56, 20 January 2014 (UTC)
Added in revision	rev 10484

rev 10484 Rjwilmsi 15:32, 29 October 2014 (UTC)

Add a "Load list" function

Status	Feature already exists in AWB
Description	Any place we can save a list (to disk), we should have an option of loading a list (from disk). A way of doing this currently is to save settings, as that also saves the current main list. But I'd like to be able to load a list into the list comparer as necessary as well. I think that being able to load lists by themselves (not only as a part of settings) would be more flexible. The loader could accept the lists in various formats, such as a flat list (a page name on each line) or using the format it currently saves to. Stevie is the man! Talk • Work 16:14, 30 August 2014 (UTC)
Added in revision

@Stevietheman: See #Import list above. In both the main window and the list comparer, the Text file (UTF-8) and Text file (Windows 1252/ANSI) options in the "Source" menu import a locally stored list. To save a list but not the other settings, use the List → Save list function in the main screen, or the Save list button in the list comparer. SiBr₄ (talk) 17:11, 30 August 2014 (UTC)

I already know how to save lists by themselves -- that's not the concern and I don't know how I left the impression that I didn't understand that already. Anyway, I now see that lists can be loaded via Source, and I thank you for pointing that out. However, it's not very intuitive. There needs to be a "Load list..." under "List" in the menu, for clarity's sake. I'm thinking many users wouldn't make the mental connection of "Text file" to "List". We have examples of two people who haven't. :) Stevie is the man! ^{Talk • Work} 17:34, 30 August 2014 (UTC)

Import list

Status	Feature already exists in AWB
Description	The list maker and comparer allow for data export through the save list button, but they don't allow for re-import of that same data. For example, there is no way you can combine the saved results of two categories and then compare them with the contents of a third category (my idea was to gather the contents of Category:Male athletes and Category:Female athletes and find the people in Category:Athletes by nationality who do not appear in those categories). Allowing list import of previously exported text files would make such tasks easier. SFB 18:54, 8 August 2014 (UTC)
Added in revision

@Sillyfolkboy: If I understand your request correctly, there actually is. The "Source" dropdown menu contains the options Text file (UTF-8) and Text file (Windows 1252 / ANSI) to import .txt files of different encodings. SiBr₄ (talk) 20:11, 8 August 2014 (UTC)

@Sillyfolkboy: To complete your task, I would set list 1 with Source of Category and fill in "Male athletes|Female athletes" in the Category box. You can use the pipe character to include multiple categories in one list. Hope this helps! GoingBatty (talk) 00:44, 9 August 2014 (UTC)

@GoingBatty and SiBr4: Thanks to both of you. These are the kind of features I was looking for, but I'm struggling to find documentation that notes either of these – do we have an appropriate venue to add this information? SFB 06:31, 9 August 2014 (UTC)

@Sillyfolkboy: See Wikipedia:AutoWikiBrowser/User manual#Make list, which has an explanation of each item in the source drop down menu and a small note at the top about using the pipe character. GoingBatty (talk) 15:59, 9 August 2014 (UTC)

Expand removal language=English from citation templates

Status	User has withdrawn this request
Description	AWB's general fixes for citation templates already "Removes |language= when it is English per citation templates manuals." Could this please be expanded to remove |sprache= when it is English in {{internetquelle}}? This will will remove the article from Category:CS1 maint: English language specified. See Wafik Moustafa for an example. Thanks! GoingBatty (talk) 00:12, 10 November 2014 (UTC)
Added in revision

I hacked a quick script that removed |sprache=en, |sprache=EN, |sprache=English, and |sprache=Englisch from about 60 pages that transclude {{internetquelle}}.

Find: (\{\{(?:internetquelle|Literatur)[^\}]*)\|\s*(?:Original)sprache\s*=\s*(?:english|Englisch|en\-us|en)

Replace: $1

The better solution perhaps, is to fix {{internetquelle}} so that it doesn't pass English on to {{cite web}}. I'll have a look at it in the morning unless someone beats me to it.

—Trappist the monk (talk) 01:01, 10 November 2014 (UTC)

Tweaked the script so that it also fixes {{Literatur}} even though that template uses {{citation/core}}.

—Trappist the monk (talk) 01:21, 10 November 2014 (UTC)

@Trappist the monk: Any luck with fixing {{internetquelle}} so that it doesn't pass English on to {{cite web}}? Thanks! GoingBatty (talk) 00:51, 27 November 2014 (UTC)

Yeah, with this edit. Category:CS1 maint: English language specified is pretty much empty right now.

—Trappist the monk (talk) 01:03, 27 November 2014 (UTC)

Thanks - request withdrawn. GoingBatty (talk) 02:34, 27 November 2014 (UTC)

Add Ctrl+A to the edit summary text box (not the dropdown menu)

Status	Feature added in next release
Description	Ctrl+Z, Ctrl+X, Ctrl+C, Ctrl+V all work in the text box, but not Ctrl+A :(   ~ Tom.Reding (talk ⋅contribs ⋅dgaf)  18:14, 6 January 2015 (UTC)
Added in revision	rev 10701, rev 10702 by Reedy. -- Magioladitis (talk) 18:47, 6 January 2015 (UTC)

Automaticly change the cats to template

Status	This feature is partially implemented
Description	Make AWB automatically change if an article has Category:Disambiguation pages on it to {{disambiguation}} and add {{surname}} if it has Category:French-language surnames etc. (t) Josve05a (c) 15:31, 14 September 2013 (UTC)
Added in revision

This is already done. -- Magioladitis (talk) 11:02, 24 January 2015 (UTC)

Remove files that contain ext links

Status	This feature is not going to be implemented
Description	A number of images turn of in Category:Articles with missing files that use an ext link as a file name (eg. [1]). I would like to see AWB remove any files of the form File:http://example.ext or File:https://example.ext. I doubt that there would be any false positives. -- Alan Liefting (talk - contribs) 06:55, 26 September 2012 (UTC)
Added in revision

Note that your example is of the form image = http://example.ext, which is another variation that would be good to remove. If there isn't already a bot that does this, I could submit a bot request. Thanks! GoingBatty (talk) 23:05, 26 September 2012 (UTC)

That would be good. There are some bots that work on images - one of them is CommonsDelinker and there is another one (forgot the name) that will sometimes tag a page revision if it is bad image related edit. The bot should revert the edit and notify the editor. I am seeing some newbies struggling to get an image into an article. -- Alan Liefting (talk - contribs) 06:06, 27 September 2012 (UTC)

That's too advanced for my simple bots. Try Wikipedia:Bot requests. GoingBatty (talk) 00:35, 28 September 2012 (UTC)

This issue is going to disappear as more infoboxes are converted to use Module:InfoboxImage. There's logic in there to ignore an image parameter that is actually an external link. -- John of Reading (talk) 16:52, 4 April 2013 (UTC)

Most infoboxes use Module:InfoboxImage now. Do we still need this FR? -- Magioladitis (talk) 18:34, 21 July 2014 (UTC)

Marked as "no". It is rare and risky. Better ask for a tag for this one. -- Magioladitis (talk) 08:47, 3 February 2015 (UTC)

Warn before opening XX number of pages

Status	Feature added in next release
Description	I was working with a very large list, I had a few thousand selected and accidentally double clicked causing AWB to attempt to open them all in tabs... After trying to close them as they opened I eventually gave up and had to hard reboot my computer to stop the constant stream of opening tabs! It would be great if AWB could provide a warning box such as "Are you sure you wish to open more than 20 pages?" to prevent this happening by accident. Jamesmcmahon0 (talk) 09:49, 9 February 2015 (UTC)
Added in revision	rev 10823

rev 10823 In List Maker, apply same "large list" check to double click as well as "open in browser" menu items. Rjwilmsi 14:41, 9 February 2015 (UTC)

Use the new serif font for headings of primary sections in preview mode

Status	Feature already exists in AWB
Description	Use a serif font for headings of primary sections in preview mode, to match the typography on Wikimedia sites that was introduced on 3 April 2014. Chris the speller yack 19:26, 4 April 2014 (UTC)
Added in revision

Chris the speller what's the status of this one? -- Magioladitis (talk) 11:08, 25 July 2014 (UTC)

Adding my sign, so that the ping works... (t) Josve05a (c) 11:10, 25 July 2014 (UTC)

For preview, Wiki does the work. So we are doing it :) -- Magioladitis (talk) 23:50, 1 March 2015 (UTC)