Seach to a specific page/word

This post by Ciencia Al Poder was moved on 2015-01-02. You can find it at Project:Support desk/Flow/2015/01#h-Seach_to_a_specific_page/word-2015-01-02T13:14:00.000Z. Ciencia Al Poder (talk) 13:42, 2 January 2015 (UTC)

[RESOLVED] Include API: and Skin: in default search namespaces

It seems the default search namespaces on this wiki haven't been updated for some time. Just now I searched for apidisabled in the search box, and only got 1 result, which was some release notes page. What I really wanted was API:Restricting API usage.

Currently the following namespaces are in our default search namespaces:

• (Main)
• Help
• Manual
• Extension

I propose that we add the following namespaces:

• API
• Skin

Any comments? This, that and the other (talk) 05:39, 5 January 2015 (UTC)

Good idea.

I believe you need to log a ticket in the bug tracker for this kind of change, as it requires modifying the site config files. HappyDog (talk) 09:44, 5 January 2015 (UTC)

+1

Should be an easy change with a lot of benefits. Florianschmidtwelzow (talk) 12:54, 5 January 2015 (UTC)

Done Api: and Skin: are now in the default namespaces (see T85807). Florianschmidtwelzow (talk) 20:22, 6 January 2015 (UTC)

Thanks! This, that and the other (talk) 06:11, 7 January 2015 (UTC)

Yep, makes sense; let's also include them in content namespaces if we didn't yet. Nemo 14:47, 6 January 2015 (UTC)

+1 (they aren't content pages atm), if there is enough content to be helpful for search, it should be a content page.

I just read it now, so that would be a new change/task :) Florianschmidtwelzow (talk) 20:21, 6 January 2015 (UTC)

Tracked in T86391 Florianschmidtwelzow (talk) 01:30, 10 January 2015 (UTC)

Done by Reedy :) Florianschmidtwelzow (talk) 21:34, 13 January 2015 (UTC)

I'm not sure if it is related to this change, but why are content pages no longer included in the default search? For a couple of weeks now I think, API: and Skin: are the only namespaces to be searched by default. To search "(Main)", "Help", "Manual", "Extension", you have to click "Content namespaces" (or check the appropriate checkboxes) after the default search has run. Cavila (MW 1.22, MySQL 5.5.37-0, Php 5.4.4-14 squeeze, SMW 1.9.2, SF 2.7) 07:38, 4 April 2015 (UTC)

I've tried by using private browsing and the default search is for (main), help, manual, extension, API and skin Ciencia Al Poder (talk) 19:40, 7 April 2015 (UTC)

OK, things are fine once I've logged out, but the same issue occurs again when I log in to the website, as if the default search behaviour is meant to be different for logged-in users. (FWIW, your message doesn't turn up in my "New messages" list either.) Cavila (MW 1.22, MySQL 5.5.37-0, Php 5.4.4-14 squeeze, SMW 1.9.2, SF 2.7) 20:42, 7 April 2015 (UTC)

The search preferences are saved if you mark the bottom checkbox of the advanced search. Maybe you marked it once and MediaWiki is just remembering it? Ciencia Al Poder (talk) 09:10, 8 April 2015 (UTC)

Thanks for that suggestion. Even if they're unlikely to be settings I ever saved myself (maybe an unforeseen side-effect of the recent change?), you're surely pointing in the right direction for a fix. I just saved my preferred settings in the advanced tab and it does what it says on the tin. Cavila (MW 1.22, MySQL 5.5.37-0, Php 5.4.4-14 squeeze, SMW 1.9.2, SF 2.7) 12:12, 8 April 2015 (UTC)

Special:Translate not working

Starting from yesterday morning, I cannot use the Special:Translate. When I clicked the strings, nothing happens. This only occured if I'm logged in.

Here's the error found in the browser console: <pre style="overflow:auto">TypeError: mw.config.get(...) is null" TypeError: mw.config.get(...) is null Pelacakan susunan: util.getUrl@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=id&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150107T194503Z line 4 > eval:9:119 VeInitMwTarget@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=id&modules=Base64.js%7Ceasy-deflate.core%2Cdeflate%7Cext.visualEditor.base%2Ccore%2Cmediawiki%2CviewPageTarget%7Cext.visualEditor.core.desktop%7Cjquery.visibleText%7Cmediawiki.api.edit%7Cmediawiki.feedback%2Ctemplate%7Coojs%2Coojs-ui%2Cpapaparse%2Crangefix%2Cunicodejs%7Coojs-ui.styles&skin=vector&version=20150107T194504Z&*:641:594 VeInitMwViewPageTarget@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=id&modules=Base64.js%7Ceasy-deflate.core%2Cdeflate%7Cext.visualEditor.base%2Ccore%2Cmediawiki%2CviewPageTarget%7Cext.visualEditor.core.desktop%7Cjquery.visibleText%7Cmediawiki.api.edit%7Cmediawiki.feedback%2Ctemplate%7Coojs%2Coojs-ui%2Cpapaparse%2Crangefix%2Cunicodejs%7Coojs-ui.styles&skin=vector&version=20150107T194504Z&*:671:643 getTarget/targetPromise<@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=id&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150107T194503Z line 4 > eval:53:1245 .Deferred/promise.then/</</<@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=id&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150107T194503Z:47:126 jQuery.Callbacks/fire@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=id&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150107T194503Z:45:106 jQuery.Callbacks/self.fireWith@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=id&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150107T194503Z:46:431 .Deferred/</deferred[tuple[0]]@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=id&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150107T194503Z:47:765 handlePending@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=id&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150107T194503Z:159:424 runScript@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=id&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150107T194503Z:161:140 execute/</checkCssHandles@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=id&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150107T194503Z:161:613 execute/</cssHandle/<@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=id&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150107T194503Z:161:743 jQuery.Callbacks/fire@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=id&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150107T194503Z:45:106 jQuery.Callbacks/self.fireWith@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=id&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150107T194503Z:46:431 jQuery.Callbacks/self.fire@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=id&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150107T194503Z:46:474 addEmbeddedCSS@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=id&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150107T194503Z:156:502 addEmbeddedCSS/<@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=id&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150107T194503Z:155:963 load.php:150

<pre style="overflow:auto">Uncaught TypeError: Cannot read property 'replace' of null load.php?debug=false&lang=id&modules=ext.centralNotice.bannerChoiceData%2CbannerController|ext.cent…:386 util.getUrlload.php?debug=false&lang=id&modules=ext.centralNotice.bannerChoiceData%2CbannerController|ext.cent…:42 TranslateEditor.prepareEditorColumnload.php?debug=false&lang=id&modules=ext.centralNotice.bannerChoiceData%2CbannerController|ext.cent…:31 TranslateEditor.renderload.php?debug=false&lang=id&modules=ext.centralNotice.bannerChoiceData%2CbannerController|ext.cent…:31 TranslateEditor.initload.php?debug=false&lang=id&modules=ext.centralNotice.bannerChoiceData%2CbannerController|ext.cent…:48 TranslateEditor.showload.php?debug=false&lang=id&modules=ext.centralNotice.bannerChoiceData%2CbannerController|ext.cent…:68 (anonymous function)load.php?debug=false&lang=id&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150107T1…:65 jQuery.event.dispatchload.php?debug=false&lang=id&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150107T1…:60 elemData.handle

Anyone having this problem too? William Surya Permana (talk) 12:07, 9 January 2015 (UTC)

Yes, but not everyone. Thanks for reporting. Nemo 17:45, 9 January 2015 (UTC)

Failed to mark for translation

Failed to mark Help:Magic words for translation:

Function: MessageGroupStats::clearGroup
Error: 1205 Lock wait timeout exceeded; try restarting transaction (10.64.16.27)

Too many translation units? Shirayuki (talk) 07:24, 25 January 2015 (UTC)

Still happening... please file a bug, hopefully the WMF DB admin will help. Nemo 15:01, 26 January 2015 (UTC)

This is probably https://phabricator.wikimedia.org/T53410 Nikerabbit (talk) 16:32, 1 February 2015 (UTC)

Shirayuki, good news: Nikerabbit has fixed the bug (hopefully). Let's remember to test and mark the page for translation... in few minutes? or perhaps next week. Nemo 21:55, 11 February 2015 (UTC)

> in few minutes? or perhaps next week.

The change isn't in wmf17, unfortunately, so you have to wait until wmf18 or backport the change :) Florianschmidtwelzow (talk) 08:33, 12 February 2015 (UTC)

The bug wasn't fixed yet. :( Nemo 07:55, 21 February 2015 (UTC)

Can someone search if a bug was filed? I saw something somewhere about clearGroup, but I can't find a thing in Phabricator. Nemo 13:58, 23 February 2015 (UTC)

Nothing that I can find. Please a file a bug about marking page for translation failing with this error. Nikerabbit (talk) 17:01, 23 February 2015 (UTC)

Error upload Files in MediaWiki

Hi,

As you try to run an upload from MediaWiki: http: //hostname/mediawiki/index.php? Title = Special% 3AUpload

We get this error and the file is not loaded:

The file you uploaded seems to be empty. This might be due to a type in the filename. Please check whether you really want to upload this file.

Doing a bit 'of research, I found the link where it would seem that they solved:

http://www.mediawiki.org/wiki/Project%3ASupport%20desk/Flow/2012/04#h-%5BFixed%5D_The_file_you_uploaded_seems_to_be_empty_-_Windows_Server_2008_R2-2012-04-14T16%3A25%3A00.000Z

