Wikipedia:Village pump (technical)

The technical section of the village pump is used to discuss technical issues about Wikipedia. Bugs and feature requests should be made at BugZilla.

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

view · edit

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

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

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

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

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

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

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

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

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

« Archives, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216

Settle this: HTML comments do not hinder performance

This is your MediaWiki preprocessor ready to format a template in an article.

I am looking for a technical essay, or message thread, that explains HTML comments are harmless to performance unless "20,000" are placed in an article or template, or placed outside <noinclude> tags in a subst'd template. Can anyone recommend some good discussion or essay pages to settle these fears about using HTML comments? Or let's settle the issue here. -Wikid77 05:39, 10 February 2011 (UTC)[reply]

The best thing to do is just tell people to view the HTML source of a page. HTML-style comments in the wikitext of a page aren't included in the rendered HTML page served to viewers regardless, although some other material is included in comment tags in the rendered version. — Gavia immer (talk) 05:48, 10 February 2011 (UTC)[reply]

Good idea. When people set their browsers to <View><Source>, or similar, they can see how the HTML-style comments were totally omitted (unless subst'd). I have added the 2 greyhound photos, as an analogy, to show just how quickly the comment lines are skipped by the preprocessor. I like the 2nd photo, for how the dog is flying over "the HTML comments" without touching. -Wikid77 07:10, 10 February 2011 (UTC)[reply]

It sounds like you're ready to write that essay yourself. You should if you're willing to, then bring it back here for comments. Cheers, ʄɭoʏɗiaɲ ^τ _¢ 13:54, 10 February 2011 (UTC)[reply]

Do we even need an essay about this? Isn't WP:PERF enough? Svick (talk) 16:33, 13 February 2011 (UTC)[reply]

Well, I think some people fear the use of more than 20 comment lines in a template, so they tend to find ways to delete important comments from templates (I know that sounds OCD, but they do delete the comments). Evidently, saying, "Don't worry," doesn't work with them because they know in reality, worrying is extremely important for many issues, and they can't fully live in the imaginary Wikiverse; hence, they worry in superstitious ways about performance. I mean, 20 different way-out-there superstitions about writing templates (such as thinking 14 nested if-else levels won't matter, but all parameter names should be 1-letter names, or whatever). Long story short:

Can someone who knows the workings of NewPP reassure us that the preprocessor skips, quickly, from "" or be honest and tell us, "No, all words in comments are emailed from Florida to England to update usage counts for the OED analysis, and any sentence containing the word "tag" is emailed to the HTML Deprecation Committee in preparation for a Krist-Tag-Nacht raid on all webpages that still use the "" tag to set font attributes".

I don't want to make the mistake of saying (again), "Use <nowiki> tags, because they are tiny with no overhead and preserve spacing for use anywhere (NOT true)", where, instead, the reality is that nowiki-tags bloat a page with 88-character markers that will kill a calculation expecting numeric data. So, I was hoping for someone to confirm if HTML-style comments are rapidly skipped (except inside subst'd markup), and reduce people's extreme fears that comments must be deleted to make templates run much faster. -Wikid77 20:23, 13 February 2011 (UTC)[reply]

It is not hard to deduce what happens with HTML comments in templates; they simply disappear. The PP simply ignores these, and no operation in computing is faster then ignoring something. — Edokter (talk) — 20:33, 13 February 2011 (UTC)[reply]

See for yourself: http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/includes/Sanitizer.php?revision=81330&view=markup#l549 Anomie ⚔ 21:52, 13 February 2011 (UTC)[reply]

Linking to foot of page

WP:ANCHOR tells us that #top and #toc link to the top and table of contents of the current page (though this warns us that #top only exists in some skins). By prowling around I have found that #footer links to the foot of the page (but do footer {{navbox}}s come into it?). I have tried it here and it could be useful in situations like this. I'll document #footer in WP:ANCHOR if it is a supported feature of the Wikimedia software. Is it? Are there any other preset anchors? Thincat (talk) 10:31, 10 February 2011 (UTC)[reply]

I have just noticed that #footer is used in the template transcluded at the top of this page (WP:VPT). However, I am still interested in its status. Also, is the remark about skins correct? Thincat (talk) 10:41, 10 February 2011 (UTC)[reply]

The #toc anchor will only exist if the page has a table of contents. There are, in fact, a surprising number of anchors which may be jumped to: to see what I mean, go to any page, and view the page source. Look through the HTML for the id= attribute; these are the anchors (from HTML 4.0 on, any tag may bear the id= attribute, so you're not looking for <a>...</a> tags with the name= attribute the way you would prior to HTML 4.0). If I do this for a very short page, I see that there are well over 60; most of these are for items in the menus along the top, down the side, even the copyright box at the bottom. For example, in Monobook skin, #p-search should move to the word "search" just above the search box.

The #footer anchor doesn't take you to the end of the article content; in fact it goes well past that point, to the start of the box with yellow (in Monobook anyway) border, which contains the "Text is available under the Creative Commons Attribution-ShareAlike License ..." stuff. The last anchor that's actually in the editable page content is #catlinks, which appears to be valid even if there are no cats (if there is at least one category, #mw-normal-catlinks is also declared immediately afterward).

Other than #top, #toc (which doesn't appear in all pages) and #catlinks, there are no other useful predefined anchors (there are about ten more within the editable content, but most are at or before the title heading, so duplicate #top). --Redrose64 (talk) 14:16, 10 February 2011 (UTC)[reply]

Using the null anchor (<a href="#">link text</a>) should jump to the absolute top of any page, regardless of said page’s content. However, it is impossible to create such a link using wiki-text (see bugzilla:17006). ―cobaltcigs 14:48, 10 February 2011 (UTC)[reply]

Thank you for those suggestions. I learnt about HTML in the days before HoTMetaL (!) but my learning curve then went flat so I never got past "name=". I shall look and learn. Thincat (talk) 20:41, 10 February 2011 (UTC)[reply]

Essentially, <a id=foo>bar</a> is identical in effect to <a name=foo>bar</a>. Since the id= attribute can be used in any tag which is valid in the body section, we can also have, for example, <li id=foo>bar</li> to make a list item into a link target. Prior to HTML 4.0 you had to do this as <li><a name=foo>bar</a></li>. The shorter HTML 4.0 forms may confuse older browsers. --Redrose64 (talk) 21:08, 10 February 2011 (UTC)[reply]

BTW, if anyone isn't sure, you can use "View, Page Source" in Firefox or, it seems, "View Source" in IE8 to see the HTML code generated. Thincat (talk) 23:34, 10 February 2011 (UTC)[reply]

Also, #p-personal and #p-logo are both higher than #top. This strikes me as being a bug. ―cobaltcigs 21:35, 11 February 2011 (UTC)[reply]

top in this case is meant for the "top of the article" and not necessarily the top of the page. I'm not sure it's a bug or a feature in that case… --Izno (talk) 21:33, 13 February 2011 (UTC)[reply]

Plan to reduce Template:Convert

11-Feb-2011: The essay about redesigning Template:Convert, to use condensed subtemplates, rather than 3,400 (of 24,000 needed) is titled "WP:A plan to reduce Convert subtemplates".
Currently, {Convert} is a vast contraption, so immensely huge that no single person really understands all of it, and parts of Convert are used (incorrectly) deep in the innards of some other templates, but never used directly by people writing articles. Hence, the improvements to Convert are chasing a moving target, of over 15 types or sub-families of conversion formats.
The redesigned, extended prototype has suffix "-x" as Template:Convertx which would allow comma=in, comma=out, comma=off, and other new features:

{{convertx|9,250|km|mi|comma=in}} → Template:Convertx
{{convertx|9,250|km|mi|comma=out}} → Template:Convertx

The only hope is this hybrid approach which "morphs" the current Convert subtemplates into updated forms, which allow passing new parameters to handle the new options. Essentially, each unit (such as: ft, m, km, sqft, oz-f) would choose between the new or old style of processing conversions. Unused units would not change (because who cares). The performance overhead is perhaps 5 levels lower for the expansion depth, but about 100 bytes more in post-expand size, for the new features, such as Convert using 300 bytes when Convertx would use 400 bytes of post-expand size. -Wikid77 05:46, 11 February 2011 (UTC)[reply]

"Comma in" and "comma out" contradict everything about proper number formatting and WP:MOSNUM. If you want to write 9250 km, then you need to write 5720 mi. Mixing styles is not appropriate. Headbomb {talk / contribs / physics / books} 06:05, 11 February 2011 (UTC)[reply]

Yes, I think mixing of styles was requested by people wanting to put direct quotes from some ignorant imbecile like Isaac Newton, or Max Planck, or Albert Einstein, who only spoke 5 languages, and did not understand the life-critical importance of using commas. Those guys never did anything more than develop reflector telescopes, or Planck's law, or relativity theories (E=mc^2). There's even talk of how they wrote unformatted equations, by hand, without using the Unicode &minus! Perhaps if WP:MOSNUM had existed centuries ago, then those guys could have been stopped, most certainly, before they became notable. -Wikid77 13:18, 11 February 2011 (UTC)[reply]

Yeah, and if you want to quote them verbatim, you don't need convert templates, because I doubt Newton et al. wrote things like "A sphere of Template:Convertx, ...". If an editorial note, parentheses should not be used for this, but rather square brackets. "A sphere of 9250nbsp;km [5,750nbsp;mi / 5750 mi], ..." And take that crass attitude of yours elsewhere. Headbomb {talk / contribs / physics / books} 15:06, 11 February 2011 (UTC)[reply]

Sorry, I thought the joke was obvious, but I should have said how Template:Convert, for years, has been used inside direct quotations, with equivalent amounts in editorial brackets "[ ]" despite no commas in the quoted text. -Wikid77 14:12, 14 February 2011 (UTC)[reply]

This outburst is not helpful to your cause, and I think you know it. You should be encouraging people to focus on the issue at hand, not encouraging them to follow you down a tangent. Happy‑melon 13:57, 11 February 2011 (UTC)[reply]

I guess I forgot how some people dislike jokes about WP:MOS. Perhaps I should have said that Convert supports conversions going back over 3,000 years ago, with or without commas in their stone carvings. -Wikid77 14:12, 14 February 2011 (UTC)[reply]

Any plans on using the convert extension mentioned in Wikipedia:Wikipedia Signpost/2011-01-31/Technology report? -- WOSlinker (talk) 13:24, 11 February 2011 (UTC)[reply]

I was planning on starting a discussion about that soon on Template talk:Convert, but there are a few more features I wanted to implement and stabilise in it [the extension] first. Happy‑melon 13:57, 11 February 2011 (UTC)[reply]

Template:Convert currently allows dynamic definition of thousands, and thousands, of new units (within a few minutes each), depending on which measurement units are used in each culture, as described in millions of articles of the other-language Wikipedias. We recently added the famous Egyptian cubit, and also added the French arpent (there are other arpents, both linear and square), due to widespread use in French colonial culture. Google estimates 143 million webpages about the word "measurement", but Convert also handles calendar dates, gun-barrel calibre, and musical notes, so we had to make Convert be a highly dynamic system, to allow users to add new units every hour of the day, and convert the words, not just numbers. Reality is so much more complex than just a list of 400 or 900 commonly used units. -Wikid77 14:12, 14 February 2011 (UTC)[reply]

My mouse cursor is ticking

Hard to explain this. Right now I have the cursor over the textbox, and it shows up as a stylus. However, each time a second ticks in the clock at the top right, the cursor flashes as an arrow for a second. It's getting to be really distracting to my work here, however. Has the clock been changed recently? - ʄɭoʏɗiaɲ ^τ _¢ 14:11, 11 February 2011 (UTC)[reply]

If you are using FireFox, you may have enabled Caret Browsing by pressing F7. Press F7 to toggle the state. ---— Gadget850 (Ed) ^talk 17:43, 11 February 2011 (UTC)[reply]

Doesn't sound like Floydian's problem... a search for Caret Browsing in Firefox's help system yields several threads, some containing links to this, and our own Caret navigation. --Redrose64 (talk) 18:16, 11 February 2011 (UTC)[reply]

I am using Firefox, but caret browsing is turned off. It definitely only happens on wikipedia and not on other websites. The cursor doesn't move, its just flashes between a regular arrow, and some other cursor icon in sync with the clock. - ʄɭoʏɗiaɲ ^τ _¢ 18:16, 11 February 2011 (UTC)[reply]

Seems to be back to normal right now. I didn't do anything though. - ʄɭoʏɗiaɲ ^τ _¢ 22:32, 11 February 2011 (UTC)[reply]

I've had Firefox do that pretty often and it is solved by opening a new tab and closing the old one. —DoRD (talk) 18:11, 13 February 2011 (UTC)[reply]

Again

Hi. i`m from ko.wikipedia. I recently created Template:Dated maintenance category on ko.wiki. but, i can`t categorize former articles that did not appointed date. so, i want to appoint date with my bot ko:wiki:user:Altobot. How to command to my bot to appoint date on maintenance template? Of course, i don`t know when the templates attached.--Altostratus (talk) 05:51, 13 February 2011 (UTC)[reply]

Are you asking how to add the category or how to determine the date the category was added? To find out when the category/template was added, you can use WikiBlame. Someguy1221 (talk) 06:00, 13 February 2011 (UTC)[reply]

Please see the reply given on your previous post above #again: set maintenance dates in kowiki articles. --Redrose64 (talk) 12:07, 13 February 2011 (UTC)[reply]

Oops, Sorry. i missed that. Sorry.--Altostratus (talk) 13:57, 13 February 2011 (UTC)[reply]

Removing the timestamp at the bottom

How can i remove the line "This page was last modified on 13 February 2011 at 09:29." at the bottom of a particular page?. I noticed that our mainpage doesn't have this line and i am trying to do the same in ta.wiki. --Sodabottle (talk) 10:00, 13 February 2011 (UTC)[reply]

See the first lines of MediaWiki:Vector.css. You will have to adapt the classname to your local variant of Main Page (look at the source code of the main page). —TheDJ (talk • contribs) 10:43, 13 February 2011 (UTC)[reply]

Thanks DJ. I have implemented it.--Sodabottle (talk) 12:56, 13 February 2011 (UTC)[reply]

Small tags at Wikipedia

What does the small tag do in a Wikipedia article? Does it depend on the context? Does the effect depend on the browser? For example, I see people using these tags, particularly in infoboxes, and then I see others removing them because they say they don't do anything. For me, personally, with my browser (Firefox), I don't see any difference, either, but of course I'm not the entire world. Take a look at the use of the small tag in the infobox of Vanessa Redgrave for her title. With or without the tag, I see the same font size, or at least I can't discern a difference.--Bbb23 (talk) 12:31, 13 February 2011 (UTC)[reply]

There is a difference; "CBE" becomes smaller. However,  is deprecated and its use should be as well. — Edokter (talk) — 12:42, 13 February 2011 (UTC)[reply]

I don't see it, but I didn't use a ruler. :-) As I understand it, deprecation means it should still continue to work because of backward compatibility. However, your comment suggests we shouldn't use the tag. Is there any policy or guideline on the issue? Is there an alternative? Is there any guidance on when the tag (or the alternative) should be used?--Bbb23 (talk) 13:16, 13 February 2011 (UTC)[reply]

Who says  is deprecated? It isn't listed as deprecated in HTML4 or in HTML5. Anomie ⚔ 13:36, 13 February 2011 (UTC)[reply]

HTML 4.0 on provides alternatives in the form of style sheets, but I don't know if ... is necessarily deprecated as far as HTML goes. However, its use in Wikipedia text can give rise to accessibility issues for partially-sighted readers, so in that sense, it's "deprecated". See also WP:FONTSIZE. --Redrose64 (talk) 13:38, 13 February 2011 (UTC)[reply]

HTML5 says <big> is deprecated, so I asumed  was as well, but apparently not. — Edokter (talk) — 16:41, 13 February 2011 (UTC)[reply]

^{[citation needed]} As mentioned above,  is not marked deprecated at [1]. Anomie ⚔ 17:12, 13 February 2011 (UTC) NB: Previous comment was changed after this comment (diff).[reply]

Ref: www.tutorialspoint.com/html5/html5_deprecated_tags.htm (copy and paste, as it seems to be blacklisted.) — Edokter (talk) — 18:16, 13 February 2011 (UTC)[reply]

 is not listed there. But I see you changed your earlier comment to claim <big> is deprecated, which actually does seem to be the case. Anomie ⚔ 18:42, 13 February 2011 (UTC)[reply]

Would someone please give some sources that explain the problem with accessibility and a small font size? Wikipedia:Manual of Style (accessibility) is mute on font size as an issue and even mentions the use of . I have skimmed through the Section 508 and Web Content Accessibility Guidelines and don't see this. I have used some online accessibility tools to check several articles and don't see a font problem. ---— Gadget850 (Ed) ^talk 18:00, 13 February 2011 (UTC)[reply]

Seeing deleted image logs?

When I click on a deleted image, the upload form appears. Is there somewhere I should look to see the deletion log? Maury Markowitz (talk) 16:29, 13 February 2011 (UTC)[reply]

Left-side menu, under "toolbox", Special pages; then under "Recent changes and logs", Logs. In the first drop-down menu, select "Deletion log"; in "Title:", enter your image name (with the "File:" prefix). Then click "Go". --Redrose64 (talk) 17:00, 13 February 2011 (UTC)[reply]

Oh, forgot to mention, if the image was held on commons, that won't work - instead, go to commons: first, then proceed as I described. --Redrose64 (talk) 17:02, 13 February 2011 (UTC)[reply]

This will be fixed in the MediaWiki update coming Wednesday (hopefully), but there is a useful script at User:Gary King/show upload deletion logs.js which adds links to both local and Commons deletion logs at the top of the upload form when you click on a redlinked image. /ƒETCH COMMS / 18:06, 14 February 2011 (UTC)[reply]

Bug in the API

I would like to bring up what I believe is a bug in the API, but I want to verify it here first. If I'm not mistaken, it's just cropped up in the past few days, so it might be related to the new mediawiki release (I am however not sure on this point).

As you will see, File:PC280020.JPG has two different images in its history. However, the API is reporting the same hash tag for both images: [2]. This problem is not echoed on the commons version of the image, File:Blyth Staithes.jpg: [3]. As a result, File:PC280020.JPG is being reported as having no duplicates ([4]), despite the fact that the commons version is indeed an exact duplicate.

Should I file this as a bug? Magog the Ogre (talk) 18:50, 13 February 2011 (UTC)[reply]

It seems to be fixed. Svick (talk) 20:09, 13 February 2011 (UTC)[reply]

disable Firefox spellchecker via css/js

Yes, I know I can switch it off in the browser and all that, don't ask me why I want this, so just flat out: Is there a way to disable Firefox spellchecker via some sort of script? (I know there is one to enable it in the edit.js) Choyoołʼįįhí:Seb az86556 ^{> haneʼ} 19:07, 13 February 2011 (UTC)[reply]

just right click in the edit box and uncheck "Check spelling" ΔT _{^{The only constant}} 19:17, 13 February 2011 (UTC)[reply]

I know that as well. So I take it it can't be done. Choyoołʼįįhí:Seb az86556 ^{> haneʼ} 19:47, 13 February 2011 (UTC)[reply]

If you want to disable it for everything:

$j(document).ready(function() {
  $j('input, textarea').attr('spellcheck', false);
});

If you only want to disable it for specific elements, you'll have to select them by ID or something. Mr.Z-man 20:20, 13 February 2011 (UTC)[reply]

Awesome. Works. Exactly what I was looking for. Choyoołʼįįhí:Seb az86556 ^{> haneʼ} 20:43, 13 February 2011 (UTC)[reply]

Subst sometimes not working

Normally when I do {{subst:FULLPAGENAME}} I get what I expected - for this page, it is "Wikipedia:Village pump (technical)", but it didn't work here. Any ideas as to why? T. Canens (talk) 20:08, 13 February 2011 (UTC)[reply]

How odd, apparently subst doesn't work inside <includeonly>.^[5] Does anyone know if this is a known bug? Anomie ⚔ 23:09, 13 February 2011 (UTC)[reply]

Umm I wouldn't call it a bug, it's what I would see as expected behaivor. "<includeonly>...</includeonly> – the text between the includeonly tags will be transcluded (substituted), but will not be processed on the template's own page". Taemyr (talk) 02:03, 14 February 2011 (UTC)[reply]

It's certainly a bug when you try to put <includeonly><nowiki>~~~~</nowiki></includeonly> in a template and it expands the signature inside the <nowiki> tags (Template:Bug). I'm not sure whether people generally expect substitution not to work inside <includeonly> or not, although I know they do expect it to work inside <ref> where it similarly doesn't. Anomie ⚔ 04:35, 14 February 2011 (UTC)[reply]

I admit I'm surprised to find that tilde expansion and pipe-trick expansion work inside includeonly tags, while subst doesn't. (IIRC, none of these expansions work inside ref tags.)--Kotniski (talk) 08:07, 14 February 2011 (UTC)[reply]

Some templates rely on the behaviour of subst: inside <includeonly>...</includeonly> in order to detect if they have been substed when they shouldn't have been, and vice versa. See, for example, {{unreferenced}} --Redrose64 (talk) 14:04, 14 February 2011 (UTC)[reply]

I don't think that's quite the same thing (since there it's only the word "subst" that's inside the tags, not the whole substituted object), but there may be some connection.--Kotniski (talk) 14:48, 14 February 2011 (UTC)[reply]

No, that's a very different beast - and there the subst is actually supposed to work... T. Canens (talk) 15:21, 14 February 2011 (UTC)[reply]

It is certainly not the same thing, and that template would continue to work were either of the patches to Template:Bug applied. OTOH, usages like that are exactly why safesubst: had to be created instead of just "fixing" subst:. Anomie ⚔ 18:19, 14 February 2011 (UTC)[reply]

It should really be surprising to find that <includeonly> disables <nowiki> for tilde expansion and pipe-trick expansion. Anomie ⚔ 18:19, 14 February 2011 (UTC)[reply]

This looks weird

[6] --Perseus8235 20:15, 13 February 2011 (UTC)[reply]

That's because a semicolon at the start of the line is Wiki markup which triggers the construction of the HTML <dl>...</dl> structure, containing a <dt>...</dt> element for each semicolon, and also a <dd>...</dd> for the first colon which occurs anywhere on the same line. Thus, this:

;The:Red/fgjdr

produces this:

The

Red/fgjdr

A colon at the start of a line also gives a <dl>...</dl> structure, but containing only <dd>...</dd> elements. --Redrose64 (talk) 20:47, 13 February 2011 (UTC)[reply]

The bolding triggered by ";" in your article name ";The:Red/fgjdr" is considered a bug within the processing of text data. Someone should perhaps change the handling of the missing-article message to embed "" or "<nowiki/>" before a user's specified article name, so that the message appears more coherent, with the text treated as simply ";The:Red/fgjdr" rather than the bolded word "The" repeated on each separate line. It is a relatively new bug, caused by recently fixing another bug, which typically happens in about 10% of bugfixes in the world at large (hence, a fairly common mistake for most software engineers). -Wikid77 21:32, 13 February 2011 (UTC)[reply]
Actually, it's a very old bug: Template:Bug opened in 2008 was caused by the fix for Template:Bug in 2004. There is nothing we can do here to work around it here, as it's the output of {{PAGENAME}} that is incorrect. Anomie ⚔ 22:05, 13 February 2011 (UTC)[reply]

Transclusion of Special:Watchlist

How can I transclude Special:Watchlist onto my userspace? I want to make a page with my article alerts, watchlist for the past 12 hours, and other useful stuff that I make use of commonly. However, transcluding Special:Watchlist creates a plain link to it.

How can I do this? If it can't be done, can we make it possible? Even if it just transcludes the watchlist of the user looking at it (or "you are not logged in" for IPs), that would work for privacy concerns. - ʄɭoʏɗiaɲ ^τ _¢ 02:54, 14 February 2011 (UTC)[reply]

I don't believe it's currently possible, perhaps the reason being that if someone were to come across a random page that shows their watchlist, then they'd be quite alarmed. That's why nothing that is personalized to a single individual can be entered onto any page. Gary King (talk · scripts) 07:13, 14 February 2011 (UTC)[reply]

Seems a silly reason. They'd come to the village pump and be informed that "somebody is transcluding special:watchlist. Whoever is viewing it will see their own watchlist." The ability to create a customized watchlist with your own gadgets. - ʄɭoʏɗiaɲ ^τ _¢ 14:43, 14 February 2011 (UTC)[reply]

Not silly at all. Imagine browsing Facebook and seeing comments from your profile posted on another person's profile, or your email from Gmail posted on another person's Google profile. If you browsed around here and came across Example and it showed your watchlist because a vandal transcluded it, and you were a newbie and so never heard of the village pump (I can certainly attest that it's quite difficult to find, considering someone had to point me there early in my wiki days when I screwed up a few times), then it can be quite difficult to grasp that someone merely "transcluded" your watchlist to a page. It's also hard for a newbie to explain what exactly is going on when the page looks a bit different to everyone who sees it. Gary King (talk · scripts) 16:09, 14 February 2011 (UTC)[reply]

The real reason it can't be done is because it would break caching. The transcludable special pages are the ones that don't have different output depending on which user visits them. Mr.Z-man 23:26, 14 February 2011 (UTC)[reply]

Anyway, methods of achieving your desired effect:

Write a script to querying the API and insert it into the page. Unfortunately, the parse API is rather broken [7]. Using iframe or AJAX also works.
Create a sub-page linking to page and use {{Special:RecentChangesLinked/User:Floydian/Watching}}. More cumbersome to add pages.
Just use bookmarks or have a script to add links/HTML to Special:Watchlist.

See guys that wasn't so hard. — Dispenser 02:45, 15 February 2011 (UTC)[reply]

The API has a specific method for grabbing the watchlist [8] Platonides (talk) 20:43, 15 February 2011 (UTC)[reply]

Citation templates add extra space in Preview or Save Page

Resolved

– Gary King (talk · scripts) 21:18, 14 February 2011 (UTC)[reply]

New little quirk that can be worked around, but it adds extra proofing time and extra steps. Been noticing it for about a week, maybe. When editing and using citation templates, they are exactly placed when I put them in. Perfect. When I click "Preview" or "Save Page", that actions sticks an extra space in front of the citation. Doesn't matter what I put the citation next to. If it's a sentence end, I end up with a period, a space, and then the citation. If it's two citations together, I end up with a citation, a space, and the other citation. Never used to do that. Annoying. Is this happening to anyone else? I use Firefox. Maile66 (talk) 20:07, 14 February 2011 (UTC)[reply]

Do you have any scripts or gadgets enabled, such as wikEd, which may affect your editing area? This isn't supposed to be happening to you; it's certainly not happening to me, regardless of what browser I try it in. Gary King (talk · scripts) 20:30, 14 February 2011 (UTC)[reply]

I don't work with scripts. But WikiEd for Firefox is enabled. Is that what is doing it, maybe? Maile66 (talk) 20:48, 14 February 2011 (UTC)[reply]

Try disabling it to see if that helps. Gary King (talk · scripts) 20:50, 14 February 2011 (UTC)[reply]

What pages is this occurring with? Please give some examples where the saved page was not as you intended. --Redrose64 (talk) 20:51, 14 February 2011 (UTC)[reply]

Un-checking the WikiEd, clearing my cache, then re-checking it...worked. Must been a "hiccup" in the gadget. Thanks for your help.Maile66 (talk) 21:08, 14 February 2011 (UTC)[reply]

User losing text and data when uploading

Can someone technical have a look at the two Help desk threads by Catchthedream (talk · contribs)? One, Two. It looks like text and data is being randomly damaged/truncated on its way from the user's PC to the Wikipedia servers. -- John of Reading (talk) 10:16, 15 February 2011 (UTC)[reply]

Reverting images with API

I cannot find any documentation under mw:API:Changing wiki content on how to revert an image to an earlier version. It is in fact written in the software: (click here to see what I'm talking about). Is there a way to do it through the API? Magog the Ogre (talk) 22:05, 15 February 2011 (UTC)[reply]

Not directly. The workaround is to do a query like [9] then feed the image or the URL to upload. MER-C 02:20, 16 February 2011 (UTC)[reply]

I don't believe Wikimedia/Wikipedia have URL based uploads enabled; am I wrong? Magog the Ogre (talk) 07:33, 16 February 2011 (UTC)[reply]

You are correct. —TheDJ (talk • contribs) 11:37, 16 February 2011 (UTC)[reply]

search messages tidyup proposal

I have suggested a couple of minor adjustments for the search result messages here, partly aesthetics, partly logic... hopefully short yet sweet. Lee∴V (talk • contribs) 00:08, 16 February 2011 (UTC)[reply]

Did the appearance just change for anybody else?

Right in the middle of editing DYKs (as in, preview on the prep, fine, then go to another hook on the talk page, and wha?!) the appearance of the editing window changed. I have 'monobook' set as my skin, but all of a sudden the editing window has the "fancy" appearance of Vector/default, but everything else is the same? (I'm using Firefox 3.6.10) - The Bushranger _{One ping only} 06:23, 16 February 2011 (UTC)[reply]

...aha. I just found the 'enable enhanced editing toolbar' thing in the Beta section of Editing Preferences, unchecked it, and it's back to normal. Panic averted, I've found my towel. - The Bushranger _{One ping only} 06:46, 16 February 2011 (UTC)[reply]

was fine for me until about 5 mins ago, then it went and broke, Everything was there, but it appeared that all the page formatting had broken. Pages taking ages to load too. I swapped to IE, and that is taking forever to load (one reason I use Firefox) so I abandoned the attempt to use IE. Seems to have settled now. Mjroots (talk) 10:23, 16 February 2011 (UTC)[reply]

This was due to maintenance. There was an attempt to switch to 1.17 again, first one was problematic, the last one succeeded. —TheDJ (talk • contribs) 11:42, 16 February 2011 (UTC)[reply]

Pages are showing up in monobook for me, but I'm getting the hideous Vector edit window. I'd just got used to it and then the RefToolbar buggered off. Can I get the monobook edit window, or at least the gadgets, back somehow? HJ Mitchell | Penny for your thoughts? 12:31, 16 February 2011 (UTC)[reply]

Well, I'm using Monobook and I followed the advice in 2nd post above and it

Works for me - Special:Preferences → Editing → Beta features - make sure that "Enable enhanced editing toolbar" is not checked. --Redrose64 (talk) 13:22, 16 February 2011 (UTC)[reply]

Ahh, I thought it was just me. Thanks, I've switched it back. More to the point - why on earth was it changed? Any discussion links about this? Lugnuts (talk) 19:13, 16 February 2011 (UTC)[reply]

Bloody awful appearence

All the gadgets stopped working, the stuff from the top of the page (my talk, prefs, etc, and all the page/discussion/edit etc) all jumped down to the bottom of the page, and it ll generally looked hideous. Now in the edit screen, it's almost back to normal but the edit box toolbar has changed its appearence and the cite hutton etc has disappeared. Is this one of the regular "improvements"? I would upload a screenshot, but the upload screen seems to have changed again and I can't find the option for WP screenshots (which I'm sure there was for a while). DuncanHill (talk) 10:18, 16 February 2011 (UTC)[reply]

That was another attempt to deploy MW 1.17. They've already reverted it. MER-C 10:23, 16 February 2011 (UTC)[reply]

IT's still taking ages for pages to load, the "discussion" and "edit" tabs at top of page are overlapping. Mjroots (talk) 10:28, 16 February 2011 (UTC)[reply]

Well, the blackscreen gadget is working again, but the tbs and links are still in the wrong place. Edit screen (I unchecked the beta thing referred to in the post above) now has no edit toolbar at all, and the special characters are all showing up at once with no drop-downs, and no clickability. DuncanHill (talk) 10:39, 16 February 2011 (UTC)[reply]

We're in software upgrade mode, and various parts of the server structure are getting hammered. Hold on to your hats, and hopefully things will settle down again soon. Happy‑melon 10:53, 16 February 2011 (UTC)[reply]

Indeed, it's called a maintenance window for a reason, and some strangeness was expected. Good news, all ok now, and were running 1.17. —TheDJ (talk • contribs) 11:43, 16 February 2011 (UTC)[reply]

All ok, except blackscreen gadget not working (except in edit screen, when the pge loads without the blackscreen and then the blackscreen "switches on" after it loads), pop-ups not working, and the clock gadget not shoing up on watchlist (or anywhere else except in the edit screen). So not all OK at all. DuncanHill (talk) 12:00, 16 February 2011 (UTC)[reply]

I think he means that, unlike the previous attempts to deploy MW 1.17 which crashed the entire cluster, this deployment has been successfully implemented. There was plenty of warning that there would be bits of user JS and CSS which would need fixing after deployment. Happy‑melon 12:04, 16 February 2011 (UTC)[reply]

And HotCat isnz't working either. Are any of the gadgets in user preferences working? DuncanHill (talk) 12:05, 16 February 2011 (UTC)[reply]

And, for the record, where were these warnings? I never had any warning that all the gadgets would stop. DuncanHill (talk) 12:09, 16 February 2011 (UTC)[reply]

The CentralNotice that you've probably hidden :P And all over wikitech-l, the techblog, etc. Happy‑melon 12:10, 16 February 2011 (UTC)[reply]

No offense to you personally, but using centralNotice as the only onwiki channel for critical issues is very stupid. It has so often been abused for trivialities and outright spam that many editors have disabled it. — Gavia immer (talk) 12:16, 16 February 2011 (UTC)[reply]

(ec)If a Central Notice is the same thing as the bloody fundraising banners, then of course it's hidden. I'm pretty sure it's not been on a watchlist notice. No idea what wikitech-l is, and not an habitué of the techblog. DuncanHill (talk) 12:18, 16 February 2011 (UTC)[reply]

It's been posted to every major Wikimedia mailing list, and here at the tech village pump. And if you're at all interested in Wikimedia technical matters, the techblog is an excellent way to keep up. I'll admit that a watchlist notice might have been a good idea though. the wub "?!" 12:24, 16 February 2011 (UTC)[reply]

My interest in Wikimedia technical matters extends to "does it work?" and "will someone please make it work again?" DuncanHill (talk) 12:29, 16 February 2011 (UTC)[reply]

It's very easy to make the mistake of thinking that the MediaWiki world revolves entirely around enwiki and that everyone should use enwiki's preferred notification methods to inform about changes like these. This deployment affected all 850 wikis in the Wikimedia cluster; there is no justification for saying that the sysadmins should have laboriously gone around and identified the preferred channels for each and every wiki, including those in languages they don't even speak; and equally no reason for enwiki to get any special treatment. Rather, the sysadmins used the channels which are already set up to allow crosswiki communication. It's unfortunate that you've chosen not to receive those messages, but really not anyone's fault but your own. Happy‑melon 12:35, 16 February 2011 (UTC)[reply]

I chose not to receive poorly written and offensive begging messages. I don't see why editors and readers should be expected to spend their time on a techblog just in order to have some idea of what is happening. When you find that your method of communication is not working, blaming the people you have failed to communicate with just comes across as arrogant. DuncanHill (talk) 12:45, 16 February 2011 (UTC)[reply]

I'd say that it would be claiming that one particular person, group or community should be given special treatment in that communication, which comes across as arrogant. By hiding the CentralNotice you have also hidden information about the Steward elections, Wikimania, and various other Wikimedia-wide issues. It's entirely reasonable to say that you are not interested in crosswiki issues, and to hide the entire CentralNotice. Or it's reasonable to say that you only dislike the fundraiser banner, and to hide that specifically. But to say that you want to be kept informed of crosswiki issues, and then to deliberately block out the communication channel which has been created for those issues, is counterproductive at best. Happy‑melon 13:04, 16 February 2011 (UTC)[reply]

Had Centralnotice not been abused for those ridiculous Jimbo fundraising banners, few people would have disabled it. From then on, Centralnotice has been perceived as spam. And the WMF has only itself to blame for it. --Morn (talk) 13:16, 16 February 2011 (UTC)[reply]

I'm sorry, Happy-Melon, I didn't realise that we weren't allowed to want to know about changes to Wikipedia unless we also wanted to know about lots of other irrelevant stuff. And, FWIW, I have seen messages about the Steward elections, and Wikimania. Like (I suspect) most editors and readers I really do not care much about cross-wiki stuff, but I do care about the reading and editing environment here. You obviously don't regard that as acceptable - it's "all or nothing". DuncanHill (talk) 13:30, 16 February 2011 (UTC)[reply]

Anyway, the thing I've got suppressed is "display of the fundraising banner", according to my prefs/gadgets. Doesn't say anything about "suppress notice of planned cross-wiki disruption" DuncanHill (talk) 14:34, 16 February 2011 (UTC)[reply]

You certainly don't seem to realise that you're not allowed to expect other overworked and un- or under-paid people to alter their professional behaviour to accommodate your personal definition of what is and is not "irrelevant", no. Essentially this is a "the world does not revolve around you" discussion, and I doubt it's going to go anywhere productive. Happy‑melon 14:45, 16 February 2011 (UTC)[reply]

Umm, just a note here - I am not sure what you mean by CentralNotice, since I also have only the Fundraising banners disabled (and that only after a glitch appeared that made them reappear immediately after they were dismissed). I can see and do notice all the other stuff at the top of pages, such as the Stewards' election notice. And I didn't see word one about this rollout on en.wiki; in fact I specifically looked for a notice about it after I saw it on de.wiki. I suspect you will find it did not actually get advertised on en.wiki. (Whether users should have been alerted that "We are enabling a new feature" means "Your preferences may get mucked up" in addition to "Things will be a bit wonky while we fine-tune this" is a separate issue.) Please stop assuming bad faith when folks tell you they didn't see the notification. Yngvadottir (talk) 22:15, 16 February 2011 (UTC)[reply]

As long as we're reporting issues here, I have another one: loading my watchlist in Firefox 3.6.13 now renders almost all of the way and then hangs briefly, obviously due to some javascript not loading properly. I haven't been able to work out the exact cause, so I will simply note that it is definitely a 1.17 issue. — Gavia immer (talk) 12:16, 16 February 2011 (UTC)[reply]

There's another change under Help, which gives the user a lot fewer options when searching Help. Now you get "Browsing", "Editing", "Guidelines", "Communication", "Questions", "Technical". OK for somebody Wikipedia savvy enough to know words or phrases to narrow their search. But what about someone who has never used Help before? If you want to narrow your search down to, say, only finding a template or a wikiproject, you need prior knowledge of Wikipedia to know to put it all in the search bar. The user does not have check boxes to help him/her narrow their search. Maile66 (talk) 12:37, 16 February 2011 (UTC)[reply]

I suspect that's a completely separate issue - someone tried redesigning Help:Contents (it's been reverted for now). Discussion at Help talk:Contents.

Thanks. Maile66 (talk) 13:01, 16 February 2011 (UTC)[reply]

The new messages bar appears to be partly broken, it still links ok, but the colour is wrong (Firefox). Mjroots (talk) 14:30, 16 February 2011 (UTC)[reply]

Yes, mine too (baby blue instead of the "orange bar of death" we've come to know and love). This is in IE. Ruhrfisch _><>°^° 15:43, 16 February 2011 (UTC)[reply]

That's the expected behaviour (r76017, Template:Bug). No comment on whether it's a positive development... Happy‑melon 16:59, 16 February 2011 (UTC)[reply]

Hm, it's definitely not the best colour choice. Would have missed it if someone didn't mention it. It really should be more of an obnoxious blue, like the {{talkback}} template uses. — Preceding unsigned comment added by Dorsal Axe (talk • contribs) 17:12, 16 February 2011 (UTC)[reply]

You can change it. I changed mine to screaming bloody red as a joke a few months ago and realized I liked it so I never switched back. Just add

.usermessage {

background-color: #ff0000

border: 1px solid #ffa500;

color: black;

font-weight: bold;

margin: 2em 0 1em;

padding: .5em 1em;

vertical-align: middle;

}

anywhere in your CSS file and it will override the default appearance. (I don't remember if the attributes for things other than the colors are redundant or not.) —Soap— 22:09, 16 February 2011 (UTC)[reply]

This has already all been sorted out down at #Blue_new_message_bars.3F.21 :) - Kingpin¹³ (talk) 22:13, 16 February 2011 (UTC)[reply]

Esams

And now the esams bits cache is dead again.[10] Secure WP server to the rescue...[11] --Morn (talk) 10:36, 16 February 2011 (UTC)[reply]

Try browser text-size smaller with MW 1.17

If your browser text size gets very large, then try setting Text-Size as smaller, to continue editing, when {{CURRENTVERSION}} = "1.17wmf1 (r82223)" or similar. Version now: 1.43.0-wmf.28 (2693c4c). Most likely, the text will not appear quite as normal as before, but it will be similar in size, to resume work on updating pages (without too much mindfry from the changed screen appearance). Try to be patient, and imagine some improvements that will come with MW 1.17. Or not, if you prefer. -Wikid77 10:59, 16 February 2011 (UTC)[reply]

Editing

The new editing template is a disaster. Clicking on Advanced, Special characters and Help does nothing (Windows XP). Please don't tell me that I need to change my IE8 settings. I want them as they are. As a chemist I need to have superscript and subscript readily available for chemical formua such as O₂⁺, not two clicks away. Also the Courier font is unpleasant to use. BTW the special characters did not work with the previous edit template, but one could get round that. Petergans (talk) 11:06, 16 February 2011 (UTC)[reply]

Another issue: the link to citation template gives an old version. Petergans (talk) 11:23, 16 February 2011 (UTC)[reply]

The preferences were temporarily incorrect after the upgrade, the preferences are being restored as we speak to their pre-upgrade settings. —TheDJ (talk • contribs) 11:47, 16 February 2011 (UTC)[reply]

12:47 < RoanKattouw> thedj: Known issue, running a script to (partially) fix it like right now. The ones still having the issue will, unfortunately, have to switch it off again

—TheDJ (talk • contribs) 11:48, 16 February 2011 (UTC)[reply]

Clarification: the script fixed most of the mess, but due to a minor FUBAR we were unable to fix the fact that certain users that had previously disabled the edit toolbar will now have it enabled again. These users will have to go to Preferences -> Editing -> Beta features and uncheck "Enable enhanced edit toolbar". There are about 4,200 affected users on English Wikipedia, if memory serves.

I realize this is an annoyance to these people, and I apologize for messing up. However, I'm sure you would've been more annoyed if you'd gotten the new toolbar and the preferences interface would refuse to turn it off, which is what would've happened if we hadn't done anything at all :) --Catrope (talk) 15:12, 16 February 2011 (UTC)[reply]

Actually, that is exactly what is happening to me. Regardless of the state of the checkbox, I have the enhanced edit toolbar active. There is no way for me to get the old one back. -- Whpq (talk) 15:15, 16 February 2011 (UTC)[reply]

Could you try again now? --Catrope (talk) 15:25, 16 February 2011 (UTC)[reply]

I followed the instructions given above and I am back in working order again. Thanks! ---RepublicanJacobite_{The'FortyFive'} 15:29, 16 February 2011 (UTC)[reply]

Reply - Still doesn't work for me. I am using Firefox version 3.6.13 on Windows XP. I shut down the browser and started it again. The checkbox was clear, but I had the enhanced edit tool bar. I checked the box and saved my preferences; opened a page to edit and confirmed I had the enhanced edit tool bar. I then unchecked the box and saved my preference. I opened a page to edit, and the enhanced edit tool bar is still there. -- Whpq (talk) 16:16, 16 February 2011 (UTC)[reply]

Try WP:BYPASS? –xeno^talk 16:18, 16 February 2011 (UTC)[reply]

Reply - Still broken for me. I cleared my entire cache and it made no difference. For extra fun, I switched to Chrome. Same problem. I then switched to IE8, and again, the same problem. Note that with IE8, I've never even visited Wikipedia so there's no way anything is cached. No matter which browser I am using, I only see the enhanced edit toolbar regardless of my preference setting. -- Whpq (talk) 16:32, 16 February 2011 (UTC)[reply]

UPDATE - I found a way to get the toolbar back! In your preferences, under the editing tab, there are two checkboxes that are related to beta features. The first is supposed to toggle between the old edit toolbar and the advanced edit toolbar. The second relates to some features. Previously, the state of the second checkbox was irrelevant. Now, in order to get the old toolbar back, you need to uncheck both boxes. -- Whpq (talk) 21:15, 16 February 2011 (UTC)[reply]

Edit toolbar preference no longer works

The new editing toolbar will not go away even when "My preferences" -> "Editing" -> "Show edit toolbar (requires JavaScript)" is cleared. :( —Lowellian (reply) 11:53, 16 February 2011 (UTC)[reply]

See thread above, this is in the process of being fixed. the wub "?!" 12:04, 16 February 2011 (UTC)[reply]

What has been done by now to fix it? Who was that who coercively enabled this so called "enhanced editing toolbar" ? And when this is going to be reverted? — Klimenok (talk) 06:58, 17 February 2011 (UTC)[reply]

Automated template updates on talk pages

There are 45 entries in the Category:Unknown-importance Pittsburgh articles, with

{{WikiProject Baseball|class=stub|importance=low}}
{{WikiProject Pittsburgh|class=Stub|importance=|auto=yes}}

templates on the talk pages. I would like to learn how to make all of these talk pages say

{{WikiProject Baseball|class=stub|importance=low}}
{{WikiProject Pittsburgh|class=Stub|importance=low}}

in an automated way. Please provide me with the tools and technical assistance to do this task.

I want to learn how to do it, not have it done for me, because I have other instances where I need to do likewise.--DThomsen8 (talk) 13:34, 16 February 2011 (UTC)[reply]

WP:AWB and/or WP:BOTREQ is the third door down. ΔT _{^{The only constant}} 13:57, 16 February 2011 (UTC)[reply]

Some revisions didn't make 1.17

It seems the changes to the diff-engine didn't make it into 1.17, especially revisions 75658 and 75662, which would have fixed some minor display issues in diffs. Were they entered in the wrong branch? — Edokter (talk) — 14:07, 16 February 2011 (UTC)[reply]

They were reverted because they changed the wrong piece of software: Wikipedia uses wikidiff2, not the PHP difference engine. The fixes were ported to the latter, but I don't know if it's been upgraded. I'll ask. --Catrope (talk) 15:14, 16 February 2011 (UTC)[reply]

Resource loader and Tracing CSS

With the new resource loader, all CSS is loaded through load.php, making it impossible to trace the origin of CSS declarations. Adding the ?debug=true to the URL does not change that. Is there another solution that enables me to trace CSS to its origin? — Edokter (talk) — 14:27, 16 February 2011 (UTC)[reply]

There's currently no way, no, though I guess it would be helpful. You can find some information in the modules= parameter to load.php, but that's it. Comments indicating where a file ends and the next one starts could be useful here. You can file a enhancement request on Bugzilla. --Catrope (talk) 15:16, 16 February 2011 (UTC)[reply]

~~Comments wouldn't help; the files are still loaded seperately as modules.~~ However, if the module names were to match the filenames (or add a dummy parameter indicating it's origin), it would solve my problem. — Edokter (talk) — 15:24, 16 February 2011 (UTC)[reply]

Actually, ?debug=true does work for me. Using that tells me the correct line number for CSS declarations. If the URL already has a "?", then you need to use &debug=true instead, though. Gary King (talk · scripts) 01:28, 17 February 2011 (UTC)[reply]

I still get the same cryptic URLs (starting with load.php), except that it shows 'debug=true'. I don't see linenumbers or what else. I'm using Webkits Web Inspector. What are you using? — Edokter (talk) — 12:56, 17 February 2011 (UTC)[reply]

Links aren't being underlined

See above. I've force-refreshed, I've gone into my preferences and set from 'Always' to 'Never' and back again, and still links aren't being underlined. --Golbez (talk) 14:31, 16 February 2011 (UTC)[reply]

They underline fine for me. Have you checked your browser settings? — Edokter (talk) — 14:34, 16 February 2011 (UTC)[reply]

Broken for me since the upgrade too. Not a browser issue. tedder (talk) 14:42, 16 February 2011 (UTC)[reply]

Me as well. I haven't changed a thing considering it happened sometime while I slept. ♫ Melodia Chaconne ♫ (talk) 14:45, 16 February 2011 (UTC)[reply]

What browser are you using? — Edokter (talk) — 14:57, 16 February 2011 (UTC)[reply]

Firefox 3.6.13. No browser settings were changed between yesterday and today. --Golbez (talk) 15:00, 16 February 2011 (UTC)[reply]

3.6.13 here too. I fired up Chrome and it's broken there too. tedder (talk) 15:02, 16 February 2011 (UTC)[reply]

I have FF 3.6.13 as well. But IE Tab also doesn't underline them. ♫ Melodia Chaconne ♫ (talk) 15:01, 16 February 2011 (UTC)[reply]

What skin are you guys using ? —TheDJ (talk • contribs) 16:26, 16 February 2011 (UTC)[reply]

MonoBook. tedder (talk) 16:31, 16 February 2011 (UTC)[reply]

Same for me, no underlining under Firefox or IE 8.0 using the MonoBook skin. Beyond My Ken (talk) 17:48, 16 February 2011 (UTC)[reply]

Same here, I'm on Minefield (Firefox 4 pre-release) and Monobook. -- King of ♥ ♦ ♣ ♠ 18:21, 16 February 2011 (UTC)[reply]

Same for me, on Monobook and no underlining on both Opera 11.01 and Chrome 9.0.597.98. Nate • (chatter) 21:28, 16 February 2011 (UTC)[reply]

Filed as bugzilla:27468. —TheDJ (talk • contribs) 20:35, 16 February 2011 (UTC)[reply]

ResourceLoader is awesome

It took literally one second to log in, usually it takes 30 seconds or so to load all the js.

However, I have a gadget or script that shows a UTC clock at the top right with a purge link, and while the clock is fine, it no longer links. Any ideas? It might be the Twinkle clock, I'm not sure. /ƒETCH COMMS / 14:57, 16 February 2011 (UTC)[reply]

I believe it is MediaWiki:Gadget-UTCLiveClock. And now it is smaller and doesn't purge. –xeno^talk 15:02, 16 February 2011 (UTC)[reply]

Had the same issue with the clock, but it is now working. ---— Gadget850 (Ed) ^talk 16:12, 16 February 2011 (UTC)[reply]

I fixed the UTC clock. —TheDJ (talk • contribs) 16:15, 16 February 2011 (UTC)[reply]

Confirmed. Back to the original size too. –xeno^talk 16:16, 16 February 2011 (UTC)[reply]

Predictive search suggestions not working in Monobook anymore?

Is there a reason that the predictive search suggestions aren't working in Monobook anymore? –xeno^talk 15:04, 16 February 2011 (UTC)[reply]

I disabled it because of a bug, fixed the bug, then forgot to re-enable it. Should be fixed now (immediately for logged-in users, may take time to propagate for anons). --Catrope (talk) 15:19, 16 February 2011 (UTC)[reply]

Only works for me in the edit screen. Monobook, Chrome, WinXP. DuncanHill (talk) 15:32, 16 February 2011 (UTC)[reply]

Try WP:BYPASS. Working again for me, thanks Catrope. –xeno^talk 15:49, 16 February 2011 (UTC)[reply]

I tried BYPASS, and now it doesn't work in the edit box either :( DuncanHill (talk) 15:59, 16 February 2011 (UTC)[reply]

Search suggestions work for me in Monobook right now. Gary King (talk · scripts) 16:59, 16 February 2011 (UTC)[reply]

Bottom notice displaying in navigation bar in Monobook

The bottom wikipedia notice (disclaimer, privacy policy, and About Wikipedia) are being displayed on the left in the navigation bar instead of being displayed at the bottom of the page. I am using Monobook, I tried vector and it appears correctly. Also, the section edit buttons are displaying on the left instead of the right. Alpha Quadrant ^talk 15:22, 16 February 2011 (UTC)[reply]

I tried Monobook on this page, and the section edit links are appearing on the right for me. I also can't reproduce the different location of the footer. Please try disabling user scripts and gadgets one at a time, and see if that fixes it. --Catrope (talk) 15:36, 16 February 2011 (UTC)[reply]

Found the issue, it is MediaWiki:Gadget-edittop.js in gadgets. After disabling this script it appears correctly. Alpha Quadrant ^talk 15:53, 16 February 2011 (UTC)[reply]

StupidNah, it's not stupid, it's just annoying banner is not working

The stewards elections banner keeps appearing and disappearing whenever I reach a page. Before I can click it, it disappears. --Perseus8235 15:43, 16 February 2011 (UTC)[reply]

It's probably an old banner that you already dismissed. You can clear your cookies for en.wikipedia.org to make them all reappear again. — Edokter (talk) — 15:52, 16 February 2011 (UTC)[reply]

Spurious/unwanted watchlist RSS token

I'm still trying to work through a problem that's causing my watchlist to hang briefly on load, but in the course of investigating it I that the watchlist RSS token field in my preferences had been filled with a random value. This could have lead to my watchlist being read by someone willing to try a lot of brute force, though of course in practice it's not very likely. The token was probably generated by various work that was done to fix preference breakage, and there's probably no way to fix erroneous tokens without clobbering good ones, but it's worth letting people know that they might have an unwanted token set. — Gavia immer (talk) 16:32, 16 February 2011 (UTC)[reply]

Code update finished?

Is the code update finished. If so, I am still having problems with inoperative scripts and gadgets (WikEd, Twinkle, Navpopups, UTC clock). --ukexpat (talk) 16:36, 16 February 2011 (UTC)[reply]

Yes finishes. Try disabling them one by one to find out which script EXACTLY is your problem, or use a javascript console. UTC clock was fixed, twinkle was fixed, popups works for me, so it's likely something other than that. —TheDJ (talk • contribs) 16:40, 16 February 2011 (UTC)[reply]

Wow, all my top links (my user page, my talk, my watchlist, etc.) are gone. Time to fiddle with the CSS again. Gary King (talk · scripts) 16:43, 16 February 2011 (UTC)[reply]

No gadgets working for me, AFAIK. Blackscreen, popups, twinkle, clock/purge, all not working. Preferences page doesn't have the tabs, it is just one long page with all the different bit under each other. Have tried bypass, logging-out-and-again. Monobook, Chrome, WinXP. DuncanHill (talk) 16:49, 16 February 2011 (UTC)[reply]

None of mine are either. In fact, unless I hit the stop button just before any page loads fully, the page disappears completely and I just get a blank white page. Something is afoot.--ukexpat (talk) 16:58, 16 February 2011 (UTC)[reply]

Also, it seems like the !important keyword in CSS doesn't work, after some quick testing. This is a crucial keyword to have. Gary King (talk · scripts) 16:56, 16 February 2011 (UTC)[reply]

Neermind, it looks like they've added "&version" to the CSS's URL, so that you won't always be loading the latest stylesheet. Which makes debugging more difficult—unless there's a way to set &debug to true? Gary King (talk · scripts) 17:10, 16 February 2011 (UTC)[reply]

Yep, just set debug=true in your query string; it will be passed to load.php and enable debug mode. It still passes version though. Reach Out to the Truth 17:37, 16 February 2011 (UTC)[reply]

Where do I do this? The wiki loads the CSS, not me, so I'm not quite sure? Gary King (talk · scripts) 17:41, 16 February 2011 (UTC)[reply]

D'oh nevermind, figured it out. Gary King (talk · scripts) 19:02, 16 February 2011 (UTC)[reply]

Change the "new section" tab text to instead display the much narrower "+". gadget looks broken (Vector, no personal js/css games). Tried unchecking (and saving) the rechecking/saving, and purging local cache and force-reloading everything. Still have "New section" instead of "+". Other gadgets (popups, UTC clock) are working correctly. DMacks (talk) 16:50, 16 February 2011 (UTC)[reply]

Well, gadgets now seem to be working, but the blackscreen is clunky - the page loads in whitescreen, then jumps to blackscreen. It used to load smoothly in blackscreen. DuncanHill (talk) 17:13, 16 February 2011 (UTC)[reply]

That's probably because all JavaScript files have been moved to the bottom of the page now, so I think all scripts will experience this "choppiness". Gary King (talk · scripts) 17:19, 16 February 2011 (UTC)[reply]

I have the same problem as DMacks; I get new section rather than +. /ƒETCH COMMS / 17:34, 16 February 2011 (UTC)[reply]

Fixed now —TheDJ (talk • contribs) 20:40, 16 February 2011 (UTC)[reply]

Not for me, and I am still having the other problems I mentioned above...--ukexpat (talk) 20:52, 16 February 2011 (UTC)[reply]

Better now ? I did some fixes. BTW you have a gigantic amount of userscripts installed, many VERY old and just bound to break on the smallest changes. —TheDJ (talk • contribs) 00:11, 17 February 2011 (UTC)[reply]

Haven't checked in the past few hours, but "+" is now working correctly for me. Thanks for all the hard work on this update! DMacks (talk) 01:17, 17 February 2011 (UTC)[reply]

I removed some scripts and all appears to be working fine now, thanks! – ukexpat (talk) 03:16, 17 February 2011 (UTC)[reply]

Missing on toolbar - Cite button and cite templates

Once again, the cite option on the Editing toolbar is missing, as are the cite templates. Maile66 (talk) 16:53, 16 February 2011 (UTC)[reply]

... and for me. Tried changing skin, toggling refTools, edit toolbar with cache clear. Fiddling with vector.js didn't help either. Thincat (talk) 18:04, 16 February 2011 (UTC)[reply]

... and for me. I've really become quite dependent on the availability of the Cite button and templates. Darrell_Greenwood (talk) 19:16, 16 February 2011 (UTC)[reply]

And for me. --j⚛e decker ^{talk to me} 20:22, 16 February 2011 (UTC)[reply]

Following this advice above, here is a faltering start towards a work-round (for me). In My preferences, Editing turn off the two options very near the bottom under beta features "Enable enhanced editing toolbar" and "Enable dialogs for inserting links, tables and more". Save. Then, when editing, position the cursor appropriately in editing window, scroll up the window (not merely the editing box) and click the button marked {{CITE}} (last on the right). Select appropriate button appearing underneath. "Preview citation" works but, sadly, "add citation" seems to do nothing. I still have "Show edit toolbar (requires JavaScript)" and "RefTools" on and I don't know whether their status matters. Thincat (talk) 22:31, 16 February 2011 (UTC)[reply]

Thanks, but this does nothing for me. I have Firefox. Since today (and not before), if I uncheck the suggested boxes in Preferences and Save, it tells me the Preferences were saved. But it puts the check marks right back. I have the old toolbar. It's just the Cite button that is missing. Also, some interesting funky stuff that is probably related to what they are working on. On any edit page, on the upper right, I get a red lettered "Page notice", and if I click on it, it tells me there is no Template with the name "Template/EditNotices/Page/whatever page I have open". So, I think they're still working - because I don't think that Page Notice is supposed to be there. Hopefully, the Cite button will come back soon. Maile66 (talk) 00:06, 17 February 2011 (UTC)[reply]

This is (mostly) fixed now. You'll have to bypass your cache. They removed the variable that I was using to detect whether the toolbar was enabled. The script will still be broken if you have dialogs disabled as I don't know how to detect whether the dialogs are enabled or not. Mr.Z-man 01:12, 17 February 2011 (UTC)[reply]

Consider this a virtual dancing in the aisles. The Cite button is fixed!! Thanks. Maile66 (talk) 01:16, 17 February 2011 (UTC)[reply]

I'm still a wallflower waiting for a dance;-( For the last three options in My Preferences, Editing ("Beta Enhanced toolbar", "Beta Enable dialogs for inserting" and "Labs Enable preview dialogs"), if all are off I get a {{CITE}} button which goes fine until the last moment when "add citation" does nothing. This has functionality for fillling in other fields from data extrracted from the supplied URL. However, if the last two options are off and on (in order) I get no cite option. Otherwise, I get the previous "Cite" tab (after "special characters...help") which seems to work as before. Thincat (talk) 09:28, 17 February 2011 (UTC)[reply]

Ah ha! I have switched from Vector to MonoBook skin after reading this. Now, with the three options I mentioned above Off, Off, On I get a working "Cite" button (new style). I have kept "edit toolbar" and "RefTools" On and I think this is also a requirement. Thincat (talk) 09:46, 17 February 2011 (UTC)[reply]

RefTools not working

Hi there. Since Wednesday, 18th February 2011, I've noticed that reftools is no longer working on my browser (I'm using Windowx XP, Firefox 3.6.13). Been using reftools since 2009 without any issues. I've tried out all options both in "Appearance" and "Gadgets" in the Preferences menu, yet the reftool bar doesn't appear each time I edit an article. (btw, I have java installed on my system as well). Any idea why I can't access reftools anymore? Amsaim (talk) 09:36, 17 February 2011 (UTC)[reply]

This side of the dateline: confirming. They're broken. --Old Moonraker (talk) 10:52, 17 February 2011 (UTC)[reply]

For the original edit toolbar, the only way to make it work is to disable wikEd either in gadgets or on the fly with the on/off button on the wikEd toolbar. For the enhanced toolbar, it works more often, but sometimes the cite window becomes wider than my browser window and there's no horizontal scroll bar. I greatly prefer the original toolbar & refTools plus anyway. I actually don't need the rest of the toolbar because I have wikEd, I just need the cite button. I don't like the ProveIt UI. I'm running FF 3.6.13. —UncleDouggie (talk) 11:15, 17 February 2011 (UTC)[reply]

This is also being discussed above at Wikipedia:Village_pump_(technical)#Missing_on_toolbar_-_Cite_button_and_cite_templates. Thincat (talk) 12:22, 17 February 2011 (UTC)[reply]

I see I am not alone in being affected by the recent media wiki and reftools changes. See Wikipedia talk:RefToolbar 1.0#broken since 14 February 2011? where I tested various Gadget combinations. I still wish that the old toolbar was brought back ([12] [13]), but this combination at least gets me the new-style Cite button working on Firefox 3.6.13 with monobook:

"Show edit toolbar" off

"refTools" Gadget ON

"Enable enhanced editing toolbar" ON

"Enable dialogs for inserting links, tables and more" ON

-84user (talk) 12:45, 17 February 2011 (UTC)[reply]

Also on FF 3.6.13 and having gone to Monobook (for exactly this reason), this gives me the Cite tab as previously but not the new Cite button. For this I need (as I reported above)

"Show edit toolbar" ON

"refTools" Gadget ON

"Enable enhanced editing toolbar" OFF

"Enable dialogs for inserting links, tables and more" OFF

"Enable preview dialog" ON

I would prefer your setup if it worked for me. Thincat (talk) 13:06, 17 February 2011 (UTC)[reply]

Maybe something changed in media wiki very recently but I can now get the old edit toolbar plus the old "cite" icon with this combination:

Preferences / Editing / Advanced options : ON: Show edit toolbar (requires JavaScript)

Preferences / Editing / Beta features : OFF: all options

Preferences / Gadgets / Editing gadgets : ON: refTools

I tested the icons B, I, #R, <ref /ref> and <<CITE>> for web and news.

Here is the combination that gets a working new-style toolbar plus working new style cite (it previewed and inserted citations for {{cite web}}):

Preferences / Editing / Advanced options : OFF: Show edit toolbar (requires JavaScript)

Preferences / Editing / Beta features : ON: Enable enhanced editing toolbar

Preferences / Editing / Beta features : ON: Enable dialogs for inserting links, tables and more

Preferences / Editing / Labs features : OFF: Enable preview dialog

Preferences / Gadgets / Editing gadgets : ON: refTools

I have no other Editing gadgets on, but I do have Browsing gadgets / Navigation popups ON; I also have this monobook.js. -84user (talk) 13:47, 17 February 2011 (UTC)expanded the prefs. -84user (talk) 13:55, 17 February 2011 (UTC)[reply]

Clear buffer if page shifted?

Hi,
This has happened to me countless times, so presumably others see it too.

The page is drawn. I click on something I want to see.
Then, it happens that WP is seeking donations, or I have new messages.
Page shifts downward.
But my mouse click is still active.
So I get something I didn't ask for.

Isn't it straightforward just to clear the input buffer in cases where you do a page redraw?
Or shift the co-ordinates of the pending click(s) to reflect the fresh page layout?
Clearly the former option is simpler.
Cheers, Varlaam (talk) 17:42, 16 February 2011 (UTC)[reply]

This is a browser-related issue, I believe. I don't think JavaScript can control what element is activated when the mouse is clicked on something else. Gary King (talk · scripts) 17:48, 16 February 2011 (UTC)[reply]

Freenode

I've just had access difficulties for quite some time - enough to make a hot drink and feed the cat. Whilst this was going on, all I could get was the standard message beginning "WIKIMEDIA FOUNDATION Error Our servers are currently experiencing a technical problem. This is probably temporary and should be fixed soon. Please try again in a few minutes. You may be able to get further information in the #wikipedia channel on the Freenode IRC network.". I have two problems here.

First, the #wikipedia link doesn't do anything at all in Chrome; in Firefox it asks me to choose an application, but I have no idea which application would be correct for this; whereas in Opera, I get to a "New account wizard". I don't necessarily want to post anything yet: I just want to find out what's wrong.

My second problem is that Freenode IRC network takes me to an "About the Network" screen, and there doesn't seem to be anywhere where I might enter this "#wikipedia" channel name, other than the Google search box upper right, which gives me a whole heap of irrelevant and out-of-date stuff. --Redrose64 (talk) 17:50, 16 February 2011 (UTC)[reply]

IRC. Prodego ^talk 17:53, 16 February 2011 (UTC)[reply]

You might want to try the Freenode webchat. --Morn (talk) 18:14, 16 February 2011 (UTC)[reply]

@Prodego: I had already worked out that it meant "internet relay chat". The point is, I can't get to anything that might tell me what's wrong with the Wikimedia servers.

@Morn: this wants me to create an account. Wikipedia (normally) allows non-registered users to read pages, so does Bugzilla. I would like to do similarly with Freenode. --Redrose64 (talk) 18:24, 16 February 2011 (UTC)[reply]

It asks you to supply a nickname, not to create an account. You'll need a nickname to connect to an IRC server, you can't connect otherwise. –xeno^talk 18:26, 16 February 2011 (UTC)[reply]

Also if you connect to freenode, your IP address will be publicly viewable by anyone else in the chat. Prodego ^talk 18:27, 16 February 2011 (UTC)[reply]

But if you have an account you can apply for a cloak. --Ron Ritzman (talk) 02:31, 17 February 2011 (UTC)[reply]

Disable smaller font size of elements gadgets no longer works without javascript

The gadget "Disable smaller font sizes of elements such as Infoboxes, Navboxes and References lists" worked fine without javascript until today with Mediawiki 1.17. I prefer to leave javascript off most of the time, but I also love being able to read the references etc text at the same font size. Is there a way to resolve this (new) issue? TransUtopian (talk) 17:52, 16 February 2011 (UTC)[reply]

What browser and skin are you using? —TheDJ (talk • contribs) 20:45, 16 February 2011 (UTC)[reply]

I'm using Opera 10.60 and Monobook. TransUtopian (talk) 23:09, 16 February 2011 (UTC)[reply]

It should work even without JS enabled for your browser, since it uses CSS, not JS. Gary King (talk · scripts) 01:25, 17 February 2011 (UTC)[reply]

Actually, it now relies on the resource loader, which is javascript, to load all the gadgets. I don't know if gadgets required javascript before the update. — Edokter (talk) — 01:32, 17 February 2011 (UTC)[reply]

Since I disable JS unless I specifically need it for something, I'd say this gadget didn't require it before. Is there something I can add to my CSS that'll duplicate the gadget, or can specific gadgets be removed from using the resource loader (or have a duplicate version that doesn't use it)? TransUtopian (talk) 12:01, 17 February 2011 (UTC)[reply]

(←) Put the following line at the top of your skin CSS file:

@import url(http://en.wikipedia.org/w/index.php?title=MediaWiki:Gadget-NoSmallFonts.css&action=raw&ctype=text/css);

That should do the trick. — Edokter (talk) — 12:46, 17 February 2011 (UTC)[reply]

The signature button is not working

The "Your signature with timestamp" button on the toolbar above editor window as well as signature sign in Wiki markup, is not working properly. When I press it while editing, nothing happens, expect my screen moves upwards towards start of the discussion. In case where I am starting a thread (like now), when I pushed the button or Wiki markup symbol, the signature appeared in Subject/headline textbox.Redtigerxyz ^Talk 18:14, 16 February 2011 (UTC)[reply]

Seems to be working in Monobook (nb with "Enable enhanced editing toolbar" disabled) - --Redrose64 (talk) 18:26, 16 February 2011 (UTC)[reply]

Horizontal scrollbar on nearly all pages

Now that the new updates have been installed, my browser places a horizontal scrollbar on nearly all pages I view while logged in. This happens in both Firefox and IE. Is this a known issue and is there a known solution? It's minor but annoying. ElKevbo (talk) 18:27, 16 February 2011 (UTC)[reply]

I'm having the same experience here; does anybody have any input? — Fourthords | =/\= | 22:05, 16 February 2011 (UTC)[reply]

I'm not experiencing this. Which skin are you guys using? Most people are using Vector and don't appear to have any problems regarding this. I'm using Monobook and don't have this problem. Gary King (talk · scripts) 01:25, 17 February 2011 (UTC)[reply]

I finally figured it out after some trial and error: in my preferences, I had enabled the gadget to widen the Wikipedia search box ("Widen the search box in the Vector skin."). Once I disabled that, my stupid horizontal scrollbar went away! Hope this works for you! — Fourthords | =/\= | 01:31, 17 February 2011 (UTC)[reply]

Yup, that's it! Thanks! ElKevbo (talk) 01:52, 17 February 2011 (UTC)[reply]

Thank you. I was wondering about that. I'm actually using a different searchbox-widening script; it looks like 1.17 forces the searchbox to grow to the right rather than touch the pristine empty space to the left. — Gavia immer (talk) 01:43, 17 February 2011 (UTC)[reply]

Mobile site redirects to regular site first now

Since JavaScript files are moved to the bottom of the page now, whenever a mobile device visits the wiki, it first loads the entire regular page, then is redirected to the mobile version. It seems better to at least move the mobile redirect code to the top of the page like it was before. Gary King (talk · scripts) 18:48, 16 February 2011 (UTC)[reply]

This is not possible at the moment I think. What is needed is that the squids take care of redirecting. JS is just an ugly bandaid that we really shouldn't use for this. There is a bugzilla ticket for that bugzilla:24859. —TheDJ (talk • contribs) 20:51, 16 February 2011 (UTC)[reply]

Blue new message bars?!

Is there a CSS snippet I can get to change it back to orange? /ƒETCH COMMS / 19:09, 16 February 2011 (UTC)[reply]

Better still, change it back. I don't remember seeing any discussion or consensus for this change. Mjroots (talk) 19:15, 16 February 2011 (UTC)[reply]

(edit conflict) Is there a good reason (or consensus, for that matter) for the change in the first instance? Should be restored in the common css, imo. –xeno^talk 19:15, 16 February 2011 (UTC) (FWIW, it is still orange for me, on monobook)[reply]

Yeah, I like the orange one better too. Catches your eye better. --T H F S W (T · C · E) 19:25, 16 February 2011 (UTC)[reply]

I don't care what color the bar is, but if someone is going to change the 'new message' notice, could I make a plea for the addition of a history button? "Last change" fairly often leads me to miss messages (when multiple edits are made to the page in short succession). WhatamIdoing (talk) 19:32, 16 February 2011 (UTC)[reply]

div.usermessage { background-color: #FFCE7B; border: 1px solid orange; } in your css would change it back, I suspect. @WhatamIdoing, there's some script to do that I believe, I'll see if I can find it for you (here you go) . - Kingpin¹³ (talk) 19:38, 16 February 2011 (UTC)[reply]

Whose decision was this? Bad. Very bad. Choyoołʼįįhí:Seb az86556 ^{> haneʼ} 19:49, 16 February 2011 (UTC)[reply]

Someone isn't reading what is written. I don't want to have to go round fiddling with codes that I don't understand to get back something that appears to have been changed without discussion and therefore without consensus. I want the message bar changed back to how it was. A RFC or similar should then be opened on whether or not the community desires the change, or whether it should be an option, like the [edit] button at the end of header text instead of at the right side of the page. Mjroots (talk) 19:55, 16 February 2011 (UTC)[reply]

I believe this can be easily fixed by editing Mediawiki:Common.css (or maybe just MediaWiki:Vector.css) and I have suggested it be changed back at MediaWiki talk:Common.css#MW 1.17 now live, juicy style/script excitingness for all. –xeno^talk 19:58, 16 February 2011 (UTC)[reply]

Mr. MediaWiki 1.17 isn't very nice. --Perseus8235 19:56, 16 February 2011 (UTC)[reply]

Now that's not very fair, I wouldn't put it down simply because it changes the colour of the new messages banner. Just to better explain how to apply my piece of css up above, simply visit Special:MyPage/vector.css, click edit, paste in div.usermessage { background-color: #FFCE7B; border: 1px solid orange; } and then select save. Everything will be back to normal for you. If we placed this code in the MediaWiki:Vector.css as xeno mentions, it would be back to normal for everyone, but we'd need consensus for that. For those asking why this was changed, it was originally changed at another wiki (they do exist) specifically for vector, because it works better with the colour scheme. It was discussed briefly at bugzilla (I believe). - Kingpin¹³ (talk) 20:11, 16 February 2011 (UTC)[reply]

I don't think we need consensus to restore the status quo. Why was it changed globally, instead of for the particular wiki that requested it? –xeno^talk 20:14, 16 February 2011 (UTC)[reply]

Consensus???? Per Xeno. Despite your sracasm Kingpin most of us are aware that other wikis exist. Pedro : Chat 20:23, 16 February 2011 (UTC)[reply]

Could you clarify what you mean by "consensus??"? I think xeno meant it wasn't needed to restore it at enwiki, not that there was no need for consensus to restore it globally.. - Kingpin¹³ (talk) 20:28, 16 February 2011 (UTC)[reply]

Yes, that would be the "per Xeno" bit. Pedro : Chat 20:38, 16 February 2011 (UTC)[reply]

Well it was to start with, you see it was changed for that particular wiki first, and they decided it worked well enough to make it global. Yeah, maybe we can just change it back, I guess the only problem is we want to be sure, so we're not going backwards and forwards with the common css files - Kingpin¹³ (talk) 20:21, 16 February 2011 (UTC)[reply]

I must admit, I'm fairly confused as to why that this change was made without local consensus. I understand that en.wiki is not the only Wikimedia project, but it is the largest. And we have a hard enough time getting changes through where unanimous local consensus exists - why was this changed without so much as a "hey, we're planning on doing this?" (I realize you personally were not responsible, do please don't take this as shooting the messenger - my question is to whoever knows the answer) –xeno^talk 20:24, 16 February 2011 (UTC)[reply]

this is the dumbest thing I've seen lately; this bar is not supposed to blend in, it's supposed to pop out at you. Choyoołʼįįhí:Seb az86556 ^{> haneʼ} 20:22, 16 February 2011 (UTC)[reply]

Geez, people could show some appreciation for the work that went into this update, it's not particularly "dumb". After-all you don't want it flashing-bright-pink do you? :). It's really a matter of personal preference, and I've given you some code up above which allows you to set it on a personal level. - Kingpin¹³ (talk) 20:28, 16 February 2011 (UTC)[reply]

As a matter of fact, flashing-bright-pink would be even better than orange. People are supposed to see it. Choyoołʼįįhí:Seb az86556 ^{> haneʼ} 20:30, 16 February 2011 (UTC)#[reply]

If you say so, but I doubt many would agree with you about that, - Kingpin¹³ (talk) 20:45, 16 February 2011 (UTC)[reply]

I appreciate the hard work that developers do, and generally cringe when I see them being bitten; but I think that they would be even more appreciated (and incur less bite marks) if they asked us, or gave us a heads up, prior to making a sweeping change like this. The new messages bar is a central component of Wikipedia that has been orange for as long as I can remember. Do you happen to have any links to where this was discussed? I couldn't find anything using an advanced bugzilla search. –xeno^talk 20:34, 16 February 2011 (UTC)[reply]

Don't worry, it's not your comments I have an issue with. Yeah, bugzilla's search is impossible to use, here's a link to a discussion about it. I got that from searching through my history, I think I originally went there from another discussion on-wiki about the changes. Apparently my memory may be a little bit wrong, and the German Wikipedia didn't actually implement it as a standard, just as a common change users made. - Kingpin¹³ (talk) 20:45, 16 February 2011 (UTC)[reply]

Thank you for the link. Based on that, I'm still pretty astonished that it went through on a global basis despite the objections raised there. –xeno^talk 20:49, 16 February 2011 (UTC)[reply]

← I've initiated an editprotected request at MediaWiki talk:Vector.css#Change "You have new messages bar" back to orange. –xeno^talk 20:49, 16 February 2011 (UTC)[reply]

Status Quo restored. However might I suggest we look at ways to make the messages bar more "vector" like, but keeping it more visible ? I think that is the least we can do. —TheDJ (talk • contribs) 21:04, 16 February 2011 (UTC)[reply]

That sounds reasonable, as long as the discussion is well-trafficked and widely-advertised and so any changes have consensus and do not take users by surprised. Thanks for fulfilling the editprotected request. –xeno^talk 21:11, 16 February 2011 (UTC)[reply]

They've been made aware of our displeasure at the lack of discussion over at bugzilla. As I stated earlier, this should really be the subject of a RFC, with all options explored (status quo, change to blue, enable blue [and possibly other colours] as a user option etc). Mjroots (talk) 21:19, 16 February 2011 (UTC)[reply]

Parkinson's Law of Triviality is in full effect. the wub "?!" 22:35, 16 February 2011 (UTC)[reply]

Sometimes the color of the bike shed really does matter (it might seem trivial to you, but the neighbors have to see it too). —Emufarmers^(T/C) 23:32, 16 February 2011 (UTC)[reply]

In this instance, a better analogy might be "the color of the life raft." The bar's appearance was based upon something other than aesthetics, and it appears that this fact was overlooked/ignored (even after it was pointed out). —David Levy 00:28, 17 February 2011 (UTC)[reply]

The orange has always driven me crazy, but I agree that the light blue was worse because it didn't stand out at all. Thanks to this thread, I now have my own pleasing medium purple. It might be a good candidate for other vector users as well. I rounded the corners slightly, but less than the blue version. —UncleDouggie (talk) 11:00, 17 February 2011 (UTC)[reply]

You have new messages (last change).

I've reverted it in revision 82315. (X! · talk) · @064 · 00:32, 17 February 2011 (UTC)[reply]

Is Phase3 the live version? Or do we have to wait until 1.18? — Edokter (talk) — 00:40, 17 February 2011 (UTC)[reply]

"Phase 3" simply means MediaWiki. The key part of that path is "trunk", which is the current development branch (1.18alpha). Wikimedia sites are running the 1.17wmf1 branch, and it hasn't been reverted there. Reach Out to the Truth 03:04, 17 February 2011 (UTC)[reply]

Yay, this seems to be fixed. However, is it just me or are redlinks appearing in a darker red? Can I have the CSS snippet to change that back to #CC2200, or is this not possible? /ƒETCH COMMS / 03:11, 17 February 2011 (UTC)[reply]

They look identical to this text sample that is #CC2200 for me. —UncleDouggie (talk) 09:14, 17 February 2011 (UTC)[reply]

Wiki loads older CSS version

Okay, so after fixing up my monobook.css, everything looks like it's back to normal now. However, the only problem is that the wiki is loading an older version of my stylesheet. What I am currently doing right now, as a (hopefully) temporary solution, is I created a Greasemonkey script to remove the "&version=" where the wiki calls my monobook.css, so that it will always grab the latest version rather than grab a version that's a few hours old. However, does anyone have a more permanent fix for this, or should I just always wait for the cached CSS on the server-side to catch up to the actual version? Gary King (talk · scripts) 20:11, 16 February 2011 (UTC)[reply]

This shouldn't happen. RL was written so that this would not be necessary. —TheDJ (talk • contribs) 20:59, 16 February 2011 (UTC)[reply]

Things seemed to have settled down regarding this. Initially, I did spend a few hours working on it, though, noticing that CSS appeared differently in Firefox and Chrome, whether debug was enabled or disabled, and whether &version= was there or not. Gary King (talk · scripts) 01:19, 17 February 2011 (UTC)[reply]

Preload text may be incorrect

1.17 includes a fix for Template:Bug, which means that "preload" pages will now honor <noinclude>. This can cause breakage if the preload page includes <noinclude> text that should be included in the newly-created page. It can be fixed easily enough, to output a into the editbox use something like <noin<noinclude/>clude>. If you understood that, please check any preload texts to ensure they still generate the correct edit box contents. Anomie ⚔ 20:14, 16 February 2011 (UTC)[reply]

The new edit box

...sucks. How can I change it back? Ten Pound Hammer, his otters and a clue-bat • ^{(Otters want attention)} 20:56, 16 February 2011 (UTC)[reply]

Agreed. Why does it take huge amounts of consensus to activate even the tiniest useful features, yet all these garbage front-end visual changes are shoved down our throats with asking? Change the vertical linespacing to the same as the regular edit window and get the vector-style tool bar out of monobook. - ʄɭoʏɗiaɲ ^τ _¢ 21:00, 16 February 2011 (UTC)[reply]

See Wikipedia:Village pump (technical)#Editing above. -- Whpq (talk) 21:09, 16 February 2011 (UTC)[reply]

(e/c)Because errors are made and not everything can be fixed after an error. See comments by catrope in #Editing. And for the last FREAKING TIME assuming some god damn good faith on part of the developers. OR F'ing leave. —TheDJ (talk • contribs) 21:10, 16 February 2011 (UTC)[reply]

I mean it by the way, I have totally had it with people complaining about the work that the developers are doing. I've warned some of these people multiple times on this page, I can't believe I would have to go towards throwing official warnings on talk pages and entering the process towards a block of a user, don't make me go that way. You people should know better. —TheDJ (talk • contribs) 21:14, 16 February 2011 (UTC)[reply]

By all means, and lose your privileges for making a shitty decision based on your emotional reaction to the situation. I have every right to complain and assert that no consensus was attained to make such changes. I have every right to assert that the new appearance looks shitty in my eyes. Please, start blocking users by this reasoning so we can open an WP:RFC/U and you can become a regular user. Developers act on a job that is given to them. Who told the developers to do this? That's who I am criticizing, not the developers that merely programmed the code as they were instructed to. - ʄɭoʏɗiaɲ ^τ _¢ 22:19, 16 February 2011 (UTC)[reply]

And don't vandalize my talk page either, TheDJ. Disagreeing with others opinion is not assuming bad faith. Nobody has to like what the developers make. We aren't obligated to applaud what they put out. Just as you placed a warning on my page, I have now placed one on yours; both are equally unwarranted. - ʄɭoʏɗiaɲ ^τ _¢ 01:50, 17 February 2011 (UTC)[reply]

If we required consensus for each and every little thing (including wiping one's butt), then nothing new would ever get implemented due to the fact that some people just don't like change, period. –MuZemike 21:13, 16 February 2011 (UTC)[reply]

And that's why reftools still isn't turned on by default, despite actual consensus? You're right, people don't like change. The correct action to such a situation is to give users the option of "upgrading" to the new appearance. - ʄɭoʏɗiaɲ ^τ _¢ 22:19, 16 February 2011 (UTC)[reply]

The reason RefTools have not been turned on is that we were waiting for the 1.17 rollout to happen to enable it. But don't let the facts get in the way of a good rant. Titoxd^{(?!? - cool stuff)} 01:59, 17 February 2011 (UTC)[reply]

I think the point is that this change is seen as an attempt to "Vectorize" the monobook style. It seems bizarre why this change would be made in the first place. At the very least, these types of changes should be opt-in, not opt-out. SnottyWong ^confer 21:15, 16 February 2011 (UTC)[reply]

Read !!!!!. —TheDJ (talk • contribs) 21:20, 16 February 2011 (UTC)[reply]

DJ, I know this is stressful on your end, and the unnamed developers. Sometimes, unless somebody like you puts that directive about "Read!!!", it's not always easy to find on this page who is saying what that impacts one's particular case. And sometimes...the issue is not about this upgrade, but it just seems to be. So, thanks to the developers and what they are trying to accomplish. Hope it gets better for us all.Maile66 (talk) 21:42, 16 February 2011 (UTC)[reply]

FWIW - I was dismayed to find the new toolbar when I logged in; but found what I needed here to unclick the button I had set in my preferences & it's back. So, no big deal, really. As long as we can get back the toolbar we're used to seeing, life is good. Truthkeeper88 (talk) 22:25, 16 February 2011 (UTC)[reply]

I totally agree. Thanks to the other users who helped me retrieve my sanity by actually making the effort to explain what to do to get it working properly again. I am, however, concerned about the hundreds of users who must be having the same experience and the same difficulty in tracking down a sensible answer. Deb (talk) 08:23, 17 February 2011 (UTC)[reply]

Broken file

See File:Blinx Time Controls.png. When I go there, I get a weird SQL error. Any ideas? SnottyWong ^talk 21:12, 16 February 2011 (UTC)[reply]

Interestingly enough, the image displays just fine, just can't go to its page:

— SnottyWong ^converse 21:14, 16 February 2011 (UTC)[reply]

Fixed

!log catrope synchronized php-1.17/wmf-config/db.php  'Depool srv178 from ES'

. —TheDJ (talk • contribs) 21:19, 16 February 2011 (UTC)[reply]

Thanks. SnottyWong ^prattle 21:34, 16 February 2011 (UTC)[reply]

Underlined links and a more general changes query

How comes i can no longer have links underlined? Frankly, something as seemingly small as this was actually one of the biggest reasons i could tell whether i was logged in or not.

Whilst we are on the subject of links, can someone point me in the direction of the changes to the user interface that have taken place today? Also what does global account do? Simply south...... 22:02, 16 February 2011 (UTC)[reply]

See #Links aren't being underlined. — Edokter (talk) — 22:20, 16 February 2011 (UTC)[reply]

Table show/hide disfunction

If I am on the right place: when asking for an uncollapse, it does not happen and my screen jumps to top-of-page. Example: (see also page Unicode character property):

General Category (Unicode Character Property)^[a] v t e
Value	Category Major, minor	Basic type^[b]	Character assigned^[b]	Count^[c] (as of 16.0)	Remarks

L, Letter; LC, Cased Letter (Lu, Ll, and Lt only)^[d]
Lu	Letter, uppercase	Graphic	Character	1,858
Ll	Letter, lowercase	Graphic	Character	2,258
Lt	Letter, titlecase	Graphic	Character	31	Ligatures or digraphs containing an uppercase followed by a lowercase part (e.g., ǅ, ǈ, ǋ, and ǲ)
Lm	Letter, modifier	Graphic	Character	404	A modifier letter
Lo	Letter, other	Graphic	Character	136,477	An ideograph or a letter in a unicase alphabet
M, Mark
Mn	Mark, nonspacing	Graphic	Character	2,020
Mc	Mark, spacing combining	Graphic	Character	468
Me	Mark, enclosing	Graphic	Character	13
N, Number
Nd	Number, decimal digit	Graphic	Character	760	All these, and only these, have Numeric Type = De^[e]
Nl	Number, letter	Graphic	Character	236	Numerals composed of letters or letterlike symbols (e.g., Roman numerals)
No	Number, other	Graphic	Character	915	E.g., vulgar fractions, superscript and subscript digits, vigesimal digits
P, Punctuation
Pc	Punctuation, connector	Graphic	Character	10	Includes spacing underscore characters such as "_", and other spacing tie characters. Unlike other punctuation characters, these may be classified as "word" characters by regular expression libraries.^[f]
Pd	Punctuation, dash	Graphic	Character	27	Includes several hyphen characters
Ps	Punctuation, open	Graphic	Character	79	Opening bracket characters
Pe	Punctuation, close	Graphic	Character	77	Closing bracket characters
Pi	Punctuation, initial quote	Graphic	Character	12	Opening quotation mark. Does not include the ASCII "neutral" quotation mark. May behave like Ps or Pe depending on usage
Pf	Punctuation, final quote	Graphic	Character	10	Closing quotation mark. May behave like Ps or Pe depending on usage
Po	Punctuation, other	Graphic	Character	640
S, Symbol
Sm	Symbol, math	Graphic	Character	950	Mathematical symbols (e.g., +, −, =, ×, ÷, √, ∊, ≠). Does not include parentheses and brackets, which are in categories Ps and Pe. Also does not include !, *, -, or /, which despite frequent use as mathematical operators, are primarily considered to be "punctuation".
Sc	Symbol, currency	Graphic	Character	63	Currency symbols
Sk	Symbol, modifier	Graphic	Character	125
So	Symbol, other	Graphic	Character	7,376
Z, Separator
Zs	Separator, space	Graphic	Character	17	Includes the space, but not TAB, CR, or LF, which are Cc
Zl	Separator, line	Format	Character	1	Only U+2028 LINE SEPARATOR (LSEP)
Zp	Separator, paragraph	Format	Character	1	Only U+2029 PARAGRAPH SEPARATOR (PSEP)
C, Other
Cc	Other, control	Control	Character	65 (will never change)^[e]	No name,^[g] <control>
Cf	Other, format	Format	Character	170	Includes the soft hyphen, joining control characters (ZWNJ and ZWJ), control characters to support bidirectional text, and language tag characters
Cs	Other, surrogate	Surrogate	Not (only used in UTF-16)	2,048 (will never change)^[e]	No name,^[g] <surrogate>
Co	Other, private use	Private-use	Character (but no interpretation specified)	137,468 total (will never change)^[e] (6,400 in BMP, 131,068 in Planes 15–16)	No name,^[g] <private-use>
Cn	Other, not assigned	Noncharacter	Not	66 (will not change unless the range of Unicode code points is expanded)^[e]	No name,^[g] <noncharacter>
Cn	Other, not assigned	Reserved	Not	819,467	No name,^[g] <reserved>
^ "Table 4-4: General Category". The Unicode Standard. Unicode Consortium. September 2024. ^ ^a ^b "Table 2-3: Types of code points". The Unicode Standard. Unicode Consortium. September 2024. ^ "DerivedGeneralCategory.txt". The Unicode Consortium. 2024-04-30. ^ "5.7.1 General Category Values". UTR #44: Unicode Character Database. Unicode Consortium. 2024-08-27. ^ ^a ^b ^c ^d ^e Unicode Character Encoding Stability Policies: Property Value Stability Stability policy: Some gc groups will never change. gc=Nd corresponds with Numeric Type=De (decimal). ^ "Annex C: Compatibility Properties (§ word)". Unicode Regular Expressions. Version 23. Unicode Consortium. 2022-02-08. Unicode Technical Standard #18. ^ ^a ^b ^c ^d ^e "Table 4-9: Construction of Code Point Labels". The Unicode Standard. Unicode Consortium. September 2024. A Code Point Label may be used to identify a nameless code point. E.g. <control-hhhh>, <control-0088>. The Name remains blank, which can prevent inadvertently replacing, in documentation, a Control Name with a true Control code. Unicode also uses <not a character> for <noncharacter>.

-DePiep (talk) 22:03, 16 February 2011 (UTC)[reply]

Collapsable and Sortable don't mix very well. — Edokter (talk) — 22:28, 16 February 2011 (UTC)[reply]

Metoo: seems to be related (so: combination => bug) -DePiep (talk) 23:39, 16 February 2011 (UTC)[reply]

Since? -DePiep (talk) 22:29, 16 February 2011 (UTC)[reply]

~~This is probably caused by a conflict between MediaWiki:CollapsibleTemplates.js and the new MediaWiki 1.17 JS code.~~ Kaldari (talk) 22:29, 16 February 2011 (UTC)[reply]

Sorry, that's on Commons. The code here is in MediaWiki:Common.js. Kaldari (talk) 22:32, 16 February 2011 (UTC)[reply]

Well, it looks like it is introduced (broken) by 1.17. What do we do? -DePiep (talk) 22:34, 16 February 2011 (UTC)[reply]

Best ask Krinkle, he made some modifications to common.js today. — Edokter (talk) — 22:53, 16 February 2011 (UTC)[reply]

Are we 100% sure this ever worked ? —TheDJ (talk • contribs) 22:57, 16 February 2011 (UTC)[reply]

Yes, it worked. btw, I asked Krinkle at their Commons talkpage. -DePiep (talk) 23:01, 16 February 2011 (UTC)[reply]

Eh, TheDJ, why the question? Anything strange in template's history or usage? -DePiep (talk) 23:16, 16 February 2011 (UTC)[reply]

Strangely, this bug doesn't happen if you're looking at the table in an edit preview, only on live pages. Kaldari (talk) 23:34, 16 February 2011 (UTC)[reply]

Come to think of it, this probably is because the sortable code breaks the collapse code. Krinkle will probably deal with that tomorrow. load order will probably matter in this case. —TheDJ (talk • contribs) 23:47, 16 February 2011 (UTC)[reply]

RSS feeds?

Why have RSS feeds stopped working? Specifically the one for new pages. — [[::User:RHaworth|RHaworth]] (talk · contribs) 22:06, 16 February 2011 (UTC)[reply]

Another unrelated regression. When I am doing speedy deletions, I used to get the reason supplied automatically for me from th speedy tag. This has stopped. Why? (I believe it was a bit of javascript.) — [[::User:RHaworth|RHaworth]] (talk · contribs) 22:11, 16 February 2011 (UTC)[reply]

I don't know but it's working for me. —Soap— 22:34, 16 February 2011 (UTC)[reply]

Worksforme. Happy‑melon 22:49, 16 February 2011 (UTC)[reply]

Which is working for you? Deletion reasons or RSS feeds? Atom feeds also seem to be broken. — [[::User:RHaworth|RHaworth]] (talk · contribs) 01:21, 17 February 2011 (UTC)[reply]

See Wikipedia:Village_pump_(technical)#Speedy-deleting_oddity for speedy deleting issue. Atom feeds seem to work for me, in Chrome 9. Gary King (talk · scripts) 01:31, 17 February 2011 (UTC)[reply]

Rollback quirk

Today's changes affected the rollback "button". In Firefox, I used to be able to <Ctrl><Click> on the rollback button to roll back vandalism from my Watchlist in a new tab. Today that no longer works. <Ctrl><Click> rolls back the vandalism in the current tab.

Not a big deal, but it was a convenience to preview the edit in Pop-Ups, roll it back in another tab, and continue down the Watchlist. — Malik Shabazz ^Talk/_Stalk 22:47, 16 February 2011 (UTC)[reply]

I don't have any issue doing this still. As far as I know ctrl+click is a browser thing. Killiondude (talk) 07:26, 17 February 2011 (UTC)[reply]

Disambigs, main topics, and dablinks

Today, I had to go through and about 200 links of proper names to a table, knowing that on initial entry many of these links would be "wrong", pointing to the wrong topic or a disambig page. No problem, I thought, I'll just dablinks on the toolserver to resolve them. However, I realized that dablinks only checks if the link goes to a disamb page and that's it, and so only 11 of what I'd estimate are 50 problem links were caught.

I was wondering if dablinks can be modified with two features:

First, taking the case where "Topic" and "Topic (disambiguation)" exist, Dablinks should recognize that the disamb page exist and highlight that area for the user, likely a different color, using the dab page to get that data. The user may have intended "Topic" in which case the user ignores the change, but if not this gives them the chance to change it.
Second, in cases where "Topic" exists, there is no "Topic (disambiguation)" but one or more "Topic (other term)" exist, it would be helpful for dablink to at least notify the user that other pages like "Topic" exist; I wouldn't expect Dablinks to list out them all but at least notification would be helpful.

I would expect this could be easily done with dablink programming and the addition of a hidden template on the affected pages, but this can be done automagically through the {{otheruses}} family of templates. --MASEM (t) 22:58, 16 February 2011 (UTC)[reply]

(edit conflict)I don't get all of your question, but this might be relevant. {{dablinks}} is a part (only) of Hatnotes world. Another metatemplate used is {{rellink}}, btw. All in all there are ~100 hatnote templates, based on these two meta T's (mostly actually using one of these). The automated (dab)-check you are mentioning, is currently applied by using multiple intrinsic options per template (overloaded templates, software speaking). So the 100 different templates can produce 200+ different hatnotes. Before we would apply your proposal, I'd like to get how the current situation will be covered, and how non-dab links (such as {{main}}) can go along. Hatnotes are not just disambiguation, really. -DePiep (talk) 23:54, 16 February 2011 (UTC)[reply]

CSS for new edit toolbar

Where is the CSS for the new (ajax) edit toolbar located? I suspect it's not editable, but it does have an error that needs adressing. — Edokter (talk) — 23:46, 16 February 2011 (UTC)[reply]

Where in the toolbar and how is it wrong ? Then I an use webkit inspector to find which part loads it. —TheDJ (talk • contribs) 07:29, 17 February 2011 (UTC)[reply]

I also use the webkit inspector; it shows the URL for the edit page. Anyway, to see the problem (which I already fixed in common.css), click Help on the toolbar; the 'What you type' column suffers the same (now fixed) monospace fontsize bug. — Edokter (talk) — 12:23, 17 February 2011 (UTC)[reply]

Show commons categories on Wikipedia image page

When one clicks on a Commons image in Wikipedia, one gets a page of metadata along with a note that says "This is a file from the Wikimedia Commons. Information from its description page there is shown below." Most of the information in the Commons file is copied over, but the Commons categories are not and I often find I need to go to the Commons file to see those categories. It would save me a lot of time if the Common category links could be shown on the initial Wikipedia image page, perhaps in the same box as the "This is a file from the Wikimedia Commons..." note.--agr (talk) 00:26, 17 February 2011 (UTC)[reply]

Make a feature request in bugzilla: —TheDJ (talk • contribs) 07:28, 17 February 2011 (UTC)[reply]

Speedy-deleting oddity

(boldly moved from WP:AN, Magog the Ogre (talk) 00:56, 17 February 2011 (UTC))[reply]

I am an admin. Until recently, when I speedy-deleted a page, the start of the contents of the text box created by the speedy-delete tag, appeared on the deletion window as the reason for the deletion. That saved much time. But, after today's Wikipedia downtime, the reason for the delete always appears as "Other reason", and I must type a reason in. Anthony Appleyard (talk) 23:25, 16 February 2011 (UTC)[reply]

This seems to be an erratic problem, it works fine for me. What skin are you using? Have you tried purging your cache? Happy‑melon 23:28, 16 February 2011 (UTC)[reply]

This is happening for me as well. The original tagger's deletion criteria no longer appears when I hit the 'delete' tab from the article page. --Jezebel'sPonyo^{bons mots} 00:06, 17 February 2011 (UTC)[reply]

That's not been working for a while now but at least I can pick one of the reasons from the box rather than having to type it in. CambridgeBayWeather (talk) 00:43, 17 February 2011 (UTC)[reply]

I'm quite sure this is a bug related to the Mediawiki upgrade to 1.17, correct? Magog the Ogre (talk) 00:57, 17 February 2011 (UTC)[reply]

Not a cache problem - I have tried three different browsers - all the same. One clue: in Firefox when I go into the delete screen, I get the message "Transferring data from meta.wikimedia.org" which does not go away. — [[::User:RHaworth|RHaworth]] (talk · contribs) 01:32, 17 February 2011 (UTC)[reply]

Just a note, but clicking on the word "deletion" inside of the templates still auto-populates the deletion summary, with the added benefit of automatically including information in the template, such as the URL for a copyvio. Cheers, everyone. lifebaka++ 02:02, 17 February 2011 (UTC)[reply]

I get the same "Transferring data from meta.wikimedia.org" message in my browser's status bar that doesn't go away even though the page is finished loading. But it happens on every page for me, not just the delete screen. I also can't get the revisionjumper gadget to work.. -- œ ^™ 02:14, 17 February 2011 (UTC)[reply]

The only thing coming from meta.wikimedia.org is JavaScript from Special:BannerController. It loads fine though, so I don't know what the browser is talking about... Reach Out to the Truth 02:38, 17 February 2011 (UTC)[reply]

I just tried to do a speedy delete, and I clicked various occurrences of the word "deletion" on the page to be deleted and in the deletion window, and the reason for deletion stayed as "Other reason". I use Firefox. Anthony Appleyard (talk) 06:38, 17 February 2011 (UTC)[reply]

Broken MediaWiki:Sysop.js loading perhaps ? —TheDJ (talk • contribs) 07:27, 17 February 2011 (UTC)[reply]

I have the same problem - as of this morning (UTC), the deletion reason has to be selected manually. Windows 7/Firefox, but also Chrome - not a browser issue. This is a pain, I hope it can be fixed soon. One oddity - which may help diagnose it - after deleting a page, when you click to delete the talk page, "G8: Talk page of a deleted page" does get automatically filled in. JohnCD (talk) 12:28, 17 February 2011 (UTC)[reply]

Interface issues

The recent MediaWiki 1.17 release caused a number of problems on my editing interface. By the way, I'm using monobook. First, vertical strip along the left side of the page is unusually shifted down (see screenshot). Can anything in my monobook.js (possibly the script labeled "Personal toolbox - from http://en.wikipedia.org/wiki/User:Brian0918/monobook.js", which appears below the standard links on the left hand side) be modified to fix this? Also, I got the old toolbar (for monobook) back by unclicking the options under "editing" in preferences, but the Wikipedia:RefToolbar 1.0 button shows up on the far left instead of the right. Any code to fix this? Thanks in advance, Goodvac (talk) 04:24, 17 February 2011 (UTC)[reply]

Right, I'm using MonoBook too, and the logo on the top left starts off a bit left and then moves right every time I open a new page, which slows down the opening. All Hallow's Wraith (talk) 06:14, 17 February 2011 (UTC)[reply]

Just try removing components that you think are problematic. That or using a JS console/debugger is likely the only thing you can do about it. The more work you do to prepare and pinpoint the problem, the less time other admins or myself have to invest to help you. —TheDJ (talk • contribs) 07:25, 17 February 2011 (UTC)[reply]

How do I remove compnents I think are problematic? The logo? I can remove that? All Hallow's Wraith (talk) 08:40, 17 February 2011 (UTC)[reply]

SVG not rendering

no longer displays for me on any of the (many) pages that use it. I'm running firefox (3.6.13). Any ideas what's happening? U+003F^? 10:42, 17 February 2011 (UTC)[reply]

I think I've seen it mentioned somewhere that Mediawiki 1.17 is more picky about SVG namespace declarations than 1.16. So maybe that's the problem? --Morn (talk) 11:52, 17 February 2011 (UTC)[reply]

I've fixed it. The issue was that the SVG tags used <svg:something> instead of just <something>. --Morn (talk) 12:59, 17 February 2011 (UTC)[reply]

Could you fix Commons:File:Current event template.svg as well? — Edokter (talk) — 13:22, 17 February 2011 (UTC)[reply]

Remark: what a shame that mediawiki decided to discard all the changes prior to yours today, Morn. Check it out: commons:File:Soccerball current event.svg#filehistory Magog the Ogre (talk) 13:53, 17 February 2011 (UTC)[reply]

All old versions are still there; MediaWiki just refuses to render them. — Edokter (talk) — 13:42, 17 February 2011 (UTC)[reply]

Oh, right, invalid SVG. Duh. Magog the Ogre (talk) 13:53, 17 February 2011 (UTC)[reply]

Writing user scripts for ResourceLoader

Knowing that use of the new modular JavaScript libraries will become necessary in a future version of MediaWiki, I am attempting to update User:PleaseStand/highlight-comments.js to not use any deprecated functions. My new version is at User:PleaseStand/highlight-comments-dev.js, and I have decided to add a feature to highlight other user's comments, not just one's own. My work on implementing this feature raises a few questions. What will be our replacement for importScript? Why aren't mw.Map and mw.user.name() (as documented on the MediaWiki site) exposed to user scripts in the currently live version of MediaWiki? What should be the standard way to give custom settings to user scripts? PleaseStand ^(talk) 12:31, 17 February 2011 (UTC)[reply]

Noticed any random script problems? wgVectorEnabledModules

I was having problems with some of my scripts not running... and from some of the posts above it seems that others in the last few days have as well. For me it was killing easyblock and some others, but I was able to track the JS error back to a protection script. It seems like wgVectorEnabledModules has either been deprecated or is not valid in all skins (and I'm using vector). I tried to put some error protection around it, but if anyone notices problems with my kludgy coding the feel free to revert back to this version of the protection script. If you are having other problems with your scrips you may want to look at whether it uses wgVectorEnabledModules. 7 13:21, 17 February 2011 (UTC)[reply]

[fn1-1] "Table 4-4: General Category". The Unicode Standard. Unicode Consortium. September 2024.

[fn2-2] "Table 2-3: Types of code points". The Unicode Standard. Unicode Consortium. September 2024.

[fn6-3] "DerivedGeneralCategory.txt". The Unicode Consortium. 2024-04-30.

[fn5-4] "5.7.1 General Category Values". UTR #44: Unicode Character Database. Unicode Consortium. 2024-08-27.

[fn3-5] Unicode Character Encoding Stability Policies: Property Value Stability Stability policy: Some gc groups will never change. gc=Nd corresponds with Numeric Type=De (decimal).

[6] "Annex C: Compatibility Properties (§ word)". Unicode Regular Expressions. Version 23. Unicode Consortium. 2022-02-08. Unicode Technical Standard #18.

[fn4-7] "Table 4-9: Construction of Code Point Labels". The Unicode Standard. Unicode Consortium. September 2024. A Code Point Label may be used to identify a nameless code point. E.g. <control-hhhh>, <control-0088>. The Name remains blank, which can prevent inadvertently replacing, in documentation, a Control Name with a true Control code. Unicode also uses <not a character> for <noncharacter>.

[a]

[b]

[c]

[d]

[e]

[f]

[g]