Wikipedia:Village pump (technical)

The technical section of the village pump is used to discuss technical issues about Wikipedia. Bugs and feature requests should be made at Bugzilla (How to report a bug). Bugs with security implications should be reported to security

wikimedia.org.

Newcomers to the technical village pump are encouraged to read these guidelines prior to posting here. Questions about MediaWiki in general should be posted at the MediaWiki support desk.

view · edit

Frequently asked questions (see also: Wikipedia:Technical FAQ)

Click "[show]" next to each point to see more details.

If something looks wrong, purge the server's cache, then bypass your browser's cache.
This tends to solve most issues, including improper display of images, user-preferences not loading, and old versions of pages being shown.

No, we will not use JavaScript to set focus on the search box.
This would interfere with usability, accessibility, keyboard navigation and standard forms. See task 3864. There is an `accesskey` property on it (default to `accesskey="f"` in English). Logged-in users can enable the "Focus the cursor in the search bar on loading the Main Page" gadget in their preferences.

No, we will not add a spell-checker, or spell-checking bot.
You can use a web browser such as Firefox, which has a spell checker.

If you have problems making your fancy signature work, check Help:How to fix your signature.

If you changed to another skin and cannot change back, use this link.
Alternatively, you can press Tab until the "Save" button is highlighted, and press Enter. Using Mozilla Firefox also seems to solve the problem.

If an image thumbnail is not showing, try purging its image description page.
If the image is from Wikimedia Commons, you might have to purge there too. If it doesn't work, try again before doing anything else. Some ad blockers, proxies, or firewalls block URLs containing /ad/ or ending in common executable suffixes. This can cause some images or articles to not appear.

For server or network status, please see Wikimedia Status. If you cannot reach Wikipedia services, see Reporting a connectivity issue.

« Archives, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212

Lua Citation deployment

In the not too distant future, we are likely to deploy the Lua version of {{cite encyclopedia}}, {{cite encyclopedia/lua}}, as a moderate scale test of Module:Citation/CS1. Lua-based citations are expected to reduce citation formatting time by about 80% without sacrificing any formatting options. The current set of test cases for this template can be seen at Module talk:Citation/CS1/test/encyclopedia. As shown, there are a number of cases where errors in the current {{cite encyclopedia}} have been corrected, as well as small formatting changes (often motivated by a desire make the different families of citation templates more consistent). Dragons flight (talk) 01:20, 17 March 2013 (UTC)[reply]

I've gone ahead and deployed the Lua version for {{cite encyclopedia}}. Dragons flight (talk) 03:46, 17 March 2013 (UTC)[reply]

{{cite news}} has now also been replaced with a Lua version. Test cases at Module talk:Citation/CS1/test/news. Dragons flight (talk) 14:20, 19 March 2013 (UTC)[reply]

{{cite journal}} has now also been deployed using Lua. Test cases as Module talk:Citation/CS1/test/journal. Dragons flight (talk) 01:00, 23 March 2013 (UTC)[reply]

{{cite book}} has now been deployed using Lua. Test cases at Module talk:Citation/CS1/test/book. Dragons flight (talk) 23:33, 24 March 2013 (UTC)[reply]

{{cite web}} has now been deployed using Lua. Test cases at Module talk:Citation/CS1/test/web. Dragons flight (talk) 00:51, 29 March 2013 (UTC)[reply]

Thanks very much for all the updates, DF. I must admit I was a bit worried about the conversion to Lua, but everything has turned out great from all the checking I've done. I certainly appreciate all the work you've done. 64.40.54.208 (talk) 05:53, 31 March 2013 (UTC)[reply]

Display Chess games (with animation) using PGN data

I'm reviving this discussion from the archive. The last time around it lived for four days, people commented on it but it didn't generate strong support or opposition and nothing came of it.

Archives:
WP:Village_pump_(proposals)/Archive_97#Display_Chess_games_.28with_animation.29_using_PGN_data
WP:Village_pump_(technical)/Archive_104#Display_chess_games_from_PGN_data

Summary: PGN is a standard format to record chess games. The proposal is to use a Javascript viewer so the user can view the chess game one move at a time, moving forwards and backwards by pressing buttons. (The current options are to include an animated GIF, a static image, or a movie, but nothing in Wikipedia right now allows the user to control the chess game interactively.) This is already working on the Hebrew Wikipedia but needs consensus to be brought over to English Wikipedia.

[Edit: this will be a Gadget, not a change to MediaWiki:Common.js. This means:

Only users who explicitly choose to install the Gadget will be able to view the animation.
The complete move list must appear in the text of the article, since not everyone will be able to view the animation.
For users who choose not to install the gadget, a static image of the chessboard will be shown instead.]

The original proposal is copied below. Mattj2 (talk) 22:21, 24 March 2013 (UTC)[reply]

There is a standard, called Portable Game Notation to describe chess games. This is the dominant standard to store and present chess games on computers, and is also used in many books and newspapers. There are numerous databases containing tens of thousands of chess games, all using this notation.

There are many chess web sites that can display chess animation based on this format, e.g., http://chesstempo.com/pgn-viewer.html (just an example - i listed it just because it was the first google hit for "pgn viewer").

There is a mediawiki extension called Extension:EmbedChessboard which displays chess games using PGN notation. This extension has it cons and pros. However, i do not believe it is likely that this extension will be accepted for any wikimedia site.