Anyone can suggested how to resolve this problem? 170.252.72.61 16:46, 4 February 2015 (UTC)

See Manual:Errors and symptoms#All uploads fail with the message "The file you uploaded seems to be empty..." Ciencia Al Poder (talk) 21:13, 4 February 2015 (UTC)

Fwd: Allow sysops to self-grant translation administrator

Proposed by Florian, MZMcBride, Glaisher and devunt at phabricator:T87797. Nemo 08:23, 11 February 2015 (UTC)

MediaWiki:Noarticletext/zh-tw

（很抱歉，我不會英語。）
translatewiki那邊早已修正錯誤了，為何這裡還沒有更新？請把搜索改成搜尋，謝謝！ -- By LNDDYL. (Talk) 08:52, 20 February 2015 (UTC)

The user claims that translatewiki was changed (in November of 2014) but the change hasn't been reflected here. Ciencia Al Poder (talk) 10:39, 20 February 2015 (UTC)

phab:T85790? Nemo 07:46, 21 February 2015 (UTC)

Change a red link

This post by Nemo bis was moved on 2015-02-21. You can find it at Project:Support desk/Flow/2015/02#c-Arystanbek-2015-02-20T20:20:00.000Z-Change_a_red_link. Nemo 07:47, 21 February 2015 (UTC)

[RESOLVED] API-head

Could Template:API-head be marked for translation please? (pinging user:Steinsplitter who so often helps me on these matters) John Vandenberg (talk) 23:40, 21 February 2015 (UTC)

It has been done. John Vandenberg (talk) 02:03, 22 February 2015 (UTC)

"Now with mustache" logo

MediaWiki:Extdist-created-extensions/zh-hant

這個頁面應該是繁體中文(Chinese Traditional, zh-hant)文字，為何變成了簡體中文(Chinese Simplified, zh-hans)文字？translatewiki:MediaWiki:Extdist-created-extensions/zh-hant

And MediaWiki:Extdist-choose-extensions/zh-hant (translatewiki:MediaWiki:Extdist-choose-extensions/zh-hant).

translatewiki was changed but the change hasn't been reflected on the Mediawiki.org. -- By LNDDYL. (Talk) 06:50, 1 March 2015 (UTC)

error in update with by web browser in MediaWiki Language Extension Bundle

This post by Ciencia Al Poder was moved on 2015-03-01. You can find it at Project:Support_desk/Flow/2015/02#[RESOLVED]_error_in_update_with_by_web_browser_in_MediaWiki_Language_Extension_Bundle. Ciencia Al Poder (talk) 16:52, 1 March 2015 (UTC)

Design of MW pages broken?

Extension:GraphViz The design of the page looks broken. Funny thing is that has been no edit recently.

• Firefox (35.0.1): completely broken
• Chrome (Version 40.0.2214.115 m): same as Firefox
• Internet Exporer: looks awful, especially the top part. Temptuousinsolence (talk) 08:52, 6 March 2015 (UTC)

Thanks for reporting this! Seems to be related to recent edits to Template:WikimediaDownload (which is used on that page) to make it translatable. I've dropped a message on the author's talk page as I have no idea what went wrong here exactly... :( AKlapper (WMF) (talk) 10:48, 6 March 2015 (UTC)

Has been fixed. Temptuousinsolence (talk) 12:28, 6 March 2015 (UTC)

[RESOLVED] Mass vandalism by User:Prianka

This user has used a bot to remove content from pages. Please revert their edits. 121.220.99.147 00:27, 17 March 2015 (UTC)

Done. I have blocked the user and reverted their edits. Thanks. Shirayuki (talk) 03:13, 17 March 2015 (UTC)

Proposal to convert LiquidThreads discussions to Flow

Workflow for OAuth clients

Some time ago I proposed this client. Unfortunately it never got approved and is now listed as "expired", but I'm still interested in it. What am I supposed to do? Ricordisamoa 23:03, 21 March 2015 (UTC)

Vague ideas, maybe ask one of the OAuth admins what's next after "expired". If you figured it out please add it on the Extension:OAuth page, and/or start a thread on Extension talk:OAuth, and/or tackle the odd m:Meta:OAuth administrators stub.

More to the point, some kind of "identification game" sounds like "bring as many privacy lawyers as the EU has members for an initial informal discussion how to get global community consensus". Be..anyone (talk) 17:55, 22 March 2015 (UTC)

Link to list open tasks from the extension's page displays both open and closed tasks

The link to list open tasks from the extension's page, displays both open and closed tasks. See for example Extension:UserMerge, which links to .

That's because now in phabricator, the project page goes to the workboard (see T89865).

Is there any other viable URL that we could use to link to all open tasks of a project? All searches give ugly URLs without a project name on them, just numeric codes or similar. Ciencia Al Poder (talk) 18:39, 27 March 2015 (UTC)

https://phabricator.wikimedia.org/maniphest/?statuses=open&projects=MediaWiki-extensions-UserMerge FriedhelmW (talk) 12:12, 28 March 2015 (UTC)

That doesn't work. It lists open tasks, but doesn't filter for that extension. Ciencia Al Poder (talk) 10:51, 29 March 2015 (UTC)

I think there is no such feature any longer: the only option would be the advanced maniphest search, but the projects selectors don't accept strings, only PHID* variables.

Maybe there is a way to get all the PHID numbers or the project description URLs for all projects, we could then store them in a switch. Nemo 13:01, 29 March 2015 (UTC)

As Nemo says. If you want to get a PHID of a project (e.g. Flow): Go to https://phabricator.wikimedia.org/conduit/method/project.query/ , enter ["Flow"] in names, get PHID-PROJ-ntg6sf6mfl2qm2e4qgxc. AKlapper (WMF) (talk) 10:13, 1 April 2015 (UTC)

The workboard view is not the problem itself. Showing also closed tasks by default is the problem and will get fixed by the next update: phab:T90661. AKlapper (WMF) (talk) 10:12, 1 April 2015 (UTC)

The current situation has become even worse. Now those links lead to a 404 ERROR page! Ciencia Al Poder (talk) 09:20, 12 May 2015 (UTC)

I've just discovered that to make those URLs to work, the tag name must be lowercase (!)

I've edited {{Extension }} and {{Ptag }} accordingly, which should fix those links. Still, the links go to the workboard instead of the project page. Ciencia Al Poder (talk) 09:28, 12 May 2015 (UTC)

LOG in

Please assist - I am unable to access/log into my account:

https://www.mediawiki.org/w/index.php?title=Special%3ACentralAuth&target=TimiOribunmi 86.154.133.104 14:57, 31 March 2015 (UTC)

Why?

(Or in a longer version: If you don't provide steps to perform, error messages shown, browser information, there's not much anyone can do :) Malyacko (talk) 09:55, 1 April 2015 (UTC)

No "Search" option?!

How come there's no search feature in the archives @ Project:Support desk?! (or here at Project:Current issues, for that matter)

You can watch such a thingy in action at WikiPedia. IMO, this is very useful, and i quite miss it here on MediaWiki.

Later edit: I guess this might be related with the new "LQT"/"Flow" design. Choosing eye-candy vs functionality, very well done. :-| Jokes_Free4Me (talk) 11:33, 3 April 2015 (UTC)

This is bugzilla:20004.

Actually, some research option is available, but doesn't check where the thread is currently located. Nemo 19:25, 3 April 2015 (UTC)

Text missing but data available via edit function and database

This post by Ciencia Al Poder was moved on 2015-04-05. You can find it at Project:Support desk/Flow/2015/04#c-192.184.57.170-2015-04-04T16:12:00.000Z-Text_missing_but_data_available_via_edit_function_and_database. Ciencia Al Poder (talk) 18:48, 5 April 2015 (UTC)

Error on website

Hi when visiting https://tools.wmflabs.org/extreg-wos/ it brings up a error saying tool does not exist but it was only working a few days ago. 151.229.250.233 23:50, 10 April 2015 (UTC)

The page says that Legoktm is the maintainer, plus this does not look MediaWiki related so Project:Current issues might be a more appropriate place to bring this up. AKlapper (WMF) (talk) 09:23, 13 April 2015 (UTC)

You should ask the maintainer (@Legoktm: ), if he can fix the problem :) I'll move this to Project:Current_issues for now :) Florianschmidtwelzow (talk) 10:15, 13 April 2015 (UTC)

Topic talk:Sewfq489tp3iic43

Hi, I've no idea what Topic talk:Sewfq489tp3iic43 is, either a weird name in the main name space, or a weird talk page for a namespace not needing any talk pages at all, but it's definitely unrelated to Talk:Phabricator/Help/2015#h-Cannot_*create*_an_account?-2015-04-05T20:17:00.000Z, please move it without leaving a redirect. Be..anyone (talk) 03:16, 11 April 2015 (UTC)

Move to what place? You're the author of the talk page: Is it really needed, or maybe it can be deleted? How you created these talk page? :/ Florianschmidtwelzow (talk) 10:14, 13 April 2015 (UTC)

It's an experiment, I tried to figure out why an existing Talk:Phabricator/Help/2015#h-Cannot_*create*_an_account?-2015-04-05T20:17:00.000Z contains a red link to itself, and is actually always shown as red link. Additional test:

Apparently there is no "Topic talk", the experiment ended up as article. JFTR this bogus article could be moved to Thread_talk:Project:Current_issues/Topic_talk:Sewfq489tp3iic43, as entertainment for the folks migrating Liquid threads to Flow, apparently namespace 91 is empty at the moment. But the red Talk:Phabricator/Help/2015#h-Cannot_*create*_an_account?-2015-04-05T20:17:00.000Z is really wrong, it exists. Be..anyone (talk) 15:10, 13 April 2015 (UTC)

