ClueBot III (talk | contribs) m Archiving 23 discussions to Wikipedia:Village pump (technical)/Archive 119. (BOT) |
|||
Line 55: | Line 55: | ||
:Note the option on one of my browsers has come back. [[User:GiantSnowman|Giant]][[User talk:GiantSnowman|Snowman]] 12:59, 7 November 2013 (UTC) |
:Note the option on one of my browsers has come back. [[User:GiantSnowman|Giant]][[User talk:GiantSnowman|Snowman]] 12:59, 7 November 2013 (UTC) |
||
== Requests to dezoomify an image == |
|||
I was asked to upload PD [http://dk.bu.uni.wroc.pl/cymelia/displayDocument.htm?docId=8200031886] (direct link to zoomified image: [http://dk.bu.uni.wroc.pl/cymelia/showPicture.htm;jsessionid=CD5576C24A75B581E5266A83D4237423?docId=8.200031886E9&shortTilesPath=/0/03/033/0332/03326/03326001.jpg]). image to Commons, but it uses the evil zoomify javascript. I tried to use the tools listed on [[:commons:Help:Zoomable images]], but they either require skills I don't have (ex. Python, Ruby + ImageMagick, etc.) or are broken ([http://toolserver.org/~kolossos/image/zoomify.php] by [[User:kolossos]] gives 404, gee, toolserver tool that is not maintained, what a surprise; [http://ophir.lojkine.free.fr/dezoomify/dezoomify.html] was loading an image, then gave me a black screen; upon a second run it froze at 92%). As it appears using those tools requires skills (or luck) I don't have, perhaps someone here will have a better luck. --<sub style="border:1px solid #228B22;padding:1px;">[[User:Piotrus|Piotr Konieczny aka Prokonsul Piotrus]]|[[User talk:Piotrus|<font style="color:#7CFC00;background:#006400;"> reply here</font>]]</sub> 02:46, 28 October 2013 (UTC) |
|||
:I've managed to get the image successfully. Can you post what I should put on its description page when I upload it? [[User:Jackmcbarn|Jackmcbarn]] ([[User talk:Jackmcbarn|talk]]) 03:21, 28 October 2013 (UTC) |
|||
::@[[User:Jackmcbarn]]: Description: <nowiki>{{de|Nationalitätenkarte der östlichen Provinzen des Deutschen Reiches nach dem Ergebnissen der amtlichen Volkszählung vom Jahre 1910 entworfen von Ing. Jakob Spett}}</nowiki> (I can't do more with that than a Google Translate myself; but ping [[User:MyMoloboaccount]]; he requested it so hopefully he will also translate the description). Author: Spett, Jakob; publisher Gotha Justus Perthes. Year: 1910. Category:Maps in German, Category:Ethnographic maps of Poland (I think). Thanks! --<sub style="border:1px solid #228B22;padding:1px;">[[User:Piotrus|Piotr Konieczny aka Prokonsul Piotrus]]|[[User talk:Piotrus|<font style="color:#7CFC00;background:#006400;"> reply here</font>]]</sub> 05:00, 28 October 2013 (UTC) |
|||
::"National map of eastern provinces of German Reich based on official census of 1910" would be ok. As to licence I believe it would be PD, but I am no expert, as to reason, to demonstrate the national census of 1910 in German Empire and its demographics.--[[User:MyMoloboaccount|MyMoloboaccount]] ([[User talk:MyMoloboaccount|talk]]) 22:08, 29 October 2013 (UTC) |
|||
:::I need a PD reason to upload it, and I still need a filename. [[User:Jackmcbarn|Jackmcbarn]] ([[User talk:Jackmcbarn|talk]]) 03:43, 3 November 2013 (UTC) |
|||
::::Jakob Spett died in 1942 according to [http://www.sankt-wendel.de/fileadmin/PDF_Dateien/kultur/stadtarchiv/1979-80.pdf], p. 77. (He was born in 1863 or 1862 according to the same source, pp. 74-75: they state his wife was 93 years old in 1968, and her husband was 12 years older.) The map is a derivative work; it is based on "Vogels Karte des Deutschen Reiches und der Alpenländer", published also by Justus Perthes in Gotha in 1915. That earlier map was created 1891-93 by cartographer Carl Vogel (1828-1897) as "Karte des Deutschen Reiches". It was revised and extended to cover the "Alpenländer" (alpine countries) 1913-15 by cartographer Paul Langhans.[http://www.deutsche-biographie.de/xsfz48109.html] Langhans lived 1867-1952 and thus the map is not yet in the public domain in Germany, and neither is Spett's derivative. Therefore not suited for uploading to the Commons. If you want to upload it locally at the English Wikipedia, that would work; it's {{tl|PD-1923-abroad}}. (Spett's map was used in the negotiations at Versailles after WWI, so it must have been published by then.) [[User:Lupo|Lupo]] 13:04, 3 November 2013 (UTC) |
|||
:::::[[:File:National map of eastern provinces of German Reich based on official census of 1910.jpg]] If you see any improvements that can be made to its description page, please make them. [[User:Jackmcbarn|Jackmcbarn]] ([[User talk:Jackmcbarn|talk]]) 15:39, 3 November 2013 (UTC) |
|||
:::::: Thank you. [[User:Lupo|Lupo]] 20:16, 4 November 2013 (UTC) |
|||
== I am not signed in == |
|||
But I am signed in. I never signed out, and I recently had to sign back in, and I assume I checked the box saying to keep me signed in for 30 days. I went to the login screen and was told I was already signed in as vchimpanzee, though I could sign in with a different name. I signed in again. After that, I clicked on "online" at the top of the screen and was told I was not signed in.— [[User:Vchimpanzee|<font color="Green">Vchimpanzee</font>]] '''·''' [[User talk:Vchimpanzee|<span style="color: orange"> talk</span>]] '''·''' [[Special:Contributions/Vchimpanzee|<span style="color: maroon">contributions</span>]] '''·''' 19:23, 30 October 2013 (UTC) |
|||
:I used the page history and undo to say I was online, and that worked fine.— [[User:Vchimpanzee|<font color="Green">Vchimpanzee</font>]] '''·''' [[User talk:Vchimpanzee|<span style="color: orange"> talk</span>]] '''·''' [[Special:Contributions/Vchimpanzee|<span style="color: maroon">contributions</span>]] '''·''' 19:57, 30 October 2013 (UTC) |
|||
::There are quite a lot of related threads in the archives, mostly from [[Wikipedia:Village pump (technical)/Archive 114]] onwards. If the circumstances suggest that Wikipedia doesn't think that I'm logged in, I use {{keypress|Ctrl|F5}} and that normally works for me. --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] ([[User talk:Redrose64|talk]]) 20:01, 30 October 2013 (UTC) |
|||
:::It didn't work. And I'm wondering if Wikipedia will think I'm not logged in next time. I did check the box. I'm about to leave anyway and change to offline. I may edit tomorrow form a library, but of course I won't already be signed in there.— [[User:Vchimpanzee|<font color="Green">Vchimpanzee</font>]] '''·''' [[User talk:Vchimpanzee|<span style="color: orange"> talk</span>]] '''·''' [[Special:Contributions/Vchimpanzee|<span style="color: maroon">contributions</span>]] '''·''' 21:28, 30 October 2013 (UTC) |
|||
::::It happened for clicking on "Offline" and CTRL-F5 didn't help.— [[User:Vchimpanzee|<font color="Green">Vchimpanzee</font>]] '''·''' [[User talk:Vchimpanzee|<span style="color: orange"> talk</span>]] '''·''' [[Special:Contributions/Vchimpanzee|<span style="color: maroon">contributions</span>]] '''·''' 21:38, 30 October 2013 (UTC) |
|||
:::::If you do have Javascript enabled and are still seeing no notice of the login, please check for Javascript errors in the browser's error console. Please also try to update your browser cache by https://en.wikipedia.org/wiki/Wikipedia:BYPASS. --[[User:AKlapper (WMF)|AKlapper (WMF)]] ([[User talk:AKlapper (WMF)|talk]]) 13:25, 31 October 2013 (UTC) |
|||
{{outdent}}I'm not at home but I'll try these steps when I get there. I got a message to update Java, which I am aware is not Javascript, but I'm not sure whether I actually did. I also got a message telling me to update my virus protection but it didn't say how, and I spent time in a live chat with someone connected with the virus protection company. This is when the problems started happening.— [[User:Vchimpanzee|<font color="Green">Vchimpanzee</font>]] '''·''' [[User talk:Vchimpanzee|<span style="color: orange"> talk</span>]] '''·''' [[Special:Contributions/Vchimpanzee|<span style="color: maroon">contributions</span>]] '''·''' 14:13, 31 October 2013 (UTC) |
|||
:Whoops. Are you sure that the "virus protection company" was legit? I get phone calls 2-3 times a week from somebody claiming to be from Windows support and asking me to visit their website for a free online check. I ''never'' do it. --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] ([[User talk:Redrose64|talk]]) 17:52, 31 October 2013 (UTC) |
|||
:Does this only happen when clicking the online/offline links? I think there might be a bug in the [[User:Cj005257/scripts/useronline.js/Version2.js|online/offline script]] you are using. The code contains hard-coded HTTP URLs, but Wikipedia now uses HTTPS by default for logged-in users. For the links to work on HTTP and HTTPS alike, the URLs should be protocol-relative (i.e. "//en.wikipedia.org/w/...") or server-relative (i.e. "/w/index.php?..."). I suggest contacting the [[User:Cj005257|script's author]]. I've already {{diff|Template:Useronline|prev|579667851|fixed}} the same issue in the [[Template:Useronline|template associated with the script]]. – '''[[User:PartTimeGnome|PartTimeGnome]]''' <span style="font-size:79%">([[User talk:PartTimeGnome|talk]] | [[Special:Contributions/PartTimeGnome|contribs]])</span> 22:16, 31 October 2013 (UTC) |
|||
::Good catch, I'v made the links protocol relative. They probably should be server relative as well, but I leave that up to the author. —[[User:TheDJ|Th<span style="color: green">e</span>DJ]] ([[User talk:TheDJ|talk]] • [[Special:Contributions/TheDJ|contribs]]) 09:52, 1 November 2013 (UTC) |
|||
:::Thanks guys. Didn't realise Wikipedia had changed to a secure transmission protocol. Cheers anyway. [[User:Cj005257|CJ]] <sup>[[User Talk:Cj005257|Drop me a line!]] • [[Special:Contributions/Cj005257|Contribs]]</sup> 15:25, 1 November 2013 (UTC) |
|||
::::To PartTime Gnome: I had the problem only when I first went to the site each day, and when clicking on the online/offline links. I go to the site using HTTP links. I saved them in an email to myself which I update as I work my way through the Help Desk archives. |
|||
::::To Redrose: I clicked on the symbol for the virus protection company (McAfee, actually) that appears on my screen automatically. From there I can go to support. I hardly think a scam artist could reproduce the entire web site or redirect me to him from the legitimate site. |
|||
::::I forgot to click "keep me signed in" so I signed out and signed in again. I also deleted history. I don't have the problem now. Thanks.— [[User:Vchimpanzee|<font color="Green">Vchimpanzee</font>]] '''·''' [[User talk:Vchimpanzee|<span style="color: orange"> talk</span>]] '''·''' [[Special:Contributions/Vchimpanzee|<span style="color: maroon">contributions</span>]] '''·''' 19:13, 1 November 2013 (UTC) |
|||
:::::Didn't work. I clicked on "back" as many times as necessary to get back to where I started, and the first page still looked like I wasn't signed in. I even changed one number in the URL and got taken to another page that looked like it. I signed in, forgot to say I wanted to stay signed in, signed out, and signed in again. Now all is well. I hope.— [[User:Vchimpanzee|<font color="Green">Vchimpanzee</font>]] '''·''' [[User talk:Vchimpanzee|<span style="color: orange"> talk</span>]] '''·''' [[Special:Contributions/Vchimpanzee|<span style="color: maroon">contributions</span>]] '''·''' 19:34, 1 November 2013 (UTC) |
|||
::::::After clicking "back" sufficient times, you may still need to force your browser to reload the page (in Firefox, {{keypress|F5}} may be sufficient, otherwise try {{keypress|Ctrl|F5}}) - otherwise it may display a cached copy, one which still suggests that you're not signed in. --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] ([[User talk:Redrose64|talk]]) 22:10, 1 November 2013 (UTC) |
|||
{{outdent}}Weird. I used the link with http rather than https and I appeared not to be signed in. Changing the URL to https solved the problem. I'm going to send myself that email with the URLs corrected.— [[User:Vchimpanzee|<font color="Green">Vchimpanzee</font>]] '''·''' [[User talk:Vchimpanzee|<span style="color: orange"> talk</span>]] '''·''' [[Special:Contributions/Vchimpanzee|<span style="color: maroon">contributions</span>]] '''·''' 19:09, 4 November 2013 (UTC) |
|||
:By the way, I'm on IE.— [[User:Vchimpanzee|<font color="Green">Vchimpanzee</font>]] '''·''' [[User talk:Vchimpanzee|<span style="color: orange"> talk</span>]] '''·''' [[Special:Contributions/Vchimpanzee|<span style="color: maroon">contributions</span>]] '''·''' 19:13, 4 November 2013 (UTC) |
|||
== Fix needed for Template:Alphanumeric TOC == |
|||
Hi, when using [[:Template:Alphanumeric TOC]], it is adding an unwanted section of <nowiki>==Contents==</nowiki> to each article wherever it is transcluded. See: [[2000s in film]] and note in the TOC that there are 2 sections labelled "Contents". The usual Template:Compact ToC does not do this. Would someone be able to fix the template for us? Thanks much [[User:Funandtrvl|Funandtrvl]] ([[User talk:Funandtrvl|talk]]) 00:05, 1 November 2013 (UTC) |
|||
:I think the problem is in [[Template:TOC top]], which inserts the offending H2: <code><nowiki><h2>{{{title|{{MediaWiki:Toc}} }}}</h2></nowiki></code>. I'd prefer if someone more familiar with TOC templates could look at this though. The templates involved are also all still full-protected. <font style="color:#0059B2;text-shadow:0px 0px 5px #80BFFF">[[User:Equazcion|<font color="#0059B2">equazcion</font>]] [[User talk:Equazcion|<font color=#0059B2>→</font>]] <span style="font-size:88%">00:25, 1 Nov 2013 (UTC)</span></font> |
|||
:(edit conflict) It's caused by the use of {{tag|h2}} in [//en.wikipedia.org/w/index.php?title=Template:TOC_top&diff=569570200&oldid=569282696] by [[User:TheDJ]]. h2 was removed earlier after discussion at [[Template talk:TOC top#Edit request]] but it has gone in and out. I think it should be out. [[User:PrimeHunter|PrimeHunter]] ([[User talk:PrimeHunter|talk]]) 00:27, 1 November 2013 (UTC) |
|||
::I doubt this will be all that controversial. Just get rid of it. <font style="color:#0059B2;text-shadow:0px 0px 5px #80BFFF">[[User:Equazcion|<font color="#0059B2">equazcion</font>]] [[User talk:Equazcion|<font color=#0059B2>→</font>]] <span style="font-size:88%">00:30, 1 Nov 2013 (UTC)</span></font> |
|||
:::In reading the Talk page referenced above, it looks like the "Content" section link/listing in the TOC of an article is usually undesirable. I vote for taking it out, since when the alphanumeric toc is used multiple times in an article, like 2000s in film, it looks very weird to have multiple Content sections in the TOC. The template is protected, and I don't know enough code to be able to fix it. Do I need to make an edit request on the template's talk page? [[User:Funandtrvl|Funandtrvl]] ([[User talk:Funandtrvl|talk]]) 01:14, 1 November 2013 (UTC) |
|||
::::It seems like [[User:TheDJ]] inadvertently re-inserted the H2 tags recently in an unrelated edit. The consensus is to leave them out. If an admin downgrades the protection level to template-protect I can probably do this but I would really rather [[User:PrimeHunter]] or [[User:TheDJ]], or someone else who knows TOC templates, to be the one. <font style="color:#0059B2;text-shadow:0px 0px 5px #80BFFF">[[User:Equazcion|<font color="#0059B2">equazcion</font>]] [[User talk:Equazcion|<font color=#0059B2>→</font>]] <span style="font-size:88%">01:38, 1 Nov 2013 (UTC)</span></font> |
|||
::::You could make an edit request at that talk page, but if you don't have a specific code replacement to provide I don't think it would happen. <font style="color:#0059B2;text-shadow:0px 0px 5px #80BFFF">[[User:Equazcion|<font color="#0059B2">equazcion</font>]] [[User talk:Equazcion|<font color=#0059B2>→</font>]] <span style="font-size:88%">01:44, 1 Nov 2013 (UTC)</span></font> |
|||
:::::There was little inadvertent about it. It was quite on purpose, to make it mirror the ACTUAL Table of Contents structure. As the [[Template:TOC top]] documentation mentions, use "primary=false" when a TOC is used in addition to a proper TOC. The reason to use h2 is for accessibility reasons. And remember that [[:Template:Alphanumeric TOC]] is not the only user of [[Template:TOC top]]. —[[User:TheDJ|Th<span style="color: green">e</span>DJ]] ([[User talk:TheDJ|talk]] • [[Special:Contributions/TheDJ|contribs]]) 09:32, 1 November 2013 (UTC) |
|||
::::::The actual TOC does use {{tag|h2}} but it doesn't produce a TOC entry saying "Contents". [[User:PrimeHunter|PrimeHunter]] ([[User talk:PrimeHunter|talk]]) 11:12, 1 November 2013 (UTC) |
|||
:::::::The primary TOC mentioning '''Contents''' is a side effect of editors using more than one TOC on a page. Most uses of {{tl|TOC top}} REPLACE a proper TOC and then there is no problem whatsoever in using H2, and you will have consistent and expected behavior for pages. It's when you add a secondary TOC, when you start to create trouble. So make that distinction by using the 'primary=false' option and you won't have a problem. —[[User:TheDJ|Th<span style="color: green">e</span>DJ]] ([[User talk:TheDJ|talk]] • [[Special:Contributions/TheDJ|contribs]]) 11:59, 1 November 2013 (UTC) |
|||
::::::::I think [https://en.wikipedia.org/w/index.php?title=2000s_in_film&diff=579729539&oldid=577779464 this edit] to [[2000s in film]]] illustrates what DJ means. Without the option, the templates cause an extra heading to appear in the template. In my experience it is more common for the template to be use as replacement for the TOC. [[User:Bkonrad|older]] ≠ [[User talk:Bkonrad|wiser]] 12:12, 1 November 2013 (UTC) |
|||
* The protection of [[:Template:Alphanumeric TOC]] has been lowered to {{Abbr|TE|template editor}} if there is a consensus for a change, <small>which there seems to be</small>. Happy editing. [[User:Technical 13|Technical 13]] ([[User talk:Technical 13|talk]]) 11:42, 1 November 2013 (UTC) |
|||
[[Template:TOC top]] is still full-protected, and that's where the change would need to be made. [[User:TheDJ]], you just told us a bunch of things that were already mentioned -- but didn't mention ''why'' you felt your change back to H2 was a benefit. Is there any reason it wouldn't be better to make multiple TOCs ''not'' produce this unintended behavior by default, rather than requiring a parameter to fix it? Edit: I see you mentioned accessibility reasons, but I'm not sure what those could be -- and most other TOC templates don't seem to produce an H2, at least not by default. Any reason it particularly belongs in templates that use [[Template:TOC top]]? <font style="color:#0059B2;text-shadow:0px 0px 5px #80BFFF">[[User:Equazcion|<font color="#0059B2">equazcion</font>]] [[User talk:Equazcion|<font color=#0059B2>→</font>]] <span style="font-size:88%">13:48, 1 Nov 2013 (UTC)</span></font> |
|||
:Now dropped to TE protection.--[[User:Salix alba]] ([[User talk:Salix alba|talk]]): 14:07, 1 November 2013 (UTC) |
|||
::Thanks Salix :) PS. For the time being I added mention of this "primary" parameter to the documentation at [[Template:Alphanumeric TOC]]. I doubt people using this template would've reasonably known to go looking at TOC top to find that information. <font style="color:#0059B2;text-shadow:0px 0px 5px #80BFFF">[[User:Equazcion|<font color="#0059B2">equazcion</font>]] [[User talk:Equazcion|<font color=#0059B2>→</font>]] <span style="font-size:88%">14:18, 1 Nov 2013 (UTC)</span></font> |
|||
:# Regarding accessibility reasons, if you don't use h2, a screenreader will not identify the header of the Article ToC in it's own Document ToC (which includes much more than just the article headers) as it does for other pages. The official TOC and most fake ToCs do actually use h2 (I did a rewrite of almost all of them not so long ago). |
|||
:#"multiple TOCs ''not'' produce this unintended behavior". That would indeed be nice, but that is unfortunately not possible since we are faking our own ToC here. There is no 'knowledge' that we can use to determine if a table is an additional fake next to a proper TOC, or if it supposed to be replacing the proper TOC. |
|||
:#Again the problem here is not the h2 itself, it's that you use are using two elements that are designed to present a ToC for an article (combined with the fact that the core software only knows about the it's own primary ToC). Another example that shows that this is a somewhat faulty usage for [[2000s_in_film]]: if I put a heading named G in between Events and Highest-grossing films, and then press the G of the [[:Template:Alphanumeric TOC]] in that article, it will take me to this newly added G instead of the G in the list. It has been visually added to the section of the page, but that doesn't magically make it specific to the section. —[[User:TheDJ|Th<span style="color: green">e</span>DJ]] ([[User talk:TheDJ|talk]] • [[Special:Contributions/TheDJ|contribs]]) 14:26, 1 November 2013 (UTC) |
|||
::::These are all valid things to consider. I nevertheless have to say it seems haphazard to change the default behavior and add a parameter required to get it back to the currently expected behavior, when that parameter would of course not be in any invocation yet, no one would know about it, the talk page consensus was against it, and without making any documentation changes to the affected parent templates (which are the only places any users would realistically be looking). And yes, regardless of your opinion on whether multiple TOCs should actually be used on a page. I've now changed the documentation for the particular template that brought the issue to VPT, but there are still another 30 or so to go, and adding this parameter to the affected uses is probably a bigger job. <font style="color:#0059B2;text-shadow:0px 0px 5px #80BFFF">[[User:Equazcion|<font color="#0059B2">equazcion</font>]] [[User talk:Equazcion|<font color=#0059B2>→</font>]] <span style="font-size:88%">14:51, 1 Nov 2013 (UTC)</span></font> |
|||
:::::It's true, there is a lot of cleanup. And it is true that when I made the original changes, I did not think about the fact that about 2-5% of the uses would be 'incorrect' to begin with. But this one problem is not more important than the problems solved. In general we should move forward and become more correct, not keep crap in simply because we have crap that depends on crap. |
|||
:::::If you ask me, we should replace every list or section section usage with a "Alphanumeric section TOC" that has primary set to false, and preferably uses prefixes for the header IDs. —[[User:TheDJ|Th<span style="color: green">e</span>DJ]] ([[User talk:TheDJ|talk]] • [[Special:Contributions/TheDJ|contribs]]) 15:14, 1 November 2013 (UTC) |
|||
::::::Thanks for adding the primary option to {{tl|Alphanumeric TOC}} in [https://en.wikipedia.org/w/index.php?title=Template:Alphanumeric_TOC&diff=579718465&oldid=579692116]. But many editors will fail to set <code>primary=false</code> when it's required. Is there no way to make it accessible in screenreaders without causing the "Contents" entry in cases where the page also has a normal TOC? [[User:PrimeHunter|PrimeHunter]] ([[User talk:PrimeHunter|talk]]) 15:29, 1 November 2013 (UTC) |
|||
:::::::We could add an option into the core software to automatically remove headers from the vanilla ToC, if given a certain paramater. But that would be highly en.wp specific behavior/requirements, I doubt it would be easily accepted. The other option is to create an option for building alternative TOC formats into the core software. I'd give that a higher chance of success, but it would be more complicated. —[[User:TheDJ|Th<span style="color: green">e</span>DJ]] ([[User talk:TheDJ|talk]] • [[Special:Contributions/TheDJ|contribs]]) 10:17, 4 November 2013 (UTC) |
|||
{{Outdent|8}}Thanks to those above that added the parameter description for "primary=false" to the /doc page. Are there any other templates that would need that description too? I would have never known to look for Template:TOC top, so I appreciate the description for the proper use. :) I agree it might be a good idea to make a Template:Alphanumeric section TOC...maybe that would be a simpler solution that would also be able to keep the main Alphanumeric template as is, for the reasons above. [[User:Funandtrvl|Funandtrvl]] ([[User talk:Funandtrvl|talk]]) 20:51, 4 November 2013 (UTC) |
|||
== Heading and image overlap == |
|||
A reader reported, via OTRS, that in [[Hinduism in Tamil Nadu]], the heading "Bhairavar" overlaps the image. I see the problem, in Mozilla Firefox, but not in Chrome. Can anyone see why?--[[User:Sphilbrick|<span style="color:#002868;padding:0 4px;font-family: Copperplate Gothic Light">S Philbrick</span>]][[User talk:Sphilbrick|<span style=";padding:0 4px;color:# 000;font-family: Copperplate Gothic Light">(Talk)</span>]] 13:45, 1 November 2013 (UTC) |
|||
:Depends on screen resolution and default fonts and font sizes on the operating system that you use. More information welcome (I cannot reproduce with 1440px screenwidth on Firefox 24 on a Fedora 19 system). --[[User:AKlapper (WMF)|AKlapper (WMF)]] ([[User talk:AKlapper (WMF)|talk]]) 15:26, 1 November 2013 (UTC) |
|||
::This is a known CSS issue, caused by the margins that we have on top of images. It's actually the appropriate behavior (according to CSS) in very specific combinations of text and floating blocks (images). It's undesirable, but not really avoidable without reducing the margin on top of the image by at least half, which I think is also not really desirable. It's one of those things that no one really thought about when defining clear behavior in the CSS specification. —[[User:TheDJ|Th<span style="color: green">e</span>DJ]] ([[User talk:TheDJ|talk]] • [[Special:Contributions/TheDJ|contribs]]) 10:14, 4 November 2013 (UTC) |
|||
== Interlanguage links in different font == |
== Interlanguage links in different font == |
||
Line 153: | Line 84: | ||
::I missed this thread and posted down below. It's a ghastly choice of font. I'm working on a 17" CRT monitor, and I'd hate to think what it looks like on anything smaller. It may look better on LCD, but I doubt it. [[User:Peridon|Peridon]] ([[User talk:Peridon|talk]]) 17:43, 11 November 2013 (UTC) |
::I missed this thread and posted down below. It's a ghastly choice of font. I'm working on a 17" CRT monitor, and I'd hate to think what it looks like on anything smaller. It may look better on LCD, but I doubt it. [[User:Peridon|Peridon]] ([[User talk:Peridon|talk]]) 17:43, 11 November 2013 (UTC) |
||
:::It looks awful everywhere. I've got a nice big flat widescreen and it still hurts to look. Luckily I have [[User:Equazcion/SidebarTranslate|SidebarTranslate]], so I don't ever need to see it (shameless plug). <font style="color:#0059B2;text-shadow:0px 0px 5px #80BFFF">[[User:Equazcion|<font color="#0059B2">equazcion</font>]] [[User talk:Equazcion|<font color=#0059B2>→</font>]] <span style="font-size:88%">18:01, 11 Nov 2013 (UTC)</span></font> |
:::It looks awful everywhere. I've got a nice big flat widescreen and it still hurts to look. Luckily I have [[User:Equazcion/SidebarTranslate|SidebarTranslate]], so I don't ever need to see it (shameless plug). <font style="color:#0059B2;text-shadow:0px 0px 5px #80BFFF">[[User:Equazcion|<font color="#0059B2">equazcion</font>]] [[User talk:Equazcion|<font color=#0059B2>→</font>]] <span style="font-size:88%">18:01, 11 Nov 2013 (UTC)</span></font> |
||
== Failed action=purge == |
|||
{{tracked|56487}} |
|||
I see a strange error message at [https://en.wikipedia.org/wiki/File:Agents_of_S.H.I.E.L.D_intertitle.png?action=purge]: |
|||
{{cquote|A database query error has occurred. This may indicate a bug in the software. |
|||
* Function: Title::invalidateCache |
|||
* Error: 1205 Lock wait timeout exceeded; try restarting transaction (10.64.32.26)}} |
|||
Any idea what's going on? --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 00:47, 2 November 2013 (UTC) |
|||
: I was getting a similar message while trying to perform the following actions: |
|||
:* Deleting [[:File:04 - Pero Me Acuerdo De Tí.jpg]] |
|||
:* Uploading a new version of a file at [[:File:44adelaidelogo.png]] |
|||
:* Modifying file description of [[:File:44adelaidelogo.png]]. |
|||
:The problem occurred both in Chrome and Firefox and seems to be resolved now -- [[User:Diannaa|Diannaa]] ([[User talk:Diannaa|talk]]) 01:08, 2 November 2013 (UTC) |
|||
::Weird. I got a watchlist notification that [[:File:Agents of S.H.I.E.L.D intertitle.png]] had been deleted by [[User:Mark Arsten]], but the file was still there, so I tried to purge the page, which failed. I see that you later deleted it. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 01:24, 2 November 2013 (UTC) |
|||
:::I just had a bunch of database query errors myself while trying to delete some images. Very frustrating. [[User:Mark Arsten|Mark Arsten]] ([[User talk:Mark Arsten|talk]]) 01:26, 2 November 2013 (UTC) |
|||
:::: I deleted it shortly after this bug resolved itself. Things have been kinda sketchy on the deletions for the last day of two, where I get the "Wikimedia Error" page. Then I would go back and see if the file had actually gotten deleted, and sometimes it was and sometimes not :/ -- [[User:Diannaa|Diannaa]] ([[User talk:Diannaa|talk]]) 01:29, 2 November 2013 (UTC) |
|||
:::::Right now it seems like I can't delete the last four files in [[:Category:Orphaned non-free use Wikipedia files as of 25 October 2013]]. Any luck there? [[User:Mark Arsten|Mark Arsten]] ([[User talk:Mark Arsten|talk]]) 01:44, 2 November 2013 (UTC) |
|||
::::::It took a lot longer than it should have, but [[:File:Cfnews13.jpg]] deleted successfully on the first try. - [[User:The Bushranger|The Bushranger]] <sub><font color="maroon">[[User talk:The Bushranger|One ping only]]</font></sub> 09:36, 2 November 2013 (UTC) |
|||
== jQuery UI CSS may no longer load by default == |
|||
See http://lists.wikimedia.org/pipermail/wikitech-l/2013-October/072779.html. As of next week, jQuery UI may not be loaded by default on some wikis. I'm not sure if this is true here - we might have something enabled for all visitors that includes jQuery UI - but if we do lose this CSS, templates like {{tl|clickable button 2}} and {{tl|help pages header}} will suffer. (What's worse, many logged-in users won't notice, since gadgets like Twinkle include jQuery UI.) — <span style="border:dashed #666;border-width:1px 0 0 1px">[[User:This, that and the other|This, that]]</span> and <span style="border:dashed #666;border-width:0 1px 1px 0">[[User talk:This, that and the other|the other<small> (talk)</small>]]</span> 01:59, 2 November 2013 (UTC) |
|||
:Hmm... {{tlf|clickable button 2}} just makes a plain link for me ([[Special:PermaLink/579881658|see my test]]). {{tlf|help pages header}} is just a horizontal list of links with bold formatting. Have the styles already been disabled? Does this depend on skin? (I'm using Monobook.) Does it require some gadget to be enabled? (I've disabled most gadgets, including many of the defaults.) |
|||
:The e-mail you link to mentions editing [[MediaWiki:common.js|common.js]] to re-enable the styling, not [[MediaWiki:common.css|common.css]] as one would expect for CSS. Is this in fact a JavaScript effect and not CSS? (I have JS disabled.) – '''[[User:PartTimeGnome|PartTimeGnome]]''' <span style="font-size:79%">([[User talk:PartTimeGnome|talk]] | [[Special:Contributions/PartTimeGnome|contribs]])</span> 16:11, 2 November 2013 (UTC) |
|||
::Since jQuery UI is a javascript library, its accompanying CSS is indeed only loaded through javascript. Instead of relying on jQuery UI, we migh consider using [[:mw:ResourceLoader/Default modules#mediawiki.ui|MediaWiki.UI]] for pretty buttons instead, or have all buttons styled pretty by default. <span style="font-family:'Trebuchet MS'"> — [[User:Edokter|<span style="color:#008"><i>E</i>dokter</span>]] ([[User talk:Edokter|<span style="color:#080">talk</span>]]) — </span> 16:27, 2 November 2013 (UTC) |
|||
:::Is 'mediawiki.ui' module loaded by default? [[User:Ruslik0|Ruslik]]_[[User Talk:Ruslik0|<span style="color:red">Zero</span>]] 19:19, 2 November 2013 (UTC) |
|||
:::: No, but there have been suggestions on making it so (and a patch pending[https://gerrit.wikimedia.org/r/#/c/87296/]). Hard to say if it will be, in the end, there was some opposition. You can always just make common.js load it here. [[User:Matma Rex|Matma Rex]] <small>[[User talk:Matma Rex|talk]]</small> 21:12, 2 November 2013 (UTC) |
|||
::::: Might as well just load jquery UI from common.js here then, since we already have templates relying on that. Plus there's the standards thing. <font style="color:#0059B2;text-shadow:0px 0px 5px #80BFFF">[[User:Equazcion|<font color="#0059B2">equazcion</font>]] [[User talk:Equazcion|<font color=#0059B2>→</font>]] <span style="font-size:88%">21:16, 2 Nov 2013 (UTC)</span></font> |
|||
:{{od|::::}}Looking at the [//bits.wikimedia.org/en.wikipedia.org/load.php?debug=true&modules=mediawiki.ui&only=scripts&skin=monobook&* mediawiki.ui JavaScript] (or lack thereof), mediawiki.ui is [//bits.wikimedia.org/en.wikipedia.org/load.php?debug=true&modules=mediawiki.ui&only=styles&skin=monobook&* pure CSS]. jQuery, on the other hand, does a lot of fancy dancing with its scripts, dynamically changing the styles on a button when various events occur (some of which could be done better with CSS pseudo-classes). I don't think there's any hope of getting the jQuery buttons to work without JavaScript. Mediawiki.ui would definitely be preferable because it can work without JavaScript. |
|||
:Obviously, loading mediawiki.ui from common.js would be a bit silly (why make pure CSS depend on JavaScript?). An option that would work for everyone would be to make it a dependency of a default-on gadget (the gadget itself wouldn't need to do anything; it's just there to pull in mediawiki.ui). – '''[[User:PartTimeGnome|PartTimeGnome]]''' <span style="font-size:79%">([[User talk:PartTimeGnome|talk]] | [[Special:Contributions/PartTimeGnome|contribs]])</span> 17:16, 3 November 2013 (UTC) |
|||
::What about loading https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&modules=mediawiki.ui&only=styles&skin=vector&* from common.css?[[User talk:Helder.wiki|Helder]] 10:19, 4 November 2013 (UTC) |
|||
::FYI: the reason that we stopped loading jquery.ui by default is both for performance reasons (latency improved visibly after doing this), and because the longterm plan is standardizing on mediawiki.ui as the CSS for controls like buttons. There's a lot of work to be done, but there's a biweekly hack day where WMF engineers are working on this now, so good things are on the way. :) <font style="font-family:Georgia, serif;">[[User:Steven (WMF)|Steven Walling (WMF)]] • [[User talk:Steven (WMF)|<span style="color: #8080b0">talk</span>]]</font> 22:46, 4 November 2013 (UTC) |
|||
:For me, it is still a button. PartTimeGnome, it's probably something specific to your setup. BTW, the [[MediaWiki:Gadget-teahouse.js|Teahouse gadget]] (which is really just a loader) used [https://en.wikipedia.org/w/index.php?title=MediaWiki%3AGadgets-definition&diff=580227046&oldid=575960420 to depend] on jquery.ui.button. However, this was not necessary since there's a using in [[MediaWiki:Gadget-teahouse/content.js]] before it's really needed anyway. [[User:Legoktm|Legoktm]] and I talked about this, and he removed the gadget dependencies just now. |
|||
:As far as jquery.ui.button, I think loading it from Common.js is simplest (although wikitext only uses the CSS, other modules use the JS too, so we shouldn't load just the CSS somehow). However, I verified a gadget that depends on jquery.ui.button and has a no-op CSS file (just a comment) will also work (there ''does'' need to be a file). The downside is this adds to preference bloat with something most users won't understand or care about. [[User:Superm401|Superm401]] - [[User_talk:Superm401|Talk]] 00:01, 5 November 2013 (UTC) |
|||
::[[User:Edokter|Edokter]] already identified what causes the problem for me: the jQuery CSS is only loaded from JavaScript (which I have disabled). I took a further look myself, and I'm not sure the jQuery CSS would work on its own anyway (someone please correct me if I'm wrong there). My preference would be to switch to mediawiki.ui for button styling since it is pure CSS. (And [[User:Steven (WMF)|Steven]] indicated MediaWiki is moving that way anyway.) – '''[[User:PartTimeGnome|PartTimeGnome]]''' <span style="font-size:79%">([[User talk:PartTimeGnome|talk]] | [[Special:Contributions/PartTimeGnome|contribs]])</span> 22:09, 5 November 2013 (UTC) |
|||
== [[Wikipedia talk:Persondata-o-matic]] editing rights == |
|||
Hi there. I've got a problem using the above, it says that I've not got the right to edit the article in question every time I try to use it on an article and then click 'save'. I've browsed the docs for the gadget and messaged the creator with no response. Anyone know a fix or what I'm doing wrong? --[[User:SGGH|S.G.<sup><small>(GH)</small></sup>]] <sub>[[User_talk:SGGH|ping!]]</sub> 20:14, 2 November 2013 (UTC) |
|||
:The author of the tool, [[User:Dcoetzee]], last edited six hours before you posted your problem at [[Wikipedia talk:Persondata-o-matic]]. Since you also sent him an email, it looks like you'll have to wait until he returns to Wikipedia matters. -- <font style="font-family:Monotype Corsiva; font-size:15px;">[[User:John Broughton|John Broughton]] </font> [[User talk:John Broughton |(♫♫)]] 04:43, 5 November 2013 (UTC) |
|||
== Tylenol == |
|||
{{la|tylenol}} |
|||
There's something up on the page. The "Advertisement" header shows up in the TOC, but it's blank in the text itself, and the link it broken. I've examined the Wikimarkup and can't figure out what's wrong. All the ref tags are closed, so what is causing this problem? [[User:Hbdragon88|hbdragon88]] ([[User talk:Hbdragon88|talk]]) 07:52, 3 November 2013 (UTC) |
|||
:Slight correction: the header was ==Advertisements== (plural). I've confirmed your observation. After I disabled AdBlock Plus for Wikipedia pages, however, the header, and the correct TOC link operation, reappeared. As a workaround, I've changed the header to ==Marketing==. {{U|Hbdragon88}}, did this resolve your issue? You can test your browser/plugin behavior against a prior revision of [[Tylenol]]. --[[User:Lexein|Lexein]] ([[User talk:Lexein|talk]]) 08:09, 3 November 2013 (UTC) |
|||
== Revert oversights edit? == |
|||
There was [https://en.wikipedia.org/w/index.php?title=Post&curid=230424&action=history an edit to Post that was reverted], and it seems that the edit was oversighted out of existance. [[Help:User contributions]] doesn't explain what a struck-out edit means, and [[Help:Reverting]] doesn't mention that this could happen. [[User:Eeekster]] is not a sysop or 'crat; I can't tell if they're an oversighter. If I remember correctly, oversighting actions are logged as such anyways - and there's nothing in [https://en.wikipedia.org/w/index.php?title=Special:Log&offset=20131102232142&limit=50&type=&user= the logs for the appropriate time]. So what happened? [[User_talk:Josh Parris|Josh Parris]] 09:49, 3 November 2013 (UTC) |
|||
:The suppression log is also private. --'''[[User:Rschen7754|Rs]][[User talk:Rschen7754|chen]][[Special:Contributions/Rschen7754|7754]]''' 09:55, 3 November 2013 (UTC) |
|||
::So, suppression is undocumented (in the help pages) and privately logged. Orwellian. [[User_talk:Josh Parris|Josh Parris]] 10:14, 3 November 2013 (UTC) |
|||
:::[[Help:User contributions#Deletion]] says: "In some limited circumstances individual contributions (that is, specific edits) may be removed from public view by [[WP:ADMIN|administrators]] using [[WP:REVDEL|Revision Deletion]]; such edits remain visible to administrators. In even more limited circumstances edits may be [[WP:OVERSIGHT|oversighted]], remaining visible only to the handful of users with the Oversight permission." The link on "[[WP:REVDEL|Revision Deletion]]" shows how it looks. There is no secrecy about the existence of the feature. It's just a question of how much overlap to have between help pages. [[User:PrimeHunter|PrimeHunter]] ([[User talk:PrimeHunter|talk]]) 10:58, 3 November 2013 (UTC) |
|||
:::Also, if you think Oversight is being misused, you can raised the matter [[Wikipedia:Arbitration Committee/Audit Subcommittee|here]]. [[User:Mark Arsten|Mark Arsten]] ([[User talk:Mark Arsten|talk]]) 19:00, 3 November 2013 (UTC) |
|||
:The only ''real'' fix to the problem is to have live updated mirrors that aren't under the same administration. I'd like to tell them not to do it, but you know full well that they may feel they have no choice under governments with a quite imperfect notion of what 'free expression' is about, and once they start doing it at all it is just so enticing to keep going further, gradually growing and expanding their godlike powers. [[User:Wnt|Wnt]] ([[User talk:Wnt|talk]]) 15:53, 3 November 2013 (UTC) |
|||
::I don't know where oversights might be logged. Example: [//en.wikipedia.org/w/index.php?title=Wikipedia_talk:Contact_us&action=history&limit=4&offset=20131030093000 here are two edits] which I [[WP:REVDEL]]led; so it's my name in [//en.wikipedia.org/w/index.php?title=Special:Log&page=Wikipedia+talk%3AContact+us&limit=1&offset=20131030093000 the deletion log]. I then sent an email to [[Special:EmailUser/Oversight]] - the oversight action took place within an hour, and I got an email back from [[Special:ListUsers/oversight|one of the oversighters]] stating (amongst other info) "We appreciate you bringing this to our attention, and a member of the Oversight team has suppressed the information in question. Thanks for the vigilance, and please let us know of any other edits needing suppression that you see in the future." I ''presume'' that it was sent by the person who actually carried out the oversight action. But I have looked at the ''visible'' logs of actions carried out by that person, and I do not see an applicable entry. --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] ([[User talk:Redrose64|talk]]) 19:48, 3 November 2013 (UTC) |
|||
:::Oversight logs are only visible to oversighters. See [[Wikipedia:Oversight#Logging]]. [[User:PrimeHunter|PrimeHunter]] ([[User talk:PrimeHunter|talk]]) 20:16, 3 November 2013 (UTC) |
|||
::::FWIW, the log is at [[Special:Log/suppress]], though you need the OS bit to see it. --'''[[User:Rschen7754|Rs]][[User talk:Rschen7754|chen]][[Special:Contributions/Rschen7754|7754]]''' 10:35, 4 November 2013 (UTC) |
|||
*Let me start by saying that although I have suppression rights I am not familiar with this specific case and have not investigated who did the suppression. So, for starters, no there is no public log of who did which suppression action. And no, the team will not explain itself to the community. I know, that sounds terrible, but our primary function is to protect privacy and remove libel. In order to accomplish this by necessity we cannot discuss it openly. However, if you wish to challenge a suppression action you may contact [[WP:AUSC|the audit subcommittee]], whose job it is to review the work of the oversight and checkuser teams and insure they are acting in accordance with the applicable policies and not overstepping their bounds or using their permissions abusively. It is my understanding that that process is also anonymous, only the members of the subcommittee know both the identity of the oversighter or checkuser who took the action and that of the user who made the report. [[User:Beeblebrox|Beeblebrox]] ([[User talk:Beeblebrox|talk]]) 20:09, 3 November 2013 (UTC) |
|||
*: I could wish for more transparency. While I understand that you cant remove content to avoid privacy violations and then say wht that content was, it surely would be possible to log who did any particular oversight action, and even to indicate a general category of content removed (attack, defamation, personal info, outsourced contentious content that violates BLP, OTRS action, or whatever). None of that would violae anyone's privacy or perpetuate any libel. [[User:DESiegel|DES]] [[User talk:DESiegel|<sup>(talk)</sup>]] 01:58, 4 November 2013 (UTC) |
|||
*::Equally, you could say "removed libellous statement about Ronald Regan" or "suppressed Privacy violating information on Donald Duck" or whatever. Those without suppression rights would have some idea of what happened, but there's also [[WP:BEANS]]. Regardless, the software doesn't allow, so: meh. [[User_talk:Josh Parris|Josh Parris]] 02:33, 4 November 2013 (UTC) |
|||
*:::However, there are some cases when revealing why an edit was suppressed would be just as bad as revealing the contents of the edit. (For the record, I am not an oversighter here, though I am on Wikidata). --'''[[User:Rschen7754|Rs]][[User talk:Rschen7754|chen]][[Special:Contributions/Rschen7754|7754]]''' 10:37, 4 November 2013 (UTC) |
|||
== Superfluous line-break in template == |
== Superfluous line-break in template == |
||
Line 321: | Line 182: | ||
*I suppose theother alternative is just to cut the article? --[[User:RoslynSKP|Rskp]] ([[User talk:RoslynSKP|talk]]) 01:15, 11 November 2013 (UTC) |
*I suppose theother alternative is just to cut the article? --[[User:RoslynSKP|Rskp]] ([[User talk:RoslynSKP|talk]]) 01:15, 11 November 2013 (UTC) |
||
**A first step would be to try my suggestion, so I edited [[User:RoslynSKP/Southern Palestine Offensive]] to replace the convert templates, although I used {{tl|convert/q}} ("quick") which was created recently for use on an article where {{tl|convert}} was apparently causing the page to time out (the "/q" and "/sandboxlua" templates currently do the same thing). I checked the displayed text before and after the change, and there is only a single difference, namely where the new template has reported that one of the converts is invalid. To see that, search the page for "convert" (the displayed page, not the wikitext). You possibly want to change the output "g" (grams) to "impgal" (imperial gallons), or omit "|g" for the default which is imperial and US gallons. [[User:Johnuniq|Johnuniq]] ([[User talk:Johnuniq|talk]]) 05:50, 11 November 2013 (UTC) |
**A first step would be to try my suggestion, so I edited [[User:RoslynSKP/Southern Palestine Offensive]] to replace the convert templates, although I used {{tl|convert/q}} ("quick") which was created recently for use on an article where {{tl|convert}} was apparently causing the page to time out (the "/q" and "/sandboxlua" templates currently do the same thing). I checked the displayed text before and after the change, and there is only a single difference, namely where the new template has reported that one of the converts is invalid. To see that, search the page for "convert" (the displayed page, not the wikitext). You possibly want to change the output "g" (grams) to "impgal" (imperial gallons), or omit "|g" for the default which is imperial and US gallons. [[User:Johnuniq|Johnuniq]] ([[User talk:Johnuniq|talk]]) 05:50, 11 November 2013 (UTC) |
||
== [[m:Special:MyLanguage/Tech/News/2013/44|Tech News: 2013-44]] == |
|||
<div class="plainlinks mw-content-ltr" lang="en" dir="ltr"> |
|||
Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please inform other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2013/44|Translations]] are available. |
|||
'''New features''' |
|||
* The style and colors for warning boxes, error messages, and success messages in all skins of MediaWiki has been changed. [https://gerrit.wikimedia.org/r/#/c/82828/] |
|||
'''[[mw:Special:MyLanguage/VisualEditor/Portal|VisualEditor]] news''' |
|||
* You will soon be able to switch from editing in VisualEditor to editing wikitext directly without having to save the page. You can't yet switch from wikitext to VisualEditor but developers hope to make it possible in the future. [https://bugzilla.wikimedia.org/show_bug.cgi?id=50687] |
|||
'''Problems''' |
|||
* There was a problem on October 31 during the activation of [[mw:MediaWiki 1.22/wmf2|MediaWiki 1.22wmf2]] on test wikis. mediawiki.org was also broken, and if you had problems logging in, it was probably because of this as well. |
|||
'''Future''' |
|||
* Because of the problem with [[mw:MediaWiki 1.22/wmf2|MediaWiki 1.22wmf2]], the calendar has changed. It will be added to mediawiki.org and non-Wikipedia sites on November 4, and all Wikipedia sites on November 7. |
|||
'''JavaScript / Gadget developers''' |
|||
* Due to a recent change, gadgets and user scripts that use jQuery UI should explicitly load the appropriate modules, as they may not be loaded by default. [http://lists.wikimedia.org/pipermail/wikitech-ambassadors/2013-October/000471.html] |
|||
* Developers have started to remove long-deprecated methods. You should check the JavaScript console (in <code>debug=true</code> mode) and look for deprecation warnings and their stack trace. [http://lists.wikimedia.org/pipermail/wikitech-ambassadors/2013-October/000472.html] |
|||
'''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/Ambassadors|tech ambassadors]] and posted by [[m:Global message delivery|Global message delivery]] • [[m:Special:MyLanguage/Tech/News#contribute|Contribute]] • [[m:Special:MyLanguage/Tech/News/2013/44|Translate]] • [[m:Tech|Get help]] • [[m:Talk:Tech/News|Give feedback]] • [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' |
|||
</div> 10:36, 4 November 2013 (UTC) |
|||
<!-- EdwardsBot 0619 --> |
|||
::version [[mw:MediaWiki 1.22/wmf2|MediaWiki 1.22wmf2]] is mentioned above in couple places, with future reference. this version was deployes last April, so most probably this is a typo, and meant to be [[mw:MediaWiki 1.23/wmf2|MediaWiki 1.23wmf2]]. peace - [[User:קיפודנחש|קיפודנחש (aka kipod)]] ([[User talk:קיפודנחש|talk]]) 18:19, 4 November 2013 (UTC) |
|||
== Module:Pagetype == |
|||
I've created [[Module:Pagetype]], a replacement for {{tl|pagetype}}, and I am thinking of updating the template to the Lua version later on this week. The Lua version has some differences from the current template, and {{tl|pagetype}} has around 5 million transclusions, so I would like to get others' comments before making the switch. Please let me know your thoughts over at [[Template talk:Pagetype#Module:Pagetype]]. — '''''[[User:Mr. Stradivarius|<span style="color: #194D00; font-family: Palatino, Times, serif">Mr. Stradivarius</span>]]''''' <sup>[[User talk:Mr. Stradivarius|♪ talk ♪]]</sup> 14:18, 4 November 2013 (UTC) |
|||
== The Wikipedia Adventure: Quick bug-help == |
|||
Hey folks, |
|||
If you're ''logged in'' could you go [https://en.wikipedia.org/wiki/WP:TWA/1/Start?tour=twa2&step=14 here], then click CONTRIBUTIONS. And tell me if the game advances to the next step ("All your work"). I've had 2 bug reports, both with Firefox 24.0+ that it's causing a loop. Cannot replicate on my end. Multiple tries or different browsers would be much appreciated. Best, Jake [[User:Ocaasi|Ocaasi]]<sup> [[User talk:Ocaasi|t ]]|[[Special:Contributions/Ocaasi| c]]</sup> 14:54, 4 November 2013 (UTC) |
|||
:Can't seem to reproduce it here. Firefox 25, Chrome 30, Opera 17. <font style="color:#0059B2;text-shadow:0px 0px 5px #80BFFF">[[User:Equazcion|<font color="#0059B2">equazcion</font>]] [[User talk:Equazcion|<font color=#0059B2>→</font>]] <span style="font-size:88%">15:09, 4 Nov 2013 (UTC)</span></font> |
|||
:Although it does seem that every page you go to afterwards shows the adventure message box, until you explicitly 'X' it out. Maybe that's the "loop" they're referring to? <font style="color:#0059B2;text-shadow:0px 0px 5px #80BFFF">[[User:Equazcion|<font color="#0059B2">equazcion</font>]] [[User talk:Equazcion|<font color=#0059B2>→</font>]] <span style="font-size:88%">15:11, 4 Nov 2013 (UTC)</span></font> |
|||
: Yes, I can reproduce this on FF24. It is a endless loop as long as you hit "Contributions". If you hit the {{Button|←|style=background: #00F; color: #FFF;}} it advances to the next stage. If you open any other page after that it also shows the next stage (for me, but I did it after hitting back which took me forward). I have screenshots if you need, let me know. [[User:Technical 13|Technical 13]] ([[User talk:Technical 13|talk]]) 15:39, 4 November 2013 (UTC) |
|||
::{{U|Ocaasi}}, it's only happening for users with spaces in their usernames. In step 14, you're comparing wgUserName with the page address -- one has underscores in place of spaces and the other doesn't, so the script is not detecting that the contributions page has been reached. <font style="color:#0059B2;text-shadow:0px 0px 5px #80BFFF">[[User:Equazcion|<font color="#0059B2">equazcion</font>]] [[User talk:Equazcion|<font color=#0059B2>→</font>]] <span style="font-size:88%">15:48, 4 Nov 2013 (UTC)</span></font> |
|||
:::Nice catch, {{U|Equazcion}}! Any idea for a fix? [[User:Ocaasi|Ocaasi]]<sup> [[User talk:Ocaasi|t ]]|[[Special:Contributions/Ocaasi| c]]</sup> 15:50, 4 November 2013 (UTC) |
|||
::::*<code>return gt.isPage( 'Special:Contributions/' + mw.config.get( 'wgUserName' ).replace(/ /g, '_') );</code> |
|||
::::I ''think'' that might do it. <font style="color:#0059B2;text-shadow:0px 0px 5px #80BFFF">[[User:Equazcion|<font color="#0059B2">equazcion</font>]] [[User talk:Equazcion|<font color=#0059B2>→</font>]] <span style="font-size:88%">15:53, 4 Nov 2013 (UTC)</span></font> |
|||
:::::Trying that now. Thanks! [[User:Ocaasi|Ocaasi]]<sup> [[User talk:Ocaasi|t ]]|[[Special:Contributions/Ocaasi| c]]</sup> 16:01, 4 November 2013 (UTC) |
|||
{{Outdent}} {{U|Equazcion}}, it works!! [[User:Ocaasi TWA|Ocaasi TWA]] ([[User talk:Ocaasi TWA|talk]]) 16:04, 4 November 2013 (UTC) |
|||
:Awesome! Glad I could help :) <font style="color:#0059B2;text-shadow:0px 0px 5px #80BFFF">[[User:Equazcion|<font color="#0059B2">equazcion</font>]] [[User talk:Equazcion|<font color=#0059B2>→</font>]] <span style="font-size:88%">16:07, 4 Nov 2013 (UTC)</span></font> |
|||
== Idea on meta about LaTeX export. Is it a feature request in bugzilla? == |
|||
I like the ideas stated in [[m:Grants talk:IEG/LaTeX Export]]. Might someone who is experienced with bugzilla track it or say whether or not it is being tracked? Thanks. [[User:Biosthmors|Biosthmors]] ([[User talk:Biosthmors|talk]]) <small>pls [[Wikipedia:Notifications#Features|notify]] me (i.e. {{[[Template:U|U]]}}) while signing a reply, thx</small> 16:08, 4 November 2013 (UTC) |
|||
:I cannot find a ticket so feel free to [https://www.mediawiki.org/wiki/How_to_report_a_bug file one]. --[[User:AKlapper (WMF)|AKlapper (WMF)]] ([[User talk:AKlapper (WMF)|talk]]) 11:10, 6 November 2013 (UTC) |
|||
::See [[bugzilla:37933]] and [[bugzilla:27574]]. [[User talk:Helder.wiki|Helder]] 15:11, 6 November 2013 (UTC) |
|||
== Mysterious watchlist entries == |
|||
Every few days, something appears in my watchlist that I don't remember needing to watch. Sometimes, I can explain it after a bit of checking, since I occasionally watch a page that I've never edited because it's the subject of a discussion that I'm involved in - for example, I've watched [[Template:LUL Platform Layout Metropolitan/island]] because I've contributed to [[Wikipedia:Templates for discussion/Log/2013 November 3#LUL platform layout templates|its TfD]]. But occasionally, I simply can't explain why a particular page is on my watchlist - one such case that's appeared today is [[Template:PBB/2492]], which I've never edited, and nor do I have any knowledge of (or interest in) this ... er, "Follicle stimulating hormone receptor", something biological I guess. I'm wondering if somebody else has attempted to watch this page but some database error has caused it to be put on my watchlist. Does that seem plausible? --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] ([[User talk:Redrose64|talk]]) 16:43, 4 November 2013 (UTC) |
|||
:You deleted [[Template talk:PBB/2492|its talk page]] in June. -- [[User:John of Reading|John of Reading]] ([[User talk:John of Reading|talk]]) 17:00, 4 November 2013 (UTC) |
|||
::OK, thanks; can you explain [[Robert Tappan Morris]]? --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] ([[User talk:Redrose64|talk]]) 22:37, 4 November 2013 (UTC) |
|||
:::Above at [[#Infobox criminal is turning programmers into murderers]] you replied to a post about that article and clearly viewed it. I guess you clicked watch on that occasion, maybe by accident. [[User:PrimeHunter|PrimeHunter]] ([[User talk:PrimeHunter|talk]]) 23:58, 4 November 2013 (UTC) |
|||
::::I did view it (twice), once to verify that there was an unwanted heading, and once after I'd fixed the infobox template that JohnnyMrNinja had mentioned, in order to verify that the heading had gone. But I didn't need to go for "edit this page" on [[Robert Tappan Morris]] because I was certain that the problem was in the infobox template. --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] ([[User talk:Redrose64|talk]]) 00:25, 5 November 2013 (UTC) |
|||
== Corrupted non-ASCII characters == |
|||
{{tracked|56583}} |
|||
For about an hour today (between 19:45 and 20:40 UTC) a bug in the MediaWiki parsoid caused all non-ASCII characters to be corrupted on page save. So if you see any strange diffs in your watchlist, for example, accented characters changing to garbage characters, please correct or revert them. A full postmortem on the problem will be released shortly. [[User:Kaldari|Kaldari]] ([[User talk:Kaldari|talk]]) 22:06, 4 November 2013 (UTC) |
|||
:i believe that this issue pertains to VE edits only. it should not be all that difficult to look for all changes with "visualeditor" tag within the time-window where the problem existed, and make sure all is good. for unrelated reason, VE is off by default on enwiki, so no anon edits should be affected, and it seems that relatively small number of registered uses use it (at least, the number of edits with the tag is not huge). peace - [[User:קיפודנחש|קיפודנחש (aka kipod)]] ([[User talk:קיפודנחש|talk]]) 00:47, 6 November 2013 (UTC) |
|||
::followed my own advice. found 3 pages with some corruptions that were not fixed yet, and rolled them back. ignored pages where the history contains summaries with "ooopsie" and/or swearwords towards VE in edits following the corruption window, and pages in userspace. hopefully these were the last 3. peace - [[User:קיפודנחש|קיפודנחש (aka kipod)]] ([[User talk:קיפודנחש|talk]]) 01:44, 6 November 2013 (UTC) |
|||
== User Talk page message == |
|||
When developers got rid of the orange bar across the top of the page showing new messages on user talk pages, new messages were highlighted in orange around the talk link in the user menu. However in the last couple of days even this has disappeared, only appearing a day late in the notifications. Why? [[User:Simply south|Simply]][[User talk:Simply south| south]]....[[User:Simply south/Poem|..]] ''cooking letters for just 7 years'' 22:49, 4 November 2013 (UTC) |
|||
:There was a bug in which the orange bar didn't show up for monobook/modern skins. This has been fixed, but I'm not sure if it has been deployed yet. [[User:Legoktm|Legoktm]] ([[User talk:Legoktm|talk]]) 23:24, 4 November 2013 (UTC) |
|||
::It's been more than a couple of days, see [[Wikipedia:Village pump (technical)/Archive 119#Talkpage notification]]. --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] ([[User talk:Redrose64|talk]]) 00:10, 5 November 2013 (UTC) |
|||
:::If it has been fixed, why did I experience this on Saturday? [[User:Difficultly north|Difficultly north]] ([[User talk:Difficultly north|talk]]) - ''<small>Simply south alt.</small>'' 12:08, 5 November 2013 (UTC) |
|||
:::: Because, as mentioned by Lego above, it has not been deployed yet. It was "fixed", which means code has been written and committed ("saved"); it was not deployed, which means that Wikipedia is not running that code yet. [[User:Matma Rex|Matma Rex]] <small>[[User talk:Matma Rex|talk]]</small> 13:04, 5 November 2013 (UTC) |
|||
:When will it be deployed? '''[[User:Lugnuts|<font color="002bb8">Lugnuts</font>]]''' <sup>[[User talk:Lugnuts|Dick Laurent is dead]]</sup> 13:25, 5 November 2013 (UTC) |
|||
:: No later than November 14 (per [[mw:MediaWiki 1.23/Roadmap]]). Maybe sooner if it is backported, but that's usually reserved for critical patches, and this is at worst annoying :) [[User:Matma Rex|Matma Rex]] <small>[[User talk:Matma Rex|talk]]</small> 13:35, 5 November 2013 (UTC) |
|||
== Notification tool not working == |
|||
[[File:Notifications-Flyout-Screenshot-08-10-2013-Cropped.png|thumb|right]] |
|||
For the past couple of days, the notification tool hasn't been working properly for me. I'm seeing the white number in the red box (see diagram right), but I can't click on it to display the actual notifications (when I hover over the number, my pointer stays as an arrow, it doesn't change to a hand). I don't ''think'' I've changed any preferences. I'm using IE9 on Windows 7 with the Monobook skin. Thanks. [[User:DH85868993|DH85868993]] ([[User talk:DH85868993|talk]]) 03:52, 5 November 2013 (UTC) |
|||
:Did you go to [[Special:Notifications]] to see if you actually have notifications? ~[[User:HueSatLum|Hue]][[User talk:HueSatLum#top|Sat]][[Special:Contributions/HueSatLum|Lum]] 03:56, 5 November 2013 (UTC) |
|||
::Yes, and I did. It seems to be exactly the same problem as was reported [[Wikipedia:Village_pump_(technical)/Archive_116#Problem_with_Notifications_Box|here]] (where, unfortunately, there was no resolution). [[User:DH85868993|DH85868993]] ([[User talk:DH85868993|talk]]) 03:57, 5 November 2013 (UTC) |
|||
:::Pinging [[User:Quiddity]] who's usually knowledgeable about this stuff :) --[[User:Elitre|Elitre]] ([[User talk:Elitre|talk]]) 10:55, 5 November 2013 (UTC) |
|||
:::: {{U|AKlapper (WMF)|Andre}}, I'm wondering if this has anything to do with the enhanced recent changes bug I've been experiencing the last few weeks where the arrows aren't expanding. Refreshing the page (sometimes multiple times is required) fixes the issue. I am using FF24 and have seen many quirks like this with it on this site and other sites (which indicates to me that it's likely not a MediaWiki bug). ''If'' I can track down the cause (or come up with a plausible explanation) and a solid set of steps to reproduce, I'll file an appropriate report on Bugzilla, of course. (I accidentally posted this on the archive as well, but thought better of it and am putting a copy here. I'm leaving the post on the archive for now because I pinged Andre there as well and don't want confusion. Not a biggie to leave it there as well.) [[User:Technical 13|Technical 13]] ([[User talk:Technical 13|talk]]) 12:53, 5 November 2013 (UTC) |
|||
:::::The notifications figure is supposed to be clickable even if it's a greyed-out zero. As such, it's working for me in Firefox 24 under Windows XP - I don't know if I have "enhanced recent changes" or not because I can't find it in {{myprefs}}. --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] ([[User talk:Redrose64|talk]]) 14:38, 5 November 2013 (UTC) |
|||
:{{od|::::}}I think [[User:Technical 13|Technical 13]] is referring to the "{{int:tog-usenewrc}}" preference. – '''[[User:PartTimeGnome|PartTimeGnome]]''' <span style="font-size:79%">([[User talk:PartTimeGnome|talk]] | [[Special:Contributions/PartTimeGnome|contribs]])</span> 21:48, 5 November 2013 (UTC) |
|||
:OK, I tried that both enabled and disabled - the greyed out zero is clickable in both cases. --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] ([[User talk:Redrose64|talk]]) 00:50, 6 November 2013 (UTC) |
|||
::Some further info. I tried logging out and back in. Immediately after I log in, my toolbar shows "DH85868993 [0] talk preferences watchlist contributions log out" and the notification tool ("[0]") is clickable. A few seconds later, "sandbox" appears between "talk" and "preferences" and a "person" icon is displayed to the left of my username, and then the notification tool is no longer clickable. (I tried this with the "{{int:tog-usenewrc}}" preference both enabled and disabled and it was the same in both cases). [[User:DH85868993|DH85868993]] ([[User talk:DH85868993|talk]]) 01:11, 6 November 2013 (UTC) |
|||
:::In fact, I can reproduce similar behaviour by refreshing any page using my browser's refresh; when I initiate the refresh, "sandbox" and the "person icon" disappear from my toolbar and the notification tool is briefly clickable; when the refresh completes, "sandbox" and the "person icon" reappear and the notification tool is no longer clickable. [[User:DH85868993|DH85868993]] ([[User talk:DH85868993|talk]]) 01:26, 6 November 2013 (UTC) |
|||
== Problem with [[Brazilian wandering spider]] == |
|||
The [[Brazilian wandering spider]] page has something weird which I can't fix. |
|||
The references and citations are not showing on the page but if you look at the source code they are all there. Can someone else have a look as I couldn't fix it. [[User:Filceolaire|filceolaire]] ([[User talk:Filceolaire|talk]]) 14:01, 5 November 2013 (UTC) |
|||
:Fixed. The trick in cases like this is to find the last visible text, and look hard at the markup that follows it, as that's probably where the error is. -- [[User:John of Reading|John of Reading]] ([[User talk:John of Reading|talk]]) 14:11, 5 November 2013 (UTC) |
|||
== Secure links == |
|||
Is there something I can add to my js or css that makes it so raw URLs to other Wikipedia pages (like to diff pages or whatever) do not direct me to the HTTPS version?—[[User:Ryulong|Ryulong]] ([[User talk:Ryulong|琉竜]]) 14:05, 5 November 2013 (UTC) |
|||
:I don't think so. If the Javascript implementation within MediaWiki permitted URLs to be modified, we'd be open to all sorts of problems. If I'm replying to a thread which contains hardcoded https://en.wikipedia.org/ links, I often remove the https: part and if it was a bare URL, I also enclose in single square brackets, because the protocol-relative form doesn't work outside square brackets - compare //en.wikipedia.org/ with [//en.wikipedia.org/]. --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] ([[User talk:Redrose64|talk]]) 14:48, 5 November 2013 (UTC) |
|||
::{{ping|Ryulong}} [[User:PiRSquared17/nosecure.js]]. [[User:PiRSquared17|<b style="color:#f90;font-family:Arial">πr<sup>2</sup></b>]] ([[User talk:PiRSquared17|<i style="color:#0f3;font-family:Arial">'''t'''</i>]] • [[Special:Contributions/PiRSquared17|<i style="color:#03f;font-family:Arial">'''c'''</i>]]) 17:01, 5 November 2013 (UTC) |
|||
:::Thank you.—[[User:Ryulong|Ryulong]] ([[User talk:Ryulong|琉竜]]) 17:14, 5 November 2013 (UTC) |
|||
== Wikipedia mobile page have a bug for sister project links == |
|||
I found Wikipedia mobile page cannot show sister project links (which is formed of {{tl|Sister}}) when I read some articles, I hope you can solve the problem, thanks.--[[User:Great Brightstar|Great Brightstar]] ([[User talk:Great Brightstar|talk]]) 14:25, 5 November 2013 (UTC) |
|||
:This is a known issue with anything constructed using {{tlx|side box}} and it's because of the <code>metadata</code> class (see [[Wikipedia:Village pump (technical)/Archive 116#'Listen' template not rendering in mobile view]] and [[Wikipedia:Village pump (technical)/Archive 116#CfDs in mobile view]]). We can fix {{tlx|sister}} by adding {{para|metadata|no}} within {{tlx|side box}} - but this should not be done without discussion. --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] ([[User talk:Redrose64|talk]]) 14:58, 5 November 2013 (UTC) |
|||
==Unable to do anything through IE8== |
==Unable to do anything through IE8== |
||
Line 538: | Line 289: | ||
::::Wonderful script! Thank you! --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 21:29, 7 November 2013 (UTC) |
::::Wonderful script! Thank you! --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 21:29, 7 November 2013 (UTC) |
||
== Search failure on "news" == |
|||
Any search involving "news" outside mainspace gives me the red error message: "An error has occurred while searching: The search backend returned an error:". Some examples: {{search link|talk:news}}, {{search link|category:news today}}, {{search link|user:no news}}, {{search link|wikipedia:good news}}. [[User:PrimeHunter|PrimeHunter]] ([[User talk:PrimeHunter|talk]]) 22:12, 5 November 2013 (UTC) |
|||
:Funky. Happens for me too. [[User:Chris857|Chris857]] ([[User talk:Chris857|talk]]) 01:31, 6 November 2013 (UTC) |
|||
: The old search engine makes me cry :( <b style="color:#c22">^</b>[[User:^demon|<b style="color:#000">demon</b>]][[User_talk:^demon|<sup style="color:#c22">[omg plz]</sup>]] <em style="font-size:10px;">02:23, 6 November 2013 (UTC)</em> |
|||
::What's even weirder is that it's not any search with the word "news" ({{search link|User:news paperclip}} works); only apparently common expressions (like {{search link|User:news paper}}) with the word return the error. ~[[User:HueSatLum|Hue]][[User talk:HueSatLum#top|Sat]][[Special:Contributions/HueSatLum|Lum]] 02:38, 6 November 2013 (UTC) |
|||
:That's pretty frikkin' weird brah. <font style="color:#0059B2;text-shadow:0px 0px 5px #80BFFF">[[User:Equazcion|<font color="#0059B2">equazcion</font>]] [[User talk:Equazcion|<font color=#0059B2>→</font>]] <span style="font-size:88%">02:45, 6 Nov 2013 (UTC)</span></font> |
|||
== Diff and other problems (probably IE8) == |
== Diff and other problems (probably IE8) == |
||
Line 566: | Line 308: | ||
#Well, until a few weeks ago, they didn't do that. When the window was too narrow for all of them, the ones that wouldn't fit fell into the drop-down. I wonder if someone has fixed something, because if I expand the widow to screen width and then restore it to normal size, they do fall into the drop-down. Clicking ''show preview'' munges it again, but the same procedure puts it right once more. None of that was the case a few hours ago. The expand/contract procedure works slowly -- I see the munged screen and then watch it fall slowly into place -- so I wonder if there's a timing quirk. |
#Well, until a few weeks ago, they didn't do that. When the window was too narrow for all of them, the ones that wouldn't fit fell into the drop-down. I wonder if someone has fixed something, because if I expand the widow to screen width and then restore it to normal size, they do fall into the drop-down. Clicking ''show preview'' munges it again, but the same procedure puts it right once more. None of that was the case a few hours ago. The expand/contract procedure works slowly -- I see the munged screen and then watch it fall slowly into place -- so I wonder if there's a timing quirk. |
||
--[[User:Stfg|Stfg]] ([[User talk:Stfg|talk]]) 17:28, 6 November 2013 (UTC) |
--[[User:Stfg|Stfg]] ([[User talk:Stfg|talk]]) 17:28, 6 November 2013 (UTC) |
||
== Page move == |
|||
How to move all the sub-pages of any page? Admins can only move up to 100.[[User:Bill william compton|<span style="text-shadow:gray 3px 3px 2px;"><font color="#009900"><sup></sup> — Bill william compton</font></span>]]<sup>[[User talk:Bill william compton|<font color="#000000">Talk</font>]]</sup> 13:41, 6 November 2013 (UTC) |
|||
:I think (haven't tried it) that admins can move 100 at a time, and could do n×100 in n batches if needed. Is there really a problem with that? [[User:PrimeHunter|PrimeHunter]] ([[User talk:PrimeHunter|talk]]) 15:06, 6 November 2013 (UTC) |
|||
::What's the procedure of n×100 move?[[User:Bill william compton|<span style="text-shadow:gray 3px 3px 2px;"><font color="#009900"><sup></sup> — Bill william compton</font></span>]]<sup>[[User talk:Bill william compton|<font color="#000000">Talk</font>]]</sup> 15:13, 6 November 2013 (UTC) |
|||
:::The best way to do that is probably to [[Wikipedia:Bot_requests|enlist a bot]] to execute the action. It can also be done manually trough the API, but it is rather cumbersome. —[[User:TheDJ|Th<span style="color: green">e</span>DJ]] ([[User talk:TheDJ|talk]] • [[Special:Contributions/TheDJ|contribs]]) 15:29, 6 November 2013 (UTC) |
|||
::::Problem solved. Thanks PH and TheDJ.[[User:Bill william compton|<span style="text-shadow:gray 3px 3px 2px;"><font color="#009900"><sup></sup> — Bill william compton</font></span>]]<sup>[[User talk:Bill william compton|<font color="#000000">Talk</font>]]</sup> 19:02, 6 November 2013 (UTC) |
|||
== Autoblock checker down == |
|||
I'm getting a "403: User account expired" but no indication of whose account it is. [[User:Peridon|Peridon]] ([[User talk:Peridon|talk]]) 17:03, 6 November 2013 (UTC) |
|||
I dont know if its related, but I get random "You are currently unable to edit pages on Wikipedia due to an autoblock affecting your IP address" [[User:Christian75|Christian75]] ([[User talk:Christian75|talk]]) 17:07, 6 November 2013 (UTC) |
|||
:Numerous users are caught up in that. See [[User_talk:Jimfbleak#Block?]] where a correct block of one editor seems to have had unintended knock on effects for many others. [[User:Valenciano|Valenciano]] ([[User talk:Valenciano|talk]]) 17:14, 6 November 2013 (UTC) |
|||
::Err, no - I'm not suffering from autoblock. I was trying to check if a blocked editor was autoblocked. This is a Toolserver account problem - if you don't go into an account there for six months they cut you off. Damn nuisance on some of the main things hosted there. [[User:Peridon|Peridon]] ([[User talk:Peridon|talk]]) 17:18, 6 November 2013 (UTC) |
|||
:::Just found it - it's User:Nakon. [[User:Peridon|Peridon]] ([[User talk:Peridon|talk]]) 17:28, 6 November 2013 (UTC) |
|||
::::There's a temp replacement [https://toolserver.org/~tparis/autoblock/autoblockfinder.php here] courtesy of {{U|TParis}}.--[[User:Ponyo|<b><font color="Navy">''Jezebel's''</font></b><font color="Navy">Ponyo</font>]]<sup>[[User_talk:Ponyo|<font color="Navy">''bons mots''</font>]]</sup> 17:30, 6 November 2013 (UTC) |
|||
:::::ec - I've mailed Nakon anyway. [[User:Peridon|Peridon]] ([[User talk:Peridon|talk]]) 17:33, 6 November 2013 (UTC) |
|||
::::::TParis emailed Nakon a couple weeks ago, and I left a notification on their talk page. [https://en.wikipedia.org/wiki/Wikipedia:Administrators%27_noticeboard/Archive255#Oh_oh A bit more context].--[[User:Ponyo|<b><font color="Navy">''Jezebel's''</font></b><font color="Navy">Ponyo</font>]]<sup>[[User_talk:Ponyo|<font color="Navy">''bons mots''</font>]]</sup> 17:41, 6 November 2013 (UTC) |
|||
:::::::I did email Nakon at the time and he was fine with my copy of the tool and said he'd get his account sorted soon.--v/r - [[User:TParis|T]][[User_talk:TParis|P]] 18:45, 6 November 2013 (UTC) |
|||
== Wikimedia Foundation IP addresses causing autoblocks == |
== Wikimedia Foundation IP addresses causing autoblocks == |
Revision as of 22:32, 11 November 2013
Policy | Technical | Proposals | Idea lab | WMF | Miscellaneous |
- Table of contents
- First discussion
- End of page
- New post
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.
Drop-down option for saved edit summaries/subject headers
The drop-down option for saved edit summaries/subject headers etc. has vanished for the second time (previously fixed by unclicking 'Always use a secure connection when logged in' on 'Preferences'), and I can't seem to fix it. Any help welcome. GiantSnowman 11:44, 24 October 2013 (UTC)
- Anyone? GiantSnowman 11:22, 29 October 2013 (UTC)
- GiantSnowman Seems you're referring to the gadget (first one in the "Editing" section). I tried enabling it and it works for me. You may want to try disabling it, saving your preference, re-enabling it, and saving your preferences again. Also bypass your cache. equazcion → 07:01, 3 Nov 2013 (UTC)
- The drop-down edit summaries - or anything else in a form field - are saved by your browser, not by Wikipedia. Have you cleared your local saved settings, switched web browser, upgraded it, etc? Andrew Gray (talk) 20:31, 4 November 2013 (UTC)
- Not that I'm aware of, and drop-down fields on other websites are as fine as usual. GiantSnowman 20:42, 4 November 2013 (UTC)
- I guess you're talking about autocomplete. I don't generally advise relying on that, as it's somewhat tenuous and there are about a million different things that can make it disappear. You may be interested in User:Equazcion/CustomSummaryPresets though. equazcion → 04:57, 5 Nov 2013 (UTC)
Interlanguage links in different font
The interlanguage links have changed their font-family. They used to be in the same font-family as the rest of the page (Arial), but now they are something called "Autonym" which is apparently pulled from
@font-face {
font-family: "Autonym";
font-style: normal;
src: local("Autonym"), url("//bits.wikimedia.org/static-1.23wmf1/extensions/UniversalLanguageSelector/lib/jquery.uls/css/font/Autonym.woff?2013-10-24T17:33:20Z") format("woff"), url("font/Autonym.ttf") format("truetype");
}
It appears to be a result of <div id="p-lang" class="portlet" role="navigation">...</div>
. The trouble with that font is that it's indistinct (Windows XP, Firefox 24, MonoBook) - it's blurred, with blue and red fringing, particularly on tall thin letters like lowercase i and l - see screenshot at right. Arial, by contrast, is sharp-edged without fringing. This isn't just English Wikipedia; it's others too e.g. French. --Redrose64 (talk) 21:13, 1 November 2013 (UTC)
- More specifically: So, I should be able to override it with
#p-lang ul { font-family: 'Autonym',sans-serif; }
in my Special:MyPage/skin.css (as indeed I can) - but when and why did the change come in, and where was it announced? --Redrose64 (talk) 21:28, 1 November 2013 (UTC)#p-lang ul { font-family: 'Arial',sans-serif; }
- More specifically:
- Gag, this looks horrible, especially as letters have "gaps" in them. Hopefully this can be quickly fixed... - The Bushranger One ping only 21:20, 1 November 2013 (UTC)
- See https://blog.wikimedia.org/2013/10/28/the-autonym-font-for-language-names/. The aim is to have all language names in all scripts visible, even where a user doesn't have the relevant fonts installed on their computer. It's a good idea, but I agree that the font itself could use some work. the wub "?!" 21:23, 1 November 2013 (UTC)
#p-lang ul { font-family: inherit; }
should reset the font its original value. I agree the font does not render well at all on Windows. — Edokter (talk) — 22:48, 1 November 2013 (UTC)- ...I find it hard to believe that there are very many computers out there that don't have Arial... thanks Redrose64 for the fix script (and btw, it works if you have it all on a single line in the skin.css as well). - The Bushranger One ping only 23:56, 1 November 2013 (UTC)
- It's not a script, it's a CSS rule. CSS is very tolerant of whitespace - generally speaking, if a newline is permitted, a space is permitted instead - and most spaces may be removed. In fact, in that particular CSS rule, only one of the spaces is mandatory - the one before
ul
- so you can putand it works equally well. --Redrose64 (talk) 13:03, 2 November 2013 (UTC)#p-lang ul{font-family:'Arial',sans-serif;}
- "inherit" is better because you don't need to specify any font; it resolves to the parent elements font, which is whatever the rest of the page uses. — Edokter (talk) — 14:54, 2 November 2013 (UTC)
- I know; but I was replying to The Bushranger, who was replying to me, so I repeated my example changing only the whitespace. I could have used but this would not have illustrated the whitespace elimination quite so well, because there were other changes not related to whitespace. --Redrose64 (talk) 19:20, 2 November 2013 (UTC)
#p-lang ul{font-family:inherit;}
- I know; but I was replying to The Bushranger, who was replying to me, so I repeated my example changing only the whitespace. I could have used
- It's not a script, it's a CSS rule. CSS is very tolerant of whitespace - generally speaking, if a newline is permitted, a space is permitted instead - and most spaces may be removed. In fact, in that particular CSS rule, only one of the spaces is mandatory - the one before
- ...I find it hard to believe that there are very many computers out there that don't have Arial... thanks Redrose64 for the fix script (and btw, it works if you have it all on a single line in the skin.css as well). - The Bushranger One ping only 23:56, 1 November 2013 (UTC)
- I like and use User:Equazcion/SidebarTranslate which solves the original missing-fonts problem (and a few others) entirely.
- I liked the idea of using the native-language name, but in practice it made things so much harder for me to find (as a monolingual reader who occasionally wants to check out various other language examples) - I'd often have to mouse-over each of the links, looking for the 2letter prefix that looked familiar or correct. –Quiddity (talk) 20:08, 2 November 2013 (UTC)
- It's spread to Main Page#Wikipedia languages. Not that I look down there very often: I wouldn't have noticed for weeks, except I got this edit on my watchlist. --Redrose64 (talk) 00:58, 7 November 2013 (UTC)
- Using some zooming, I just realized Autonym is based on FreeSans, possibly the worst rendering open source font out there. I realize FreeSans has extensive unicode support, but if possible, Autonym should source its glyphs from Nimbus Sans L (which is what FreeSans is based on). — Edokter (talk) — 10:41, 10 November 2013 (UTC)
- It is ironic that a change specifically intended to make this list more readable has gone and made it less legible. I'm surprised that there isn't more of a fuss about this. Presumably the more vocal techies have larger screen resolutions and are unaffected. SFB 11:57, 10 November 2013 (UTC)
- I missed this thread and posted down below. It's a ghastly choice of font. I'm working on a 17" CRT monitor, and I'd hate to think what it looks like on anything smaller. It may look better on LCD, but I doubt it. Peridon (talk) 17:43, 11 November 2013 (UTC)
- It looks awful everywhere. I've got a nice big flat widescreen and it still hurts to look. Luckily I have SidebarTranslate, so I don't ever need to see it (shameless plug). equazcion → 18:01, 11 Nov 2013 (UTC)
- I missed this thread and posted down below. It's a ghastly choice of font. I'm working on a 17" CRT monitor, and I'd hate to think what it looks like on anything smaller. It may look better on LCD, but I doubt it. Peridon (talk) 17:43, 11 November 2013 (UTC)
Superfluous line-break in template
Hello.
Could someone help identify where there's an unnecessary line-break in {{Year in Norway}}. The line-break is transcluded, which makes the articles that use the template look a bit awkward.
Thanks.
HandsomeFella (talk) 11:35, 3 November 2013 (UTC)
- I removed some line breaks between categories that seemed extraneous, which fixes the issue in tests, but the whitespace is still showing up when this template is used just after {{Use dmy dates}} (as seems to be the case with most of its uses). equazcion → 11:59, 3 Nov 2013 (UTC)
- This seems to be caused by the line break in the code before the wikitable begins. Since that wikitable code needs to be at the beginning of its own line, I can't find a way to get rid of the whitespace, aside from chopping off everything that comes before it (which does effectively remove the whitespace in these articles, FYI). This seems like it might be a common issue for templates so maybe someone knows of a solution I'm unaware of. equazcion → 12:07, 3 Nov 2013 (UTC)
- I think there is at least some improvement. Thanks for trying. HandsomeFella (talk) 14:29, 3 November 2013 (UTC)
- I've managed to fix it. That was a tricky one. A single line break before the table is fine, the problem was caused by having two consecutive line breaks before the table. The first line break is not in the template itself, but in the articles that use it (between the {{Use dmy dates}} and {{Year in Norway}} templates). The fix was to put something between those line breaks to stop them being consecutive, but that doesn't cause a visible gap itself. An empty <nowiki/> tag did the trick. – PartTimeGnome (talk | contribs) 16:33, 3 November 2013 (UTC)
- The real problem was the text before the beginning of the table, which introduces a whiteline before the
{| class=
. See the warning about whitelines on WP:NOINCLUDE. I moved the text to the beginning of the template, and removed the <includeonly> tag. The obvious minus being that the page Template:Year in Norway itself now looks ugly. Debresser (talk) 09:08, 5 November 2013 (UTC)- I think you've misunderstood the warning at WP:NOINCLUDE. It refers to white space before
<noinclude>
, after</noinclude>
, after<includeonly>
or before</includeonly>
, warning that said white space will be included in the template's output. There wasn't any white space on either side of the<includeonly>
tags you removed. I tested re-adding them without making any other change, and the template still displayed correctly in the article 1972 in Norway (I didn't save this test). - Also, your changes moved text inside the table, but before the first table row, which is neither valid nor logical. The error text is intended to be shown outside the infobox, so should not be inside the table. Your changed worked in articles thanks to HTML Tidy fixing the invalid markup by moving it outside the table. If you'd tried this at Special:ExpandTemplates (where HTML Tidy does not run), invalid HTML is generated due to a
<span>
tag between<table>
and the first<tr>
. W3C's validator reports "Start tag span seen in table. Cannot recover after last error. Any further errors will be ignored.". (There are two other errors reported by the validator, but those are down to HTML generated by MediaWiki itself, unrelated to the template.) - Since your changes generated invalid HTML and messed up the appearance of the template page itself, I have undone them. (I completed your move of the category to the doc page. The doc page is the right place for categories.)
- PS: I see you made several attempts before you found something you liked. Please don't make test edits on a live template. You can see what effect your changes will have on another page without saving by using the "Preview page with this template" options beneath the edit box. – PartTimeGnome (talk | contribs) 23:57, 5 November 2013 (UTC)
<includeonly>...</includeonly>
is bad template engineering to begin with. You should just have a dummy default variable value in<noinclude>...</noinclude>
tags in the#if
conditional, like{{{1|<noinclude>dummy year</noinclude>}}}
. Then you can include a default value for{{{1|}}}
so that the template displays on its own page. VanIsaacWS Vexcontribs 00:37, 6 November 2013 (UTC)- I agree with you completely that one template per line is the standard, and looks good. I was surprised you didn't see the whiteline: it is the break between the end of the remark about the red warning text and the beginning of the table with
{|
. That is why I moved the warning inside the template. Even conceptually, I think the warning is not out of place inside the template proper, as you claim above. The biggest minus I see is that the template page became real ugly. Debresser (talk) 01:17, 6 November 2013 (UTC)
- I agree with you completely that one template per line is the standard, and looks good. I was surprised you didn't see the whiteline: it is the break between the end of the remark about the red warning text and the beginning of the table with
- I think you've misunderstood the warning at WP:NOINCLUDE. It refers to white space before
- The real problem was the text before the beginning of the table, which introduces a whiteline before the
- I've managed to fix it. That was a tricky one. A single line break before the table is fine, the problem was caused by having two consecutive line breaks before the table. The first line break is not in the template itself, but in the articles that use it (between the {{Use dmy dates}} and {{Year in Norway}} templates). The fix was to put something between those line breaks to stop them being consecutive, but that doesn't cause a visible gap itself. An empty <nowiki/> tag did the trick. – PartTimeGnome (talk | contribs) 16:33, 3 November 2013 (UTC)
- I think there is at least some improvement. Thanks for trying. HandsomeFella (talk) 14:29, 3 November 2013 (UTC)
- Er... I did see that. See my first post in this section: "A single line break before the table...". As I think you realised, a line break is required before a table unless it is the first thing in the template. This is not normally a problem since a single line break does not create a gap; it is only when combined with another line break from the transcluding page that a gap appears. Since it is clearly no-one's intent that these two line breaks should combine to make a gap, I added the <nowiki/> to stop them combining. (Perhaps in a more logical markup language, code from inside and outside a template would not be allowed to combine like this.)
- I think there might be an argument for showing the error message inside the table, but it would have to be done properly so it actually displayed inside the table rather than being moved out again by HTML Tidy. Another idea would be to replace the table with the error message, since nothing else in the template makes sense if the parameter was omitted.
- The template page becoming ugly was more down to removing the <includeonly> tags (see my next reply). – PartTimeGnome (talk | contribs) 23:23, 7 November 2013 (UTC)
- I know that the template becoming ugly was because the <includeonly> tags were removed. But that in its turn was done to remove the whiteline before the beginning of the template. You really don't need to speak with me as though I am making my first edit on intricate templates, and then perhaps you will also understand me better. Debresser (talk) 02:12, 8 November 2013 (UTC)
- My apologies. I tend to be rather verbose, and I understand how I might seem like that. I'm not very good at adjusting my tone for the person I'm talking to. I do not consider you to be a beginner at template editing.
- I guess you didn't see my other reply below? I already addressed your claim that removing the <includeonly> tags eliminated whitespace. (Sorry if I confused matters by making multiple replies in a single edit last night.) – PartTimeGnome (talk | contribs) 21:39, 8 November 2013 (UTC)
- I know that the template becoming ugly was because the <includeonly> tags were removed. But that in its turn was done to remove the whiteline before the beginning of the template. You really don't need to speak with me as though I am making my first edit on intricate templates, and then perhaps you will also understand me better. Debresser (talk) 02:12, 8 November 2013 (UTC)
- (I have moved your response above, to be immediately after the post to which you were responding.) One of us is misunderstanding that WP:NOINCLUDE bit, we both understand it but don't understand each other, or we're both thoroughly confused . I did test that taking your latest version of {{Year in Norway}} and re-adding the <includeonly> tags did not cause any gaps to appear. For example, see how that appears in "1972 in Norway", one of the articles that displayed a gap before either of us edited the template. – PartTimeGnome (talk | contribs) 23:23, 7 November 2013 (UTC)
- Vanisaac, you make a good point. I've made the changes you suggested. I used {{CURRENTYEAR}} for the default value to show on the template page. – PartTimeGnome (talk | contribs) 23:23, 7 November 2013 (UTC)
Fixing the problem in other templates
That's interesting. This trick could fix the common problem that occurs whenever two "invisible" templates are placed at the top of an article. See the white space at the top of User:John of Reading/Sandbox. -- John of Reading (talk) 16:56, 3 November 2013 (UTC)
- The first three templates in your sandbox all use {{Dated maintenance category}}. Adding a <nowiki/> to that template fixes the gap in your sandbox too. Before I make a protected edit request, can anyone think of any undesirable side effects this could cause? – PartTimeGnome (talk | contribs) 17:53, 3 November 2013 (UTC)
- I would strongly oppose the addition of stray code to template. First of all because another user will surely remove it sooner or later, not knowing why it is there. Secondly, because it is ugly. It is against all rules of coding to do such things. But the main reason is that there is a simpler solution to the problem: put all the invisible templates right after each other without any spaces between them. See User:John of Reading/Sandbox where I did so and the whitespaces are gone. We could add a warning about this to the documentation of certain templates like {{Use dmy dates}} and others, but even if there would be an extra space, this is not a big problem. Debresser (talk) 11:42, 4 November 2013 (UTC)
- Alternatively, since templates like
{{use dmy dates}}
or{{use British English}}
do nothing except categorise, put them with the other cats - at the bottom. Any spurious blank lines which may be generated will be much less obtrusive in such a position. There is precedent for this, since templates like{{coord|display=title}}
which place their output somewhere other than the actual position of the template, are typically placed at the bottom as well. --Redrose64 (talk) 11:52, 4 November 2013 (UTC)- Another thing that might artificially reduce the problem is adding the problematic templates to {{Multiple issues}}. Debresser (talk) 07:27, 5 November 2013 (UTC)
- There are problems with that.
{{multiple issues}}
is for enclosing cleanup message boxes: requests to fix the article, to be removed when the fix has been done; when all have been done, and when there are none left to fix,{{multiple issues}}
gets removed as well. By contrast,{{use dmy dates}}
and similar are not requests to fix the article - they are permanent indicators of the article's writing style. If the article has no cleanup issues, and you addit looks kind of odd, see User:Redrose64/Sandbox5, it's got a blank area within the{{multiple issues| {{use dmy dates|date=November 2013}} {{use British English|date=November 2013}} }}
{{multiple issues}}
box with the implication that there should be some message or other. --Redrose64 (talk) 15:41, 5 November 2013 (UTC)
- There are problems with that.
- Another thing that might artificially reduce the problem is adding the problematic templates to {{Multiple issues}}. Debresser (talk) 07:27, 5 November 2013 (UTC)
- Regarding someone possibly removing the code because it is not clear what it does, an
<!--
editor comment-->
will fix that. (I'd hope administrators would show more care editing a fully protected template, but maybe I hope for too much... ) - On the point about ugliness, I agree, but I couldn't think of a better way to do it. There is much that is ugly about MediaWiki's markup language, so we often have to do ugly things to get the job done.
- As for the "simpler" solution: good luck getting editors to use the templates all on one line. Many editors find placing each template on a separate line to be more intuitive, as evidenced by the many pages where this is the case. Generally, templates should be designed to be easy for editors to use, rather than expecting editors to adapt to their quirks. Templates should try to hide the complexities of wiki markup from the people that use them. One template per line is certainly easier to read. Keep the ugly stuff in a template so other editors don't need to worry about it.
- One template per line is consistent with how categories are normally used (given the main purpose of the templates is categorisation): categories are typically one-per-line too. Also note that the current behaviour is inconsistent: where the template outputs a category, it is safe to use one per line. Where it outputs nothing, it will cause a gap. Code that looks fine in article space will show with gaps when copied to a user sandbox (because the categories are suppressed in userspace). – PartTimeGnome (talk | contribs) 23:00, 5 November 2013 (UTC)
- I agree that templates are best placed on consecutive lines. I still strongly oppose the addition of code for the purpose of avoiding whitelines. It is a counter-intuitive non-solution. If the problem, i.e. a whiteline, should arise in any given article, it should be taken care of on an ad hoc basis, just like we did with the Year in Norway template. Debresser (talk) 17:07, 9 November 2013 (UTC)
- It is counter-intuitive, but I don't think an intuitive solution exists. I don't think "non-solution" is the right word, since it does solve the blank line issue. Why should this be solved over and over on a case-by-case basis when it can be solved once for all cases? The editors using the templates might not know how to fix the unwanted blank lines. If we fix it in the template, they would never be troubled by the problem in the first place.
- I don't know if you'll like this any better, but here's an alternative proposed edit for {{Dated maintenance category}}. (Here's John's sandbox example using the new version.) I've added comments explaining why the nowiki tags are there. Furthermore, because no blank line occurs when a category is output, the nowiki tag is only used if the template won't output any category. – PartTimeGnome (talk | contribs) 23:33, 10 November 2013 (UTC)
- I called it a "non-solution" because it is only a workaround. The real problem is the existence of whitelines, in the code of the other templates or simply in the articles if the templates are placed on different lines. The alternative proposal is the same as the first, with an added explanation.
- I agree that templates are best placed on consecutive lines. I still strongly oppose the addition of code for the purpose of avoiding whitelines. It is a counter-intuitive non-solution. If the problem, i.e. a whiteline, should arise in any given article, it should be taken care of on an ad hoc basis, just like we did with the Year in Norway template. Debresser (talk) 17:07, 9 November 2013 (UTC)
- Alternatively, since templates like
- I would strongly oppose the addition of stray code to template. First of all because another user will surely remove it sooner or later, not knowing why it is there. Secondly, because it is ugly. It is against all rules of coding to do such things. But the main reason is that there is a simpler solution to the problem: put all the invisible templates right after each other without any spaces between them. See User:John of Reading/Sandbox where I did so and the whitespaces are gone. We could add a warning about this to the documentation of certain templates like {{Use dmy dates}} and others, but even if there would be an extra space, this is not a big problem. Debresser (talk) 11:42, 4 November 2013 (UTC)
Help needed tracking recent changes to medical content
User:Femto Bot used to populate Wikipedia:WikiProject Medicine/Recent changes (Warning: page is 700k now -DePiep) which in turn updated Special:RecentChangesLinked/Wikipedia:WikiProject Medicine/Recent changes. I think that's how it worked. It reported all changes to pages with {{WPMED}} on their talk page. Anyway, it was an awesome tool for patrolling some of Wikipedia's most sensitive content. But since Rich Farmborough was banned from bot work it's stopped working - it only reports recent changes to pages beginning with "A". Does anyone feel like volunteering to fix it, or is there someone at WMF who I could ask to arrange it?
This tool aims to do the same thing but it's slow and often times out, and when it works it's running a couple of days behind.
Anybody? If no one wants to volunteer, can someone please tell me who at WMF to approach? We need this feature. Without it, anything could be happening to our medical content. --Anthonyhcole (talk · contribs · email) 16:53, 3 November 2013 (UTC)
- There was also Tim1357's tool, but his account has expired from the Toolserver. This does look like a fairly urgently needed feature - perhaps ask over at Wikipedia:Bot requests to see if a willing bot operator wants to take it on? Not all of our bot operators are regular readers of this page. — Mr. Stradivarius ♪ talk ♪ 14:23, 4 November 2013 (UTC)
- Thanks, Mr S. I've left them a note. --Anthonyhcole (talk · contribs · email) 18:05, 4 November 2013 (UTC)
- I also think this should be a core service WMF provides to the community. I perceive a large disconnect between community needs and what the WMF does. Why is that? We shouldn't have to do think we have to become project managers with m:IEG proposals just to get some WikiProject support... Biosthmors (talk) pls notify me (i.e. {{U}}) while signing a reply, thx 17:52, 4 November 2013 (UTC)
- Let's see what happens at Bot requests. But if there's no response there we should take it to the WMF. --Anthonyhcole (talk · contribs · email) 18:05, 4 November 2013 (UTC)
- No response yet. I've asked Rich if he can help. --Anthonyhcole (talk · contribs · email) 06:52, 5 November 2013 (UTC)
I see from the talk page of the bot that seems to drive this (User_talk:Femto_Bot) that the bot has been blocked. If that block were lifted, would Special:RecentChangesLinked/Wikipedia:WikiProject Medicine/Recent changes start working again? --Anthonyhcole (talk · contribs · email) 07:16, 5 November 2013 (UTC)
- Over at WP:ELEMENTS we have
a differentthe same solution. We have a project page with all article pages (maintained manually). Then we have a link on the project page that opens special page Related changes (not RC). The page is Special:RecentChangesLinked/Wikipedia:WikiProject Elements/Articles/List of articles, the link is RELC. - Technical notes: WP:RELC has useful features like showing editors, edits per day, and more. Maybe the base list page could be updated by some bot, adding the project pages (list of WP:ELEMENT pages is not that volatile, medicine more I guess). We have added the talkpages too, as a choice. We have the same for templates, see here. -DePiep (talk) 08:09, 5 November 2013 (UTC)
- oops lol. I now see that the page has the same intention. That leaves the question: needs a bot that puts all pages in Category:WikiProject Medicine articles and cats below on a page (undouble, with/wout talkpage). Is there no other bot? -DePiep (talk) 08:19, 5 November 2013 (UTC)
- I asked if it could be done by a module (Lua) in-site: Wikipedia:Lua_requests#Filling_the_RELC_page_using_Lua. -DePiep (talk) 08:59, 5 November 2013 (UTC)
- Over at WP:ELEMENTS we have
- The block on Femto Bot (talk · contribs) cannot be lifted under the terms of Rich Farmbrough (talk · contribs)'s ban. One possibility (which I may be entirely wrong about) would be for ownership of Femto Bot to be transferred away from Rich Farmbrough, with somebody else (perhaps an established bot operator) taking it on. This would mean (under the terms of the ban) that provisions would be needed to ensure that Rich Farmbrough never use Femto Bot again. More feasible is that Rich Farmbrough could disclose the whole of the source codes for Femto Bot, which would then be used to create an entirely new bot - and that would of course require a WP:BRFA, similar to the situation here. --Redrose64 (talk) 10:14, 5 November 2013 (UTC)
- You have got to be kidding me (and that is only in reply to your first sentence). We're going to shoot a WikiProject in the face because somebody/some people got pissed off at an individual? WTF is going on in this place? Biosthmors (talk) pls notify me (i.e. {{U}}) while signing a reply, thx 10:52, 5 November 2013 (UTC)
- Note: At the moment I am working on a manual solution for WP:MED. Am I the only one, or do we have an edit clash ahead? -DePiep (talk) 12:48, 5 November 2013 (UTC)
- I use a slightly modified version of Ganeshbot for generating the project lists. Keith D (talk) 14:44, 5 November 2013 (UTC)
- Even more calm everyone. I made the list manually (28000 MED articles) and prepared the RELC link. WARNING: this new RELC list page is 700k. I also moved the page to Wikipedia:WikiProject Medicine/List of pages/Articles because this name is more automatable (other namespaces, other projects) and also because the old name was incorrect (it did not show what it said).
- Now it is up, recent, and running for WP:MED: WP:MED Articles - Related changes. I'll go to their talkpage for details.
- Bot actions (I cannot do) are welcome, and my question to the masters is to work into the generic setup I made (task name: "RELC list"). -DePiep (talk) 15:18, 5 November 2013 (UTC)
- There is an up to date solution available for WP:MED (presented to them at WT:MED). So no time pressure. Then at the bot request page there is follow up on this (for future updates). We may pilot this one into a generic solution for projects. Looks like this thread can be closed. -DePiep (talk) 17:24, 5 November 2013 (UTC)
A bit late, but there is a replacement available for Tim1357's tool mentioned above. Dispenser's transcluded changes tool shows all recent changes for pages that have a particular template on their talk page. (Though right now it's suffering from a few days of toolserver DB lag). Toohool (talk) 17:56, 5 November 2013 (UTC)
- Thanks. At WP:BOTREQ a future bot solution was initiated, expanding into a more generic solution proposal (could it work for all wikiprojects?). That requires the bot to more interact with a request from a project (think, like the archiving bot).
- I should note that the original bot, mentioned on top here, listed only 5% of the pages (1500/30000) [1]! The letter A was not even complete. -DePiep (talk) 06:17, 7 November 2013 (UTC)
Wikimedia Foundation Error notice
Since yesterday there has been a problem with saving edits to User:RoslynSKP/Southern Palestine Offensive. When the edit is saved, instead of going back to the article, the Wikimedia foundation error notice appears. Then by backtracking and hitting reload the edit finally appears. Is there any way of fixing this problem? --Rskp (talk) 04:46, 4 November 2013 (UTC)
- The page is too complicated to finish rendering before the connection times out. After a next visit, parts of the page have been cached, and rendering will be faster, so that's why it works on other pageviews. This is a common problem with overly complex pages. The advise is to simplify the page using fewer and less complex templates (which include references). —TheDJ (talk • contribs) 09:51, 4 November 2013 (UTC)
- Assuming that RoslynSKP means this sort of message, yes it does happen with overcomplex pages, but yesterday I got it for edits to three relatively small pages: of the three, the largest was Oxford, Witney and Fairford Railway. --Redrose64 (talk) 10:46, 4 November 2013 (UTC)
- Thanks for that. Yes, it is very long, but it only has one template plus the refrences. I'm in the process of cutting it down. --Rskp (talk) 01:04, 5 November 2013 (UTC)
- The article has been shortened down to 169,000 bytes but its still showing the error every save. The Information for "User:RoslynSKP/Southern Palestine Offensive" page shows 109 transcluded templates. Is there any way of getting rid of some of these? --Rskp (talk) 01:46, 10 November 2013 (UTC)
- That page has 84 calls to {{convert}} which is a complex template. If you want to give it a try, you could do a "search and replace" to change each "convert|" to "convert/sandboxlua|" which would cause the converts to use Module:Convert that is still under development (groan). However, it should be fine for temporary use and chances are that {{convert}} will use the module in a couple of weeks (although I've been saying that for a while). Using the module reduces the CPU time usage from 8.369 to 4.308 seconds when previewing the current page. Johnuniq (talk) 04:02, 10 November 2013 (UTC)
- The article has been shortened down to 169,000 bytes but its still showing the error every save. The Information for "User:RoslynSKP/Southern Palestine Offensive" page shows 109 transcluded templates. Is there any way of getting rid of some of these? --Rskp (talk) 01:46, 10 November 2013 (UTC)
- Thanks for that. Yes, it is very long, but it only has one template plus the refrences. I'm in the process of cutting it down. --Rskp (talk) 01:04, 5 November 2013 (UTC)
- I suppose theother alternative is just to cut the article? --Rskp (talk) 01:15, 11 November 2013 (UTC)
- A first step would be to try my suggestion, so I edited User:RoslynSKP/Southern Palestine Offensive to replace the convert templates, although I used {{convert/q}} ("quick") which was created recently for use on an article where {{convert}} was apparently causing the page to time out (the "/q" and "/sandboxlua" templates currently do the same thing). I checked the displayed text before and after the change, and there is only a single difference, namely where the new template has reported that one of the converts is invalid. To see that, search the page for "convert" (the displayed page, not the wikitext). You possibly want to change the output "g" (grams) to "impgal" (imperial gallons), or omit "|g" for the default which is imperial and US gallons. Johnuniq (talk) 05:50, 11 November 2013 (UTC)
Unable to do anything through IE8
I have seen this problem posted by someone else on one or another help page but now I can't find it. For the past few days (since around the end of October) I've been unable to do any meaningful editing of wikipedia pages on a computer I regularly use that runs IE8 (it's not mine and I don't have the option to change browser). If I scroll down, the text runs all over the place. If I enter anything in the search box, it doesn't show up. I can't use any drop-down menu. I daresay the answer to this is that IE8 is old and has stopped working (I've already changed to Chrome on my home PC), but I just wanted to check.Deb (talk) 19:02, 4 November 2013 (UTC)
- Firefox doesn't work either. Funandtrvl (talk) 18:04, 5 November 2013 (UTC)
- Re: Funandtrvl, what version of Firefox? Re both, what operating system? - Jarry1250 [Vacation needed] 18:07, 5 November 2013 (UTC)
- Firefox 25.0 doesn't work, it doesn't show the links at the top right of page. I can get IE10 and Chrome to work right now with WP. Funandtrvl (talk) 18:11, 5 November 2013 (UTC)
- Re: Funandtrvl, what version of Firefox? Re both, what operating system? - Jarry1250 [Vacation needed] 18:07, 5 November 2013 (UTC)
Ok, the rebooting worked... thanks for the reminder when all else fails...reboot (or hit) the computer. Funandtrvl (talk) 18:24, 5 November 2013 (UTC)
- Unfortunately it doesn't help me. I reboot every evening. Deb (talk) 18:28, 5 November 2013 (UTC)
- In your case, it is probably the IE8 browser. Is there a compatibility mode that you can turn on? Or anyway to get someone to upgrade the browser on that PC/laptop? Funandtrvl (talk) 18:32, 5 November 2013 (UTC)
- Would you be able to provide a screen capture of the problem in action? We should probably still be support IE8. - Jarry1250 [Vacation needed] 18:33, 5 November 2013 (UTC)
- Please delete the word "probably" in the above post - you should be supporting IE8. The above posts exemplify WP's arrogance towards IE - the original post is about IE, but immediately switches to concern about Firefox.
Arjayay (talk) 19:27, 5 November 2013 (UTC)- I'm guessing Jarry1250 was referring more to IE8 being a few years old, rather than it merely being IE. equazcion → 19:37, 5 Nov 2013 (UTC)
- As the original poster states "a computer I regularly use that runs IE8 (it's not mine and I don't have the option to change browser)". Many editors are still using XP, so cannot use IE9 or IE10.
The current versions of IE are not supported either - I use IE10 and haven't been able to use the cite templates on the Ref Toolbar for months, whilst the search and replace hasn't worked on IE for years.
Wikipedia wonders why so many experienced editors are leaving - I'm not claiming any great contributions, 44K edits over 6 years, but if anything is likely to cause me to quit it is the combination of implementing half tested software (I'm being very generous with the half) and the arrogance towards users of IE Arjayay (talk) 20:03, 5 November 2013 (UTC)- If you just assume that people are aware problems exist, they will never get fixed, especially when it comes to IE problems, as few tech-y people use it. I just tested Reftoolbar in IE10 and it worked fine, so the problem may be specific to your browser configuration, or a conflict with a user script or gadget (try it logged-out).
- There are at least 5 major non-mobile browsers, each of which has a slightly different implementation of HTML, JS, and CSS, and they also vary between versions of the same browser. According to [2] there are currently 13 different browser/version combinations with more than 1% usage share. Compare this to traditional application development where it's generally only necessary to get things to work on a handful of platforms and where the implementation of programming languages are generally held to common standards and you can see some of the challenges of web design.
- Keep in mind that things like Reftoolbar, Popups, and wikEd are not WMF projects, they were and are fully developed by community volunteers, often only 1 or 2 people. Mr.Z-man 20:26, 6 November 2013 (UTC)
- As the original poster states "a computer I regularly use that runs IE8 (it's not mine and I don't have the option to change browser)". Many editors are still using XP, so cannot use IE9 or IE10.
- I'm guessing Jarry1250 was referring more to IE8 being a few years old, rather than it merely being IE. equazcion → 19:37, 5 Nov 2013 (UTC)
- Please delete the word "probably" in the above post - you should be supporting IE8. The above posts exemplify WP's arrogance towards IE - the original post is about IE, but immediately switches to concern about Firefox.
- Would you be able to provide a screen capture of the problem in action? We should probably still be support IE8. - Jarry1250 [Vacation needed] 18:33, 5 November 2013 (UTC)
- In your case, it is probably the IE8 browser. Is there a compatibility mode that you can turn on? Or anyway to get someone to upgrade the browser on that PC/laptop? Funandtrvl (talk) 18:32, 5 November 2013 (UTC)
- I just logged in to the Wikipedia on a WinXP PC running IE 8 and could not replicate any of the above issues. Let's try to move away from that "what browser you should/should not use" and get to what exactly is happening on the original user's PC. Tarc (talk) 20:10, 5 November 2013 (UTC)
- I don't think anyone's actually focusing on which browser to use, other than Arjayay, who is just assuming others are. I'm thinking Deb has some local PC issue. You could try following the cache clearing instructions. When I get wonky browser behavior and none of the usual methods seem to work, I use CCleaner to perform a nice scrubbing, which works a large percentage of the time. It's a free program, though you do need to install it generally -- not sure if you have the ability to do that. equazcion → 20:36, 5 Nov 2013 (UTC)
There's more people with this problem. Seems to me like every fifth (or even every third) IE8 user is unable to use the site. I'm currently editing with Chrome tho. I can't use IE8 on XP or Windows 7. There's nothing all that odd about the way it looks, so I don't see how a screenshot is going to help you.
- When loading any page, it loads a blank page. Sometimes the previous page stays on screen until I minimize and maximize again, which makes the page blank.
- In compatibility mode, the page does seem to get loaded, but none of the links work; it's impossible to highlight text (it's sort of like a picture, instead of text) and scrolling completely messes up the page, creating vertical lines all over the window.
This has been hapening sinse about the 2'nt november. GMRE (talk) 18:23, 6 November 2013 (UTC)
- Can't provide a screenshot, but on looking at my watchlist, everything is fine for the first 2-3 entries, and then from that point everything else on the screen is long vertical streaks leading from characters. IE8 on WinXP. Only resolution is to close the window; more than once it's frozen the browser entirely. Risker (talk) 19:00, 6 November 2013 (UTC)
- When I look at a page, it appears normal until I try to scroll down - then it goes berserk, much as you describe. Deb (talk) 19:37, 6 November 2013 (UTC)
- Posting via IE8 here now. I've been trying to reproduce these errors but so far no dice. Deb, if you could, can you list the gadgets you have enabled -- or just try disabling all of them, bypass your chache, and see if stuff clears up? equazcion → 20:04, 6 Nov 2013 (UTC)
- Not trying to be difficult, but I don't know what you mean by "gadgets". Deb (talk) 20:37, 6 November 2013 (UTC)
- I guess that answers that, then :) Gadgets are in your Preferences, they're extra tools and tweaks you can enable. If you don't know what they are then it's safe to assume you have the defaults only. equazcion → 20:49, 6 Nov 2013 (UTC)
- Gadgets are the settings listed at Preferences → Gadgets. A big problem with that list - not just the fact that there are so many (over 50) - is that several of them are opt-out, so will have been enabled without you being aware of the fact. So if you make a list of enabled gadgets, you may actually be listing several that the majority of people also have (probably without realising it). The Gadgets enabled by default (i.e. opt-out gadgets) are:
- Enable the Teahouse "Ask a question" feature
- (D) Reference Tooltips: hover over inline citations to see reference information without moving away from the article text (does not work if "Navigation popups" is enabled above)
- Form for filing disputes at the dispute resolution noticeboard
- (D) CharInsert: add a toolbar under the edit window for quickly inserting wiki markup and special characters (troubles?)
- Add a "Sandbox" link to the personal toolbar area.
- The ones that Equazcion is interested in are most likely anything other than those five. --Redrose64 (talk) 00:48, 7 November 2013 (UTC)
- Gadgets are the settings listed at Preferences → Gadgets. A big problem with that list - not just the fact that there are so many (over 50) - is that several of them are opt-out, so will have been enabled without you being aware of the fact. So if you make a list of enabled gadgets, you may actually be listing several that the majority of people also have (probably without realising it). The Gadgets enabled by default (i.e. opt-out gadgets) are:
- I guess that answers that, then :) Gadgets are in your Preferences, they're extra tools and tweaks you can enable. If you don't know what they are then it's safe to assume you have the defaults only. equazcion → 20:49, 6 Nov 2013 (UTC)
- Not trying to be difficult, but I don't know what you mean by "gadgets". Deb (talk) 20:37, 6 November 2013 (UTC)
- Posting via IE8 here now. I've been trying to reproduce these errors but so far no dice. Deb, if you could, can you list the gadgets you have enabled -- or just try disabling all of them, bypass your chache, and see if stuff clears up? equazcion → 20:04, 6 Nov 2013 (UTC)
- When I look at a page, it appears normal until I try to scroll down - then it goes berserk, much as you describe. Deb (talk) 19:37, 6 November 2013 (UTC)
- Not to be rude, but why would anyone use IE anymore? KonveyorBelt 20:40, 6 November 2013 (UTC)
- Deb explains that in her original post, Konveyor Belt. equazcion → 20:49, 6 Nov 2013 (UTC)
- IE 8 is the default browser on the corporate machine I use at work. (I work as a contractor at a very well-known technology company. I can't say which, but their products are doubtlessly in the computers everyone here is using. Unless you are using exotic hardware.) I could use another browser with the work computer & take my chances with with IT, but I don't use most of the gadgets or fancy add-ons available for Wikipedia, & another browser would fix certain problems while introducing another set. No
browsersoftware is completely free of gotchas of some shape or flavor. -- llywrch (talk) 17:59, 7 November 2013 (UTC)
i do not think the problem described have anything to do with IE. to the original poster: please try to see if same problems exist when you are logged out. once you see they do not happen in this case, you probably want to go over Special:MyPage/common.js and Special:MyPage/vector.js (or monobook, if this is the skin you use), and eliminate stuff, until the behavior disappear. you can then bring stuff back in until the behavior returns - at this point you found the culprit. clearly wikipedia is compatible with IE8, with some limitations (i.e., some things do not work with ie8, such as displaying references in columns, some features related to "universal language", visual editor and such), but the basic functionality works with IE8 and even with IE7 (probably once you go to 6 and below, things stop working, and the same is probably true for ancient versions of netscape.... peace - קיפודנחש (aka kipod) (talk) 21:10, 6 November 2013 (UTC)
- I already checked Deb's .js files, they're empty. equazcion → 21:18, 6 Nov 2013 (UTC)
- Same behaviour when logged out. Risker (talk) 22:55, 6 November 2013 (UTC)
- Perhaps it's a geo located central or geonotice or something that is causing the breakage... That would explain why only some people are seeing this. —TheDJ (talk • contribs) 09:33, 7 November 2013 (UTC)
- Hmm maybe the new big ugly donation thing is doing it? equazcion → 12:57, 7 Nov 2013 (UTC)
- I'm trying to get the donation thing to come up again for me but I'm not sure how. I think I hid it when it initially came up. I logged out and cleared cache and cookies, but it still won't show up. Ironic, that. equazcion → 13:05, 7 Nov 2013 (UTC)
- deb, risker, stfg, could you post your general locations so we can check for geo notices that might be causing this? equazcion → 13:28, 7 Nov 2013 (UTC)
- Berkshire, England. --Stfg (talk) 15:00, 7 November 2013 (UTC)
- There are three geonotices covering Berkshire at the moment; these are at MediaWiki:Geonotice.js as follows:
- WikiTakesTube13: "Wiki takes the Tube, 9th November - photographers wanted to fill in some gaps of our coverage of London's finest buildings."
- UK131102: "Interested in having a chat with fellow Wikipedians? There are forthcoming meetups in: Cambridge, 9 November; London, 10 November; and Oxford, 17 November!"
- Belfast201311: "Interested in having a chat with fellow Wikipedians? There is a forthcoming meetup in: Belfast, 23 November!"
- All three display fine for me in Firefox 24; I live in Didcot. --Redrose64 (talk) 17:09, 7 November 2013 (UTC)
- There are three geonotices covering Berkshire at the moment; these are at MediaWiki:Geonotice.js as follows:
- South Wales. Deb (talk) 17:36, 7 November 2013 (UTC)
- (edit conflict) Even though all the current geonotices appear to be simple lines of text with nothing more complex than wikilinks, it is interesting that you're both in the UK. My next step would generally be to see what happens when these users disable javascript altogether. It may be a teensy bit involved for those not accustomed to technical settings but this shows how to do it, if any of the sufferers feel like giving it a try. equazcion → 17:42, 7 Nov 2013 (UTC)
- I see all three geonotices just fine. Disabling javascript is interesting. Diffs accessed through https work fine when it's disabled and the problem reappears when it's re-enabled. OTOH, my problem with the misplaced tabs (item 3 in the #Diff and other problems (probably IE8) section) reappears when javascript is disabled, and goes away again on re-enabling. --Stfg (talk) 19:32, 7 November 2013 (UTC)
- Berkshire, England. --Stfg (talk) 15:00, 7 November 2013 (UTC)
- Perhaps it's a geo located central or geonotice or something that is causing the breakage... That would explain why only some people are seeing this. —TheDJ (talk • contribs) 09:33, 7 November 2013 (UTC)
- Southern Ontario, Canada. I did try to take screenshots when the "striping" occurred, but the screenshots show a blank page, and not what I see on the screen. However, after taking the screenshot and trying to download it, when I returned to the Wikipedia screen, it was completely blank, and I had to close the browser to get back on. Risker (talk) 17:41, 7 November 2013 (UTC)
- Southern Ontario shouldn't be getting any current geonotices. The nearest active one is CHFNov13: "Wikipedians are invited to the GLAM Café at the Chemical Heritage Foundation to meet, talk, and edit. We provide the space, the coffee, and the snacks: you provide ideas and enthusiasm! On the second Tuesday of each month, starting November 12, 2013. " --Redrose64 (talk) 18:52, 7 November 2013 (UTC)
- I did succeed in taking a screenshot although it doesn't look quite like it did on screen. But no one seems interested in looking at it. Actually, I'm not so concerned about my own position because I can still edit at home - what worries me is that there could be a lot of potential users out there who wouldn't dream of trying to edit but can't now access wikipedia to look at articles.Deb (talk) 18:07, 7 November 2013 (UTC)
- You could upload it via Special:Upload. Click the "Browse" button to locate the screenshot file, enter something like "Screenshot of IE8 glitch" for the "Destination filename", and enter anything for the description -- I can take care of that afterwards. I'd be interested in seeing it just in case it could tell us something. equazcion → 18:13, 7 Nov 2013 (UTC)
- Okay, I've done what you suggested - it's called Screenshot_of_IE8_glitch.jpeg Deb (talk) 19:41, 7 November 2013 (UTC)
- Thanks for doing that Deb :) I placed it at the top of the this discussion for future reference. It looks like the display isn't updating properly as you scroll down, and is rather just cascading shadows of the same screen. Is this similar to what's happening to Stfg and Risker? equazcion → 21:10, 7 Nov 2013 (UTC)
- Okay, I've done what you suggested - it's called Screenshot_of_IE8_glitch.jpeg Deb (talk) 19:41, 7 November 2013 (UTC)
- You could upload it via Special:Upload. Click the "Browse" button to locate the screenshot file, enter something like "Screenshot of IE8 glitch" for the "Destination filename", and enter anything for the description -- I can take care of that afterwards. I'd be interested in seeing it just in case it could tell us something. equazcion → 18:13, 7 Nov 2013 (UTC)
- Southern Ontario, Canada. I did try to take screenshots when the "striping" occurred, but the screenshots show a blank page, and not what I see on the screen. However, after taking the screenshot and trying to download it, when I returned to the Wikipedia screen, it was completely blank, and I had to close the browser to get back on. Risker (talk) 17:41, 7 November 2013 (UTC)
- Stfg, you seem to have a few things in your common.js and vector.js files. I would try removing them and bypassing your cache to see if any of those are causing the diff problem. equazcion → 21:23, 7 Nov 2013 (UTC)
- I've sometimes seen the same sort of thing on IE8. Have you tried toggling the browser's "compatibility mode" button (the torn-page icon at the right end of the address bar, beside the reload button)? LeadSongDog come howl! 22:25, 7 November 2013 (UTC)
- I've tried completely emptying my common.js and vector.js (and didn't forget to bypass the cache :), but even with them completely empty, the situation is the same. In compatibility mode, it's slightly different: the top screenful displays, but scrolling and page movement keys have no effect at all (in normal mode, I get the same as shown in deb's screenshot). Has anyone any thoughts about the fact that this only happens with htpps diffs, while normal http diffs behave fine? (And is this the case for deb too? The screenshot doesn't show the title bar.)
I've had the problem ever since trying to play an OGG file on 2 November 2013. Got a "Do you want to run this application" security warning. Does anyone know what was installed & how to get rid of it. When I go use IE 8 on a different user name on the same PC, Wikipedia works fine. --Chaswmsday (talk) 10:01, 8 November 2013 (UTC)
Something has been fixed! I haven't been able to test it on XP yet, but I can now use IE8 on Windows 7 again. GMRE (talk) 13:08, 9 November 2013 (UTC) No change on XP. :( GMRE (talk) 23:55, 9 November 2013 (UTC)
- Ugh. Still doesn't work for me. But I created a user, then answered "yes" to the same prompt from the OGG file with no problem. Has anyone had any luck eliminating IE problems with what appears to be the preferred fix: turning the IE "Window feature" OFF, then back ON? --Chaswmsday (talk) 11:53, 11 November 2013 (UTC)
- What is this "Window feature", and how do you turn it off and on again? As far as I can see, nothing has been fixed. Wikipedia pages accessed through https still have the scrolling problem. I haven't accessed any OGG files for ages, and I don't believe that's related. --Stfg (talk) 16:51, 11 November 2013 (UTC)
Today I installed a copy of IE8 on XP in my VirtualBox in hopes of finding what might be causing this. Unfortunately i was unable to reproduce. I don't know how to help any further, if a problem is this localized to certain users it becomes very hard to figure out what the problem might be. If i look at the screenshot that Deb is providing though, then that issue very much looks like a screen buffer problem. Do you see this problem more often on very large pages compared to smaller pages ? There can be many causes for such a problem. A bug in the application itself, mouse (scroll) drivers and graphics drivers are all often to blame. If i google a bit I also see some indications of that a bug like this was introduced in XP Service Pack 3 for some people (and never fixed). —TheDJ (talk • contribs) 21:42, 11 November 2013 (UTC)
- I did the same thing, vmware, and was unable to reproduce -- although I did get some slight buffer-type glitches. On initial setup of IE8 where it asks you about default search engines and whatnot, when the window disappeared and I was at Wikipedia, a big blank white box was left in its place, with Wikipedia around it. It cleared up instantly on refresh though. equazcion → 21:49, 11 Nov 2013 (UTC)
- PS. Stfg reported one major issue cleared up by disabling Javascript. Deb didn't try that but her issue sounds about the same, and I have feeling that would do it for her. Both users report this began somewhat recently. I'm wondering if there's maybe simply more javascript around right now and is making the browser work too hard? Or something. equazcion → 21:53, 11 Nov 2013 (UTC)
Potential bug
I made a good-faith revert using STiki to Drake (rapper) (pp-pc1), and it did not automatically accept my change, but I have the reviewer right. So... I accepted it myself? See the review log. Should I report this as a bug? — MusikAnimal talk 21:12, 5 November 2013 (UTC)
- Yes, that's an issue with STiki. Jackmcbarn (talk) 02:12, 7 November 2013 (UTC)
Skipping Wikipedia:File Upload Wizard when I click a redlinked file
Some time ago the decision was made that if you clicked on a redlinked file, (for example, if you clicked File:Example Nonexistant Image.png), it would take you to the upload wizard, rather than to the file namespace page (so you would get this instead of this). While I'm sure that this was done to be a convenience for new editors unfamiliar with uploading, it is a tremendous inconvenience for people who work with files, like myself. People that work with files want to be able to click on a redlink and get to the file namespace page, because that allows them to see whether the file is redlinked because it has been deleted, or because it has been mistyped (which obviously require two different fixes). I could have sworn that at one time someone wrote a fix for me to stick in my custom .js or custom .css that would allow me to click on a redlinked file and get the file namespace page instead of the upload wizard, but that fix either stopped working or is a figment of my imagination that never existed in the first place, as I am getting redirected to the upload wizard (again?).
TLDR: Can someone please tell me how to skip the upload wizard and go straight to the file namespace page when clicking redlinked files? Sven Manguard Wha? 20:17, 5 November 2013 (UTC)
- Sounds like a pretty easy script to write, I'd be happy to do so, for my own benefit as well. I'll look into it later tonight :) — MusikAnimal talk 22:23, 5 November 2013 (UTC)
- @Sven, this User:Gary King/show upload deletion logs.js might have been the script you were thinking of. NtheP (talk) 22:46, 5 November 2013 (UTC)
- I just created User:Equazcion/SkipFileWizard, in case that's what you wanted. It should change all file redlinks to take you to the filespace page as you wanted. Not sure if Gary King's script does something similar... (and pinging MusikAnimal in case he was going to create it). equazcion → 23:00, 5 Nov 2013 (UTC)
- Thanks! — MusikAnimal talk 00:27, 6 November 2013 (UTC)
- Thanks for the assistance everyone. Turns out I did have another script doing that, but for some reason it stopped working. Hopefully Equazcion's will work for a while. Sven Manguard Wha? 00:47, 6 November 2013 (UTC)
Diff and other problems (probably IE8)
Hi. I've been having various problems which I suspect may be to do with IE8 (on Win XP Home SP3 fully patched). They don't occur on Chrome. I use Vector skin.
- When opening a diff linked via https (like this one]), the first screenful looks fine, but: no text cursor appears when over text; double clicking a word of text fails to select it; clicking links on the top row, like Preferences and Watchlist, doesn't open the linked page; scrolling doesn't move the scroll bar but scolls garbage into the main area; and page-down key just puts nonsense on the page. The same diff linked via ordinary http (like this one) doesn't exhibit these problems. This issue has existed since late last week.
- Clicking the triangle to obtain enhanced diff view (wikEdDiff preference) has not worked for months. It just gives a shaded box with three dots inside.
- For about a month, the line of tabs to functions "Article, Talk, Read, Edit, ..." in some cases gets broken up and some of the tabs overwrite the page title. For example, as I type this, I see the "Project page" and "Talk" links are in the right place, but "Read, Edit, ..." are over the page title. (Clicking the displaced ones has the correct effect, though.) I have text size set to largest in my browser.
Thanks in advance for your help. --Stfg (talk) 13:15, 6 November 2013 (UTC)
- Seems related to #Unable to do anything through IE8.equazcion → 13:38, 6 Nov 2013 (UTC)
- I don't have IE8 unfortunately, but I can't replicate it on IE7. It does indeed sound related to what Equizcion is pointing at. The description appears to indicate that there might be some sort of 'overlay', which makes me fear you might have some spyware of advertisement toolbar or other type of browser extension installed that could be causing this. Could you check if you have any unexpected toolbars installed ? —TheDJ (talk • contribs) 14:12, 6 November 2013 (UTC)
- This is broken for me as well it seems. The script is maintained by User:Cacycle, and his feedback page for the script is User_talk:Cacycle/wikEdDiff
- When the tabs don't fit the screen anymore, they will indeed jump to the next line and partially overlap the title. This is expected behavior. It is also expected that dimensions at times change. If you use the largest text setting, then effects like these are to be expected, though less than ideal, the site is generally not optimized for 'extreme' situations. —TheDJ (talk • contribs) 14:12, 6 November 2013 (UTC)
(←) @TheDJ: thanks for looking at them.
- I've checked browser add-ons and installed programs, and nothing seems amiss. I've run a registry cleaner. No change. Will run a full scan overnight, but this only happens on Wikipedia and only with htpps.
- OK, I've posted there.
- Well, until a few weeks ago, they didn't do that. When the window was too narrow for all of them, the ones that wouldn't fit fell into the drop-down. I wonder if someone has fixed something, because if I expand the widow to screen width and then restore it to normal size, they do fall into the drop-down. Clicking show preview munges it again, but the same procedure puts it right once more. None of that was the case a few hours ago. The expand/contract procedure works slowly -- I see the munged screen and then watch it fall slowly into place -- so I wonder if there's a timing quirk.
--Stfg (talk) 17:28, 6 November 2013 (UTC)
Wikimedia Foundation IP addresses causing autoblocks
On User talk:Jimfbleak#Block.3F several users have reported autoblocks on IPs including 2620:0:862:1:A6BA:DBFF:FE38:FC71, which belongs to the Wikimedia Foundation[3], this is not the users' IP address. Another is 2620:0:862:1:A6BA:DBFF:FE38:D75F - there have also been several edits from the range today. Peter James (talk) 17:36, 6 November 2013 (UTC)
- I remember last week (ish) we were having similar issues with vandalism from IPv4 addresses on the Wikimedia server range.--Jezebel'sPonyobons mots 17:44, 6 November 2013 (UTC)
- Yes. This was again a problem caused by missing MediaWiki configuration for new Varnish cache servers that we deployed in Europe today. In some cases our cache servers use IPv6 to communicate with eachother, and MediaWiki wasn't yet configured to recognize their IPv6 IPs, causing these misattributed edits. This should have been fixed now. Our apologies! -- Mark Bergsma (talk) 17:49, 6 November 2013 (UTC)
- There have been more edits from 2620:0:862:1:91:198:174:67 and 2620:0:862:1:91:198:174:70 today. Peter James (talk) 21:38, 7 November 2013 (UTC)
This is not my IP address
Special:Mytalk is taking me to User talk:2620:0:862:1:91:198:174:67. That's a Wikimedia IP6 address. 149.241.39.156 (talk) 17:33, 7 November 2013 (UTC)
- This and the issue below are likely related to Wikimedia Foundation IP addresses causing autoblocks above. – PartTimeGnome (talk | contribs) 22:11, 7 November 2013 (UTC)
User talk:2620:0:862:1:91:198:174:70
It looks like a big lot of random IPs (including mine) get a "You have new messages" for everything that happens in this page. Do something, please--176.58.248.185 (talk) 17:57, 7 November 2013 (UTC)
Search box problem with back button
In the last day, I've noticed a problem with the search box (Monobook, Firefox 25, Windows XP). I click in the search box in the left margin, type in the first few letters of the page name, and when it appears in the suggestions, I arrow down to it and press Enter; this takes me to the appropriate page as it always has done. The problem arises when I then use either backspace (or alt+left-arrow) - it goes back, but then re-processes the search and moves forward again. I need to use backspace (or alt+left-arrow) twice quickly in order to go back and stay back. Is this a result of a MediaWiki change, or a bug introduced with Firefox 25 (to which I was upgraded recently)? --Redrose64 (talk) 00:29, 7 November 2013 (UTC)
Horrible slowdown
I can barely edit at the moment. It appears to be the usual recurring problem with bits.wikimedia.org (at least that seems to be what my browser says is the hang-up). It took several minutes just to get this page to display. I use the latest version of Firefox, if that matters.--Bbb23 (talk) 00:46, 7 November 2013 (UTC)
- By "latest", have you upgraded from FF 24 to FF 25 in the last couple of days? --Redrose64 (talk) 00:50, 7 November 2013 (UTC)
- I'm on v.25, but I can't remember how many days ago I upgraded. In any event, the slowdown just occurred late this afternoon, and it acts like all previous slowdowns I've seen.--Bbb23 (talk) 01:02, 7 November 2013 (UTC)
- I'm having similar problems attempting to access or edit articles and article histories in article space. I also use FF 25, but I also tried in Chrome (logged out) and it doesn't work any better. Not much trouble on this page, however. --Arxiloxos (talk) 01:22, 7 November 2013 (UTC)
- Just to chime in, all is well on my end. This could be an "availability zone" issue, maybe. I'm in the NYC area. The current WikiMedia performance status appears to be okay as well. I'm on Chrome 30 OSX. — MusikAnimal talk 01:39, 7 November 2013 (UTC)
- Fine here too, also NYC. For the record though I seem to have consistently experienced the slowdowns on queue with the reports here previously -- just none showing right now. equazcion → 01:48, 7 Nov 2013 (UTC)
- I'm having similar problems attempting to access or edit articles and article histories in article space. I also use FF 25, but I also tried in Chrome (logged out) and it doesn't work any better. Not much trouble on this page, however. --Arxiloxos (talk) 01:22, 7 November 2013 (UTC)
- I'm on v.25, but I can't remember how many days ago I upgraded. In any event, the slowdown just occurred late this afternoon, and it acts like all previous slowdowns I've seen.--Bbb23 (talk) 01:02, 7 November 2013 (UTC)
- I'm getting the same slowness. Pinging and tracerting bits.wikimedia.org doesn't seem to show any problems. --Closedmouth (talk) 02:01, 7 November 2013 (UTC)
- All seems fine on FF25 for me. Thinking it's a caching issue for Bbb... Try WP:BYPASSing. Technical 13 (talk) 03:55, 7 November 2013 (UTC)
- Whole site has been very slow for me (IE9 on Win7 in Australia) for the last 12 hours at least. DH85868993 (talk) 04:21, 7 November 2013 (UTC)
- Also very slow for me in Japan. I'm on Firefox 25/WinXP at the moment. — Mr. Stradivarius ♪ talk ♪ 05:51, 7 November 2013 (UTC)
- Working fine for me on Firefox 25/Windows 8 in Ohio. Based on locations provided here and listed on user pages, it seems that Americans are not having problems, but Australia and Japan are. Not sure how large the problem area is. Bbb23 and Arxiloxos, where are you at? I can't get a location off of either of your user pages. Knowing a location could help the devs track down the issue. jcgoble3 (talk) 07:52, 7 November 2013 (UTC)
- Also very slow for me in Japan. I'm on Firefox 25/WinXP at the moment. — Mr. Stradivarius ♪ talk ♪ 05:51, 7 November 2013 (UTC)
- Sounds like there could be some trouble in the new ulsfo Oceania caching center. —TheDJ (talk • contribs) 09:27, 7 November 2013 (UTC)
- Performance is much improved for me (in Australia) now. DH85868993 (talk) 09:41, 7 November 2013 (UTC)
- Whole site has been very slow for me (IE9 on Win7 in Australia) for the last 12 hours at least. DH85868993 (talk) 04:21, 7 November 2013 (UTC)
- We had network issues (congestion in one of our links) in our new ulsfo (San Francisco) datacenter that resulted in significant slowdowns during peak hours. We route traffic to datacenter based on users' geolocation and hence this issue affected only traffic coming from US & Canada West, Oceania and a minority of Asian countries. We've redirected North American traffic back to Ashburn, Virginia to free up the link and this seems to have alleviated the issues for now. We're still monitoring the situation and working on it so that we can have the issue permanently fixed and traffic rerouted back to San Francisco within the next days. Thanks to everyone here and on IRC for the report, this helped a lot. Faidon Liambotis (WMF) (talk) 11:51, 7 November 2013 (UTC)
- Sorry I was off-wiki and unable to answer the question about my location, but Faidon Liambotis (WMF)'s comment makes total sense as I'm in Southern California. I just got back on-wiki, and things seem to be okay. Thank you for looking into it and fixing it.--Bbb23 (talk) 00:58, 8 November 2013 (UTC)
Edit window collapsing when editing common.js
If this is just me, never mind, there are easy workrounds. With Windows 7, Firefox and WikEd, when I try editing common.js (or vector.css) the edit window displays and shrinks to nothing before I can get there. Preview showing OK. Disabling WikEd solves the problem. I wonder if this is FF 25 but I don't often edit custom.js. Editing other pages OK. Both Monobook and Vector. With WikEd running, same problem with IE8 but Chrome 30 is OK. Thincat (talk) 11:30, 7 November 2013 (UTC)
- I believe it's a known conflict between WikEd and the new default editor that attempts to show up for all .js pages. equazcion → 12:51, 7 Nov 2013 (UTC)
Notification bug?
So I saw somewhere where someone tried to notify me with a lowercase u. In other words, they used {{u|Biosthmors}} instead of {{U|Biosthmors}} but I didn't get a notification, I don't think. Is this a bug? Is it tracked? Can someone test it and see if it notifies me or not? Thanks. Biosthmors (talk) pls notify me (i.e. {{U}}) while signing a reply, thx 12:25, 7 November 2013 (UTC)
- Hi, Biosthmors. Thincat (talk) 12:27, 7 November 2013 (UTC)
- Echoing Thincat's sentiments, I, too, would like to express my hi to you, Biosthmors. equazcion → 12:49, 7 Nov 2013 (UTC)
- Biosthmors, I too would like to echo what Thincat and Equazcion had to say, and follow up with a strong hi. Technical 13 (talk) 12:55, 7 November 2013 (UTC)
- It works it works! Thanks all. Biosthmors (talk) pls notify me (i.e. {{U}}) while signing a reply, thx 13:16, 7 November 2013 (UTC)
Edit window: automated inserting bug
I'm using Firefox 25.0 with Java 1.7.0_45-b18, and I'm currently not able to use the automated text insertion tool below the edit window. It doesn't matter whether I select "Insert", "Wiki markup" or anything else from the dropdown menu, everytime I click on any of the templated options shown there, my browser automatically scrolls up to the top without putting anything into the edit window. The funny thing is also that the "Wiki markup" view is still showing the options from "Insert" in the first line. Is anybody else experiencing these problems? De728631 (talk) 19:52, 7 November 2013 (UTC)
- Yes, I'm having the same problem with Firefox 25.0 as you are. Funandtrvl (talk) 20:28, 7 November 2013 (UTC)
- Ditto (tritto?) on Chrome, Version 30.0.1599.116. — PinkAmpers&(Je vous invite à me parler) 20:33, 7 November 2013 (UTC)
- Twas the "Developers have started to remove long-deprecated methods. You should check the JavaScript console (in
debug=true
mode) and look for deprecation warnings and their stack trace. [4]" thing mentioned above in #Tech News: 2013-44. That should do it. Bypass your cache, if necessary. Anomie⚔ 20:36, 7 November 2013 (UTC) - Following up on a hunch... For those of you who are also seeing this, could you please go to d:WD:RFD and tell me if the
[show]
buttons in the collapsed-text templates work for you? — PinkAmpers&(Je vous invite à me parler) 20:39, 7 November 2013 (UTC)- No, they don't work either, when I click on them it scrolls the page up but doesn't open the "show" part. Funandtrvl (talk) 20:43, 7 November 2013 (UTC)
- It seems to be improving. I can now add stuff to the edit window but the scrolling issue is persisting. I've also run a JS console check of the edit window: I don't get any deprecation warnings but there seem to be lots of unknown and unfinished declarations. Btw, Funandtrvl, I can't use the [show] buttons either. De728631 (talk) 21:02, 7 November 2013 (UTC)
- The 'Show' buttons, they do nothing. (FF22) - The Bushranger One ping only 21:55, 7 November 2013 (UTC)
- And Wikidata's version of CollapseButtons did indeed use one of the removed methods that Anomie mentioned. Should be fixed now. Thanks, folks! — PinkAmpers&(Je vous invite à me parler) 22:34, 7 November 2013 (UTC)
- Indeed it is, and thanks for the quick fix! - The Bushranger One ping only 22:56, 7 November 2013 (UTC)
- And Wikidata's version of CollapseButtons did indeed use one of the removed methods that Anomie mentioned. Should be fixed now. Thanks, folks! — PinkAmpers&(Je vous invite à me parler) 22:34, 7 November 2013 (UTC)
- Something strange has happened to MediaWiki:Edittools - when I open a fresh edit window, all the links like – — ° ″ ′ ≈ ≠ ≤ ≥ ± − × ÷ ← → · § are blue, just as they used to be. But if I click any one of them, they all turn to the visited link colour (purple for most people). They didn't do that before today. I don't know enough about Javascript to know if this edit by Anomie (talk · contribs) would have caused it directly, or if it was an unintended side-effect. --Redrose64 (talk) 13:00, 8 November 2013 (UTC)
- Also, when using Wikimarkup:Insert, now the item is inserted, but there is a "top of page" action happening after the insert that didn't happen before, on FF25.0. Funandtrvl (talk) 19:05, 8 November 2013 (UTC)
- More: the first click to an edittools link doesn't just change the colour, it also adds a trailing # to the URL in the address bar, which in turn adds an entry to the browser's tab history. This means that the next time that you use the "back" button, nothing seems to happen - except that a trailing # disappears from the URL in the address bar. --Redrose64 (talk) 20:45, 8 November 2013 (UTC)
- Try it now (bypass your cache if necessary). Anomie⚔ 20:52, 8 November 2013 (UTC)
- It works, it doesn't jump to top of page now, thanks! Funandtrvl (talk) 21:21, 8 November 2013 (UTC)
- Try it now (bypass your cache if necessary). Anomie⚔ 20:52, 8 November 2013 (UTC)
- More: the first click to an edittools link doesn't just change the colour, it also adds a trailing # to the URL in the address bar, which in turn adds an entry to the browser's tab history. This means that the next time that you use the "back" button, nothing seems to happen - except that a trailing # disappears from the URL in the address bar. --Redrose64 (talk) 20:45, 8 November 2013 (UTC)
- Also, when using Wikimarkup:Insert, now the item is inserted, but there is a "top of page" action happening after the insert that didn't happen before, on FF25.0. Funandtrvl (talk) 19:05, 8 November 2013 (UTC)
Undismissable watchlist notice
A new notice has appeared at the top of my watchlist advertising three different discussions about paid editing. It's rather unusual that the notice doesn't have a "dismiss" link or any other way of removing the notice beyond editing my CSS to suppress all such notices. Where do I inquire about this further or whose attention should I get to address this? ElKevbo (talk) 21:49, 7 November 2013 (UTC)
- Same here; the "Dismiss" button, which was always previously present, is now AWOL. - The Bushranger One ping only 21:54, 7 November 2013 (UTC)
- I am seeing this as well. The notice needs a "dismiss" link added. Who needs to be asked to fix it? – Jonesey95 (talk) 22:54, 7 November 2013 (UTC)
- Same here -- and strange that this actually seems to be a two week-old notice that used to have the dismiss link, which I previously used, and now it's back with no link. None of MediaWiki:Watchlist-details, Template:Display/watchlist, or Template:Display seem to have been modified recently enough to cause it. equazcion → 23:01, 7 Nov 2013 (UTC)
- Looks like the same problem as above, this time with calls to "addOnloadHook" from MediaWiki:Common.js and calls to "getElementsByClassName" from somewhere not clearly indicated. To find this sort of thing, add
debug=true
to the URL and then look for warnings beginning with "MWDeprecationWarning" in your JavaScript console. Hopefully someone will fix these soon, otherwise I'll do it in a few hours (it's dinner time here). Anomie⚔ 23:08, 7 November 2013 (UTC)
- Looks like the same problem as above, this time with calls to "addOnloadHook" from MediaWiki:Common.js and calls to "getElementsByClassName" from somewhere not clearly indicated. To find this sort of thing, add
- Same here -- and strange that this actually seems to be a two week-old notice that used to have the dismiss link, which I previously used, and now it's back with no link. None of MediaWiki:Watchlist-details, Template:Display/watchlist, or Template:Display seem to have been modified recently enough to cause it. equazcion → 23:01, 7 Nov 2013 (UTC)
- I am seeing this as well. The notice needs a "dismiss" link added. Who needs to be asked to fix it? – Jonesey95 (talk) 22:54, 7 November 2013 (UTC)
"Dismiss" option missing from Watchlist Messages
Starting sometime yesterday, the "dismiss" option came up missing on Watchlist Messages. First it started with the "Three parallel policy proposals" message, and today on the "Editors are invited to comment on a proposal for a new Draft namespace" message.
Like most, I typically dismiss these messages as I am not that involved in discussions. Perhaps a search party should be called for the missing "dismiss" option? :) - Neutralhomer • Talk • 15:19, 8 November 2013 (UTC)
- Hi Neutralhomer. What you're reporting is likely related to these changes by Mr.Z-man to MediaWiki:Common.js/watchlist.js on November 8. Have you tried bypassing your browser cache? Do any error messages appear in your browser's JavaScript error console? --MZMcBride (talk) 19:12, 8 November 2013 (UTC)
- Sorry for the slow reply, had to run a few errands. After seeing your message, I tried Ctrl+F5 and that fixed it. I'm glad that fixed it, cause I honestly don't know where the JavaScript error console is on Firefox. :) Take Care...Neutralhomer • Talk • 20:08, 8 November 2013 (UTC)
- For future reference: WP:JSERROR describes how to do that for the major browsers. Amalthea 01:16, 9 November 2013 (UTC)
- Sorry for the slow reply, had to run a few errands. After seeing your message, I tried Ctrl+F5 and that fixed it. I'm glad that fixed it, cause I honestly don't know where the JavaScript error console is on Firefox. :) Take Care...Neutralhomer • Talk • 20:08, 8 November 2013 (UTC)
I had the same problem as described above, fortunately I had the idea to search here and your advice to use CTRL-F5 fixed it. Then I thought, for others who don't find this discussion, maybe it would be an idea to put up a watchlist message about this? --Ørjan (talk) 04:26, 11 November 2013 (UTC)
History popup link not working in Popups gadget
The "history" popup link in the Popups gadget ceased working properly a few hours ago. The popup does show the list of edits made to an article but responsible editors and the edit summaries are all "undefined." Has there been a recent change to the API or something similar that would cause this? Or is there something specific to the Popups gadget that has happened and requires attention at the Talk page specific to that gadget? ElKevbo (talk) 21:52, 7 November 2013 (UTC)
- @ElKevbo:: You are importing an outdated popups version in your user scripts. That version is broken since two days ago when a number of old deprecated functions were removed.
Remove those imports and activate the gadget in your preferences instead.
Amalthea 08:47, 8 November 2013 (UTC)
Category request
Can someone add a category to Category:BLP articles lacking sources and the associated templates in order to have an "All BLP articles lacking sources" category? Thanks. Werieth (talk) 00:34, 8 November 2013 (UTC)
- All that is needed on the template side is to add
|all=All BLP articles lacking sources
to the{{ambox}}
within{{BLP sources}}
, along the lines of the|all=All articles needing additional references
that's in{{refimprove}}
, and then for Category:All BLP articles lacking sources to be created. But has this been proposed at Template talk:BLP sources? See WP:EDITREQ. --Redrose64 (talk) 00:59, 8 November 2013 (UTC)- I havent filed an edit request because I was unsure of what needed modified and where to file it because I think it involves multiple templates. Werieth (talk) 01:01, 8 November 2013 (UTC)
- Sorry. I worded it wrongly above. Have modified.
- Besides
{{BLP sources}}
, which templates populate the existing subcats of Category:BLP articles lacking sources? --Redrose64 (talk) 01:04, 8 November 2013 (UTC)- {{BLP sources}} and {{BLP unsourced section}} where what was listed on the category. Werieth (talk) 13:27, 8 November 2013 (UTC)
- I havent filed an edit request because I was unsure of what needed modified and where to file it because I think it involves multiple templates. Werieth (talk) 01:01, 8 November 2013 (UTC)
Introducing Beta Features and Media Viewer
We're pleased to announce the first release of Beta Features, a new program that lets you try out new features before they are released widely. Beta Features is intended as a digital laboratory where community members can preview upcoming software and give feedback to help improve them. This special preference page lets designers and engineers experiment with new features on a broad scale, but in a way that's not disruptive.
One of the first beta features we will be testing together is Media Viewer, which aims to improve your viewing experience by displaying images in larger size and with less clutter than the current file info page. This first version 0.1 is still in early stages of development, but we invite community feedback right away on this discussion page, so we can improve it together in coming months. For a sneak peek at the next version 0.2 of the Media Viewer, check out these first mockups.
Beta Features and Media Viewer are now ready for early testing by logged-in users on MediaWiki.org, on Wikimedia Commons and on Meta.Wikimedia.org. Based on test results, we aim to release these beta features on all wikis worldwide on 21 November, 2013.
Here are some of the other beta features in our pipeline:
- VisualEditor Formulæ — edit algebra or equations on your pages (only on MediaWiki.org)
- Typography Refresh — make text more readable (scheduled for release Thursday, 14 November)
Would you like to try out Beta Features and Media Viewer now? After you log in on MediaWiki.org, Commons or Meta, a small 'Beta' link will appear next to your 'Preferences'. Click on it to see features you can test, check the ones you want, then click 'Save'. Learn more on the Beta Features page.
After you've tested these features, please let us know what you think here -- or join the discussions on this Beta Features page or on this Media Viewer page. You can report any bugs here for Beta Features or here for Media Viewer.
You're also welcome to join this IRC office hours chat on Friday, 8 November at 18:30 UTC.
Beta Features and Media Viewer were developed by the Wikimedia Foundation's Multimedia team, in collaboration with the Design, Mobile and VisualEditor teams. Along with other developers, we will be adding new features to this experimental program every few weeks. We are very grateful to all the community members who advised these projects — and look forward to many more productive collaborations in the future. :)
Enjoy, and don't forget to let us know what you think! Fabrice Florin (WMF) (talk) 02:03, 8 November 2013 (UTC)
- With all due respect (and not being sarky there...), if I saw that under a G11 tag, I'd delete it on sight... I'll look in, but you might not really be including me in the invite (bearing in mind my frequent underpoliteness at times on this page. Peridon (talk) 18:56, 8 November 2013 (UTC)
- To clarify in case the above isn't clear, VisualEditor like other parts of the Wikimedia software will be using Beta Features to introduce new features, for testing and feedback before they are made available to everyone. For the English Wikipedia, and other wikis where VisualEditor is available but not yet by default, VisualEditor itself will be a "Beta Feature", as well as the new features coming along (initially, formula editing and maybe in-line language editing). Jdforrester (WMF) (talk) 00:44, 9 November 2013 (UTC)
Page remaining 'unreviewed'
The page Preston Hill Country Park is marked as unreviewed in the Special:NewPagesFeed, when set to sort by oldest. I am assuming that unreviewed means un-patrolled as the is no [Mark this page as patrolled] 'button'on the article page to click, as on 'truly' new pages.
One point to note is that this page was started as a user draft in 2011, and has just (19:53, 7 November 2013) been moved to article space.
Sorry if this is a known bug. Or is there a workaround to get the page off the new pages list? 220 of Borg 02:53, 8 November 2013
- I see that this has now been 'resolved' in that the page now shows as 'reviewed' with a green tick, and as reviewed by Vantine84 (talk · contribs). I am certain I was logged in at the time. Any feedback on this? 220 of Borg 13:19, 8 November 2013 (UTC)
Contribution to Administrators' noticeboard
Hi, my edit made at 01:53 has been shaded and crossed out here [5]. So along with 16 other edits, it can't be displayed in history mode, although its available at 03:36 in Reaper Eternal's edit of "A matter of trust". I guess its a mistake, as the actual edit is still up on the noticeboard. Can the link to my 01:53 edit be fixed? --Rskp (talk) 06:56, 8 November 2013 (UTC)
- Looks like those edits were oversighted. It's probably not a mistake, but an intended hiding of history revisions that contained something bad, like someone's personal information. There's apparently no other way to make information hidden from public view, other than hiding entire history revisions. I don't think there's anything to be done about it -- but as long as your edit shows up in the latest revision, it shouldn't matter too much. equazcion → 07:26, 8 Nov 2013 (UTC)
- Yes, the edits were WP:OVERSIGHTed, which means that not only can regular users not see them, but admins can't either. If somebody posts something (hereinafter referred to as "the offending text") that falls within either WP:REVDEL or WP:OVERSIGHT, what normally happens first is that the offending text is removed: either the whole edit can be reverted, or if it was a substantially good edit with just part being the offending text, just that portion of the text can be removed (possibly being replaced with the
{{redacted}}
template). Whichever method was chosen, what happens next is that the original edit containing the offending text gets hidden. If there were edits after this but before the one where the offending text was removed, they will still contain the offending text (albeit not in the "diff" part at the top), so those must be hidden as well. You can still use the two columns of radio buttons in the history page to select the last edit before the hidden edits together with the first edit after them, and so compare them. --Redrose64 (talk) 12:19, 8 November 2013 (UTC)
- Yes, the edits were WP:OVERSIGHTed, which means that not only can regular users not see them, but admins can't either. If somebody posts something (hereinafter referred to as "the offending text") that falls within either WP:REVDEL or WP:OVERSIGHT, what normally happens first is that the offending text is removed: either the whole edit can be reverted, or if it was a substantially good edit with just part being the offending text, just that portion of the text can be removed (possibly being replaced with the
Easing use of an existing template & a request for help about creating a template
Could someone with more knowledge about editing templates than me please add an empty version of Template:Auto images there so that people can copy and paste it easily for the purposes of filling it out? Also, I am looking to create my first template soon, so if anyone is interested in helping me on this project, could they please say so on my talk page? I would want for the template to query an external website daily—so this might require a bot—in order to update a short amount of text on Wikipedia talk pages for medical topics. I'm hoping to get a proposal going that might get Wikipedia incoming links from an external website in return for links on our talk pages to theirs per this. Best regards. Biosthmors (talk) pls notify me (i.e. {{U}}) while signing a reply, thx 09:55, 8 November 2013 (UTC)
- I've added a blank for
{{auto images}}
to the doc page. --Redrose64 (talk) 12:45, 8 November 2013 (UTC)
Toolserver replication lag
I've noticed the lag on toolserver is up to 5 days (example). I don't think I've ever seen it so high. Is this normal? Ritchie333 (talk) (cont) 10:30, 8 November 2013 (UTC)
- Five days? I've seen it five weeks, and then some. The toolserver has been ropey for well over a year now; there's plenty in the archives for this page. --Redrose64 (talk) 12:49, 8 November 2013 (UTC)
- Have they already stopped maintaining it? Kudpung กุดผึ้ง (talk) 13:03, 8 November 2013 (UTC)
- I can see reports over the last year and half complaining about replication lag, to be sure, but they're all in the magnitude of seconds or hours, not days. Ritchie333 (talk) (cont) 14:21, 8 November 2013 (UTC)
- Replag used to be fairly common. It's less common nowadays. The Toolserver is deprecated and is no longer actively maintained. It is scheduled to be fully killed at the end of 2014. Users are advised to switch to private hosting or Wikimedia Labs. --MZMcBride (talk) 20:57, 8 November 2013 (UTC)
- I'm seeing database server lag on the order of 7 1/2 days now. VanIsaacWS Vexcontribs 12:27, 9 November 2013 (UTC)
- Since we know that Toolserver is being deprecated, it might be fair to assume that s1 replication has been turned off or broken in such a way that there is no motivation to fix it, with the expectation that anything important has migrated over to wmftools. The only regular thing I use now that (AFAIK) is still on Toolserver is Scottywong's AfD Stats tool, which is a good way of keeping track of AfDs I've contributed to, to see if there are any further developments. Ritchie333 (talk) (cont) 13:09, 10 November 2013 (UTC)
If Toolserver is being run down, can anyone point me in the direction of replacements for edit counter and article creator please? GiantSnowman 13:17, 10 November 2013 (UTC)
- Edit counter is now here. Article creator's main page is here, though doing an actual query seems to time out at the moment. Ritchie333 (talk) (cont) 14:01, 10 November 2013 (UTC)
Little diff issue
When showing diff, like in here, file links should contain hyperlinks to theirs pages, like templates or ordinary wikilinks. --Rezonansowy (talk • contribs) 13:58, 8 November 2013 (UTC)
- This is not a native MediaWiki feature, but rather an aspect of wikEd and its baby sister wikEdDiff. You will need to report this at User talk:Cacycle/wikEd. (ping Cacycle) jcgoble3 (talk) 19:21, 9 November 2013 (UTC)
Wikipedia changelog
Hi,
where i can find the log of changes made on wikipedia (on the server side) by developers?
I'm asking because, since yesterday (7/11/2013, ~14:00 UTC+2), my common.js not work properly. But on Nov 7, i haven't made any changes on my script. It worked perfectly, and then suddenly stoped to work (when i click on elements, nothing happens, seems like jquery/js conflict/error). The script reproduce gadged with characters and tags below textarea (because on ro.wiki our gadget is not so advanced, i made my own).
So can i view somewhere this changelog? XXN (talk) 17:30, 8 November 2013 (UTC)
- The functions from wikibits.js are now deprecated and many of them have been replaced by non-working ones, including
addHandler
that you’re using. See mw:ResourceLoader/JavaScript Deprecations — Ltrl G☎, 19:01, 8 November 2013 (UTC)
- Hi XXN: I believe wikitech:Server Admin Log is what you want. It's also replicated to Twitter, if you're into that kind of thing. --MZMcBride (talk) 20:54, 8 November 2013 (UTC)
- Thanks for answers. XXN (talk) 21:57, 8 November 2013 (UTC)
- XXN, you can also look for Special:Version#Installed_software and then navigate through the list of changes in the corresponding MW branch. In particular, notice the change named "Wrap up remaining legacy javascript (IEFixes, wikibits)", which replaces the old addOnloadHook by a dummy function. Helder 17:23, 9 November 2013 (UTC)
- @Helder.wiki: Ugh, no, it's not that bad.
addOnloadHook
andappendCSS
are among functions which will continue to work for now; but some others, likehookEvent
andgetElementsByClassName
, were replaced with dummies. Matma Rex talk 18:07, 9 November 2013 (UTC)
- @Helder.wiki: Ugh, no, it's not that bad.
- XXN, you can also look for Special:Version#Installed_software and then navigate through the list of changes in the corresponding MW branch. In particular, notice the change named "Wrap up remaining legacy javascript (IEFixes, wikibits)", which replaces the old addOnloadHook by a dummy function. Helder 17:23, 9 November 2013 (UTC)
I solved my problem by replacing addHandler, but after that still remain a litlle glitch. Each time i click on tags/characters below the textarea, this element is inserted, but also page is scrolling up automatically, like it′s clicked element such as #top. Paranormal activity )) XXN (talk) 21:00, 9 November 2013 (UTC)
Wikimedia error, site very slow, looks like when Internet first developed
I just got a Wikimedia error when I tried to go to any page on the site. I forgot to make a note of the number. Then I got a Gateway Time-Out error. Eventually, I got to the page I wanted. I was getting from one page to another just fine for the most part, then the site was very slow. On both the Technical Village Pump and on the page where I am now, fonts and blue links look like they did when the Internet was new, before anyone tried making pages appear more interesting.— Vchimpanzee · talk · contributions · 18:35, 8 November 2013 (UTC)
- Pages look normal now. All other sites have come up normally.— Vchimpanzee · talk · contributions · 18:39, 8 November 2013 (UTC)
- I suspect it was a temporary server problem that prevented style sheets from loading properly.--ukexpat (talk) 18:44, 8 November 2013 (UTC)
- So no major problem to report that caused the Wikimedia errors?— Vchimpanzee · talk · contributions · 18:50, 8 November 2013 (UTC)
- Every Wikipedia page is built from many more than one computer file: besides the file which shows the layout and text of the actual page, the other files mainly comprise images, style sheets and scripts. When certain servers are slow, the files that are requested from them may fail to be sent back before your browser gives up. If one of those files is a CSS file (a style sheet that describes the normal page styling for Wikipedia), your browser cannot format the page using that styling and so falls back on its defaults. These look like 20th century internet because style sheets were not generally used until HTML 4 was released in late 1997. --Redrose64 (talk) 20:33, 8 November 2013 (UTC)
- So no major problem to report that caused the Wikimedia errors?— Vchimpanzee · talk · contributions · 18:50, 8 November 2013 (UTC)
- I suspect it was a temporary server problem that prevented style sheets from loading properly.--ukexpat (talk) 18:44, 8 November 2013 (UTC)
Proposed change to MediaWiki:Linkshere
Hi. At (for example) Special:WhatLinksHere/Template:Infobox, the MediaWiki message MediaWiki:Linkshere is displayed. I've proposed a small change to its output here: MediaWiki talk:Linkshere#Change "transclusion count" link. --MZMcBride (talk) 19:03, 8 November 2013 (UTC)
Problem with protected templates now have pink background in edit mode
See: for an example. My main concern is that the pink background is too dark, I'm having a bit of trouble reading it, and I don't have red-green color blindness. I can only imagine the difficulty of someone that has that problem. I think a white background would be best, the "notice" would still be pink. See: WP:ACCESS, we really shouldn't make WP harder to read for anyone out there. Thanks for your consideration. Funandtrvl (talk) 21:32, 8 November 2013 (UTC)
- I was wondering about that too. Is that just standard to signify that one is editing a protected page? Ie. is that what admins see when editing sysop'd pages? While I don't personally have trouble with it, I could see other people having trouble, depending on their displays and eyes. equazcion → 21:48, 8 Nov 2013 (UTC)
- From my experience on other projects, yes, this is what admins see on FPP'd pages. I think it's a fairly recent change (I could be wrong about that, though), but the idea is to avoid situations where an admin doesn't realize they're editing through protection. That should go doubly for template editors, so I think this background is definitely a good idea. (The notice is the same color regardless of protection level, so you might just think the page is semi'd.) @Funandtrvl: If you really don't like the background, though, just modify the
mw-textarea-protected
class in your personal common.css. — PinkAmpers&(Je vous invite à me parler) 22:10, 8 November 2013 (UTC)- I'm pretty sure that semi-prot pages get a normal white edit box, except for unconfirmed users who get grey. Anyway, to change the background colour of the edit box on a template-prot page to a paler pink, put this in Special:MyPage/common.css: - the
.mw-textarea-protected, .ns-8 textarea { background-color: #ffe8e8; }
, .ns-8 textarea
is not necessary if you're not an admin, since it's to apply the same colour to the edit box of pages in the MediaWiki: namespace. --Redrose64 (talk) 00:03, 9 November 2013 (UTC)
- I'm pretty sure that semi-prot pages get a normal white edit box, except for unconfirmed users who get grey. Anyway, to change the background colour of the edit box on a template-prot page to a paler pink, put this in Special:MyPage/common.css:
- It was introduced almost at the same time as Wikipedia:Template editor (an editors privilege to edit protected templates, but not with full adminship).
It is a dark tone indeed. Not that much. -DePiep (talk) 22:22, 8 November 2013 (UTC) -DePiep (talk) 01:08, 9 November 2013 (UTC)- I'm fairly certain it wasn't. I've been getting that on Wikidata for months on fully protected pages. The only reason you're just noticing it here is that you're a template editor now, and you don't see the pink background unless you have the ability to edit the page in the first place. — PinkAmpers&(Je vous invite à me parler) 22:38, 8 November 2013 (UTC)
- The pink background for the edit box of a template-protected page is exactly the same as that which admins have had for years when editing a full-prot page. Personally I would favour a different colour (yellow?) for template-prot pages, since the pink is a warning to admins that the page is full-prot and that they should exercise greater caution. The unusual colour is in-your-face, and if a different colour were used you wouldn't need to carefully check whether the message at the top states "... only users with administrative rights can make edits ..." or "... only users with administrative or template-editor rights can make edits ...". --Redrose64 (talk) 23:49, 8 November 2013 (UTC)
- A fair point. Shall we take a quick straw poll and file a bug? (Until recently it wasn't possible to set things like this for protection levels other than autoconfirmed and sysop, but I think the necessary core updates have been made.) — PinkAmpers&(Je vous invite à me parler) 01:44, 9 November 2013 (UTC)
- If anything, protected templates need the most caution, because a mistake could potentially screw up tens of thousands of pages. I don't think a distinction is really necessary. Mr.Z-man 02:30, 9 November 2013 (UTC)
- I agree, there's no good reason that editors should use a different level of caution when editing a template-protected page versus a fully-protected page. The only reason I can think of is that there's a somewhat larger pool of editors with the ability to revert the former. Anomie⚔ 13:49, 9 November 2013 (UTC)
- The term "template-protected" is perhaps misleading. When an admin goes for the "protect" or "change protection" tab, they get some selection lists. Two of these are titled "Edit" and "Move", and they each offer exactly the same four options for all pages: "Allow all users"/"Require autoconfirmed or confirmed access"/"Require template editor access"/"Require administrator access". This means that any page where it is possible to set the protection level may be set as template-protected, even if it's not a template. Templates may still be set as full-prot, and these are surely the ones requiring greatest caution, otherwise the prot level wouldn't be set so high. An admin may still screw up almost three million pages by making an ill-advised edit to
{{reflist}}
. --Redrose64 (talk) 11:59, 10 November 2013 (UTC)- That's only because it's not technically possible to limit protection levels to certain namespaces in MediaWiki. If we really wanted to, we could hide the option on non-template pages with Javascript. There's really no reason not to reduce the level on {{reflist}}; I assume it hasn't been done only because no one has asked yet. The template editor group was specifically made for templates that are protected only due to transclusion count. {{Navbar}} has been changed to templateeditor and is used on over 7 million pages. Strictly speaking, I don't think anything in the current protection policy would justify fully-protecting a template solely for visibility reasons (except things on the Main Page). Mr.Z-man 16:28, 10 November 2013 (UTC)
- The term "template-protected" is perhaps misleading. When an admin goes for the "protect" or "change protection" tab, they get some selection lists. Two of these are titled "Edit" and "Move", and they each offer exactly the same four options for all pages: "Allow all users"/"Require autoconfirmed or confirmed access"/"Require template editor access"/"Require administrator access". This means that any page where it is possible to set the protection level may be set as template-protected, even if it's not a template. Templates may still be set as full-prot, and these are surely the ones requiring greatest caution, otherwise the prot level wouldn't be set so high. An admin may still screw up almost three million pages by making an ill-advised edit to
- I agree, there's no good reason that editors should use a different level of caution when editing a template-protected page versus a fully-protected page. The only reason I can think of is that there's a somewhat larger pool of editors with the ability to revert the former. Anomie⚔ 13:49, 9 November 2013 (UTC)
- The pink background for the edit box of a template-protected page is exactly the same as that which admins have had for years when editing a full-prot page. Personally I would favour a different colour (yellow?) for template-prot pages, since the pink is a warning to admins that the page is full-prot and that they should exercise greater caution. The unusual colour is in-your-face, and if a different colour were used you wouldn't need to carefully check whether the message at the top states "... only users with administrative rights can make edits ..." or "... only users with administrative or template-editor rights can make edits ...". --Redrose64 (talk) 23:49, 8 November 2013 (UTC)
- I'm fairly certain it wasn't. I've been getting that on Wikidata for months on fully protected pages. The only reason you're just noticing it here is that you're a template editor now, and you don't see the pink background unless you have the ability to edit the page in the first place. — PinkAmpers&(Je vous invite à me parler) 22:38, 8 November 2013 (UTC)
- This is a local CSS override that enwiki made. It only shows up for admins and users in the templateeditor group, since both have custom group CSS. Legoktm (talk) 02:04, 9 November 2013 (UTC)
- Specifically, the page with the CSS is MediaWiki:group-templateeditor.css. Anomie⚔ 13:49, 9 November 2013 (UTC)
- Correct. It is however a very very old customization. It's been in place since early 2008 at least. I suspect it was changed to align it a bit with other edit notices in the the visual styles of talk page, documentation and mbox (specifically) deletion templates. Since it is mostly to warn about fully protected situations, I have little problem with us removing that highlight from template protected rights. —TheDJ (talk • contribs) 09:54, 11 November 2013 (UTC)
- If we remove the pink from MediaWiki:group-templateeditor.css but leave it in MediaWiki:group-sysop.css, this means that if a user with templateeditor rights edits a template-prot page, they will get a white background; but if a user with sysop rights edits the same page they will still get a pink background. That to me is the wrong way around: if admins are to get a warning which is different from that shown to templateeditors, the admin's warning should be weaker, not stronger. --Redrose64 (talk) 20:29, 11 November 2013 (UTC)
- Correct. It is however a very very old customization. It's been in place since early 2008 at least. I suspect it was changed to align it a bit with other edit notices in the the visual styles of talk page, documentation and mbox (specifically) deletion templates. Since it is mostly to warn about fully protected situations, I have little problem with us removing that highlight from template protected rights. —TheDJ (talk • contribs) 09:54, 11 November 2013 (UTC)
- Specifically, the page with the CSS is MediaWiki:group-templateeditor.css. Anomie⚔ 13:49, 9 November 2013 (UTC)
- From my experience on other projects, yes, this is what admins see on FPP'd pages. I think it's a fairly recent change (I could be wrong about that, though), but the idea is to avoid situations where an admin doesn't realize they're editing through protection. That should go doubly for template editors, so I think this background is definitely a good idea. (The notice is the same color regardless of protection level, so you might just think the page is semi'd.) @Funandtrvl: If you really don't like the background, though, just modify the
Disappearing edit
I'm afraid that my edit (response) on Talk:Internet_Archive has disappear, I remember I've responded to him. I've checked my browser history, I've visited this page around 12. Is it possible that something like this to happen? --Rezonansowy (talk • contribs) 21:40, 8 November 2013 (UTC)
- I do see a comment by you on that page. If you can do a page search, look for "dilemma", should point you to your comment. equazcion → 21:51, 8 Nov 2013 (UTC)
- That was yesterday, but there is no comment today. Perhaps you forgot to press "save page"? — Martin (MSGJ · talk) 21:54, 8 November 2013 (UTC)
- I hope that's my memory holemy brain bug???, but is it possible that edit may disappear? --Rezonansowy (talk • contribs) 22:51, 8 November 2013 (UTC)
- Nope, it isn't. Graham87 09:04, 9 November 2013 (UTC)
- Err, of course it is. We intentionally "disappear" edits regularly (using oversight, suppression, super-suppression, or selective undeletion). It's also possible (for example) for slave servers to become out of sync with master servers or other server-side strangeness to occur (cf. bugzilla:56589 and bugzilla:56577). While it's most likely human error (e.g., forgetting to press "save page"), we cannot and should not definitively say that edits can't disappear. --MZMcBride (talk) 16:00, 11 November 2013 (UTC)
- Nope, it isn't. Graham87 09:04, 9 November 2013 (UTC)
- I hope that's my memory holemy brain bug???, but is it possible that edit may disappear? --Rezonansowy (talk • contribs) 22:51, 8 November 2013 (UTC)
- That was yesterday, but there is no comment today. Perhaps you forgot to press "save page"? — Martin (MSGJ · talk) 21:54, 8 November 2013 (UTC)
Serif font-family specification in user CSS now does nothing
I'm not sure how long this has been the case; maybe a week or so? My CSS consists of
body {font-family: serif; font-size: 88%;}
and yet Firefox displays Wikipedia text in its sans-serif font. (Of course I can set the serif font to be the default, but I don't want to do that.) Archelon (talk) 21:52, 8 November 2013 (UTC)
- Also, when I "Allow pages to choose their own fonts, instead of my selections above" (in Firefox's preferences) Wikipedia displays in some other sans-serif font. Archelon (talk) 23:22, 8 November 2013 (UTC)
- Does a span-tag work, when the body text remains sans-serif font, as in:
- <span style="font-family: serif; font-size: 88%;">This is serif text</span>
- As showing "This is serif text" and what font appears for the span-tag? -Wikid77 (talk) 09:36, 9 November 2013 (UTC)
- Well, that's strange. The text between the tags there appears in a different (narrower) sans-serif font from all the other text, both with and without allowing pages to choose their own fonts (but it's a different skinnier sans-serif font in each case). ...No, to be precise I think it's the same font as the surrounding text when I don't allow pages to choose their own fonts, but reduced in size; the 88% is being applied twice. (How does it look to you?) Archelon (talk) 19:13, 9 November 2013 (UTC)
- I think the font I'm seeing between the serif tags is the same as the one it's using for the menu items along the top and edge of the page. Also, italicized text is appearing in (the italic version of) my serif font, but only when I "allow pages to choose their own fonts"; otherwise, it's just the italic version of my default sans-serif font. Where does Wikipedia's font specification come from, anyway? It must be demanding that a sans-serif font be used. Although Firefox may also be doing something weird. Archelon (talk) 19:13, 9 November 2013 (UTC)
- You should check Firefox's font setting; it probably has a sans-serif font set for your default serif. — Edokter (talk) — 22:17, 9 November 2013 (UTC)
- Nope; my Default font is "Droid Sans", and then on the Advanced menu I've got Proportional set to "Sans Serif", Serif set to "CMU Classical Serif", Sans-serif set to "Droid Sans", and Monospace set to "Droid Sans Mono". Oh, and of course with these same settings I used to have Wikipedia displaying in my serif font. I have now discovered your essay here; perhaps it will prove helpful. It confirms my suspicion that Wikipedia specifies sans-serif (I wonder why it is not considered best to let the user decide...?); it has also caused me to realize that I was missing the mscorefonts package (I'm on Ubuntu), but that of course was not the problem. Archelon (talk) 00:07, 10 November 2013 (UTC)
- Have you checked that the CMU Classical Serif font is not corrupt or not properly installed? Does it work in another application? Also try setting a different serif font, ie. Droid Serif. — Edokter (talk) — 11:01, 10 November 2013 (UTC)
- It appears you are correct; I thought I had already tested that, but apparently I hadn't. So everything works as expected as long as I don't try to use the specific font "CMU Classical Serif". Now all I need to do is figure out what has gone wrong with that font. Thank you. Archelon (talk) 19:47, 10 November 2013 (UTC)
- Have you checked that the CMU Classical Serif font is not corrupt or not properly installed? Does it work in another application? Also try setting a different serif font, ie. Droid Serif. — Edokter (talk) — 11:01, 10 November 2013 (UTC)
- Nope; my Default font is "Droid Sans", and then on the Advanced menu I've got Proportional set to "Sans Serif", Serif set to "CMU Classical Serif", Sans-serif set to "Droid Sans", and Monospace set to "Droid Sans Mono". Oh, and of course with these same settings I used to have Wikipedia displaying in my serif font. I have now discovered your essay here; perhaps it will prove helpful. It confirms my suspicion that Wikipedia specifies sans-serif (I wonder why it is not considered best to let the user decide...?); it has also caused me to realize that I was missing the mscorefonts package (I'm on Ubuntu), but that of course was not the problem. Archelon (talk) 00:07, 10 November 2013 (UTC)
- You should check Firefox's font setting; it probably has a sans-serif font set for your default serif. — Edokter (talk) — 22:17, 9 November 2013 (UTC)
- I think the font I'm seeing between the serif tags is the same as the one it's using for the menu items along the top and edge of the page. Also, italicized text is appearing in (the italic version of) my serif font, but only when I "allow pages to choose their own fonts"; otherwise, it's just the italic version of my default sans-serif font. Where does Wikipedia's font specification come from, anyway? It must be demanding that a sans-serif font be used. Although Firefox may also be doing something weird. Archelon (talk) 19:13, 9 November 2013 (UTC)
- Well, that's strange. The text between the tags there appears in a different (narrower) sans-serif font from all the other text, both with and without allowing pages to choose their own fonts (but it's a different skinnier sans-serif font in each case). ...No, to be precise I think it's the same font as the surrounding text when I don't allow pages to choose their own fonts, but reduced in size; the 88% is being applied twice. (How does it look to you?) Archelon (talk) 19:13, 9 November 2013 (UTC)
Syntax highlight problem on common.js
Syntax highlight doesn't work when I preview my common.js. And code editor feature doesn't work as well, the edit box is empty. --Rezonansowy (talk • contribs) 22:45, 8 November 2013 (UTC)
- Do you use WikEd? If so, see #Edit window collapsing when editing common.js above. --Redrose64 (talk) 23:52, 8 November 2013 (UTC)
- Thanks! --Rezonansowy (talk • contribs) 23:08, 9 November 2013 (UTC)
Make SidebarTranslate into a gadget
See Wikipedia:Village pump (proposals)#Make SidebarTranslate into a gadget. equazcion → 02:59, 9 Nov 2013 (UTC)
Image in infobox rendering incorrectly after it has been updated in commons
I am working on the page Hat Works. On 8th November, the image File:Hat Works.jpg in the infobox showed a lot of tarmac and little of the supject. I went to Commons, downloaded, cropped and replaced the image. Simply it went from a portrait to a landscape. Back to Hatworks, and the new image was there but stretched to occupy original portrait format in the infobox. Ouch. Re loaded the page still the same. Loaded the page on a different computer- the stretch image was there too.
Edit the page to see if there was some fixed parameter in the infobox. In the edit mode- the image was rectified. I did a dummy edit and saved. The page came up correctly this time. Tested the same on the other computer and it was fixed there too. Not a serious problem- I am just reporting it to assist.
For what it is worth the browser is 24.0 Firefox for Linux Mint on the main machine and on the second 24.0 Firefox for Ubunt canonical. Skin monobook. -- Clem Rutter (talk) 10:41, 9 November 2013 (UTC)b
- This sounds like Template:Bug. You could probably also have just purged the page or made a null edit. Anomie⚔ 13:55, 9 November 2013 (UTC)
At last: a word for non-talk namespaces
In talking namespaces the words like "talkpage" and "talk namespaces" are well-understood and independent. The opposite is often described as "non-talkpage" or "non-talk namespaces" - clumsy and relative. Wikipedia:Namespace uses "Basic namespace(s)" for the non-talkies -- a wording I am not familiar with am do not associate with its apparent meaning.
Now at last I found a word that describes these namespaces clear, once and for all : Subject space(s). It is exactly and exclusively the opposite of "Talk space(s)" (as to be used in: "Take the subject page of this page"; "A page has its subject space and talk space"). And brilliantly this is the complete pair of magic words: {{SUBJECTSPACE}}, {{TALKSPACE}}
.
My question now is: why is this word not commonly used in talks &tc.? Let me put it this way: I suggest to use Subjectspace instead of anything else as the complementary of "Talkspace" (and don't mention the alternative magic word ever). Am I missing something? -DePiep (talk) 16:40, 9 November 2013 (UTC)
- Adding: writing "Talkspace" is OK. But is "Non-talkspace" a namespace at all? -DePiep (talk) 16:44, 9 November 2013 (UTC)
- Usually it's clearer to just specify what kind of page it is - "article", "project page", "user page", etc. "Article talk page" or "Project talk page" is just a little clunky and redundant, so it's usually just shortened to "talk page." I suppose if you're referring to all of the non-talk namespaces it might be better, but that's not as common of a scenario. Mr.Z-man 17:18, 9 November 2013 (UTC)
- A bit around the point. I needed a word to say "The AQ assessment template is placed on the talk page, but refers to the subject page". -DePiep (talk) 09:22, 10 November 2013 (UTC)
- Yeah, there are certainly situations where one needs to refer to a non-specific non-talk page. I had this dilemma when writing the script and documentation for CatListMainTalkLinks. I dealt with it by making my own word. equazcion → 09:27, 10 Nov 2013 (UTC)
Date dependent template?
Is it possible to have date dependent templates? For example, I just added a new announcement to Wikipedia:WikiProject Basketball/Women's basketball. I added the new item template to mark it, but would like that to go away after, say two weeks. Is there a way to display one things before a specified day and other thing (in this case blank) after that date? — Preceding unsigned comment added by Sphilbrick (talk • contribs) 14:42, 10 November 2013 (UTC)
- Template:Expiry can do this. However, the announcement might still show after the expiry date you set, because MediaWiki caches page content. The announcement would disappear next time someone did something to invalidate the cache, such as editing the page, purging the page, or editing a template used on the page. (There might be a delay for the latter case; it can take a while for template changes to work through the job queue.) – PartTimeGnome (talk | contribs) 21:58, 10 November 2013 (UTC)
ToC and vertical margin increase?
On the majority of articles, table of contents box is positioned too close to the lead section, making that specific part of articles layout looking not so nice. How about having about 10 pixels of spacing there, something like adding style="margin-top: 10px;"
to the outer <div>
element? It would make positioning of the content box much, much better... Thoughts? -- Dsimic (talk) 18:37, 10 November 2013 (UTC)
- You can make this change for just yourself by adding the following to User:Dsimic/common.css, then bypassing your cache:
#toc { margin-top: 10px; }
- However, I'd suggest using measurements in em (e.g. 0.5em) rather than px. Measurements in px will be a different physical size depending on screen resolution. – PartTimeGnome (talk | contribs) 21:25, 10 November 2013 (UTC)
- That's great, but it would probably be beneficial to make this change system-wide. Maybe it's just me, :) but the layout looks so much more consistent with that additional spacing. -- Dsimic (talk) 21:33, 10 November 2013 (UTC)
- Just tried it out, and 0.9em fits almost perfectly. -- Dsimic (talk) 21:42, 10 November 2013 (UTC)
Ads appearing in Wikipedia
I once accidently downloaded the Java update virus then I did a scan using Malwarebytes' Anti-Malware, which did not completely get rid of that virus and now there are ads appearing in Wikipedia when I use Google Chrome Blackbombchu (talk) 22:25, 10 November 2013 (UTC)
- Yes, Wikipedia:FAQ/Readers#Why do I see commercial ads at Wikipedia? mentions that some malware or browser extensions can add ads to Wikipedia pages. I don't know how to get rid of them in your case if it isn't a Google Chrome extension which can be disabled. PrimeHunter (talk) 22:48, 10 November 2013 (UTC)
Edit count
Hello.
The pie chart diagram on the edit counter special page seems to suffer from an expired certificate.
HandsomeFella (talk) 22:38, 10 November 2013 (UTC)
Need help using software MWdumper
Hello I'm trying to export 800 .xml files to the mediawiki localhost using the software 'MWdumper', and I was wondering if I can upload more than 1 file at a time since uploading 800 articles individually will take a lot of time. Please let me know what to do or if there is a software that I could use that can perform this function. Thanks alot! Kclalwani (talk) 22:39, 10 November 2013 (UTC)
Convert all outgoing links from http:// to https:// ?
What does the team think? It will make us all more Secure and in these terrorism-filled times, we can all use a bit more Security. See context Andy Dingley (talk) 01:53, 11 November 2013 (UTC)
- Your link is to a user who changes http://web.archive.org/ to https://web.archive.org but doesn't appear to change links to other sites. If you literally mean all links then at Wikipedia:Village pump (technical)/Archive 116#Lua-based cites could auto-link as https I said: "Strong oppose to creating millions of unchecked links. A sample of five websites I frequently visit gave four failures on https." PrimeHunter (talk) 02:15, 11 November 2013 (UTC)
- [6] http://www.youtube.com to https://www.youtube.com
- If you want a concrete example of what this breaks, look at translate.google.co.uk – which won't process a https:// link Andy Dingley (talk) 02:24, 11 November 2013 (UTC)
- I see you first posted to an existing discussion at Wikipedia:Village pump (miscellaneous)#Internet Archive and HTTPS. Let's not start a new discussion here. PrimeHunter (talk) 02:33, 11 November 2013 (UTC)
CSD helper script
Would some kind JavaScript coder be willing to fix User:Ale jrb/Scripts/csdhelper.js? It has stopped working since the last time I tried it (last week maybe?), and I presume that it is using some of the deprecated JavaScript that the developers recently removed. — Mr. Stradivarius ♪ talk ♪ 02:57, 11 November 2013 (UTC)
(edit conflict) hookEvent
is depreciated. Change the last line from
hookEvent ( 'load', launchCsdHelper );
to$( document ).ready( launchCsdHelper );
Additionally, for good measure, User:Ale_jrb/Scripts/waLib.js should probably be fixed as well. Change
hookEvent ( 'load', function () { wa_window.prototype = new wa_document; wa_element.prototype = new wa_document; });
to
$(document).ready( function( $ ) { wa_window.prototype = new wa_document; wa_element.prototype = new wa_document; } );
Let me know if for some reason this doesn't work. Thanks, Theopolisme (talk) 03:13, 11 November 2013 (UTC)
- I tried that, but it still doesn't seem to be working. I hadn't done it for waLib but did after your post, and it still doesn't appear to be working. I'm using copies in my userspace, User:Equazcion/csdhelper.js and User:Equazcion/waLib.js. I'm still not not sure what I'm supposed to be seeing if it works, but these seem to be breaking other js, so I'm pretty sure there is still something wrong. equazcion → 03:20, 11 Nov 2013 (UTC)
- I think you're mistaken, it works -- read the docs and then test it on a page in CAT:CSD. :) Theopolisme (talk) 03:23, 11 November 2013 (UTC)
- Alrighty, long as it works for those who need it :) equazcion → 03:25, 11 Nov 2013 (UTC)
- I've updated Ale jrb's scripts,[7][8] but the CSD helper still isn't working. You're supposed to see an extra tab at the top of pages that have been tagged for speedy deletion, immediately to the right of the "Talk" tab. When you click on it, it pops up a menu of actions, e.g. delete the page, decline this speedy deletion, send a note to the tagger, etc. I tried Equazcion's version too, but that doesn't seem to be working either. — Mr. Stradivarius ♪ talk ♪ 05:16, 11 November 2013 (UTC)
- Mr. Stradivarius, could you try my version again? It appears to be working for me now. The major difference was that I copied the entire waLib.js into the parent script, in place of the importScript line that used to bring it in. There's been some talk of importScript lately, not sure if there have been changes that could explain this. equazcion → 06:18, 11 Nov 2013 (UTC)
- Yep, your version is working for me now. Thanks! — Mr. Stradivarius ♪ talk ♪ 06:24, 11 November 2013 (UTC)
- Mr. Stradivarius, could you try my version again? It appears to be working for me now. The major difference was that I copied the entire waLib.js into the parent script, in place of the importScript line that used to bring it in. There's been some talk of importScript lately, not sure if there have been changes that could explain this. equazcion → 06:18, 11 Nov 2013 (UTC)
- I've updated Ale jrb's scripts,[7][8] but the CSD helper still isn't working. You're supposed to see an extra tab at the top of pages that have been tagged for speedy deletion, immediately to the right of the "Talk" tab. When you click on it, it pops up a menu of actions, e.g. delete the page, decline this speedy deletion, send a note to the tagger, etc. I tried Equazcion's version too, but that doesn't seem to be working either. — Mr. Stradivarius ♪ talk ♪ 05:16, 11 November 2013 (UTC)
- Alrighty, long as it works for those who need it :) equazcion → 03:25, 11 Nov 2013 (UTC)
- I think you're mistaken, it works -- read the docs and then test it on a page in CAT:CSD. :) Theopolisme (talk) 03:23, 11 November 2013 (UTC)
User:Armbrust has reported that my edit to the CSD helper script broke Hotcat and Twinkle for him. Has anyone else noticed any problems with either of these? — Mr. Stradivarius ♪ talk ♪ 14:26, 11 November 2013 (UTC)
- Yes, that's what I was referring to above about javascript breaking. I don't think it was your edit in particular, but whatever caused the script to break originally. If you replace it with my version it should clear up. equazcion → 14:28, 11 Nov 2013 (UTC)
Error, unable to save edit at meta.
Tried several times to save an edit, in Preview it says, "Your edit has been rejected because your client mangled the punctuation characters in the edit token. The edit has been rejected to prevent corruption of the page text. This sometimes happens when you are using a buggy web-based anonymous proxy service." What does it mean? What's the solution to this? --Ansuman (talk) 10:14, 11 November 2013 (UTC)
- Well...are you using a web-based anonymous proxy service? If so: stop using a web-based anonymous proxy service ;p Ironholds (talk) 12:26, 11 November 2013 (UTC)
- Not that i know of, been using the same data connection since a year. It worked once, then again same issue. 2 days back faced the same issue, but it worked after a while. Today it's been a long while. Is this how we get to know that we are on "anonymous proxy"? Could it be some other technical issue? How come I face this on Meta, but not here on enwiki? Please help! -- ɑηsuмaη « ৳ᶏ ɭϞ » 14:25, 11 November 2013 (UTC)
Tech News: 2013-45
13:08, 11 November 2013 (UTC)
- I found this informative. Thank you. Killiondude (talk) 18:21, 11 November 2013 (UTC)
Photosphere
User:Wikiwal has permission to use this set of pictures http://sphereshare.net/#!/s/b124ad9c80361f933195c423da8e73a4 for wikipedia (OTRS-pending), commons:Category:Evangelische Kirche Bettenhausen (Lich). Is there any chance to use it in a proper way? -- Cherubino (talk) 13:42, 11 November 2013 (UTC)
European slowdown
European users might have noticed a bit of a slowdown on sunday evening and monday morning. (I personally had bits requests of over 12 seconds). It looks like there was an issue with an overloaded link between Europe and America. Some traffic was moved to another link and operations will be working on resolving the root problem. In case anyone was wondering what was going on :D —TheDJ (talk • contribs) 13:49, 11 November 2013 (UTC)
- I did notice, but thought it was just the usual talk page slow save that I get... 8-( Peridon (talk) 17:11, 11 November 2013 (UTC)
Adding links to other Wikipedias
I just went to add a frwiki link to an article here. I clicked on the little cog wheel. It told me I must be logged in. Yes, I was logged in here. OK, I went to the WikiData link and logged in there. No, the cog wheel and its pop-up wouldn't accept that I was logged in. So I did it the old way with [[fr:title]], and it's put the link in in the sidebar. But it's added a second line with a bullet point but no text as well as the Français line. Am I doing something wrong, or is it the way the thing's supposed to work? Or should I just ignore the cog wheel and stick to the old way? If so, what it the little wheel for? The article in question is Passage du milieu. Peridon (talk) 17:07, 11 November 2013 (UTC)
Side bar font
On the side bar, I can read 'Changes' and 'here' clearly. But in the languages bit on the main page, I can see what looks like 'Doutsch' and 'Esporanto' (and more too). Possibly like Dcutsch and Espcranto. Why is the languages bit in a different font that (for me at least) has issues with the monitor display? I don't remember it being like this until recently. I use Monobook and en-gb on (for this machine) a 17" CRT monitor. Peridon (talk) 17:21, 11 November 2013 (UTC)
- @Peridon: Because of ULS. See #Interlanguage links in different font above. Matma Rex talk 17:35, 11 November 2013 (UTC)
- (edit conflict) Are you using Windows? They recently changed the font, and it has issues on Windows (I've seen it on my home WinXP machine). Chris857 (talk) 17:37, 11 November 2013 (UTC)
- XP Pro set to classic view (I detest big bright buttons for kids...). Who decided to use something that has issues with Windows? I mean, Linux might be better but some of us are tied to Windows by software compatibility. I've got loads of stuff in formats that won't even work on Vista upwards, let alone Linux, and progs that are Windows only (most versions). And then there are all the people that have Windows because it came with the machine. Probably only a few million here and there... Thanks to Matma Rex, by the way. I missed that thread., but have now joined it. Peridon (talk) 17:58, 11 November 2013 (UTC)
References
Is there a gadget or script that would notify / stop the user from adding a reference if it is already linked to on that page. Its easy to spot if the article only has a few refs, but if there is say a 100 its not so easy.Blethering Scot 19:19, 11 November 2013 (UTC)
- Something as simple as manually searching for the URL in the whole article source should work. Maybe that's lame, but at least that's what I usually do. :) -- Dsimic (talk) 19:45, 11 November 2013 (UTC)
Slowdowns, style/js failures
I'm getting slowness and intermittent failure to load CSS and javascript features. Reporting from NYC now. Back to you. equazcion → 19:50, 11 Nov 2013 (UTC)
- Same here, in western Washington (state):Jay8g [V•T•E] 19:53, 11 November 2013 (UTC)
- From the wikitech IRC and twitter feed: "Switching 588 wikis to 1.23wmf3 in one go seems to have upset the bits app server pool". So it is known and being worked on. The deploy process has changed slightly this time round and it seems a performance bottleneck has been reached because of this. As always, recovering might require bypassing your browser cache. —TheDJ (talk • contribs) 19:55, 11 November 2013 (UTC)
- fwiw, enwiki (and any other wikipedia i sampled) is still on wmf2. maybe some non-wikipedia projects (wikivoyage?) were switched, though... peace - קיפודנחש (aka kipod) (talk) 21:54, 11 November 2013 (UTC)
- From the wikitech IRC and twitter feed: "Switching 588 wikis to 1.23wmf3 in one go seems to have upset the bits app server pool". So it is known and being worked on. The deploy process has changed slightly this time round and it seems a performance bottleneck has been reached because of this. As always, recovering might require bypassing your browser cache. —TheDJ (talk • contribs) 19:55, 11 November 2013 (UTC)