i developed a pgn animation script+template which is now deployed in hewiki (demo page: he:משתמש:קיפודנחש/ארגח 1, example of one of the articles using the template: he:עמוס ברן.

The script is a roughly 720 lines of easy to read JS. in order to use it on enwiki it will have to be included from common.js. it can be viewed here: he:Mediawiki:common.js/pgn.js. discussions in chessclub here: Wikipedia talk:WikiProject_Chess#PGN_viewer. discussion in WP:VPT here: Wikipedia:Village pump (technical)/Archive 104#Display chess games from PGN data.

Proposal: Add the pgn script, optionally with required modification to common.js, and Create a template to display chess games using PGN format.

קיפודנחש (aka kipod) (talk) 04:30, 24 December 2012 (UTC)[reply]

Comment Why do we need to display chess games? "If" there was a valid reason for displaying a game for historic purposes (these would likely be slim and likely not worth the resources imho), then I could possibly see allowing the script to be activated as a WP:Gadget, certainly not something everyone is required to load via MediaWiki:common.js. — User:Technical 13 ( C • M • Click to learn how to view this signature as intended ) 22:35, 24 March 2013 (UTC)[reply]

The dynamics of a chess game (and its analyses) are a major encyclopedic issue. It's just you are not used to time-based information? Don't say that you do print WP pages before reading, I'd suggest. -DePiep (talk) 01:53, 25 March 2013 (UTC)[reply]

Yes, if you want to understand a game you have to go through the moves. Now we have the moves listed, which means that most people will have to follow along with a chessboard and set. Not so with the PGN method proposed. Bubba73 ^{You talkin' to me?} 03:10, 25 March 2013 (UTC)[reply]

So what happens for people without Javascript, or users of the mobile site ? I think you should come up with a strategy to retain this information in a readable form for those users. Also, there are quite a few accessibility issues when it comes to capturing information in JS. Don't forget our blind readers. —TheDJ (talk • contribs) 13:06, 25 March 2013 (UTC)[reply]

Retain the present method of listing the moves. Besides the readers you mention, some people would want to see the moves written out instead of, or in addition to, the animation. Bubba73 ^{You talkin' to me?} 14:49, 25 March 2013 (UTC)[reply]

There are a few articles about individual games, e.g. The Game of the Century (chess). There is a large number of biographies that contain games, e.g. Frank Marshall (chess player). There are many other articles that contain sequences of moves, from the start of the game, (e.g. Philidor Defence) or from a certain position ( e.g Lucena position, checkmate, and Bishop and knight checkmate). Bubba73 ^{You talkin' to me?} 23:18, 24 March 2013 (UTC)[reply]

Some of the pages that would benefit from this: Category:Chess_openings (168 pages) Mattj2 (talk) 04:37, 25 March 2013 (UTC)[reply]

Sigh. — Hex (❝?!❞) 10:22, 25 March 2013 (UTC)[reply]

Comment I kind of sympathize with the idea, but look at it on the mobile Wikipedia, not good: https://he.m.wikipedia.org/wiki/%D7%A2%D7%9E%D7%95%D7%A1_%D7%91%D7%A8%D7%9F#section_1 --Atlasowa (talk) 23:29, 24 March 2013 (UTC)[reply]

Comment (This is me commenting on my own proposal; I hope I'm allowed.) (1) In response to Technical_13, this is something that would only be used by a tiny minority of users, but to those users it would be a huge improvement. (2) The most important thing to me is that this be a slideshow that is controlled by the user. If there isn't support for a chess-specific widget, then let it be a widget that just shows a bunch of pictures one after the other, with the user able to go forwards and backwards at will. This could be used for any board game like checkers or Go. Every board game has pages that list sequences of moves, and all of those pages could benefit from a slideshow widget. I'm kind of new.. should I list the "generic slideshow widget" as a separate proposal on this page? This proposal is for a chess-specific viewer. Thanks. Mattj2 (talk) 05:17, 25 March 2013 (UTC)[reply]

I'm not saying I'm opposed to the script or having it available. What I'm saying is that it should be an optionally loaded script (such as a gadget or something the individual user can add to their common.js or skin.js). What I am opposed to is forcing it to be "unconditionally loaded for all users on every wiki page."^source There is already enough stuff the majority of people don't use that is loaded and doesn't need to be, which in turn slows down every page on the wiki. — User:Technical 13 ( C • M • Click to learn how to view this signature as intended ) 11:24, 25 March 2013 (UTC)[reply]

Actually, such a script is usually only loaded on pages that actually require it (although it seems he.wp is not that smart about it). So it would only slow down those pages with chess animations, it wouldn't even register as an addition (in terms of processing) of all the JS that we already have. The complexity of pages themselves, and the numerous tools that we already have that do actually run on all pages dwarf the addition of a 'doest this page require png.js' check. —TheDJ (talk • contribs) 13:06, 25 March 2013 (UTC)[reply]

Scholar's mate has an animation in the upper right. But the reader can't control the speed or pause it to study. This proposal would be much better than that animation. Bubba73 ^{You talkin' to me?} 05:57, 25 March 2013 (UTC)[reply]

Having looked at the demo page, I support this, and Mattj2's suggestion of a generic animation system as a extremely useful addition to our coverage of board games. — Hex (❝?!❞) 10:22, 25 March 2013 (UTC)[reply]

as the script author, i'd like to respond to some of the comments:

User:Technical 13 says: "Why do we need to display chess games?"
- just open several of the articles transcluding {{Chess diagram}} - most of them do show chess games, and would benefit from this tool
  - That is fair enough. It does apparently have a practical use. — User:Technical 13 ( C • M • Click to learn how to view this signature as intended ) 21:14, 25 March 2013 (UTC)[reply]

And that's not all - there is also {{Chess diagram small}}. Bubba73 ^{You talkin' to me?} 22:50, 25 March 2013 (UTC)[reply]

Same user says: "certainly not something everyone is required to load via MediaWiki:common.js", aluding to the weight of the script.
- i do not think this script is that heavy. it weighs less than 1/4 of, say, MediaWiki:Gadget-HotCat.js, which was made "default" for all registered users recently. in all the discussions of making everyone load hotcat as default, i did not see a single mention to the size or weight of the script as consideration. However, it will be very easy to load this script from common.js only if needed (basically moving the very simple test whether or not the page contains a PGN from the script itself to common.js)
  - That is rich... Let's run with your comment here though. You think that a script that will be actually used on a minority of a minority of pages (yeah, I wanted to emphasize it is a minority), should be loaded in MediaWiki:common.js when MediaWiki:Gadget-HotCat.js that is potentially useful or used on every page spent three years, four days, six hours, and twenty-eight minutes as a gadget from 12:18, March 21, 2008 to 18:46, March 25, 2011? I'm not saying it shouldn't be available, I'm saying I think it should be available as a gadget so that all of those people that don't want it or that it won't properly run for will be able to opt-out of it. — User:Technical 13 ( C • M • Click to learn how to view this signature as intended ) 21:14, 25 March 2013 (UTC)[reply]
    - Now that I've had time to think about it, I think you're right that a chess animation thing has too much of a niche audience to lobby for inclusion in Common.js right away. Also, for accessibility reasons the chess animation should be a helpful addition to the page but not a requirement. So nothing important is lost by making it a Gadget. I edited the proposal above. (Am I allowed to do that?) Mattj2 (talk) 07:33, 28 March 2013 (UTC)[reply]

That was all I was saying. I fully support this script as a Gadget, and would be happy to offer any assistance I can to the possible appearance and mechanics of this project. I have some great ideas on how this could appear on the pages and some of the mechanics of it, is there a specific project page that I could offer my layout idea on? — User:Technical 13 ( C • M • Click to learn how to view this signature as intended ) 11:42, 28 March 2013 (UTC)[reply]

Yay! Thanks for your enthusiasm! I created a project page: WP:WikiProject_Chess/PGN_Chess_Viewer.
(This is a subproject of the chess project. I posted on their talk page.) Have fun. :) Mattj2 (talk) 03:19, 29 March 2013 (UTC)[reply]

User:TheDJ asks about users with no JS.
- The template in hewiki displays for users with no JS a short message stating that in order to see the games one needs to enable JS. An alternative would be to display the PGN of the games. either of these two approaches is possible. to some extent it's like asking "what do people browsing using pure text browser (such as Lynx) see when the editor puts a photo on the page", or "what happens when the browser does not support a specific media type that we allow (sound, video etc.)". the standard answer is that if your browser do not support a specific WP-supported media type, you will not be able to see some of the content on some of the pages. it's important that editors will not make the whole article dependent on the ability of all users to view specific media types, and the same holds here: one should not create an article such that being able to see the PGN animation is critical for reading and understandingthe article.
Several people, including [[User:Hex and User:Mattj2 discussed some means to display other board games interactively
- i'd like to make the point that this specific script will be of no help for other board games. it's very specifically limited to chess + PGN. it does support some very close variation of chess - specifically Chess960, but not any variation with different pieces or different moves (i.e., no Fairy chess support).

peace - קיפודנחש (aka kipod) (talk) 18:36, 25 March 2013 (UTC)[reply]

There is a lot to be said for animated gif... it works without javascript and you can put the notation besides or under. (unblurred --Atlasowa (talk))

kipod, again: This makes an unreadable mess of the mobile Wikipedia pages, or is this just me? You seem to be saying that you don't care anymore about those mobile user than about Lynx user? The page views to mobile Wikipedia are steadily growing. You want to establish a new template that disregards mobile user trends? Confused: --Atlasowa (talk) 20:10, 25 March 2013 (UTC)[reply]

What you're talking about is a bug. IMHO the bug is serious enough that this animation thing shouldn't be used on English Wikipedia until it's fixed. I'd like to address (if possible) the more central question of: is this a good idea or not? Bugs can always be fixed. Is this something that will be of enough benefit to enough pages that it is worth including, in Common.js or a Gadget or whatever? Mattj2 (talk) 20:34, 25 March 2013 (UTC)[reply]

regarding mobile view: originally it was an oversight on hewiki. now that i've became aware of it i fixed it (i think) but currently the fix doesn't do anything, due to a bug in the MobileView extension. once this is fixed, we'll test to see if my fix actually solves the problem, and if it doesn't, we'll find another way to solve it. peace - קיפודנחש (aka kipod) (talk) 17:44, 26 March 2013 (UTC)[reply]

That sounds good. :-) BTW, your PGN chess thing has got some admiration by chesslovers on german WP. I'll give them a note about this discussion, an improved chess template would be most interesting. deWP is currently using the Article Feedback Tool on category chess in german WP - and some readers do actually ask for PGN and the like. I see why this would be great and i see why animated gif kind of sucks in comparison. But there are other considerations as well, compatibility and loading i.e., and i'm glad that you care about that too. peace :-) --Atlasowa (talk) 18:53, 26 March 2013 (UTC)[reply]

Speaking of the chess template, there is a version in the works that uses Forsyth–Edwards Notation (FEN) to specify a position rather than doing it the way it does now. The main reason is probably performance. The author says that saving an article with the current chess template takes about 1 second per template. That seems to be true; and some pages have dozens of chess templates. Bubba73 ^{You talkin' to me?} 01:29, 27 March 2013 (UTC)[reply]

small correction: the template is not "in the works" - it's done. so far nobody made any comments or reported any problems. i don't think it's in actual use, but there is no work being done on it, and no work is planned (if someone _will_ make a comment or report a problem, then of course, it might trigger some changes. otherwise no addition to the template is planned). fyi - the template is {{Chess diagram-fen}}. peace - קיפודנחש (aka kipod) (talk) 06:44, 27 March 2013 (UTC)[reply]

Comment (My second comment, not trying to distort consensus.) Given some of the objections to the original proposal (and support for a simplified and more generic version), I spun that off as a separate proposal: WP:Village_pump_(technical)#Javascript_Slideshow_Widget_for_Board_Games. Just to reiterate, this proposal is for kipod's cool and wonderful Javascript PGN chess thing. Mattj2 (talk) 20:45, 25 March 2013 (UTC)[reply]

Have a look at Template:Scroll_gallery, Wikipedia:Village_pump_(proposals)/Archive_92#Scroll_galery, Wikipedia:Village_pump_(technical)/Archive_102#Scroll_galery. It is activated on german WP as de:Vorlage:Galerie and it is unpopular because it breaks pages for IE and mobileWP. Compare on mobile. --Atlasowa (talk) 21:08, 25 March 2013 (UTC)[reply]

Thanks! I don't want to reinvent the wheel. I can't push for the adoption of that one until the bugs are fixed but otherwise it looks great! Mattj2 (talk) 06:02, 28 March 2013 (UTC)[reply]

comment about the animated gif - that doesn't really serve the purpose. Sure, it shows the moves, but the point is that the reader needs to be able to control it. The user needs to study each position and move to understand why it was made or why it is good or bad. PGN supports inserting comments after moves. These could be displayed, although I don't know if that is included in this proposal. Also, the pieces are blurry in the animated gif. Bubba73 ^{You talkin' to me?} 15:52, 26 March 2013 (UTC)[reply]

Thanks. What I was trying to say was: the most important thing is to allow the user to study the chess game, not as an animated GIF and not as a static image, but where they can take as much time as they need to analyze each position. I personally am not concerned about supporting every single feature in PGN. For accessibility purposes, I think it's best if the full list of moves is written out in the article. If there's a comment it could be listed in plain text in the article as well. About the blurry pieces.. they're not blurry for me. Are they blurry for anyone else? Mattj2 (talk) 06:02, 28 March 2013 (UTC)[reply]

regarding animated gif: first, i do not think this is suitable for showing a full game. it may work for a repeating sequence of relatively small number of moves, but not a full game.

what's more, the vast majority of editors do not have any means to create those animated gif images.

this is in contrast to the template/script combo discussed here (as used in hewiki), which any editor can use relatively easily - all you really need is the PGN, which is readily available, without copyright, for huge number of games. i believe it's fair to say that the PGN of every single documented game of every chess player for whom there is an article in enwiki, can be obtained without too much difficulty. you can't compare this with animated gif - even if using a gif animation for a full game was acceptable, i do not know of any way for an editor to create or obtain such a gif for any specific game they might want to write about. peace - קיפודנחש (aka kipod) (talk) 07:06, 28 March 2013 (UTC)[reply]

i supported this. the usage of the optional gadget und a static chessboard fallback (also in case javascript disabled?) sounds perfect. Antimaterie (talk) 08:27, 28 March 2013 (UTC)[reply]

About the fallback chessboard, I think instead of just a static chessboard, it should be the animated gif. I also think that the animated gif should mirror the actual game. By this I mean, the moves in the gif should be timed to accurately mirror the actual game in instances of a representation of a game that was played. I think that a reasonable delay between moves (maybe 2500ms?) should be set as a guideline of sorts for how a generic set of moves/game should be played. I would be happy to assist with the creation of a few of these animated gifs (color scheme should probably be different than the one above that is hard for me with out vision problems to see well) and write a documentation on how to create them for the chess enthused community to take it from there and create the rest. — User:Technical 13 ( C • M • Click to learn how to view this signature as intended ) 11:42, 28 March 2013 (UTC)[reply]

just wondered: how do you envision creating those gif animations? is there an available tool or website that would consume a chess game (presumably in PGN format - after all this is the undisputed standard for representing chess games in a machine-consumable form) and squirt out gif animation? if so, could you point to it? thanks, peace - קיפודנחש (aka kipod) (talk) 16:18, 28 March 2013 (UTC)[reply]

in my opinion there is no need for the animated gifs, i'am following Bubba73 statement above. and as kibod pointed out, there's no ready tool to create this animated gifs. the static chessboard fallback doesn't break the other media types? maybe the template should also take the standard links to chessgames, chessresults & co? Antimaterie (talk) 17:28, 28 March 2013 (UTC)[reply]

I was going to build them one frame at a time using a program like UnFREEz. I'm sure that a program could be created specifically for this purpose, but I do not personally have the knowledge or programming experience to write it myself yet. It would be a long and tedious process and likely take quite a few people working on it. The biggest problem I have at the moment with the PGN setup is that there is no time parameter. Part of the excitement of watching a chess game using this format would be watching it in real time as it was played. Was that data ever recorded? Are there YouTube videos or something of the sort where the original games could be watched to add that data? — User:Technical 13 ( C • M • Click to learn how to view this signature as intended ) 17:32, 28 March 2013 (UTC)[reply]

hmmmm... this will be mighty nice of you, but i'm not sure it's an answer to the need - iiuc, this means that anyone who writes or edits a chess article and wants to include a game animation will have to ask for your services, right? if this is so, then i don't believe this can be "The Answer"™

IMHO, only a solution that will allow editors to do it independently is applicable on a reasonable scale. there are hundreds, if not thousands of chess-related articles, and dozens of active editors editing them. if there isn't a tool, or at least a recipe that reasonable person can use to create those, i don't think it's a viable general solution.

as to timing data: standard PGN does not include timing data per move. sometime there is some timing-related information in the Tags (these are the data pieces that appear in square brackets, and tells you who is black, who is white, when and where the game took place etc.), but these pertain to the whole game rather than to individual moves. pgn supports per-move comments, and it's conceivable that on some databases these comments are used to record timing information, but it's not part of the standard, and you can't rely on it or expect it.

peace - קיפודנחש (aka kipod) (talk) 18:11, 28 March 2013 (UTC)[reply]

i commit to kibod on this, only a programmatic solution is suitable. but once again, in my opinion the the reader needs to be able to control the moves. Antimaterie (talk) 18:32, 28 March 2013 (UTC)[reply]

I don't think that a real-time animation will be of much use, other than to the aficionados. Chess, when played well (particularly by masters) is a slow game. There are long periods where nothing seems to happen: yes, you and I know that the player is considering all the possible moves, and the likely outcomes of each one, but is the average person likely to be interested? They might instead assume that the animation has somehow "stuck", and blame Wikipedia for again producing faulty pages. If the moves are played at a steady rate (whether two per second or one every five seconds), the viewer will observe that something is still happening. --Redrose64 (talk) 22:32, 28 March 2013 (UTC)[reply]

No, no, no... That wasn't what I was suggesting. I'm still saying the buttons should be there to allow the user to control the playback (I think there should be a table with player one's moves on the left, player 2 on the right, and in the middle the ability to use first, back, play, forward, last. I guess I'm not really that knowledgeable when it comes to chess, but I thought there was a play clock that limited the players to a few minutes per move? As far as the animated gifs, the idea was I would create a few, write a document on how I did it to allow everyone to easily write their own... It may even be possible to expand svg somehow to accommodate this automatically. I'd have to do a lot more research for something like that though. I would be happy to go further into my production ideas for this project once there is a gadget talk page for it. I don't feel this is the place or that this project should take much of any more space on this forum. Seems there is a pretty reasonable consensus that this project should go ahead as a gadget. As far as your concern about people thinking it is stuck Rose, we could simply offer a play clock that counts down to the next move. — User:Technical 13 ( C • M • Click to learn how to view this signature as intended ) 23:03, 28 March 2013 (UTC)[reply]

Chess clocks are commonly used in tournaments, but their use does not necessarily imply that there is a restriction on time taken to make a move. Some tournaments do have such rules; but by no means all. At the end of the game, the clock records the aggregate time taken by each player - it does not record the moments when each move is made. --Redrose64 (talk) 23:17, 28 March 2013 (UTC)[reply]

I think he is talking about displaying a clock that shows low long it is until the animation shows the next move. Bubba73 ^{You talkin' to me?} 01:10, 29 March 2013 (UTC)[reply]

Very Strong Support. The supporters above (especially Bubba73) have already summarized almost everything I was going to say. Double sharp (talk) 03:07, 29 March 2013 (UTC)[reply]

Thank you all for your support!! Please continue this conversation on the talk page for the project. — Preceding unsigned comment added by Mattj2 (talk • contribs) 03:25, 29 March 2013 (UTC)[reply]

Title blacklist

Dear Tech guys: I have been having a problem that two more experienced editors could not explain, so they suggested I come here. To see what's been happening, will someone who knows about title blacklists please read the discussion at User talk:Anne Delong#Speedy deletion declined: User:Mohammad sameer hussain/sandbox and explain why I am occasionally having trouble moving pages. Thanks! —Anne Delong (talk) 00:38, 26 March 2013 (UTC)[reply]

Depending on exactly what triggered the filter it was probably the title being in all CAPITAL LETTERS. Werieth (talk) 00:46, 26 March 2013 (UTC)[reply]

Yes. 13 consecutive characters without a lowercase letter. --Carnildo (talk) 03:35, 26 March 2013 (UTC)[reply]

Thanks - I was just moving a page to Articles for creation so that I could review it; next time I'll change the case. I wonder, though, if a more informative message could be used, since "title blacklist" lead to several editors spending their time trying to figure out what was wrong, since it made it seem as though the subject of the article was in bad repute. My guess was that an article of that name had been deleted multiple times. Maybe the message could say "bad title format" or "too many capital letters". —Anne Delong (talk) 14:39, 26 March 2013 (UTC)[reply]

It is vague for a reason see WP:BEANS if you tell the vandals exactly what triggers the filter they can make the filter useless. Werieth (talk) 14:44, 26 March 2013 (UTC)[reply]

Ah, I see that, I think... —Anne Delong (talk) 15:11, 26 March 2013 (UTC)[reply]

I don't think all caps titles are a very good indication of vandalistic intent. Foolish non-vandals could also try creating pages with titles in all caps. Our normal attitude with such good faith efforts is to let them get it wrong, since the nature of wikis means it will eventually be fixed by someone. I agree with Anne's earlier comment that the editor should be told what they've got wrong, so they can correct it. – PartTimeGnome (talk | contribs) 21:18, 26 March 2013 (UTC)[reply]

This is admittedly cynical, but what are the chances that a user who hasn't read enough basic policy to know not to all-cap a title has produced an article that's otherwise suitable? The help desk routinely gets questions from those who have had some sort of technical problem in the creation process, only to find that the articles are unsuitable for inclusion anyway. Good faith or not, it's better if they are "nipped in the bud" than after multiple people spend time on them, isn't it? —[AlanM1(talk)]— 08:03, 28 March 2013 (UTC)[reply]

Easyblock

I use the very useful easyblock script for admins. Initially the "Block" button would show on a contributor's User, Talk, Contribution and Diffs, but now it only appears on Contributions and Diffs. I tried to fix this by adding some extra lines, but no joy. I don't really know what I'm doing, please help! The current script in my commons.js is importScript("User:Animum/easyblock.js"); //User:Animum/easyblock.js ebPrefs = {showOnPages : ["user_usertalk", "contribs", "diffs", "ipblocklist"]};

thanks Jimfbleak - talk to me? 10:01, 26 March 2013 (UTC)[reply]

Wouldn't ebPrefs = {showOnPages : ["user", "talk", "contribs", "diffs", "ipblocklist"]}; make more sense? — User:Technical 13 ( C • M • Click to learn how to view this signature as intended ) 23:36, 28 March 2013 (UTC)[reply]

That seemed the obvious thing to try, didn't make any difference though Jimfbleak - talk to me? 09:48, 31 March 2013 (UTC)[reply]

Strange error in edit mode

I don't know whether this is related to some of the above posts, but suddenly two of the icons from the edit toolbar, namely the New line button and the Table button appear below the bar and inside the edit window. I have no idea what might be causing this, so I am bringing it here. (See screenshot for how it appears in my browser Safari). -- Toshio Yamaguchi 13:53, 26 March 2013 (UTC)[reply]

Well, I still have no idea what caused this, but it seems to be normal again, now. -- Toshio Yamaguchi 22:00, 26 March 2013 (UTC)[reply]

This was probably the CSS issue above. - The Bushranger _{One ping only} 22:39, 26 March 2013 (UTC)[reply]

this intermittent error is caused by local (i.e., enwiki specific) modification to the toolbar content, and by changes to JS modules loading order. it's an old problem that gets "fixed" periodically and then resurfaces again. it happens only if you leave one of the panels (usually "advanced") open. in the past, reproduction was highly browser dependent, i.e., it was very easy to reproduce on some browsers and very difficult to reproduce on others, though it could happen with any browser.

there is an easy workaround: when you encounter this "icon leakage" from the toolbar to the editbox, fold and reopen the tab (again, more often than not it's the "advanced" tab). this is not a solution, just a workaround - someone should probably open a bug in bugzilla, or even better - find the old bug that was closed and reopen it (i won't be surprised at all if there were multiple, duplicate such bugs - this often happens with high visibility issues). peace - קיפודנחש (aka kipod) (talk) 00:47, 28 March 2013 (UTC)[reply]

I'm having the same problem in Chrome and the find/replace button is totally gone. Carlossuarez46 (talk) 17:27, 29 March 2013 (UTC)[reply]

This is not related to the previous reports of the "cssText.indexOf" exception. The WikiEditor icons sticking out of the toolbar is bugzilla:27698 (an old bug that returns from the past - or perhaps wasn't properly fixed to begin with). Krinkle (talk) 04:04, 30 March 2013 (UTC)[reply]

Copyright violation page notice red link

I don't if it is a new one or I never noticed... the link beside common copyright violation notice you get while editing any page is a redlink! --Tito Dutta (contact) 06:21, 27 March 2013 (UTC)[reply]

It's not a red link for me. It leads to WP:CV --Ushau97 ^talk 06:33, 27 March 2013 (UTC)[reply]

Content that violates any copyrights will be deleted. Encyclopedic content must be verifiable. Work submitted to Wikipedia can be edited, used, and redistributed—by anyone—subject to certain terms and conditions.

I see no redlinks there. — User:Technical 13 ( C • M • Click to learn how to view this signature as intended ) 12:06, 27 March 2013 (UTC)[reply]

Titodutta, at Preferences, what is your language setting? --Redrose64 (talk) 14:14, 27 March 2013 (UTC)[reply]

And please quote what the red link says so we know what you are talking about. Is it "Page notice"? As an account creator I think you have that link. It can be used to create a Wikipedia:Editnotice for that page. Most users don't have the link when it's red. Battle of Baxi is an example where the link should be blue, visible to everybody, and lead to Template:Editnotices/Page/Battle of Baxi. PrimeHunter (talk) 01:05, 28 March 2013 (UTC)[reply]

yes, it is because of my recently added AC flag. I did not know it! --Tito Dutta (contact) 14:47, 28 March 2013 (UTC)[reply]

Exposing Wikidata equivalence

On an article which exists only in English (i.e. with no interwikis), such as Ampelocissus asekii, there appears to be no link to the corresponding Wikidata entry, either in the reading or editing views. Can we change that? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:55, 27 March 2013 (UTC)[reply]

Does the wikidata entry exist? Werieth (talk) 19:59, 27 March 2013 (UTC)[reply]

Yes - d:Q8441774 Chris857 (talk) 20:18, 27 March 2013 (UTC)[reply]

If you are talking about an missing "edit links" link for items with only one language link, then that has been done and is only waiting for deployment. See Wikidata weekly summary #50 for details.--Snaevar (talk) 00:52, 28 March 2013 (UTC)[reply]

Thank you. That's a partial solution, I suppose, but I should like to see the Wikidata ID exposed for articles with either one or more languages, perhaps "Edit Wikidata Q8441774" rather than just "Edit links". Or perhaps the final entry after the languages, but before the edit link, could be "Wikidata Q8441774". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:26, 28 March 2013 (UTC)[reply]

You don't need to know the Q number in advance. The universal syntax is [[d:Special:ItemByTitle/enwiki/pagename]], as in d:Special:ItemByTitle/enwiki/Ampelocissus asekii. --Redrose64 (talk) 20:58, 28 March 2013 (UTC)[reply]

Lua error messages not displaying on "preview page with this template"

Tracked in Phabricator
Task T48633

Hello all. I've noticed that when previewing Lua modules using the "preview page with this template" option, if there is a script error, the JavaScript error message doesn't show up when you click the link. To demonstrate this, I have made Module:User:Mr. Stradivarius/previewbug and User:Mr. Stradivarius/Sandbox/Previewbug. If you click on the link in User:Mr. Stradivarius/Sandbox/Previewbug you can see the error message, but if you edit Module:User:Mr. Stradivarius/previewbug and then use "preview page with this template" with User:Mr. Stradivarius/Sandbox/Previewbug, the error message does not appear.

However, this bug does not occur on the test2 wiki - see the equivalent module and sandbox over there. This makes me think that it's not a Scribunto bug, but something local. But I could be wrong. Does anyone know what's causing this, and if so how to fix it? — Mr. Stradivarius ^{♪ talk ♪} 04:16, 28 March 2013 (UTC)[reply]

Just musing aloud here: Alternatively, it could be that it has already been fixed, and the patch has been deployed to test2, but is still awaiting deployment to enwiki. Just a possibility. jcgoble3 (talk) 05:47, 28 March 2013 (UTC)[reply]

Well, ok, you're probably right, and this was probably a stupid question. But how can I go about finding if this is actually the case? I did look through the Scribunto extension page and bugzilla, but I didn't find anything relating to this bug. Was I just looking in the wrong places? — Mr. Stradivarius ^{♪ talk ♪} 06:17, 28 March 2013 (UTC)[reply]

test2 saw its last deployment on March 22, en.wp on March 25, see mw:MediaWiki_1.21/Roadmap. Please feel free to file a new bug report against Scribunto or ask on mw:Talk:Lua_scripting so the developers will see it. Thanks! — Preceding unsigned comment added by AKlapper (WMF) (talk • contribs) 11:22, 28 March 2013 (UTC)[reply]

Thanks for the reply. Maybe it wasn't such a bad question after all. :) I've submitted bugzilla:46633, so we'll see what comes of that. Best — Mr. Stradivarius ^{♪ talk ♪} 11:58, 28 March 2013 (UTC)[reply]

It works for me here on enwiki when I try it. Note that the "link" is actually JavaScript; are you getting any sort of JavaScript error when using the TemplateSandbox that might be preventing the script from running? BJorsch (WMF) (talk) 14:36, 28 March 2013 (UTC)[reply]

Aha, that got it. It's clashing with Wikipedia:Citation expander, one of the gadgets available in preferences. I was getting these errors on using "preview page with this template":

Timestamp: 03/29/2013 12:04:50 AM
Error: TypeError: document.getElementById(...) is null
Source File: https://en.wikipedia.org/w/index.php?title=MediaWiki:Gadget-citations.js&action=raw&ctype=text/javascript&471744142
Line: 36

Timestamp: 03/29/2013 12:04:51 AM
Error: TypeError: $(...).data(...) is undefined
Source File: https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.codeEditor%2CwikiEditor%7Cext.wikiEditor.dialogs%2Ctoolbar%7Cext.wikiEditor.toolbar.hideSig%7Cjquery.codeEditor%2CwikiEditor%7Cjquery.wikiEditor.dialogs%2Ctoolbar%7Cjquery.wikiEditor.dialogs.config%7Cjquery.wikiEditor.toolbar.config%2Ci18n&skin=vector&version=20130328T022227Z&*
Line: 1

After I disabled the gadget in preferences, I stopped getting JavaScript errors, and the Lua script errors started showing up properly.

In fact, the problem isn't limited to the Lua script errors, something I should have realised before. I get the exact same JavaScript errors when I click the edit link on Module:User:Mr. Stradivarius/previewbug even without using "preview page with this template", and it prevents both the module editing/highlight script and the debug console from running. Again, when I disable the citation expander from my preferences, they run with no problems. — Mr. Stradivarius ^{♪ talk ♪} 15:26, 28 March 2013 (UTC)[reply]

I've notified Smith609, the author of the citation expander gadget. — Mr. Stradivarius ^{♪ talk ♪} 15:44, 28 March 2013 (UTC)[reply]

Village pump tab order doesn't match icon order

Does it bother anybody else that the order of the icons on the Wikipedia:Village pump page is

Policy, Technical, Proposals, Idea lab, Miscellaneous

while the order of the tabs after the new design is

Idea lab, Miscellaneous, Policy, Proposals, Technical

I think one should be changed to match. Jason Quinn (talk) 04:42, 28 March 2013 (UTC)[reply]

I hadn't actually even noticed. I think the more intuitive order is "Policy, Technical, Proposals, Idea lab, Miscellaneous" and they should all be set to that. — User:Technical 13 ( C • M • Click to learn how to view this signature as intended ) 11:54, 28 March 2013 (UTC)[reply]

lo:ແມ່ແບບ:ລາຍການອ້າງອິງ

Resolved

lo:Template:ລາຍການອ້າງອິງ

I'm very active at lowp at the moment and cleaning up that small Wikipedia. Does anybody know which template this is? It looks like Reflist, but that isn't it (or is it something like a duplicate?)

I want either to add it to wikidata (to the correct item) or want to transform it to a redirect for the case it is already there. mabdul 09:57, 28 March 2013 (UTC)[reply]

It is an an older version of {{reflist}}. --— Gadget850 (Ed)^talk 10:58, 28 March 2013 (UTC)[reply]

Uhm thanks... I checked the date and chose the nearest version, but that looked somehow different for me. I transformed it to a redirect as reflist is also existent. Thanks. mabdul 14:03, 28 March 2013 (UTC)[reply]

JS code for "Expand Table all the time" stopped working

Hi, I have been using a js code that expands all collapsible tables in talk pages so I can easily see the WikiProjects a page belongs to and their class and importance assessments, avoiding the BannerShell collapse effects. Apparently this code has stopped working. I am using the Vector skin and have the code in the /vector.js subpage, as well as in a /common.js. I use Firefox 19.0.2. but have also tested it with Chrome 25.0.1364.172 and IE8 and it does not work. I have purged cache in all. Here is the code in question (between nowiki tags):

function expandTable()
{
  var autoCollapse = 2;
  var collapseCaption = "hide";
  var expandCaption = "show";
 
  for ( var tableIndex = 1; tableIndex  < 100; tableIndex ++ ) {
 
    var Button = document.getElementById( "collapseButton" + tableIndex );
    var Table = document.getElementById( "collapsibleTable" + tableIndex );
 
    if ( !Table || !Button ) {
        return false;
    }
 
    var Rows = Table.rows;
 
    if ( Button.firstChild.data == expandCaption ) {
        for ( var i = 1; i < Rows.length; i++ ) {
            Rows[i].style.display = Rows[0].style.display;
        }
        Button.firstChild.data = collapseCaption;
    }
  }
}
 
if ( wgPageName.indexOf("Talk\:")>-1 || wgPageName.indexOf("talk\:")>-1 ) {
    addOnloadHook( expandTable );
}

Any update/suggestions? Thank you.

Additional note: up to yesterday or the day before, I used to see ALL banners of a talk page fully expanded, which is what stopped working.Hoverfish Talk 16:02, 28 March 2013 (UTC)Hoverfish Talk 15:56, 28 March 2013 (UTC)[reply]

the code seems a bit complicated for the amount of work it's supposed to do. please try to replace it with:

if ( mw.config.get( 'wgNamespaceNumber' ) % 2 == 1 ) 
$(function() { $( 'span.collapseButton  a:Contains(show)' ).click() } )

peace - קיפודנחש (aka kipod) (talk) 16:55, 28 March 2013 (UTC)[reply]

Hi kipod and thanks for your help. I first erased the previous code, placed this one, shift-reloaded and it was still all the same. But after deleting once more the code, refreshing, entering it anew and refreshing, I got finally the desired effect. Thanks again and peace. Hoverfish Talk 17:44, 28 March 2013 (UTC)[reply]

JavaScript tool request

Can someone write a tool that adds a tab while editing when pressed it prompts for a reason, then includes that reason in {{archive top}} just below the section header and then throws {{archive bottom}} at the end of the text. ?? Thanks. Werieth (talk) 17:10, 28 March 2013 (UTC)[reply]

The easiest way to do this might be to modify one of User:Doug/closetfd.js, User:King of Hearts/closeffd.js, User:King of Hearts/closecfd.js, or User:King of Hearts/closerfd.js. jcgoble3 (talk) 19:49, 28 March 2013 (UTC)[reply]

Probably, but I ended up writing one from scratch. Try User:Writ Keeper/Scripts/autoCloser.js (you might want to keep an eye on it for a bit, though). Writ Keeper (t + c) 20:47, 28 March 2013 (UTC)[reply]

Aerobic exercise

We have received a report at OTRS (that I have confirmed) that this article is not displaying correctly in IE8, but is in Firefox. Anyone else seeing this and if so any idea what the problem might be? (don't say upgrade to IE9, for some of us that is not an option). Thanks.--ukexpat (talk) 17:41, 28 March 2013 (UTC)[reply]

I don't see anything wrong with it using Internet Explorer 7.0.6001.18000, Internet Explorer 9.0.8112.16421, Google Chrome 26.0.1410.43 m, or Firefox 19.0.2. What is wrong with it using IE8? — User:Technical 13 ( C • M • Click to learn how to view this signature as intended ) 18:52, 28 March 2013 (UTC)[reply]

Looks fine in ie8 on my machine (please don't make me use that, often!) under WinXP. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:36, 28 March 2013 (UTC)[reply]

Typical, "no fault found" now just like when I take my car to the dealership. When I saw the fault before it was just a page of random ASCII characters.--ukexpat (talk) 20:58, 28 March 2013 (UTC)[reply]

Wikidata Bug ?

Hello,

I have a questions on this article Cape Esperance. Using Chrome (and Firefox), I can not edit the interwiki links / have access to Wikidata at the bottom of the interwiki links. Is it a known bug ? What can I do ? Thanks in advance. Poppy (talk) 18:25, 28 March 2013 (UTC)[reply]

"Edit links" appeared when I purged the page. PrimeHunter (talk) 18:57, 28 March 2013 (UTC)[reply]

It depends: if there isn't any wikidata item, the edit links button doesn't appear. But I sometimes also have the problem, that the link is not displayed in Opera 12.14... I don't know when it happens, but it drives me somehow sometimes crazy, resulting in empty wikidata items... mabdul 02:06, 30 March 2013 (UTC)[reply]

I'd recommend asking on http://www.wikidata.org/wiki/Wikidata:Contact_the_development_team whether it's a bug and whether to create a request in the bugtracker. --AKlapper (WMF) (talk) 11:46, 2 April 2013 (UTC)[reply]

Changes to Special:UserLogin (signup)

Hey all,

If you visit Special:CreateAccount (or rather, it's redirect destination, Special:UserLogin/signup), you'll notice that it's been reverted back to the original version prior to new interface that the Foundation's experimental features team built and enabled. (Original blog post about the project.)

We removed the experimental version today, in prep for deploying a more permanent version, able to be fully localized and used on all the projects on a permanent basis. For those familar with MediaWiki development: the version here on enwiki for the last few months was built in an extension and relied heavily on JavaScript to transform the interface on the fly. Our new commits are to MediaWiki core, and are a more robust implementation.

The good news is that we're doing this because we expect the upcoming changes to the account creation and login pages to be ready for everyone to try soon, hopefully within the next couple weeks. We are basing our new interface on the version that tested most successfully in terms of the number of signups (more details about that data), with a few other enhancements and changes to the login page to make the design consistent with the new look across desktop and mobile Web.

Keep your eyes peeled for another announcement about when and how to test the next iteration, including login updates. Just as a quick description: you'll be able to try both the new signup and login on an opt-in basis at first, so we can make sure to iron out bugs before making it the default.

Many thanks, and please speak up if you have any questions. Steven Walling (WMF) • talk 22:38, 28 March 2013 (UTC)[reply]

Email article option

I know that there is no consensus for social media links ("share buttons") on Wikipedia, but looking through those proposals, I did not notice anyone suggesting that an "email article" option at least be considered. I personally email links to dozens of Wikipedia articles to many people each month, and I know many others who do so as well, but since there is no option to email a link(s) to someone directly from Wikipedia within the "export" area (where you can export to PDF or view a printable version), obviously you have to do so using some kind of browser plugin or from the email client. Is it realistic for Wikipedia developers to add an "email link to article" option within the export sidebar, or some such option? If this is feasible to implement, then it would greatly streamline sharing articles with others via email without having to rely on special browser plugins that may not be available on mobile devices or other platforms. Laval (talk) 04:13, 29 March 2013 (UTC)[reply]

Hi Laval. I assume you already found the Share pages on Facebook perennial proposal. I did a search for "email article" (no quotes) in the archives of the Village Pump. Here is someone suggesting the same thing back in 2007:

WP:Village_pump_(technical)/Archive_AR#.22Email_this_article.22

You might want to suggest that it be a Gadget that is only usable for users who are logged in, as opposed to something that all users have access to. Have fun! Mattj2 (talk) 04:55, 29 March 2013 (UTC)[reply]

Hello. I am concerned that if we start allowing Facebook or any third party "share buttons" on wiki we will be giving Facebook and Youtube the opportunity to make money every time someone clicks on their logo. We are also allowing Wiki to be associated with these brands. The amount of advertising currently on Youtube in particular is very concerning, and I do not think it aligns with Wiki values. If wiki designed it's own "share" option, it could provide on request a unique wiki url address which could be hyperlinked from any external source and direct the person to the exact same place the link was generated from. Imagine instead of a Twitter "button" there was a non commercial, secure, permanent URL provided. I think we take it for granted at the moment that we can still see url codes in google. I recently updated my OSx Lion and the address bar has been replaced with a single google search bar which will only display the main part of the address in black while the extended URL link is in GREY, they are fading it out!Katherine Herrington (talk) 16:06, 29 March 2013 (UTC)[reply]

There is already a "non commercial, secure, permanent URL" for every article. Just send them the URL to the article. Unless the article is moved or deleted, that will work just fine. It's really not much more work to copy the URL from the address bar, go to whichever social media site you want to go to, and then post the URL there. ···日本穣^? · 投稿 · Talk to Nihonjoe · Join WP Japan! 16:16, 29 March 2013 (UTC)[reply]

Claim an iPad2 popup

Maybe Norton has let some malware slip by, but at Talk:David Chalmers when I hover over the 'Wikipedia' link in "Wikipedia, the free encyclopedia" (the line just after Talk:David Chalmers. It also happened on the page that comes up after you block someone. Dougweller (talk) 14:22, 29 March 2013 (UTC)[reply]

Norton let some malware slip by. --Golbez (talk) 14:35, 29 March 2013 (UTC)[reply]

Odd malware then as I no longer have the problem on that page. Possible of course. Dougweller (talk) 15:23, 29 March 2013 (UTC)[reply]

Not malware, some weird Firefox addons. Gone now. Dougweller (talk) 19:33, 29 March 2013 (UTC)[reply]

If the Firefox add-ons mysteriously appeared on your computer, possibly through a browser exploit, I would consider them to be malware. PleaseStand (talk) 03:29, 30 March 2013 (UTC)[reply]

Wikidata phase 2 is coming soon

Hi :)

2 days ago the first 11 Wikipedias got the ability to include data from Wikidata in their articles. These are the Italian, Hebrew, Hungarian, Russian, Turkish, Ukrainian, Uzbek, Croatian, Bosnian, Serbian and Serbo-Croatian Wikipedias. This means they are now able to make use of the structured data that is available on Wikidata. It includes things like conservation status for a species, ISBN for a book or the top level domain of a country.

The next step is to roll out phase 2 of Wikidata on English Wikipedia. We are currently planning this for Wednesday next week (April 3). We are currently carefully monitoring performance on the first 11 Wikipedias to make sure everything is ok. If problems arise we might have to postpone the deployment a bit longer but I wanted to give you a heads-up that this is the current plan.

We have prepared an FAQ for this deployment and are looking forward to your testing and feedback. You can already test it on test2.

And some more details about how this will work: There are two ways to access the data:

Use a parser function like {{#property:p169}} in the wiki text of the article on Yahoo!. This will return “Marissa Mayer” as she is the chief executive officer of the company.
For more complicated things you can use Lua. The documentation for this is here.

We are working on expanding the parser function so you can for example use {{#property:chief executive officer}} instead of {{#property:p169}}. The complete plan for this is here.

Thank you so much for helping us bring Wikidata to all Wikipedias!

Cheers Lydia Pintscher (WMDE) (talk) 14:45, 29 March 2013 (UTC)[reply]

Hey Lydia. I was going to email you and Denny about this, but I figure here is as good a place as any to ask, since some community members might be wondering the same thing. To be clear: this is a pretty broad question, not one that I think should hold up enabling Phase II.

When it comes to implementing use of Wikidata properties in infoboxes and the current state of the syntax, what is the actual, step-by-step workflow for updating content? I see description of the syntax linked from the FAQ, but not a clear description of the steps involved in editing something should we implement properties in infoboxes or directly in articles willy-nilly. I am of course looking at this through the eyes of my own editing as an admin on enwiki, and with my editor engagement hat on. This is my understanding: Previously, if an editor wanted to update an infobox, all they'd need to do is click Edit and change the value. For new editors, the hurdle was scary infobox wikitext, but in theory you could figure out the relationship between the markup, values, and what the article looked like. Now, when you click edit, you can't actually change the content in a wiki page by clicking edit here, you have to know to go to Wikidata and update the property.

That workflow is extremely problematic from a user experience design perspective, because it adds a number of potentially annoying and complicated steps to do what once a two-step "edit-save". There seems to be zero indicator of how to do so that is obvious too, which is bound to confuse even experienced editors until everybody across the wikis learns the new system.

How are we going to solve this problem? I don't think asking all editors to head over to a completely different wiki to update infobox values is okay at all, because it forces end users to conform to the needs of the Wikidata software architecture, rather than using software to help us keep the content up to date. The main solution I am thinking is that we allow local updating of Wikidata values which the software then pulls back in to the main revision history on wikidata.org. This would be best accomplished with VisualEditor of course, so it's probably not going to happen immediately. However, I'd really like us to consider how we can reduce user confusion and introducing multiple new steps in to the workflow of updating infobox content. Steven Walling (WMF) • talk 18:29, 29 March 2013 (UTC)[reply]

My take: Ideally we should work towards an inline invocation of Wikidata editing for properties. Til then, "edit" links in infoboxes that point straight to wikidata.org may be an acceptable solution. Property invocations in the article namespace should probably be avoided completely and perhaps made impossible. On the plus side, having parameter-less templates will make wikitext less cluttered.

Cf. an example of a parameter-less template invocation.--Eloquence * 18:50, 29 March 2013 (UTC)[reply]

Inline edit links to Wikidata (ala the interwiki links implementation) is definitely a good interim solution, since it is an obvious pointer to where the content is coming from. That is a good point about templates without huge parameters, and it's actually quite likely to reduce headaches for first time editors around seeing massive amounts of infobox markup at the head of articles. Steven Walling (WMF) • talk 18:54, 29 March 2013 (UTC)[reply]

Eloquence, in your example, for property with multiple value ("It's named after ... Linus Torvalds, Unix, Linux kernel"), they are not linkable (Linus Torvalds, Unix, Linux kernel. Has anyone raised this issue before? Bennylin (talk) 14:45, 1 April 2013 (UTC)[reply]

This will be done. I've filed it as bugzilla:46788 so we don't forget. --Lydia Pintscher (WMDE) (talk) 14:29, 2 April 2013 (UTC)[reply]

(ec) One quick-and-dirty solution would be a discreet [edit] link in the top of the infoboxes similar to the (V D E) links which currently exist for a lot of navigational templates; rather that take you to the template page, however, it would send you to Wikidata.

That aside, remember that this depends on how the infobox is set up; there won't be any changes to enwiki infoboxes until someone actually codes the explicit use of wikidata into them. (It's not like the interwiki links, which effectively superseded existing content). As such, we can't really write guidance until we have some functioning examples to explain how it'll work - wikidata can't dictate that behaviour centrally. Andrew Gray (talk) 19:00, 29 March 2013 (UTC)[reply]

One thing for sure: integrating Wikidata to infoboxes will change the dynamic of revision diff. For example let say Yahoo's infobox is automated as of today, and a couple years from now (2020) it's CEO has changed, but looking back at today's revision, you won't find Marissa Mayer as it's past (2013) CEO, instead you'll find 2020's CEO in 2013 text.. Automated infoboxes, while it surely has its advantages, loses it's ability to be checked at exactly what diff the change occur (Wikiblame came to mind). And, as a consequence, automated infoboxes would rely on other website (Wikidata) to be vandal-free, or at least have the critical mass to revert problematic edits which could affect hundreds of projects.. Bennylin (talk) 20:19, 29 March 2013 (UTC)[reply]

We already have this problem to some degree with templates, of course! Andrew Gray (talk) 21:35, 29 March 2013 (UTC)[reply]

With template,s the diff could still be checked on the corresponding transcluded template's history, which is located on the same site (and listed on the bottom of the edit page). Having said that, it would be great to have list of property used in an article on the bottom of edit page. Bennylin (talk) 03:33, 30 March 2013 (UTC)[reply]

Isn't there the same issue with Commons as well? Alterations to the file or even deletions could easily happen without a corresponding change to the revision history locally. They just don't happen often because files are less prone to mutability than text. Steven Walling (WMF) • talk 22:50, 31 March 2013 (UTC)[reply]

Yes, and that is recognized as enough of a problem that the {{keep local}} template exists. Regards, Orange Suede Sofa (talk) 22:57, 31 March 2013 (UTC)[reply]

No. No matter you view the page locally or in Commons, they all have their file history on the image information screen. It's working great already. See if Wikidata can do the same thing, for example, for every "data"/"property" provided by Wikidata using parserfunction, one can click a different colored link (like, black?) which ideally go to a page complete with the revision history on the page itself, akin to image namespace. Bennylin (talk) 14:42, 1 April 2013 (UTC)[reply]

Update: We encountered some small issues that we'll have to sort out. Deployment will probably not happen on Wednesday as initially planned but hopefully soon after. I'll keep you posted. --Lydia Pintscher (WMDE) (talk) 20:16, 29 March 2013 (UTC)[reply]

I would hope that the wiki page history would reflect changes to both the wiki page and any data which it fetches. Perhaps at the same time, the similar issue with template changes not being reflected in wiki page histories could be handled. There is also the related issue of source citation, the elements of which probably need to be properties of the data (covering multiple data items), which could then be pulled into the wiki page cites. —[AlanM1(talk)]— 23:13, 29 March 2013 (UTC)[reply]

I have a request for anyone involved in updating infobox templates: do not make the templates completely parameterless, but instead allow optional parameters to override data from Wikidata. It's going to take time for the data we have in infoboxes to be added to Wikidata, so we still need to use the data in wiki pages. As with the interwiki links, there will probably be some situations where we need to override data from Wikidata. Also, since Wikidata is not so easily edited as Wikipedia (both in terms of usability and technical requirements), editing the page on Wikipedia is the only way some editors can change infobox content. (Ideally, a bot could pick up such edits and transfer them to Wikidata. The infobox should still display local overrides while waiting for the bot to transfer them to Wikidata.) – PartTimeGnome (talk | contribs) 22:32, 30 March 2013 (UTC)[reply]

As just an editor: having stuff like {{#property:p169}} is as un-wiki as it can be - (wiki as in "everyone can edit", without much trouble) It should definitely be only a short temporary use, probably betrer not to be used at all (if if it short and temporary let'«s skip such a incredibly nasty looking thing). Something like {{#property:chief executive officer}} is still hardly easy to understand to the non-programmer mind (I presume, I have a programmer mind, I think it is easy :-), but the gains may outweight that. But please don't go to "The president of {{#property:p123}} is {{#property:p456}}, since {{#property:p789}}", not even "The president of {{#property:company-short-name}} is {{#property:president}}, since {{#property:term-begin}}". - Nabla (talk) 23:18, 31 March 2013 (UTC)[reply]

Replag

Replag seems to be going up in real time about 17 1/2 hours and counting. Any idea what's causing this?--Gilderien Chat|List of good deeds 16:51, 29 March 2013 (UTC)[reply]

Not an official answer, but based on the reports from Ops regarding two brief outages yesterday, the culprit is mostly likely Wikidata's impact on the job queue (i.e. refreshing interwiki links). It's not really the fault of Wikidata per se, but rather that the job queue needs to be rebuilt to scale better than the current system. Steven Walling (WMF) • talk 18:49, 29 March 2013 (UTC)[reply]

Are such reports public somewhere? Dragons flight (talk) 21:03, 29 March 2013 (UTC)[reply]

This wasn't a report per se, I just meant that Ops reported it. In this case, the message was forwarded to the Wikidata public mailing list. Steven Walling (WMF) • talk 00:14, 30 March 2013 (UTC)[reply]

Link. Legoktm (talk) 02:01, 30 March 2013 (UTC)[reply]

You might want to mention to someone at Ops that the first outage occurred a couple minutes after I made this edit to Module:Citation/CS1. That module, a core part of the citation system, had about 1 million uses at the time, so editing it leads to 1 million pages being queued for rebuilding. I can't help wondering if that was the straw that broke the jobqueue's back, either instead of or in addition to heavy load from Wikidata. I actually recall seeing error messages shortly after making the edit, so I remembered it. I've made edits to that page and other pages that are very heavily transcluded on many occasions, and they aren't usually associated with all of Wikipedia locking up, so my guess would be that it was a combination of factors that pushed things too far that specific time. Dragons flight (talk) 01:33, 30 March 2013 (UTC)[reply]

Apply hAudio microformat to Template:Audio

Please comment on the proposal at Template talk:Audio#Apply hAudio microformat. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:59, 29 March 2013 (UTC)[reply]

Just out of curiosity

It seems to have gone now, but yesterday I had a load of 'nanny says' type info coming up when performing admin actions (i.e. deletions and blocks). There was so much, I had to scroll down to get to the blocking bit. What was it there for, and why's it gone again? (Note I am not begging for its return - just being nosy...) Peridon (talk) 20:58, 29 March 2013 (UTC)[reply]

If you want them back, set your interface language to "en". Not British English, not Canadian English. All of the "nanny says" kind of stuff only shows up in the plain English version of the site. There was a problem with selecting overrides of the user interface based on language settings. For a while, I was getting volumes of English on every action I took even though I keep my user interface set to Dutch. That change got undone because it really irritated the foreign language users. I think someone should undertake the effort to realign all the English interfaces, though.

The history can be found at https://bugzilla.wikimedia.org/show_bug.cgi?id=46579 and WP:Village pump (technical)#Language preferences getting mishandled—Kww(talk) 23:54, 30 March 2013 (UTC)[reply]

Thanks. For anyone technical reading this, I hadn't changed my preferences (Brit English), and there's a bit more discussion at AN, 'Repost from VP (Tech)' thread. Peridon (talk) 00:07, 31 March 2013 (UTC)[reply]

File upload bot's uploads aren't registering in the log history

See https://commons.wikimedia.org/w/api.php?action=query&list=recentchanges&rcprop=title%7Cloginfo%7Ctimestamp&rcnamespace=6&rclimit=200&rctype=log

Why aren't uploads by commons:User:File Upload Bot (Magnus Manske) showing up in this log? Is this new or has it been this way for a while? It is totally messing up my bot. Magog the Ogre (t • c) 22:56, 29 March 2013 (UTC)[reply]

Hi. Hmmm. At commons:Special:Contributions/File Upload Bot (Magnus Manske), I currently see...

21:25, 29 March 2013 (diff | hist) . . (+510)‎ . . N File:Spruce Creek, Pennsylvania (7070387667).jpg ‎ (Transferred from Flickr by User:GrapedApe) (top)
21:25, 29 March 2013 (diff | hist) . . (+510)‎ . . N File:Spruce Creek, Pennsylvania (6924307424).jpg ‎ (Transferred from Flickr by User:GrapedApe) (top)
21:25, 29 March 2013 (diff | hist) . . (+510)‎ . . N File:Spruce Creek, Pennsylvania (6924307270).jpg ‎ (Transferred from Flickr by User:GrapedApe) (top)
21:24, 29 March 2013 (diff | hist) . . (+510)‎ . . N File:Spruce Creek, Pennsylvania (7070386259).jpg ‎ (Transferred from Flickr by User:GrapedApe) (top)
21:24, 29 March 2013 (diff | hist) . . (+510)‎ . . N File:Spruce Creek, Pennsylvania (6924307088).jpg ‎ (Transferred from Flickr by User:GrapedApe) (top)
21:24, 29 March 2013 (diff | hist) . . (+510)‎ . . N File:Spruce Creek, Pennsylvania (6924306760).jpg ‎ (Transferred from Flickr by User:GrapedApe) (top)
21:24, 29 March 2013 (diff | hist) . . (+510)‎ . . N File:Spruce Creek, Pennsylvania (6924306646).jpg ‎ (Transferred from Flickr by User:GrapedApe) (top)
21:24, 29 March 2013 (diff | hist) . . (+510)‎ . . N File:Spruce Creek, Pennsylvania (6924306472).jpg ‎ (Transferred from Flickr by User:GrapedApe) (top)

At your API link, I currently see...

      <rc type="log" ns="6" title="File:Spruce Creek, Pennsylvania (7070387667).jpg" timestamp="2013-03-30T02:25:07Z" logid="59314832" logtype="upload" logaction="upload" />
      <rc type="log" ns="6" title="File:Spruce Creek, Pennsylvania (6924307424).jpg" timestamp="2013-03-30T02:25:07Z" logid="59314829" logtype="upload" logaction="upload" />
      <rc type="log" ns="6" title="File:Spruce Creek, Pennsylvania (6924307270).jpg" timestamp="2013-03-30T02:25:00Z" logid="59314802" logtype="upload" logaction="upload" />
      <rc type="log" ns="6" title="File:Spruce Creek, Pennsylvania (6924306646).jpg" timestamp="2013-03-30T02:24:59Z" logid="59314793" logtype="upload" logaction="upload" />
      <rc type="log" ns="6" title="File:Spruce Creek, Pennsylvania (7070386259).jpg" timestamp="2013-03-30T02:24:59Z" logid="59314791" logtype="upload" logaction="upload" />
      <rc type="log" ns="6" title="File:Spruce Creek, Pennsylvania (6924307088).jpg" timestamp="2013-03-30T02:24:59Z" logid="59314792" logtype="upload" logaction="upload" />
      <rc type="log" ns="6" title="File:Spruce Creek, Pennsylvania (6924306760).jpg" timestamp="2013-03-30T02:24:59Z" logid="59314790" logtype="upload" logaction="upload" />
      <rc type="log" ns="6" title="File:Spruce Creek, Pennsylvania (6924306472).jpg" timestamp="2013-03-30T02:24:59Z" logid="59314789" logtype="upload" logaction="upload" />

It looks like everything is getting logged, but some of the uploads have the exact same timestamp, so the order of the results isn't exactly the same. Is this what you mean? --MZMcBride (talk) 02:42, 30 March 2013 (UTC)[reply]

I've spotted the error; in the querycontinue variable in the API, there is subvariable recentchanges, but there is no longer the rcstart subvariable. Magog the Ogre (t • c) 17:55, 30 March 2013 (UTC)[reply]

Search term wildcard

I tried to use the asterisk (*) as a wildcard on the Special:PrefixIndex page and it didn't work. I was looking specifically for pages that were prefixed "C*:". If the asterisk had worked there would have been listings like "C:xxxxx", "CAT:xxxxx" and so forth, but the page was empty. Evidently the asterisk is not seen by the software as a search term wildcard, and I wonder if there is another symbol that is recognized as a wildcard? – PAINE ELLSWORTH ^CLIMAX! 04:37, 30 March 2013 (UTC)[reply]

I'm not sure that it works on namespaces, read somewhere it only works on page names. — User:Technical 13 ( C • M • Click to learn how to view this signature as intended ) 05:34, 30 March 2013 (UTC)[reply]

Neither C: nor CAT: are namespaces. Rather, they are pseudo-namespaces. As far as MediaWiki is concerned, pages with those prefixes are in main article space and the C: or CAT: is just part of their title. – PartTimeGnome (talk | contribs) 22:06, 30 March 2013 (UTC)[reply]

No, there is no wildcard for Special:PrefixIndex. Anomie ⚔ 12:11, 30 March 2013 (UTC)[reply]

Oh d a r n. Had to give it a shot. Thank you both very much! – PAINE ELLSWORTH ^CLIMAX! 19:58, 30 March 2013 (UTC)[reply]

you can't use "prefix search", but you can still use the search: in the special search screen (i.e., the page that opens when you press the little magnifying glass icon in the search box) you can press "advanced", and select exactly the namespaces you want to search. then you can use "intitle:XXXX", to look only for articles where this string appears as part of their title. this may not be as precise as "prefix", but it's much closer than nothing at all (you can look for more advanced search options in the help page linked from "advanced search")... peace - קיפודנחש (aka kipod) (talk) 22:31, 30 March 2013 (UTC)[reply]

Are there instructions somewhere on how to format my signature?

Nothing seems to work, including copying others. I've asked around and no one says anything more than go to Preferences and change it. Well, I've been trying for the last two hours, and even copying others doesn't work. Isn't there a page of instructions or something? (I wouldn't bother you folks here with this, but I'm really frustrated and there doesn't seem to be help anywhere. I asked on IRC but no help there.) Thanks, [[User talk:Star767|Star767]] (talk) 05:29, 30 March 2013 (UTC)[reply]

most of the information can be found on WP:SIG. What are you trying to make it look like? — User:Technical 13 ( C • M • View signature as intended) 05:43, 30 March 2013 (UTC)[reply]

Try checking (☑) Treat the above as wiki markup in Preferences and see if that helps. If you want hands-on help, feel free to contact me on my talk page. The Anonymouse (talk | contribs) 05:45, 30 March 2013 (UTC)[reply]

I did all that. Over and over again. But you can see the results! I'm trying to get my signature to go to my talk page and skip my user page, because I just have a few notes for myself on it. [[User talk:Star767|Star767]] (talk) —Preceding undated comment added 05:51, 30 March 2013 (UTC)[reply]

So, what you want is [[User_talk:Star767|Star767]]. Before you say it, since that pipe character (|) is inside a wikilink, it is required to be just a regular pipe character. — User:Technical 13 ( C • M • View signature as intended) 05:57, 30 March 2013 (UTC)[reply]

Thanks! I'll use that. (I tried with the normal pipe first, but that didn't work, so that's why I added the (|) - since that's the only tip in preferences.) [[User talk:Star767|Star767]] (talk) 06:10, 30 March 2013 (UTC)[reply]

(edit conflict) Or Star767 ([[User talk:Star767|talk]]) – looks like this: Star767 (talk). The Anonymouse (talk | contribs) 06:12, 30 March 2013 (UTC)[reply]

(edit conflict) Well, I guess I don't add the nowiki? <nowiki>[[User_talk:Star767|Star767]]</nowiki> (talk) 06:14, 30 March 2013 (UTC)[reply]

Just kill the nowiki and you'll be fine. —Theopolisme (talk) 06:16, 30 March 2013 (UTC)[reply]

<span class="ShoeSig">— [[User:Technical 13]]   ( [[Special:Contributions/Technical_13|C]] • [[User_talk:Technical_13|M]] • [[User:Technical_13/Sig|Click to learn how to view this signature as intended ]])</span> is the exact raw text code for my signature. Feel free to take what you want from that. Just copy what I gave you from the content section, not from the edit input box. — User:Technical 13 ( C • M • View signature as intended) 06:18, 30 March 2013 (UTC)[reply]

(edit conflict) ok Star767 06:20, 30 March 2013 (UTC)[reply]

Looking good! — User:Technical 13 ( C • M • View signature as intended) 06:22, 30 March 2013 (UTC)[reply]

(edit conflict) Sorry, I'm so tired from working on this for hours. Thanks for the tips. I'll try them tomorrow. Meanwhile, this works! Star767 06:25, 30 March 2013 (UTC)[reply]

Import a Wordperfect document containing footnotes?

Over at this Help desk thread, a new user has prepared a long article in WordPerfect X6 using Wordperfect footnotes for referencing. Can anyone think of a way to get the text and its footnotes into Wikipedia? -- John of Reading (talk) 18:36, 30 March 2013 (UTC)[reply]

Announcing new Module: Charts

After some discussions in Wikipedia:Lua requests, i developed a module that can display bar-charts from user input. There are several options, such as stacking the bars on top of each other or showing them side by side, using different scales for different groups in one chart, and a little more. see Module:Chart for partial documentation and some examples.

{{ #invoke:Chart | bar-chart
| group 1 = 40 : 50 : 60 : 20
| group 2 = 20 : 60 : 12 : 44
| group 3 = 55 : 14 : 33 : 5
| colors = green : yellow : orange
| group names = Apple : Banana : Orange
| x legends = Before : During : After : Post mortem
}}

10

20

30

40

50

60

Before

During

After

Post mortem

Apple
Banana
Orange

comments and bug reports expected on Module talk:Chart. peace - קיפודנחש (aka kipod) (talk) 21:18, 30 March 2013 (UTC)[reply]

Very cool. Thanks kipod. Is there something similar to {{Line chart}} in a Lua module? 64.40.54.208 (talk) 01:37, 31 March 2013 (UTC)[reply]

Overall, very nice. I think the legend is a little awkward, though. Maybe better to have simple text labels adjacent to colored boxes rather than inside them. Dragons flight (talk) 03:05, 31 March 2013 (UTC)[reply]

you are correct, of course. this is how i did it to begin with. don't know why it did not work at first shot, and instead of fixing the problem i found a way around it. i think it's better now. one of the problems is that i can't write a decent unit-test. there may also be a better solution for the Y-scale units (see example in Module:Chart). maybe use border instead of background or something. problem is, some light colors may be OK for the bars, but not good enough for text, like yellow, so we can't use it for the text itself. peace - קיפודנחש (aka kipod) (talk) 04:36, 31 March 2013 (UTC)[reply]

oh, and about {{line chart}}: no way i can touch this thing. my sincere admiration to the people who managed to do this by perverting the timeline extension, but i feel that if i state at this convoluted code for two more minutes i might go blind. the only way i can think of ATM for creating line chart is by using something called "transform", which is semi standard. the problem is that i am not sure all browses support it, and i am not sure that the ones that do, behave exactly the same. the problem is not writing the Lua code, the difficulty is that this requires some deep html magic - prolly more than i posses at the moment... maybe what we should do is to lobby the developers to create a decent chart extension. then we can have not only bar and line charts but also pie charts, and more goodies. peace - קיפודנחש (aka kipod) (talk) 04:55, 31 March 2013 (UTC)[reply]

{{line chart}} is well beyond my my ability, but thanks for taking a look. BTW, I've added Module:Chart to WP:Graphs and charts. Cheers. 64.40.54.208 (talk) 06:35, 31 March 2013 (UTC)[reply]

Which edit counter

Ok back in 2009 I created User:Nthep/Editcounter obviously in connection with an edit counter but for the life of me I can't remember which one. Does anyone know which and is it still functioning? I know it's not tparis's as that relies on User:Nthep/EditCounterOptIn.js. Thanks. NtheP (talk) 22:40, 30 March 2013 (UTC)[reply]

See User talk:X!/Archives/6/2010#OptIn. The links there to Interiot's tool don't work - "Account expired". -- John of Reading (talk) 07:21, 31 March 2013 (UTC)[reply]

References

In an article i use note references but i also have a real reference i wish to use to back up the note, Is there anyway to add a reference to the note and if not whats the best way to ref a note?Blethering Scot 00:13, 31 March 2013 (UTC)[reply]

If I understand correctly, Help:Footnotes#Embedding references within footnotes is what you are looking for. If that's not it, please provide the article you're working on and I can give you better answer. Cheers. 64.40.54.208 (talk) 06:55, 31 March 2013 (UTC)[reply]

Navboxes and edit tools broken

Just how soon will all the navboxes on Wikipedia be fixed? While we're at it, when will be get the tools at the top of the pages back? -------User:DanTD (talk) 00:22, 31 March 2013 (UTC)[reply]

They're all working fine here... - The Bushranger _{One ping only} 00:31, 31 March 2013 (UTC)[reply]

Not really. The navboxes haven't been collapsible for the past several days, and there's no edit tools above my page. I used to be able to click on an icon for my signature, or bold or italic type, or images, etcetera, and that tool bar is gone. -------User:DanTD (talk) 15:18, 31 March 2013 (UTC)[reply]

I'll bet you inadvertently disabled javascript on your browser.קיפודנחש (aka kipod) (talk) 15:48, 31 March 2013 (UTC)[reply]

What kipod said. To check, click on this link; if it says "NO", then you've disabled JavaScript accidentally. jcgoble3 (talk) 18:26, 31 March 2013 (UTC)[reply]

Nope. It said "Yes." There were other complaints about this earlier this week, but I can't find them. -------User:DanTD (talk) 22:39, 31 March 2013 (UTC)[reply]

Sounds like you have something stuck in your browser cache. —TheDJ (talk • contribs) 08:43, 2 April 2013 (UTC)[reply]

Incorrect interwiki

In articles which I've written in Polish and English Wikipedia happened something wrong with the interwikis. It has something to do with recent activity of Addbot, I suppose. I mean the series of articles about Vetulani family - interwiki redirects not to the article about particular person in Wikipedia in different language, but to the template with whole family tree (for example interwikis in article Adam Vetulani - Adam Vetulani). I have no idea how to fix it. Can someone help? Francesco 13 (talk) 09:30, 31 March 2013 (UTC)[reply]

Templates must have interwiki links inside <noinclude>...</noinclude> to prevent the interwiki link from also applying to pages transcluding the template. Fixed in [1] and [2]. PrimeHunter (talk) 12:24, 31 March 2013 (UTC)[reply]

Thank you very much! Francesco 13 (talk) 15:28, 31 March 2013 (UTC)[reply]

Link to copy page content to clipboard?

I don't even know if this is the right place to ask about this, but it seems more appropriate than any other place I can find. What I'm trying to do is see if there's a way to copy a page's contents to the clipboard - so you can paste in a page you're editing - by clicking a link on another page. Is this something that can even be done with the current wikimedia software? ~~Should I put in a Lua request?~~ Is this just not technically feasible at all for security reasons? I would like to implement it as a template for use on template/module documentation pages to help editors transclue them with the right parameters, eg infoboxes. Any pointers or thoughts would be appreciated. Van Isaac_{WS Vex}^contribs 14:04, 31 March 2013 (UTC)[reply]

Copying content to the clipboard can only be done via JavaScript; lua (as a server-side script) has no access to local clipboards. — Edokter (talk) — 14:55, 31 March 2013 (UTC)[reply]

Well, that's good to know; struck that option. Is JavaScript even allowed on Wikipedia pages? Van Isaac_{WS Vex}^contribs 15:18, 31 March 2013 (UTC)[reply]

JavaScript cannot be used directly in wiki pages. What you can do is write scripts that are loaded on every page you view that modify the loaded page if it contains certain content (e.g. it could add a copy link where it finds <span class="van-copy-link"></span> in the page). You can place JavaScript that only affects yourself in Special:MyPage/common.js. To write a script for other users to use, create a subpage in your userspace with a name that ends .js. Other users can load the script by adding something like importScript( 'User:Yourname/yourscript.js' ); to their own common.js file. See Wikipedia:WikiProject User scripts/Guide for more information about user scripts.

Administrators can write scripts that other users can use without needing them to muck around in their common.js file. Admins can create gadgets, which registered users can turn on and off in Preferences. Admins can also edit MediaWiki:common.js to make changes that affect everyone without any option to turn them off (without turning off JavaScript altogether, that is). – PartTimeGnome (talk | contribs) 16:05, 31 March 2013 (UTC)[reply]

So I could actually do this completely within my own user space without any special permissions, just make my own JS script, and import it to my common.js, and only once it works would it get included in global files so it works for everyone? Van Isaac_{WS Vex}^contribs 16:39, 31 March 2013 (UTC)[reply]

Yes. I think a lot of gadgets start life as a user script. Once other people have had a chance to test it and find that they like it, you can propose that it be added as a gadget at Wikipedia:Gadget/proposals. – PartTimeGnome (talk | contribs) 16:54, 31 March 2013 (UTC)[reply]

Well, that pretty much answers that. Thanks for all your help. Van Isaac_{WS Vex}^contribs 17:16, 31 March 2013 (UTC)[reply]

The way I do it is click to edit the page and then click anywhere in the edit box. Then press CTRL+A then CTRL+C. This copies the content of the page to the clipboard. Then I go to the new page, put the cursor where I want to add the content and press CTRL+V. — User:Technical 13 ( C • M • Click to learn how to view this signature as intended ) 21:21, 31 March 2013 (UTC)[reply]

Yeah, I'm looking for a bit more functionality than that, so even though it started out as an idea about copying code I store on test pages in my user space, I'm trying to make an interface for editors to copy template parameters from /doc pages. Something along the lines of "Click here to copy the basic infobox code to your clipboard, here for extra code X, here for extra code Y, or here for extra code Z." Van Isaac_{WS Vex}^contribs 01:48, 1 April 2013 (UTC)[reply]

We do have preloads for page creation and input box. They are limited in functionality, but often enough. —TheDJ (talk • contribs) 08:31, 2 April 2013 (UTC)[reply]

Bulleted lists and the signpost subscription template

I noticed that the multi-level bulleted list on my talk page we're displaying correctly, level 2 was inline with level 1 (see below, the second "L2. Bulleted list item 2 asterisks" line is not indented, but directly under the L1 line). It seems to have something to do with the signpost subscription template. See below, after the signpost, the two asterisks indentation isn't done, but it is OK before the template.

L1. Bulleted list item 1 asterisk
- L2. Bulleted list item 2 asterisks
  - L3. Bulleted list item 3 asterisks

L2. Bulleted list item 1 colon, 1 asterisk

L3. Bulleted list item 2 colons, 1 asterisk

- L3. Bulleted list item 1 colon, 2 asterisks

Num list
1. Num list level 2

L1. Bulleted list item 1 asterisk
- L2. Bulleted list item 2 asterisks
  - L3. Bulleted list item 3 asterisks

L2. Bulleted list item 1 colon, 1 asterisk

L3. Bulleted list item 2 colons, 1 asterisk

- L3. Bulleted list item 1 colon, 2 asterisks

Num list
1. Num list level 2

The :* method seems to work OK. No problems with # either. Is there something "wrong" with the template? As a side question, is ** or :* the preferred/recommended way of having an indented bulleted list? The-Pope (talk) 17:38, 31 March 2013 (UTC)[reply]

It displays fine for me in regular viewing and breaks only on edit-preview. I don't know what could be wrong. jcgoble3 (talk) 18:40, 31 March 2013 (UTC)[reply]

I've noticed that any template that uses the MediaWiki's method of short handing Unordered Lists using the MWML shorthand confuses the parser. It has something to do with the wikicore I think... I've been meaning to put in a ticket if one doesn't already exist. I guess I'll make sure to do that tomorrow (I have the same problem with {{Tbullet}}) As far as the sign-post goes, you could probably change the template to use the HTML tags for the bulleted list and prevent the problem spawning from that template (<ul><li>Item content</li><li>Item content</li><li>....</li></ul>) To answer your other question, if you want the bullet indented all by itself without being nested in another list, than you use :*. ::Examples:

List
- Nested list

- Not nested **

Not nested but properly indented :*

— User:Technical 13 ( C • M • Click to learn how to view this signature as intended ) 21:17, 31 March 2013 (UTC)[reply]

This is the issue explained in detail at Template talk:Shortcut#Changing wiki-markup to pure HTML in lists. The proper fix is to correct the wikitext in the template to not result in tag soup. Not that it shouldn't be done, but be aware that filing a bug isn't likely to help. Changing the behavior of wikitext lists would require some fairly drastic parser changes that few are able to do and likely none are willing.

Regarding the "double bullet" effect: Any subitem should begin with the same sequence of characters as its parent item. This is more clear when using numbered lists rather than bulleted:

	Wikitext	Rendering	Wikitext	Rendering
Correct:	* Number 1 Subitem with "" * Number 2	Number 1 Subitem with "**" Number 2	# Number 1 #* Subitem with "#*" # Number 2	Number 1 Subitem with "#*" Number 2
Incorrect:	* Number 1 :* Subitem with ":" Number 1 again?!	Number 1 Subitem with ":*" Number 1 again?!	# Number 1 ::* Subitem with "::" # Number 1 again?! (Note the above uses two colons because the indent for "#" is twice that of "" or ":")	Number 1 Subitem with "::*" Number 1 again?!

Using differing "prefixes" causes separate lists to be generated, as can be seen by the resetting of the numbering. Those multiple separate lists are also what causes the "double bullet" effect. Also, I am told, the multiple separate lists can be annoying to screenreader users even when the visible page appears fine. I'm not sure what tangent User:Technical 13 is going off on above. Anomie ⚔ 02:50, 1 April 2013 (UTC)[reply]

Re: Screen readers, see this section of the accessibility guideline. Graham87 07:37, 1 April 2013 (UTC)[reply]

Want to block myself from going on Wikipedia forever due to addiction to it, tried Wikibreak Enforcer, it isn't working

I set a ridiculously long Wikibreak of 100 years in the Wikibreak Enforcer to make sure I can quit my current addictive behaviour to Wikipedia completely. But it is not working, I thought I entered the right material, this is what I entered for the Wikibreak Enforcer here: [3]. Could someone please correct it so that the Wikibreak is in place?--R-41 (talk) 18:46, 31 March 2013 (UTC)[reply]

I recommend that you use the new Wikibreak enforcer:

/*** BEGIN WIKIBREAK ENFORCER ***/
addOnloadHook(function() {
 
        /*** Start editing here ***/
 
        // When you want to end your break?
        // no leading zeroes. (example: 7 - correct, 07 - incorrect)
 
        var date = { year: 2100, month: 1, day: 1};
        var time = { hours: 0, minutes: 0, seconds: 0 };
 
        /*** Stop editing here ***/
 
        var currentDate = new Date();
        var enforcedBreakEnd = new Date(
                date.year,date.month-1,date.day,time.hours,time.minutes,time.seconds);
        if (currentDate <= enforcedBreakEnd) {
                alert("Enforced wikibreak until "+enforcedBreakEnd.toLocaleString()
                        + "\n(now is "+currentDate.toLocaleString()+")\n\nBye!");
                location = "//"+location.host+"/w/index.php?title="
                        + "Special:Userlogout&returnto=Main_Page";
        }
});
/*** END WIKIBREAK ENFORCER ***/

Sorry to see you go. —Theopolisme (talk) 19:03, 31 March 2013 (UTC)[reply]

"the crap on this page"

For some reason, Indigenous peoples is displaying with the sentence "please don't fall for the crap on this page" in the lead paragraph--but the wiki text doesn't show this comment when I went in to edit it out. Has a template or something been compromised? Thanks, -- Khazar2 (talk) 21:05, 31 March 2013 (UTC)[reply]

There was vandalism of the page, which was automatically reverted by a bot. apparently, bot edits do not trigger purging of the page, so you saw the cached, vandalized version. "Purge" or simply null-edit (i.e., pressing "edit" and then saving without actually changing anything on the page) cures it. peace - קיפודנחש (aka kipod) (talk) 21:20, 31 March 2013 (UTC)[reply]

I got it corrected.by removing the mis-formated [ethnic minorities]].that had been left there by an IP edit. It was deliberate vandalism, and perhaps some hidden code in what I removed. Cluebot tried to delete it and didn't. — Maile (talk) 21:23, 31 March 2013 (UTC)[reply]

there was no "mis-formatting". you removed a perfectly good internal link - cluebot reverted it just fine. peace - קיפודנחש (aka kipod) (talk) 21:34, 31 March 2013 (UTC)[reply]

I say it was "mis-formatted", because it only had one bracket on the left instead of the double bracket. It WAS...— Maile (talk) 21:54, 31 March 2013 (UTC)[reply]

Whatever the case, the page is again displaying correctly. Thanks for the fix. -- Khazar2 (talk) 21:56, 31 March 2013 (UTC)[reply]

Resolved

I just took care of it. — User:Technical 13 ( C • M • Click to learn how to view this signature as intended ) 21:59, 31 March 2013 (UTC)[reply]

View count bot

The page Aho–Corasick string matching algorithm has for the past week been experiencing a view count bot. I hope someone can fix this. Pass a Method talk 21:52, 31 March 2013 (UTC)[reply]

{{PAGENAME}} in the address bar

Hello. I created a template. If I use articles with one word, it is functioning properly [4]. But if in the title a few words with spaces, template is no longer functioning properly [5]. What should I do to have turned out to use the template and articles whose title contains spaces? Thanks.--Ворота рая Импресариата (talk) 08:09, 1 April 2013 (UTC)[reply]

You need to use {{urlencode:{{PAGENAME}}}} in order to replace spaces with underscores for bare urls, like your links to en.wiki. Your code currently interprets the first space in the page name as the end of the URL. Van Isaac_{WS Vex}^contribs 08:25, 1 April 2013 (UTC)[reply]

Or {{PAGENAMEE}} may be better (depending on situation) -- WOSlinker (talk) 08:38, 1 April 2013 (UTC)[reply]

Well, he's trying to link to an en.wiki article in another wiki with [en.wikipedia.org/wiki/{{PAGENAME}} {{PAGENAME}}], which doesn't work when the article name has a space. So the first {{PAGENAME}} needs to get urlencoded with underscores. Van Isaac_{WS Vex}^contribs 09:12, 1 April 2013 (UTC)[reply]

Thank you all!! I'm sorry, but where can I read more about these and similar templates? Up to this point I did not know about their existence. Thanks.--Ворота рая Импресариата (talk) 09:51, 1 April 2013 (UTC)[reply]

WP:PF Van Isaac_{WS Vex}^contribs 10:58, 1 April 2013 (UTC)[reply]

I humbly thank you. :-)--Ворота рая Импресариата (talk) 11:27, 1 April 2013 (UTC)[reply]

I agree that [http://en.wikipedia.org/wiki/{{PAGENAMEE}} {{PAGENAME}}] would be more efficient than [http://en.wikipedia.org/wiki/{{urlencode:{{PAGENAME}}}} {{PAGENAME}}]. Just my Template:2c — User:Technical 13 ( C • M • View signature as intended) 12:39, 1 April 2013 (UTC)[reply]

"efficient " - yes; useful - no! Try it with a page containing a whitespace... mabdul 09:00, 2 April 2013 (UTC)[reply]

That is why they are using {{PAGENAMEE}} or {{urlencode: it will change the whitespaces to usable characters for the URL string. On a side note, I went back and looked at your template again and it is possible to have characters that won't work the way you have it now (? & = to name a few)...

{{PAGENAME}} → Village pump (technical)
{{PAGENAMEE}} → Village_pump_(technical)
{{URLENCODE:{{PAGENAME}}}} → Village+pump+%28technical%29
{{URLENCODE:{{PAGENAMEE}}}} → Village_pump_%28technical%29

I'd use {{URLENCODE:{{PAGENAMEE}}}} instead to make sure that "every" page name was properly converted. — User:Technical 13 ( C • M • View signature as intended) 11:02, 2 April 2013 (UTC)[reply]

Can someone disambiguate the names affected by tl:sortname?

Some disambig errors are reported at Talk:List_of_Shadowrun_books#Author_links. I tried to fix them, but the article now uses {{sortname}} and I don't know how to tell it to use a red link. --_{Piotr Konieczny aka Prokonsul Piotrus| reply here} 11:19, 1 April 2013 (UTC)[reply]

{{sortname}} shows documentation. {{sortname|Tom|Dowd}} gives Tom Dowd with the bad link to the disambiguation page. {{sortname|Tom|Dowd|Tom Dowd (author)}} gives Tom Dowd. It's the same syntax whether the link is blue or red. {{sortname|Tom|Dowd|nolink=1}} gives Tom Dowd. PrimeHunter (talk) 11:59, 1 April 2013 (UTC)[reply]

Bots and the sudden loss of communication

Hello. I ran a bot add_text.py. But his work was terminated error 503. I stopped at the article on the letter E. Tell me, is it possible to continue the action of the script from the page where the failure occurred? If not, then how should I complete the planned my action? Thank you.--Ворота рая Импресариата (talk) 15:38, 1 April 2013 (UTC)[reply]

I think you can use the argument -start:E. —Theopolisme (talk) 00:36, 2 April 2013 (UTC)[reply]

Yes, I certainly tried, but in one case the bot is still starting from the beginning of the list, in the other - to make transactions in the space of articles, even though I asked to perform tasks in templates, and the third - did nothing.

So, I completed the task with AWB - this program is always less hassle - but what if I need to do something that is not in the standard functional AWB and there is the same error - I do not know. Thanks.--Ворота рая Импресариата (talk) 05:55, 2 April 2013 (UTC)[reply]

Lua implementation of Template:Portal

I've written a Lua version of Template:Portal at Module:Portal, and I hope it can be rolled out fairly soon. {{Portal}} has more than four million transclusions, though, so I want to make sure it is done right. There are test cases at Template:Portal/testcases and I've outlined the details of the implementation at Template talk:Portal#Lua implementation. If people could take a look over my code and comment over there, I'd be most grateful. — Mr. Stradivarius ^{♪ talk ♪} 19:06, 1 April 2013 (UTC)[reply]

Error mesage

Just for documentation purposes, I got sent to a page that said the Wiki was having a problem. It was not the normal "Wikimedia error" page that usually appears.— Vchimpanzee · talk · contributions · 20:49, 1 April 2013 (UTC)[reply]

We had three outages in the last days, the latest on Sunday 2013-03-31 around 21:20 UTC, and the operations team is aware of it and has fixed them. Are there specific steps to reproduce? Did this happen with any page on en.wikipedia.org, is this still reproducible for you, and if yes what is the exact error message? (Screenshot or copying the text welcome). Thanks & sorry for the problems. --AKlapper (WMF) (talk) 11:52, 2 April 2013 (UTC)[reply]

Convert HTML into an infobox

Can someone convert the HTML at Joel Goffin into an infobox and put his image in the infobox rather than the center of the article? Ryan Vesey 21:46, 1 April 2013 (UTC)[reply]

Done -- WOSlinker (talk) 22:03, 1 April 2013 (UTC)[reply]

Thank you so much. Ryan Vesey 23:28, 1 April 2013 (UTC)[reply]

Convert HTML into an infobox Part 2

I'm very active at lowp at the moment and cleaning the complete wiki (only ~850 article at the moment). Would somebody help me and cleaning up the infoboxes and converting them to "wikimarkup infoboxes? Here is a link for them for some [6]. More will likely follow in a few days if I find some in articlespace which aren't covered by this link. If there are still interwiki links, feel free to help there, too. ;-)

Regards,

mabdul 22:30, 1 April 2013 (UTC)[reply]

Some more infoboxes: [7]. mabdul 11:42, 2 April 2013 (UTC)[reply]

Question for those familiar with MediaWiki template parameters / variables

Resolved

– Bug filed - bugzilla:46768 7 04:15, 2 April 2013 (UTC)[reply]

Can I ask anyone who is an expert in this topic to take a look at the question here. Thanks 7 01:59, 2 April 2013 (UTC)[reply]

Is there a tool to update an infobox automatically?

I was looking at the infobox at Open Knowledge Foundation. It seems to be using old parts of the syntax such as | Non-profit_name = | Non-profit_logo = | vector_logo = (you can see them in the 2007 version but not in the modern {{Infobox non-profit}}). Is there any tool that could update this in the article replacing old syntax with new or do we have to do this by hand? --_{Piotr Konieczny aka Prokonsul Piotrus| reply here} 02:34, 2 April 2013 (UTC)[reply]

You could either use WP:AWB for that, or request a bot operator to do this at WP:BOTREQ (multiple bots do these kind of replacements and removals on a regular basis). mabdul 04:52, 2 April 2013 (UTC)[reply]

Bugday today (16:30 - 20:30UTC) on MediaWiki skin and page rendering issues

Hi everybody, today is a Wikimedia Bugday from 16:30-20:30 UTC in #wikimedia-office on Freenode IRC. Everyone is welcome to join, and no technical knowledge needed! Just say Hi and that you're here for the bugday when joining at any time. It's an easy way to get involved in the community or to give something back. This even is part of the QA weekly goals. This information and more can be found on the wiki. There is also more information available on Bug triaging in general. Looking forward to seeing you there! --AKlapper (WMF) (talk) 14:32, 2 April 2013 (UTC)[reply]

Change in logged-in status

In the past, I'd get a warning that I was not logged in every day or two, while attempting to save an edit, even though I was definitely logged in when I started, as evidenced by the top menus, nav popups, WikEd use, edit settings, etc.

I've noticed that, in the last couple of weeks, this has changed, and I haven't needed to log in again during that time. I generally leave a WP page open in a browser (FFox 15), and generally hibernate the machine between sessions.

I also noticed another change today. I log in and use the https (secure) web interface to WP. When I Google search (i.e. from Google) in another tab or window and click on a link to a WP article, it is usually to the non-secure http page. In the past, even though I am logged in and viewing an https page in another tab/window, the http page I clicked on would not be logged in. If I proceeded to log into that page, I believe (but am not sure) it would log me out of the https page. Now, it seems that has changed. When I click on an http link, it still shows me as logged in (based on the top menu, nav popups, etc.).

If this is a fix, thanks! I thought I'd mention it for the benefit of those who were routinely logging in every day as a (now un-necessary) preventative measure. —[AlanM1(talk)]— 18:36, 2 April 2013 (UTC)[reply]

Classic skin and CSS

The WMF has announced that in two weeks time, it will stop supporting the Classic skin. As per this XKCD strip, this will severely impede my workflow.

I've been told that the majority of Classic's features can be replicated via .css tinkering. However, this would require a skillset I don't have. Can anyone help out?

(I want serif fonts - preferably Times New Roman. I know how to set my browser so that all pages everywhere will be in Times New Roman, but I'd rather it was just all WMF pages. Because those are the pages that are affected by my user skin. This is doable, yes?

(And I prefer the 'toolbox' links to be off to the left side, not the top, and I don't want collapsibles.) DS (talk) 19:06, 2 April 2013 (UTC)[reply]

toolbox on the left: unless you mean something else in "toolbox" than what i think you mean, this is already the default for vector.
non-collapsible: this is settable from Preferences => Appearance => Enable collapsing of items in the sidebar in Vector skin
fonts: if you want times all over, add the following to your CSS page
```
body { font-family: "Times new roman";}
```
if you want it for content only, use
```
#bodyContent { font-family: "Times new roman";}
```

peace - קיפודנחש (aka kipod) (talk) 19:22, 2 April 2013 (UTC)[reply]

Although it will only affect a small minority of users, I believe that by making this change, without any form of discussion and only minimal notice, the Foundation is seriously overstepping its mark. This should be fully discussed, on all Wikis, and there should only be change if there is good reason and consensus to do so. Objections to this heavy-handed approach can be made [8]. An optimist on the run! 19:34, 2 April 2013 (UTC)[reply]

Ironic that you would call for making objections on that page. The purpose of that Meta page is to get translations for advance notifications to each local community about the reasons for the change, who it will impact and so on. Oliver Keyes and others are working on making sure there are announcements etc., so please assume good faith instead of rushing to get your pitchfork. There will be an opportunity to comment about the change without needing to go to Meta. Steven Walling (WMF) • talk 20:23, 2 April 2013 (UTC)[reply]

Then please tell us where we can make objections, and let us know if such objections will be listened to. An optimist on the run! 20:46, 2 April 2013 (UTC)[reply]

I let Oliver know over IRC so he can explain the plan. Steven Walling (WMF) • talk 20:49, 2 April 2013 (UTC)[reply]

Both users have now commented on the meta page provided, which explains the plan - that seems to resolve that :). Okeyes (WMF) (talk) 21:30, 2 April 2013 (UTC)[reply]

badly positioned magnifying glass in search bar using Firefox

Tracked in Phabricator
Task T32525

I have seen a problem with the positioning of the magnifying glass in the search bar using Firefox for a while now (at least about a half a year). I have uploaded a screenshot that shows the problem here. Notice how the magnifying glass is shifted down to the point of being partly outside the search box. Do other Firefox users see this? Not sure if problem here or with Firefox's rendering yet. This is the Linux version of Firefox. That shouldn't but may be important. Jason Quinn (talk) 19:48, 2 April 2013 (UTC)[reply]

Actually, it does seem to be important that it's the Linux version of Firefox. I don't see it in the Windows version. Most likely a bug in Firefox now. Jason Quinn (talk) 20:13, 2 April 2013 (UTC)[reply]

There's already a Wikimedia bug report (Template:Bug) regarding the positioning of the icon, although it seems that your case is particularly bad. May I ask which version of Firefox are you running? On my Linux installation, Firefox 19 seems to match the "Epiphany" screenshot. PleaseStand (talk) 20:54, 2 April 2013 (UTC)[reply]

It's 19.0.2. Jason Quinn (talk) 21:13, 2 April 2013 (UTC)[reply]

Watchlist group by section?

I'm playing with the WP api and wondering if a watchlist variant that grouped by section name (when available) as well as by article would be useful. Has this been done already in some user script or extension or something? Just wondering if it would be useful. Mainly for busy pages like VP or teahouse or Jimbo talk. Silas Ropac (talk) 20:27, 2 April 2013 (UTC)[reply]