Done Florianschmidtwelzow (talk) 11:21, 15 April 2015 (UTC)

Manual thanks, I miss the tnx-button whenever it doesn't show up—IPs, bots, liquid threads, …  Be..anyone (talk) 23:47, 16 April 2015 (UTC)

np :) Yeah, Flow would be better, just because you can thank another user for a post :D Florianschmidtwelzow (talk) 13:17, 17 April 2015 (UTC)

Some translation that won't save for the how to contribute page

Hi, I updated a translation, but it won't save because of a cascade protection. I put my new version here : Translations_talk:How_to_contribute/26/fr It's the relevant discussion page.

I put that here then. TomT0m (talk) 09:12, 12 April 2015 (UTC)

The difference was apparently only "Le code est open source, libre et gratuit." I added it, clicked on save, and it was saved. Maybe the cascading protection or whatever it was is gone. Be..anyone (talk) 06:21, 13 April 2015 (UTC)

Cannot start a new discussion in support desk

I've been trying to start a new discussion in the support desk but when I click on 'Save Page', my browser keeps reloading the Support desk page in editing mode with my post still inside the editor and not yet posted in the discussion.

(and apparently I can post here without a problem)

Using OS X Yosemite10.10.2. Tried Google Chrome 41.0.2272.118, and Safari 8.0.4. Genesishana (talk) 11:28, 14 April 2015 (UTC)

It's completely broken script hell, Chrome never knows what the URL is, what the state is (crying "don't leave unsaved page" long after it was saved), wild guess, was your attempt over a slow/shaky connection? Maybe test a Project:Support desk/Flow/2015/04#c-Be..anyone-2015-04-14T11:55:00.000Z-Be..anyone-2015-04-14T11:53:00.000Z to figure out what's wrong. Be..anyone (talk) 12:04, 14 April 2015 (UTC)

It wasn't over a slow or unstable connection. It seemed to be related to the inclusion of external URLs, you can see my various experiments in the edit history found in Project:Support desk/Flow/2015/04#c-Be..anyone-2015-04-14T11:55:00.000Z-Be..anyone-2015-04-14T11:53:00.000Z

I was able to modify my original MediaWiki issue by eliminating the http:// part of the URL to my wiki and I was able to post successfully.

But yes, totally broken script. I've been getting those "don't leave unsaved page" prompts more often now. Genesishana (talk) 14:44, 14 April 2015 (UTC)

git.wikimedia.org down

error: rendering process died with non zero code: 1

dearest,

Has anyone had seen this error before while converting/rendering

an assembled book in to pdf ?

Tim Tim.claessens (talk) 07:17, 15 April 2015 (UTC)

Yes, it's rather common. It can have several reasons, so it's best if you mention the specific page which is giving you the error. Nemo 07:18, 15 April 2015 (UTC)

I have tried at least ten times and it is giving same message.

Page address: Book: Optical illusions - Wikipedia, the free encyclopedia Tejasvi Singh Tomar (talk) 10:49, 14 May 2015 (UTC)

That's covered in phab:T94308 AKlapper (WMF) (talk) 13:15, 25 May 2015 (UTC)

Special:SupportedLanguages restored

Nikerabbit just put an end to the painful wait! Now the special page works again; you have to open a specific subpage to see usernames. Example: Special:SupportedLanguages/it. Nemo 15:14, 23 April 2015 (UTC)

Great ! Kiitos Nikerabbit :) ~ Seb35 [^_^] 10:06, 26 April 2015 (UTC)

Cannot edit talk pages

Something claiming to be an "IPA phonetic alphabet" popup intercepts my keyboard input (skin Monobook, browser Chrome, visual editor off, template data on, no other tricks). It also happens here, I cannot add the colons required for indentation, it appears as some gibberish. I cannot add < (more gibberish). Be..anyone (talk) 11:20, 4 May 2015 (UTC)

This is the stupid Universal Language Selector IME, the little keyboard icon that appears next to the textarea (when the textarea is focused), that has a shortcut-key for switching keyboards.

Click on that keyboard and change the input method to native. Ciencia Al Poder (talk) 01:56, 5 May 2015 (UTC)

Thanks, presumably I somehow managed to input a key combination switching it in an undesired position, and surviving a "restart browser" in that position. I certainly didn't open it, until I figured out that this helps to reset "native keyboard". Is there a way to get rid of it completely? I can barely guess what IPA tries to express in very simple cases, I'll never need to input it. Be..anyone (talk) 06:46, 5 May 2015 (UTC)

Pressing Ctrl+M toggles on/off. FriedhelmW (talk) 17:29, 5 May 2015 (UTC)

Thanks, I think I found a more permanent solution on Disabling the tool for your user account hopefully good for all browsers and all Wikimedia projects:

• Skip the "from the sidebar" blurb (I failed to grok it, maybe it is for Vector)
• Interpret "from the Keyboard menu" as…
  • click edit on any page that can be edited
  • click on the input method icon directly below the input area at the end of the row (right side for LTR)
  • click on the last entry in the popup with a tool icon
  • click disable IME everywhere, click on apply, ready.

No idea how I ended up to opt-in to this feature, presumably I was curious as always and forgot it. Be..anyone (talk) 08:59, 7 May 2015 (UTC)

Problem in html2wiki

This post by Ciencia Al Poder was moved on 2015-05-08. You can find it at Project:Support_desk/Flow/2015/05#Problem_in_html2wiki. Ciencia Al Poder (talk) 01:45, 8 May 2015 (UTC)

Delete user page on MediaWiki

i can't install mediawiki on my webserver please help me

This post by Ciencia Al Poder was moved on 2015-05-20. You can find it at Project:Support desk/Flow/2015/05#c-Borahola-2015-05-20T03:54:00.000Z-i_can't_install_mediawiki_on_my_webserver_please_help_me. Ciencia Al Poder (talk) 09:25, 20 May 2015 (UTC)

Gitblit replication of gerrit has stopped.

Hi please see https://phabricator.wikimedia.org/T99990 about gitblit replication of gerrit not working. Please fix it. 86.135.252.201 00:42, 24 May 2015 (UTC)

Long term support release #2

There it is again. Since the release of the 1.25.0-version the 1.24.2-version is marked as LTS version again on the download page. This has happend already in September 2014 when 1.24.0 was launched. Someone stated, that 1.27.0 is going to become a LTS version and not 1.24.0. (https://www.mediawiki.org/wiki/Project%3ASupport%20desk/Flow/2014/11#h-%5BRESOLVED%5D_Long_term_support_release-2014-11-28T12%3A29%3A00.000Z). Wgkderdicke (talk) 19:04, 25 May 2015 (UTC)

I've edited Template:DownloadMediaWiki to fix that. I hope it's now correct. Someone needs to mark that version for translation, though Ciencia Al Poder (talk) 19:37, 25 May 2015 (UTC)

Done Marked for translation. Florianschmidtwelzow (talk) 05:28, 26 May 2015 (UTC)

Where to discuss broaders template issues? A Phabricator tag ?

Note phab:T101362 A #Templates tag for tasks related with creating/fixing MediaWiki templates?

When I'm making changes to templates in API docs, or deciding how to move source code links from git.wikimedia.org to diffusion, I'm not sure how to broaden the discussion beyond a particular template's talk page. Is this a good forum for it? Would a phabricator task help or make it worse?

(I'm a technical writer at the WMF, hi!) SPage (WMF) (talk) 20:01, 5 June 2015 (UTC)

A forum on the wiki where those templates are would be a good option, since it's a change that affects the wiki. For me, raising such issues here (Project:Current issues) would be fine. But that's just my personal opinion :) Ciencia Al Poder (talk) 11:12, 6 June 2015 (UTC)

MobileFrontend and Mantle problem

This post by Ciencia Al Poder was moved on 2015-06-11. You can find it at Project:Support desk/Flow/2015/06#c-2601:8:B300:23C:79B6:F52C:189F:543A-2015-06-11T05:04:00.000Z-MobileFrontend_and_Mantle_problem. Ciencia Al Poder (talk) 09:47, 11 June 2015 (UTC)

Collection 1_25 download link not working

This link does not work. The file is missing from that location. Other extensions at the same location have a version 1_25, but Collection 1_25 does not.

https://extdist.wmflabs.org/dist/extensions/Collection-REL1_25-d898236.tar.gz 199.133.194.84 21:26, 12 June 2015 (UTC)

I just checked the link and it now works. 199.133.194.109 15:44, 24 June 2015 (UTC)

Adding a dev namespace for "Data and developer hub" articles

(Please read dev.wikimedia.org for some background on this project.) The articles for the new API:Data and developer hub are currently in the API: namespace. I would like the pages to be in a new dev: namespace. Here's why:

• They will render by default using a different skin, "Blueprint" (see it on Template:Devhub). The easiest way to show articles with a different skin is using Extension:SkinPerNamespace.
• I want to use Flow on all the talk pages of these articles. The easiest way for this to happen is by setting $wgFlowOccupyNamespaces to this dev namespace.
• It's mildly useful to be able to search only these pages.
• The existing namespaces don't fit articles "to encourage third-party developers to use our data and APIs".

  Manual

  Different audience: "a technical manual for the MediaWiki software. It contains information for developers and system administrators on installing, managing and developing for the MediaWiki software."

  API

  Close, and it's what I'm using for articles to start, but an article like API:Recent changes stream is not about the MediaWiki API.

  Main (default) namespace

  proliferation of articles, hard to search.

Note the motivation to use a different skin and an easier discussion system (Flow) is that the Data and developer hub focuses on third-party developers who are not MediaWiki hackers or wiki editors. (Of course we hope some will align with our cause and contribute to our projects.)

None of these are definitive, but they lean towards creating a dedicated dev: namespace. I'm interested in technical alternatives for the first (e.g. use Extension:SkinPerPage instead, or use SkinPerCategory logic to set a different default skin). You can comment here or in phab:T369. SPage (WMF) (talk) 02:35, 25 June 2015 (UTC)

I agree, seems the best option. Ciencia Al Poder (talk) 09:23, 25 June 2015 (UTC)

If this is for documentation/discussion relating to the API, then why not stick with 'API' as the namespace? I think 'dev' is going to be a very confusing name, as the vast majority of this wiki (across all namespaces) could come under the category 'development'. Or 'developer'. Or whatever 'dev' stands for. And what would happen to the existing content in the API namespace?

Also, I am not sure what the purpose of an alternative skin is. Isn't that confusing, to have different parts of the site look completely different? If I'm browsing the site in Monobook, say, and then click a link to this new namespace, then I would assume I was on a different site. Doesn't seem very user-friendly to me. HappyDog (talk) 10:03, 25 June 2015 (UTC)

Yes, I don't know why change the skin. That would be rather unexpected and shocking to a user from mediawiki.org that reaches one of those pages from RecentChanges or a link from another page. Ciencia Al Poder (talk) 14:56, 26 June 2015 (UTC)

The dicussion about the namespace is still open and we can evaluate the implications of using "API" instead of "Dev".

About the different skin, the starting point was to create an own site with own look&feel, following the example of most API/developer sites versus their products. The intention was to avoid Vector's outdated look & feel and mediawiki.org's fully charged sidebar wiith links that could be definitely confusing to third party developers not interested in MediaWiki itself or in contributing patches.

While I was among the very determined advocates of improving mediawiki.org instead of creating a separate site, I agree with the original problem. While using "a different skin in a same site" might confuse to some, I think the confusion and loss will be higher and more expensive if we stick to the current mediawiki.org interface.

In fact, I think this exercise might be useful to sanitize and improve mediawiki.org's UI. For us regular users it is easy to become blind to the problems it has, but this project is all about reaching out to new developers and engage them in the use of our APIs (which can lead to other type of contributions over time). Qgil-WMF (talk) 13:48, 27 June 2015 (UTC)

Here's how I think this should work:

• Use the existing API namespace for this.
  1. The name is clear and unambiguous, unlike 'dev'
  2. A new namespace leaves the question about what to do with existing API pages - move them (in which case the API namespace will end up empty, aside from redirects) or leave them (in which case we will end up with pairs of similar articles in different namespaces). Neither of these seem like a good outcome.
• Create an appropriate hub page (if it doesn't already exist) which is the focal point for this new sub-site.
• Use this as an opportunity to improve the content of that namespace as well as adding whatever other API-consumer-related documentation is appropriate. I am comfortable for the API documentation to be written with a focus on third-party use, rather than an MW developer focus.
• If there are pages in the API namespace that are not appropriate to be there, then they can be moved.
• I can sort of see why you want a separate skin, but I don't really agree with it, and I'm not sure how well it would work in practice. Unless you plan to ban internal links to other namespaces (including links to user pages), there will be plenty of places where users will 'break out' of the skin, which will be confusing for the third-party users, as much as it will be for the MW regulars who suddenly find their skin changing as they navigate the site. Perhaps a useful compromise would be to use the separate skin for anonymous (non-logged-in) visitors only. Would that work? HappyDog (talk) 14:54, 27 June 2015 (UTC)

I've just been having a play with the proposed skin, and to be honest it leaves me a bit lost.

• I couldn't find any way to get to a discussion page.
• I eventually managed to find the edit/view history links, which are hidden away. Not sure I like the fact that editing/involvement is being discouraged in this way.
• A lot of the features I am used to (edit section, add to watchlist, save as PDF, etc.) I couldn't find at all - I assume they have simply been removed to make things 'cleaner'.

Having had a play with the skin, my feeling is that there is possibly a third approach, which might satisfy the two different camps (the people who basically want a static website that is easy to use and navigate, aimed at third-party consumers of the API vs. the people who want editable online documentation, and for it all to be in one place).

My revised suggestion is the same as what I wrote in my previous post, except that the whole skin business is abandoned - the pages are part of mediawiki.org, and remain in the site skin in the same manner as all other pages on the site. Then, in addition to this, a separate site is set up, using a variant of the new skin, which pulls it data from the API namespace of MediaWiki and presents it in a static format that is very friendly to third-party consumers. The new skin would be broadly like the prototype, with a couple of changes:

• There is no functionality related to editing, logging in, etc. except insomuch as is appropriate in relation to the next point
• There is a clear notice (possibly as part of the header, or possibly as part of the slide-out menu) saying this content comes from mediawiki.org - "to edit, discuss or otherwise contribute to it click here".

Obviously, there are details to be worked-out, but what do you think of this approach? HappyDog (talk) 15:12, 27 June 2015 (UTC)

I'm not convinced (at all) about the idea of a separate site that will bring extra work and extra maintenance. Still, do you have any idea of how this would work and how much effort should be put to build it? My instinct says that I'd rather put that effort improving Blueprint skin. Qgil-WMF (talk) 17:07, 27 June 2015 (UTC)

Well, in theory there should be no maintenance required. It is effectively a read-only window into a section of mediawiki.org, and therefore once set-up it should just tick along.

I would imagine that it runs either directly off the live MediaWiki.org database or a live-replicated slave, or hooks in via the API (which would be quite apt). Either way, it is effectively a read-only mirror of a portion of mediawiki.org, skinned to be user-friendly to a subset of users who want a read-only documentation site. There will be links to edit or discuss the content (which can be as prominent, or not, as you feel is appropriate) but they link to the MediaWiki site with the standard skin.

I have no idea how much work this is. In theory, it should be fairly trivial (the hard work is in implementing the skin, which seems to be broadly done), but I don't know enough about WMF infrastructure to know how hard it is in practice. HappyDog (talk) 18:57, 27 June 2015 (UTC)

The MusicBrainz project uses basically this system for their documentation. https://musicbrainz.org/doc/Main_Page is a read-only mirror of their wiki, using the normal MusicBrainz UI instead of their modified MonoBook. Legoktm (talk) 07:31, 8 July 2015 (UTC)

This is the page explaining how they do it (although I still don't quite see how to replicate it): https://musicbrainz.org/doc/WikiDocs Qgil-WMF (talk) 09:42, 8 July 2015 (UTC)

I chatted with devs on #musicbrainz-devel ^connect.

• musicbrainz.org is a custom web server;
• admins maintain a list of wiki page revisions to transclude to it;
• a Perl module requests the HTML of those wiki pages with ?action=render, cleans up links, and stores the HTML in their server. SPage (WMF) (talk) 23:32, 8 July 2015 (UTC)

Hi HappyDog, thanks for engaging with us about this.

• a separate site is set up, using a variant of the new skin, which pulls it data from the API namespace of MediaWiki and presents it in a static format that is very friendly to third-party consumers
  That sounds like http://devhub.wikimedia.org! It's read-only and limited functionality, and I Special:Import mw.org content to it. The idea of configuring a separate site in production so that a single set of content can live a second lifestyle at a different host is intriguing and might have wider applicability for special sites like Wikimania, annual reports, etc., but I have no idea what the engineering challenges are. Maybe it's been done, before my time. :)
• I don't think it's a problem for new developers to encounter different skins. They'll already switch skins when they follow a link to doc.wikimedia.org or out of the API (or dev) namespace.
• We could develop logic to not show existing mediawiki.org users the Blueprint skin. Obviously "if user's skin is not default, then no Blueprint", maybe "if user is logged in, then no Blueprint" (this sounds like SkinPerNamespace's $wgSkinPerNamespaceOverrideLoggedIn = false), maybe a hidden preference or session variable to identify new visitors, or a definitive "Never screw with my skin choice!!" preference. But it's complex logic that will never catch all circumstances (e.g. long-time user browsing MediaWiki anonymously). I don't think it's the end of the world if a long-time MediaWiki user is exposed to a new skin on a few dozen pages targeted to a different audience.
• Perhaps SkinPerNamespace is the wrong idea. I would like to see the OOUI living style guide http://living-style-guide.wmflabs.org moved to mediawiki.org (phab:T93610) for similar reasons, but then we would want two different Blueprint sidebars, so two different namespaces, ... it doesn't scale. I will investigate extension:SkinPerPage and explore an explicit <skin sidebar="ooui-lsg">Blueprint</skin> in pages. SPage (WMF) (talk) 04:43, 2 July 2015 (UTC)

I can see the benefits and consistency of using the API: namespace as you propose, combined with api.wikimedia.org and a central focus on web API documentation. The more precise but also narrower "API" meme leaves aside datasets, websockets, and what not, but as you say we could always highlight related technologies in the main page and wherever it is appropriate. It's not that the "Dev" meme doesn't bring its own inconveniences, so we will need to evaluate both.

About the skin, I would like to ask for a chance to try it, with a plan for a quick revert if needed. The risk of user confusion is theoretical. Users deal with changes of UI by clicking links all the time. They might be confused or satisfied depending on many factors. The deployment of this extension in mediawiki.org as an optional skin has its own benefits, and would get us more feedback from users willing to give it a try.

Blueprint skin has some virtues and some problems. The possibility of being deployed in a production server contributes to highlight the serious problems and work on them. The lack of Discussion link is a known bug that I just set as blocker of the deployment of this extension in mediawiki.org. If we (and that includes you) find more blockers, we will add them. Just find/create specific Phabricator tasks to discuss them. Qgil-WMF (talk) 17:05, 27 June 2015 (UTC)

I have no objection to the new skin being enabled as an optional skin on mediawiki.org, for those who want to try it out.

I think there would be a lot of objections (from me and many others) if it were made the default skin, even if only for anons and/or new users.

I don't know what other people think about it being the default skin for a single namespace, but I've already made my feelings known on this.

For me, the biggest risk of confusion is the skin changing randomly as you navigate within the site. As you say, confusion within the skin itself is something that can (hopefully) be resolved by further user-testing and development. You also need to balance the ease of use for new users against the disorientation and confusion for existing users, but in most cases this can be mitigated by the fact that users can pick their own skin. HappyDog (talk) 19:02, 27 June 2015 (UTC)

As commented here, it might make sense to have separate discussions to simplify this complex discussion:

1. Literally Deploy Blueprint on mediawiki.org as optional and experimental skin, which is useful to find technical blockers before the deployment and more testers after the deployment.
2. Implement a namespace in mediawiki.org to host the developer hub, leaving aside the skin discussion, focusing on which namespace (renovating Api:, creating Dev:, or else).
3. IF Blueprint is heading to mediawiki.org AND the namespace plan is clear, THEN discuss the combination of skin and namespace. Qgil-WMF (talk) 09:30, 3 July 2015 (UTC)

• I don't like the name "dev" for the namespace. I don't have any better suggestions, but dev is super confusing.
• I think this could maybe conceivably fit in the API namespace, but a separate namespace also sounds fine to me provided there is some clear criteria what does and does not belong there.
• I'm not really all that much of a fan of the Blueprint skin. More importantly I don't like the idea of half the site looking different.
  • I don't really understand the reasoning behind wanting a different skin. "Note the motivation to use a different skin and an easier discussion system (Flow) is that the Data and developer hub focuses on third-party developers who are not MediaWiki hackers or wiki editors" is not very convincing. How does having a different skin make it any easier for these users. Bawolff (talk) 10:01, 3 July 2015 (UTC)

API:Showing_nearby_wiki_information vs http://devhub.wmflabs.org/wiki/API:Showing_nearby_wiki_information might look basically equivalent to regular users of mediawiki.org because we are used to Vector skin and the dozens of extra links in the header and sidebar (to which we are effectively blind by now). However, for new users interested only in the Wikimedia API and landing directly in one of these pages... most of those 36 links (I counted) will contribute between noise and confusion, on top of the outdated look of Vector.

Considering that most mediawiki.org users don't land lightly in Api: namespace, and those who land there probably also land in doc.wikimedia.org (which has a completely different UI), I think that offering a good experience to these new developers is better than risking a bit of confusion to some mediawiki.org users. And I still claim that such confusion is more theoretical than practical, which is why I'm proposing to run a test with a big button to revert. Qgil-WMF (talk) 11:07, 3 July 2015 (UTC)

Is there research on whether/when navigational bars make it harder for users to find and see the actual content of a page? Probably http://nngroup.com/ has something. Nemo 12:19, 5 July 2015 (UTC)

There is no lack of web design articles about navigation bars concluding that less is more. Find and see is just the beginning. Focusing on the content and navigating to next destinations comes next. In this sense, mediawiki.org's sidebar offers no benefits and many distractions to our target audience of third-party developers.

The problem with our expanded sidebar with 29 links is not only that these links can be distracting and unrelated to the topic of the page. These links have a high potential of being confusing for these third-party developers, because they include labels that might appeal to them with different meanings i.e. "User help", "FAQ", "Technical manual", "Support desk", "Sandbox". Qgil-WMF (talk) 15:06, 6 July 2015 (UTC)

As proposed in my comment above, let's separate topics (the namespace, the Blueprint skin, and eventually the use of a specific skin fr the namespace decided).

Back to the initial post on "Adding a dev namespace for "Data and developer hub" articles". After all the feedback received, I think it is better to NOT create a Dev: namespace, and to improve the Api: namespace instead. This change comes together with a more focused scope and a different name for the project. We will stress the more precise "Api" aspect (web APIs) instead of the more vague "developer" aspect. These are details that can be discussed in the Phabricator project.

Once the namespace topic has been agreed, we will discuss the skin topic. Qgil-WMF (talk) 15:57, 6 July 2015 (UTC)

The problem there is that the "API" namespace is currently for the api.php action API. If you try to make it about APIs more generally (restbase, rcstream, etc) things might get a bit confusing on pages like API:Main page, API:Localisation, API:Calling internally, API:Client code, API:FAQ, and so on. Anomie (talk) 16:43, 6 July 2015 (UTC)

Yes, it is clear that we cannot just throw the new pages in Api: without considering the existing content. Still, the end result should be useful: all documentation about our web APIs in one place. Once we agree on the principle, S could plan carefully the next steps with the help of Anomie and other regular editors in that namespace. Qgil-WMF (talk) 07:45, 7 July 2015 (UTC)

While I welcome the focusing of scope around the better-defined "web APIs" designation, I think we must keep in mind that api.php is a mediawiki feature that all MW wikis will have access to, while other web APIs depend on WMF infrastructure and Wikimedia wikis' content. On the other hand, other MW features don't have their own namespace, so I guess it might work to transition the namespace to include other APIs. The problem remains of confusion between "the" MW API (api.php) and other APIs, but that's a transversal issue to the namespace discussion. If we make sure api.php documentation remains well organized and navigable, I suppose it could work. Waldir (talk) 22:30, 7 July 2015 (UTC)

I have created T105133 Organize current and new content in the API: namespace at mediawiki.org as a blocker of our quarterly goal. Qgil-WMF (talk) 10:23, 8 July 2015 (UTC)

I retract the proposal to add a 'dev:' namespace (for now).

The new articles are already in the 'API:' namespace, along with 150 pages in English plus translations.

The 'API:' namespace is mostly about the MediaWiki PHP API, but that's not carved in stone anywhere.

What makes the MW API somewhat navigable is {{API }} on most of those pages, which displays "[This page is part of the MediaWiki API documentation.]" along with "MediaWiki API" contents.

These articles don't have that template, nor would other potential pages about RESTBase API, or reusing content. SPage (WMF) (talk) 08:35, 8 July 2015 (UTC)

mediawiki最新版1.24.2在windows下无法上传带有中文的目录文件名

This post by Ciencia Al Poder was moved on 2015-06-30. You can find it at Project:Support desk/Flow/2015/06#c-ITliuhuan-2015-06-30T08:21:00.000Z-mediawiki最新版1.24.2在windows下无法上传带有中文的目录文件名. Ciencia Al Poder (talk) 15:28, 30 June 2015 (UTC)

Add user page speedy deletion reasons

Hi all, I inform you that I've started a discussion in order to add some additional speedy deletion reasons for user pages. Discussion is here: Project talk:Deletion#More speedy deletion reasons. Regards. Syum90 (talk) 07:10, 1 July 2015 (UTC)

Error on 'mwlib' server

This post by Ciencia Al Poder was moved on 2015-07-01. You can find it at Project:Support desk/Flow/2015/07#c-Ace.philscan-2015-07-01T10:21:00.000Z-Error_on_'mwlib'_server. Ciencia Al Poder (talk) 12:16, 1 July 2015 (UTC)

Add something to Wikilove?

Translating MediaWiki messages

RESOLVED

Done by Glaisher

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Hi! How could I translate MediaWiki messages? It is needed to create some pages in Ukrainian: MediaWiki talk:Mw-supportdesk/uk, MediaWiki talk:Mw-discussion/uk, A1 (talk) 07:30, 12 July 2015 (UTC)

Hi, I've created these pages with the translations you provided on the talk pages. As these interface messages are specific to MediaWiki.org, they have to be added by local sysops (unlike the normal MediaWiki interface messages which can be translated at translatewiki.net). Thanks. Glaisher (talk) 16:53, 13 July 2015 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Unprotect this Skin:Metrolook and Extension:CollapsibleVector page

Hi please unprotect this Skin:Metrolook and Extension:CollapsibleVector page. Since it was blocked because I was blocked but then I was unblocked and so there is no need to keep that page blocked. Paladox (talk) 15:24, 14 July 2015 (UTC)

Related:

https://www.mediawiki.org/w/index.php?title=Project:Support_desk&offset=20150714162410#x.5BRESOLVED.5D_Unprotect_this_.5B.5BSkin:Metrolook.5D.5D_and_.5B.5BExtension:CollapsibleVector.5D.5D_page_58613

Done Florianschmidtwelzow (talk) 08:07, 15 July 2015 (UTC)

LQT -> Flow conversion: empty and broken LQT Archive 01 pages (by design)

Congratulations on the conversion of LiquidThreads pages to Flow.

Flow boards link to the "archived LQT version". But often there's nothing in the archived LQT version. E.g. Skin talk:Metrolook shows

Previous page history was archived for backup purposes at Skin talk:Metrolook/LQT Archive 1 on 2015-06-25.

If you follow the link to its LQT Archive subpage, you notice there's nothing on the subpage except for the template identifying it as an LQT Archive.

Similarly, Manual talk:Interwiki/LQT Archive 1 has no content except two broken templates {{Archive box|[[/Archive 01]]}} and {{help talk}}.

This makes sense if you read the link more carefully: "page history was archived." The only content on most LQT pages was a magic word turning LQT on and perhaps some templates guiding user to archives and how to use the talk page; all the actual threads lived in the separate Thread namespace. So an LQT Archive subpage is of no interest except that its history records these edits and any page content before it was LQT-ized. I guess any irrelevant broken templates on LQT Archive subpages should be removed.

I think the language in the templates {{LQT page converted to Flow }} and {{Archive for converted LQT page }} could make this clearer. Also maybe "/LQT history" would be a better subpage name, note how this Project:Current issues has both "archives overview" (interesting, actual content) and "/LQT Archive 01" (boring). SPage (WMF) (talk) 02:06, 15 July 2015 (UTC)

LQT -> Flow conversion: stray lqt_method=talkpage_new_thread links

A few pages, including Project:Current issues/Archive and VisualEditor/Feedback, encourage people to "start a new discussion" or "post a comment" by linking to a page URL with lqt_method=talkpage_new_topic in the query string. Flow ignores that and shows the Flow board which has Start a new topic near the top. So the links aren't broken, but they're obsolete. The functionality of pre-filling the new topic using lqt_subject_field=New topic subject here is gone, but searching for insource:"lqt_method" shows only external links to translatewiki using lqt_subject_field. SPage (WMF) (talk) 02:23, 15 July 2015 (UTC)

{{sofixit}}? Ciencia Al Poder (talk) 09:17, 15 July 2015 (UTC)

• Is there an anchor in Flow boards to scroll to "Start a new topic", in case there's a lot of "About this discussion" above it (in a narrow window)?
• Maybe there is a way to prefill "Flow's Start a new topic".

@Quiddity (WMF) might know SPage (WMF) (talk) 20:11, 15 July 2015 (UTC)

I don't think there's such an anchor.

There is a way to pre-fill the topic title: https://www.mediawiki.org/wiki/Project:Current_issues?topiclist_preloadtitle=Foo . You can also preload the body with a template. Mattflaschen-WMF (talk) 20:54, 15 July 2015 (UTC)

I documented prefillinging topic title and body with a template in Flow/Architecture/URLs . There are tests for these URL parameters, so I hope it's somewhat stable :) SPage (WMF) (talk) 22:30, 12 November 2015 (UTC)

Why not point that link to the main board, or remove the link? Ciencia Al Poder (talk) 09:38, 16 July 2015 (UTC)

Done for Project:Current issues/Archives. I also cleaned up Project:Current issues/LQT Archive 1. SPage (WMF) (talk) 17:28, 16 July 2015 (UTC)

Broken page

This page is broken, please revert to classic talk page style:

1. There's some huge mw-flow script: delete, the page MUST work without script.
2. Some braindead CSS class decided that all browser windows are suited for max.width of 700px (+ sidebar per skin). This is untrue, delete'.
3. I've had enough of the unusable editor, delete. –Be..anyone 💩 07:11, 15 July 2015 (UTC)

1. The page does work without script. If you're having issues with the no-JavaScript experience, please let us know. Not all features can practically (or at all) be implemented without JavaScript, but we've made sure all the basic functionality is available. If there's something you want, we'll see what we can do.
2. What browser window width are you using, and what issues are you having? It actually does adapt to window size.
3. It's not clear what editor you're using (VE?). You can switch at any time with the </> icon, and it will remember your choice. Mattflaschen-WMF (talk) 20:18, 15 July 2015 (UTC)

There's a huge empty white box at the top of the page, which is a bit crap - the screen size issue definitely needs addressing.

I disabled JavaScript and was still able to read, navigate and post this link so it looks like JS is not a requirement (though I didn't do a thorough test).

No comment on the editor, but would be good to have some more constructive criticism - what are the problems with it? Why do you think it is unusable? HappyDog (talk) 07:41, 15 July 2015 (UTC)

Can you post a screenshot showing the empty box? What browser are you using? Mattflaschen-WMF (talk) 20:20, 15 July 2015 (UTC)

Also, lack of reply indentation makes the page very difficult to read! HappyDog (talk) 07:42, 15 July 2015 (UTC)

Interface localization

Changing "Code repository" sidebar link to diffusion

WMF is changing its repository browser from gitblit (at https://git.wikimedia.org/) to Phabricator's Diffusion (at https://phabricator.wikimedia.org/diffusion/MW/). There's a dedicated project phab:tag/gitblit-deprecate/ for it. Note this doesn't affect gerrit as our remote repository of record.

So I've changed the sidebar link Development > Code repository to link to Diffusion. I apologize to the cabal in charge of site changes like this, I don't know who you are :) . Revert if there are problems, at the moment it's not critical either way. If you have issues with switching to diffusion, file a bug against project gitblit-deprecate.

(Related, T101358 is "Update {{Git file }} to link to diffusion") SPage (WMF) (talk) 18:46, 21 July 2015 (UTC)

Reply to "Changing "Code slide shares 197.156.95.233 (talk) 22:05, 27 July 2015 (UTC)

AbuseFilter 39

Hi all, I've created this filter in order to detect the removal of deletion templates by new users; in this moment this filter is capable to detect only deletion templates, but any kind of template can be added to the filter, so if you want to add a template to the filter just add it or request it to me. Regards. Syum90 (talk) 14:33, 1 August 2015 (UTC)

Sample article

Hi everyone,

I'm not sure that this is the right place to ask, but I figure that someone here will know: I have an idea that I'd like to run past you all. One of the things that I do (and need to do more of soon) is make screenshots for help documentation. Especially for VisualEditor, there's a lot of this, and all of it needs to be produced in a couple dozen languages. The contents of the screenshots therefore varies a lot between languages, and also through the history of the page, as different people used different pages at different times.

What I'd like is a fake "article" or page that:

• contains only public domain images and CC-0 text,
• uses most of the core wikitext markup (bold, italics, sections, images, references, lists, tables, etc.), and
• could be translated into any language.

Do we have something like this already? Does anyone foresee any problems or have any advice if I create one? Whatamidoing (WMF) (talk) 19:12, 5 August 2015 (UTC)

This would create an accessibility issue because it's not actual text, but text within graphics. Screen readers can't read these, so this method isn't suggested :( Also, help pages are bound to be edited, so if you want to provide up-to-date information you'd have take another screenshot for every revision (or every 5 revisions per say?) These files would be bigger too than just actual characters (letters, symbols, numbers) which are a byte each, so performance is another issue.

It is an interesting idea, but I'm not sure what advantages this could have. SamanthaNguyen (talk) 23:14, 6 August 2015 (UTC)

I think you've misunderstood. I don't want screenshots of the help pages; I want screenshots in the help pages. "Type the data in the blank field labeled 'TYPE HERE'" is easier for most people to understand if those instructions are next to a picture of a blank field labeled 'TYPE HERE' (and maybe with circles and arrows and half of a word typed there).

Most of my screenshots need to show Wikipedia-style articles, which means that I'm always creating different bits of articles just to make a screenshot (like this one). I was thinking that if I made a whole article, that nobody would have to keep creating bits and pieces. Whatamidoing (WMF) (talk) 23:06, 7 August 2015 (UTC)

We already have software that automatically takes screenshots in multiple languages. The problem is not having content. Jdforrester (talk) 02:56, 7 August 2015 (UTC)

I think a fake article is a good idea. And if it was on astronomy (mentioned elsewhere), you could look at NASA topics, such as https://www.nasa.gov/topics/journeytomars/index.html or https://www.nasa.gov/topics/solarsystem/index.html .

Still, I wonder if you're overthinking this. If the article is about a fake topic, where all the words are your own, then you don't have to worry about copyright issues. I'm not suggesting you spend a lot of time creating content - rather, that you modify an existing topic. And images from the Commons shouldn't raise any copyright issues.

So, specifics - I suggest using a Simple English article, not an article from the main English Wikipedia, as your base, because the translation should be easier. And, looking at the most recent "very good articles" - https://simple.wikipedia.org/wiki/Wikipedia:Very_good_articles - one jumps out (to me) as most useful: https://simple.wikipedia.org/wiki/Hurricane_Vince_(2005) . That's because the images for an article on hurricanes can all be from NOAA, and thus public domain. (There are actually three articles about hurricanes, of the ten listed; you could also use https://simple.wikipedia.org/wiki/Tropical_Depression_Ten_(2005) for some wording.)

Or, to return to your original idea, consider https://simple.wikipedia.org/wiki/Andromeda_galaxy - you can name your own galaxy, rather than your own hurricane. John Broughton (talk) 17:25, 10 August 2015 (UTC)

I've started this at Help:Sample page and used it for a series of new screenshots that I added to Help:VisualEditor/User guide. I'm still sorting out what content will be convenient, but so far I think this is going to be a practical solution to my screenshot problems. Also, when I'm a little further along, I think it will need a re-write with Simple English in mind, as John suggested.

I think I'm going to need to import at least simple versions of a couple of popular template styles, so that I can show template uses in a page. Maybe a simple infobox and a common citation template would be sufficient. Whatamidoing (WMF) (talk) 18:49, 13 August 2015 (UTC)

Also some type of template that is normally subst:ed. The VisualEditor documentation shows a barnstar, which is not ideal for that context. (VisualEditor is usually disabled on discussion pages.) Whatamidoing (WMF) (talk) 18:56, 13 August 2015 (UTC)

I'm not convinced that template substitution is worth including; it is vanishingly rare in articlespace. But if you're determined, you might use <nowiki>{{No more links}}</nowiki>, as mentioned at https://en.wikipedia.org/wiki/Wikipedia:Substitution#Article_namespace . John Broughton (talk) 00:20, 14 August 2015 (UTC)

I've added an old (non-Lua) copy of {{Cite journal}} for this project. I figured that, of the common types, it was the least likely to be (mis)used in other pages on mediawiki.org. I'm still thinking about an infobox. {{infobox person}} might work, since it's common, but there should be no use for that template in the mainspace. If someone has other ideas, then feel free to let me know. Whatamidoing (WMF) (talk) 20:37, 19 August 2015 (UTC)

Update: I think it's nearly done. I still need to add a non-citation template (probably an infobox) and maybe some computer code. If someone wants to make a "Hello, World" section with his or her favorite (and not too complicated, please) computer code, then that would be great. Whatamidoing (WMF) (talk) 21:15, 19 August 2015 (UTC)

It's just amazing how many fiddly little features VisualEditor supports these days. I need a template that doesn't display on the page. Something like would work fine, except that it doesn't exist at mw.org. Is there anything here? I could always import it if that were necessary, but I'm hoping to find something that's already here/useful for other purposes. Whatamidoing (WMF) (talk) 19:01, 25 August 2015 (UTC)

Is it so hard to do?

How translate FAQ to persian language

Hi

I want translate FAQ page to persian but Translate this page message in top page not found.

Please help me. Beginneruser (talk) 13:39, 19 August 2015 (UTC)

Are you looking at Manual:FAQ? Whatamidoing (WMF) (talk) 21:12, 19 August 2015 (UTC)

I've asked at Manual talk:FAQ/Flow export#h-How_to_translate?-2015-09-21T22:54:00.000Z. Quiddity (WMF) (talk) 22:55, 21 September 2015 (UTC)

IRC office hour on APIs and the mw.org namespace

Tuesday 2015-09-01T18:00 UTC (11am San Francisco time) we will be having an IRC office hour about

• T105133 - Organize current and new content in the API: namespace at mediawiki.org
• T101441 - Integrate the new Web APIs hub with mediawiki.org
• T98897 - Deploy SkinPerNamespace extension on mediawiki.org

If you're interested in developing with, documenting, or promoting MediaWiki/Wikimedia APIs, you should attend. I hope by having a realtime conversation we can come to a shared understanding faster. SPage (WMF) (talk) 02:44, 27 August 2015 (UTC)

m:Requests for comment/Global ban for Tobias Conradi

Per [[m:Global bans]], I am notifying the project of this proposal. Everyone is welcome to go and voice their opinion of the proposal and about the user in general. GZWDer (talk) 09:42, 28 August 2015 (UTC)

Neither has the named user (Tobias Conradi), nor has the sock puppet (Helmut_Schönberg) contributed to mediawiki.org, so there shouldn't be a need for this notification :) Florianschmidtwelzow (talk) 00:06, 29 August 2015 (UTC)

See Special:Contributions/Tobias Conradi~mediawikiwiki, which is blocked here. GZWDer (talk) 08:11, 29 August 2015 (UTC)

Sorry, haven't seen, that the username is given to another user on mediawiki.org :) Thanks for linking to the correct one! Florianschmidtwelzow (talk) 13:30, 29 August 2015 (UTC)

Wikidata access is coming

Hi everyone,

Many Wikimedia projects already have access to Wikidata and make good use of it to improve their content. I wanted to let you know that your project will be among the next to receive access to Wikidata. As a first step we will enable access to the interwiki links. This is currently scheduled for Oktober 20th. If that goes well we will then later also enable access to the actual data from Wikidata. I'll let you know in advance once we get to that point.

I am excited about welcoming you to Wikidata and hope we'll be able to support you well with structured data. If you have questions please ask here. Lydia Pintscher (WMDE) (talk) 16:11, 9 September 2015 (UTC)

\o/ This helps documentation simply because Special:ApiSandbox and {{ApiEx }} can link to local URLs, whereas before extension WikiBase wasn't present on this wiki. SPage (WMF) (talk) 23:34, 5 October 2015 (UTC)

Do we even use interlanguage links on MediaWiki.org? I don't know of any use for them here. This, that and the other (talk) 08:49, 24 September 2015 (UTC)

Maybe not here but it is still important to link the respective pages on Wikidata. Take help pages for example. They will be connected through a common item on Wikidata and wikis that have the in other projects sidebar enabled can show those links in their sidebar if they want it. It's also a necessary first step towards giving you access to the data. Lydia Pintscher (WMDE) (talk) 09:41, 24 September 2015 (UTC)

Hey everyone :)

I recently announced that you'll get access to Wikidata. We start with access to interwiki links. This means you can for example add your help portal to the Wikidata item for all the other projects' help portals (https://www.wikidata.org/wiki/Q914807). This has happened now.

If everything goes well the next step is giving you access to the actual data like the date of birth of a famous person, the current version of some software and so on. I'll let you know in advance again when that'll happen.

In case you have questions or need some help please come to D:Wikidata:MediaWiki.

Cheers

Lydia Lydia Pintscher (WMDE) (talk) 07:40, 21 October 2015 (UTC)

Problematic gadget

Last week I was unable to edit Flow pages and translations, and use gadgets as popups or HotCat; all problems disappeared when I removed this gadget from my preferences. Syum90 (talk) 07:33, 22 September 2015 (UTC)

I think that gadget had to be updated recently but that never happened, so I wonder if that may be the reason. Elitre (WMF) (talk) 08:25, 22 September 2015 (UTC)

Unloadable page

https://www.mediawiki.org/wiki/Project:Current_issues and

https://www.mediawiki.org/wiki/Help_talk:CirrusSearch are

inaccessible on FF and Chrome. THe pages are in a fog,

and the wheel turns round and round, and I can't write anything.

When I disable JavaScript, these pages load.

Which user preference is likely be to blame? In other words, are there any known MediaWiki preferences that cause an inability to access MediaWiki help or MediaWiki discussion?

Must I reset all my preferences? 2601:601:0:25:B5C1:413F:6866:75 (talk) 20:40, 22 September 2015 (UTC)

Resetting all my preferences to default worked. Cpiral (talk) 20:44, 22 September 2015 (UTC)

Help

Hello,

A link brought me to Extension:ParserFunctions/Help/sl, which should be better located at Help:Extension:ParserFunctions/sl to be consistent with other translations of Help:Extension:ParserFunctions (see links on top of the page). However, I can't rename the page, being redirected to the translation tool.

Can someone help? Place Clichy (talk) 12:42, 23 September 2015 (UTC)

I'm not sure, if moving a translated page to another translated page (both versions seems to be very different for me). Maybe @Shirayuki, Nikerabbit, and Nemo bis: can help? :) Florianschmidtwelzow (talk) 14:14, 24 September 2015 (UTC)

I'd say this can't be done. A translated page now consists of translation units, so basically you'll need to manually translate the page, placing each paragraph to the translation unit where they belong. The sad part is that history would be lost.

And I'm not sure if that's also "right" from copyright perspective, since Help pages are PD, but the current page is supposed to have a CC-By-SA license... Ciencia Al Poder (talk) 14:37, 24 September 2015 (UTC)

OK. Do you think maybe a redirect is possible then? Otherwise, the original authors or the page, or someone at the Slovenian Wikim/pedia, might be asked to contribute to the page at the correct location. Place Clichy (talk) 14:12, 11 January 2016 (UTC)

What page is for being translation administrators?

Hi, I'm E.Z.O.

I'd like to be translation administrators to make translation work easier. however I wasn't able to find page for being translation administrators. What page is such one? E.Z.O. (talk) 17:27, 24 September 2015 (UTC)

See Project:Requests. Matiia (talk) 00:41, 30 September 2015 (UTC)

Opt-in BetaFeature for Flow on your user talkpage is now available

It is now possible for editors to opt-in (and out) of using Flow on their user talkpages via Special:Preferences#mw-prefsection-betafeatures on this wiki. This BetaFeature will NOT be automatically enabled, even if the user has "Automatically enable all new beta features" checked.

Editors who opt-in, will be shown a short (3-step) GuidedTour, and their old talkpage will be archived (the process takes a few seconds). Opting-out of this feature will move the Flow board to a subpage and un-archive the previous talkpage. More details and discussion are at phab:T98270 and linked tasks.

Please let us know if you experience any problems, either here, or at Talk:Flow, or on IRC in #wikimedia-collaboration. Thanks. Quiddity (WMF) (talk) 23:45, 29 September 2015 (UTC)

I'm biased, but it's awesome. Notice blue Echo badge, click it, click the "Username created a new topic on User talk:Your Name" notification, enter a reply, choose Summarize from the topic's menu. Bam. SPage (WMF) (talk) 19:58, 6 October 2015 (UTC)

OAuth handover

Hey everyone, please see this proposal "to hand over OAuth administration to the community so that selecting OAuth administrators and deciding about OAuth policies can be done in a more transparent manner. " Thank you. Elitre (WMF) (talk) 15:21, 30 September 2015 (UTC)

Caution: and Warning: templates broken!

For example the caution in Manual:Installing third-party tools and the warning in Extension:Git2Pages , neither shows the text parameter. I'm not sure what changed. @Legoktm suggested User:Anomie/previewtemplatelastmod.js to indentify. SPage (WMF) (talk) 23:13, 5 October 2015 (UTC)

@Shirayuki moved existing {{Warning }} to {{Warning/core }} on September 26 and the replacement invokes this via a module:

{{#invoke:Template translation|renderTranslatedTemplate|template=Warning/core|1={{{1|}}}}}

So perhaps this is more translation machinery that breaks when not invoked with the magic {{TNT }} incantation, which most mediawiki.org pages don't use. SPage (WMF) (talk) 23:29, 5 October 2015 (UTC)

The renamed warning/core "subtemplate" still works:

{{TNT|warning/core|Here is the text}} produces the correct:

warning/core

so it must be something about Module:Template translation or its invocation.

@Shirayuki moved the /doc subpage down to Template:Warning/core/doc, but I think that was unintentional. SPage (WMF) (talk) 22:59, 14 October 2015 (UTC)

Bawolff reverted Template:Warning, so

{{Warning|Here is the text}} works again:

Warning:

Here is the text

but as of 10 November 2015 Category:Pages containing potentially dated statements, {{Caution|Here is the text}} is still broken:

Caution:

Here is the text

SPage (WMF) (talk) 03:20, 10 November 2015 (UTC)

Why not just import Wikipedia's version of Template:Caution? Peculiar Investor (talk) 00:02, 9 January 2016 (UTC)

Because our templates are translated, although this seems the main reason for the break. Wikipedia templates are always in English, not translatable. Ciencia Al Poder (talk) 12:15, 9 January 2016 (UTC)

{{Warning|Here is the text}}

Warning:

Here is the text

{{Caution|Here is the text}}

Caution:

Here is the text

Shirayuki (talk) 12:49, 10 January 2016 (UTC)

Let's stop breaking pages when templates i18n-ize

As I understand it, when someone internationalizes a template here using Project:Translation machinery, every page using it displays garbled <translate>...</translate> tags until it is updated to invoke {{TNT }}.

This happened with {{MW version }}, it happened with {{Soft redirect }} (until @Krenair reverted it), etc.

Although the translation work that @Shirayuki and others do is immensely valuable, I think it's unfair to other mw.org users when it breaks pages that aren't internationalized. Surely there's a way that a template can do the right thing and not f*** up untranslated pages? If not, then we need a process for "Templates that are going to be translated", "Pages that need update for i18nized templates", [[Category:Templates that only work on i18n pages]], and maybe a bot to do the work.

Thanks for everyone's hard work, I appreciate it. SPage (WMF) (talk) 20:28, 9 October 2015 (UTC)

I created {{Template only works on internationalized page }}, and have begun adding it to the doc of templates that don't work unless you internationalize the calling page (sample). I still don't understand the root of the problem. SPage (WMF) (talk) 20:02, 13 October 2015 (UTC)

I asked him some time ago to ask for a bot to replace all templates that were being translated with {{TNT }} or {{TNTN }} where applicable. Sadly, that hasn't been done AFAIK Ciencia Al Poder (talk) 09:25, 10 October 2015 (UTC)

{{Warning }} seems broken on non-translated pages, even when using {{TNT }}, see the top of Extension:DeletePagePermanently Ciencia Al Poder (talk) 09:34, 14 October 2015 (UTC)

If you mean the text of the caution or warning doesn't appear, I earlier created topic {{Caution}} and {{Warning}} templates broken! on this board. SPage (WMF) (talk) 22:34, 14 October 2015 (UTC)

Unable to install Information template

I have tried to install the information template but am getting a "Unexpected property "params.Description.suggested". error . I copied the code and tried to save but it will not save and give this error.

Hereis a screenshot.http://i.imgur.com/SEIduPN.jpg Gmdesignuk (talk) 16:47, 14 October 2015 (UTC)

mediawikiwidgets.org is down

Hi all,

mediawikiwidgets.org is down :( :

2015-10-15 12:33:12 ERREUR 403: Forbidden.

Best regards,

Kevin Kbinetruy (talk) 10:35, 15 October 2015 (UTC)

Ok my bad is down and the issue is documented ... http://web.archive.org/web/20150109073433/http://www.mediawikiwidgets.org/Widgets_Catalog Kbinetruy (talk) 10:37, 15 October 2015 (UTC)

Note that mediawiki.org has no relation with mediawikiwidgets.org Ciencia Al Poder (talk) 13:30, 15 October 2015 (UTC)

Do you talk about Extension:Widgets ? Rical (talk) 15:17, 15 October 2015 (UTC)

A database query error has occurred. This may indicate a bug in the software

Recently received this error creating a new page.

The alias name for a field was not bracketed and the sequel server had a problem with this. Used the following code to change which resolved the issue.

The file : .\includes\db\Database.php

Before:

         
/**
              
* Get an aliased field name
* e.g. fieldName AS newFieldName
*
* @param string $name Field name
* @param string|bool $alias Alias (optional)
* @return string SQL name for aliased field. Will not alias a field to its own
name
*/

public function fieldNameWithAlias( $name, $alias = false ) {
                             
if ( !$alias || (string)$alias === (string)$name ) {
                                            
return $name;
                             
} else {
                                            
return $name . ' AS ' .
$alias; //PostgreSQL needs AS
                             
}
              
}

After:

              
/**
* Get an aliased field name
* e.g. fieldName AS newFieldName
*
* @param string $name Field name
* @param string|bool $alias Alias (optional)
* @return string SQL name for aliased field. Will not alias a field to its own
name
*/
              
public function fieldNameWithAlias( $name, $alias = false ) {
                             
if ( !$alias || (string)$alias === (string)$name ) {
                                            
return $name;
                             
} else {
                                            
return $name . ' AS [' .
$alias . ']'; //PostgreSQL needs AS
                             
}
              
}

196.36.226.1 (talk) 07:57, 21 October 2015 (UTC)

That shouldn't be necessary unless the alias contains spaces or weird characters on it, something I doubt would happen on mediawiki. See http://www.techonthenet.com/postgresql/alias.php Ciencia Al Poder (talk) 09:38, 21 October 2015 (UTC)

URLs with colons in query string on windows causes error

(20024)The given path is misformatted or contained invalid characters: Cannot map GET.....

This Apache Error on Windows will not be fixed.

The underlying idea was to prevent people from referencing DOS style device names, e.g. C: which could create havoc

Unfortunately, MediaWiki started out life on Linux / Unix platforms, and they decided to use colons for namespaces. Apmuthu (talk) 17:46, 23 October 2015 (UTC)

I think you placed your message on the wrong place.

This doesn't seem to be a documented problem on Manual:Running MediaWiki on Windows. Maybe you should be using IIS instead of apache? Ciencia Al Poder (talk) 11:01, 24 October 2015 (UTC)

Postgres & "Connect to database" setup wizard page

Hi,

The help text for the Database Host field reads "If you are using PostgreSQL, leave this field blank to connect via a Unix socket." Then if you leave this blank and press Continue, it won't allow you. It errors "You must enter a value for Database host".

I think this wizard page needs amending to allow a blank Database Host.

Many thanks. Jolly fellopian (talk) 19:36, 26 October 2015 (UTC)

Could you please open a BUGREPORT about this? Ciencia Al Poder (talk) 21:23, 26 October 2015 (UTC)

Blocked user by Abusefilter

Any admin around?

Wikidata data access is coming

Hi everyone :)

A while ago you received access to the interwiki links from Wikidata. Everything seems to be going well so I'd like to move on to the second stage. You will get access to the actual data in Wikidata like the date of birth of a person. You'll be able to make use of them in your templates via Lua or a new parser function (#property). We'll be enabling this on December 2nd. This will be the day for Wikinews, Wikispecies, Meta and MediaWiki. I hope this will open up great new possibilities for you and make your work easier. If you have questions please come to d:Wikidata:Sister projects. Lydia Pintscher (WMDE) (talk) 16:56, 18 November 2015 (UTC)

Hi everyone :)

We just enabled access to the data on Wikidata for you. This means you can now access data like the number of inhabitants of a city or get a link to a picture for a famous person and much more. You can access the data in two ways - via a parser function and via Lua.

How to use it:

• Parser function: {{#property:P36|from=Q183}} to get the capital (Property:P36) from the item about Germany (Q183)
• Lua: see mw:Extension:Wikibase Client/Lua

I hope this will help you do great things here. If you have any questions please don't hesitate to ask. Good places to start are the relevant pages for your project on d:Wikidata:Sister projects and d:Wikidata:Project chat.

Cheers

Lydia Lydia Pintscher (WMDE) (talk) 14:17, 2 December 2015 (UTC)

Internal sever error popped up

I have been running a wiki fine for a couple months now . However when I opened the wiki recently I got a internal server error with a 404 for the error document for my request and it took 2 minutes to give my the error . I am using a cloud server and am not able to see my server error logs. I believe this may be caused by the HEAVY spam and bots my site was getting. My site didn't really have any good pages. So I would delete all the pages in the site if I could.

First is the error possible not do to robots ? Second how should I fix it. Hans.gundlach (talk) 08:29, 4 December 2015 (UTC)

The long time to give a response may be a timeout of some sort. Maybe the database server is down or extremely lagging. See Manual:How to debug and try to enable the display of errors to see if that helps, or set a debug log. Ciencia Al Poder (talk) 10:44, 4 December 2015 (UTC)

Also please ask support questions in Project:Support_desk! Ciencia Al Poder (talk) 10:52, 4 December 2015 (UTC)

Moving a page ...

Wikimania 2016: call for proposals is open!