Project:Current issues

Jump to: navigation, search
This page is for discussing issues related to site. To get help with MediaWiki software, ask on Project:Support desk.
An archive box Archives 

Current issues archive overview

Start a new discussion
First page
First page
Previous page
Previous page
Last page
Last page

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 Topic:Sewfq489tp3iic43, please move it without leaving a redirect.

Be..anyone (talk)03:16, 11 April 2015

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

It's an experiment, I tried to figure out why an existing Topic:Sewfq489tp3iic43 contains a red link to itself, and is actually always shown as red link. Additional test:

Quick namespace test
Namespace Talkspace
  90 Thread pages   91 Thread talk pages
 100 Manual pages  101 Manual talk pages
2600 Topic pages 2601 pages

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 Topic:Sewfq489tp3iic43 is really wrong, it exists.

Be..anyone (talk)15:10, 13 April 2015

YesY Done

Florianschmidtwelzow (talk)11:21, 15 April 2015

Manual thanks, I miss the tnx-button whenever it doesn't show up—IPs, bots, liquid threads, … smile

Be..anyone (talk)23:47, 16 April 2015

np :) Yeah, Flow would be better, just because you can thank another user for a post :D

Florianschmidtwelzow (talk)13:17, 17 April 2015

error: rendering process died with non zero code: 1


Has anyone had seen this error before while converting/rendering

an assembled book in to pdf ?


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

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.

Nemo07:18, 15 April 2015 down

Is down? I tried to look in the irc logs for mediawiki/mediawiki tech and search here, but could not find anything about it...?

Christian75 (talk)18:36, 14 April 2015

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

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 Thread:Project:Support desk/Cannot starting a new discussion in support desk/reply to figure out what's wrong.

Be..anyone (talk)12:04, 14 April 2015

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 Thread:Project:Support desk/Cannot starting a new discussion in support desk/reply

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

Error on website

Hi when visiting it brings up a error saying tool does not exist but it was only working a few days ago., 10 April 2015

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

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

[RESOLVED] Mass vandalism by User:Prianka

Edited by 2 users.
Last edit: 20:54, 12 April 2015

This user has used a bot to remove content from pages. Please revert their edits., 17 March 2015

YesY Done. I have blocked the user and reverted their edits. Thanks.

Shirayuki (talk)03:13, 17 March 2015

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)

TomT0m (talk)09:12, 12 April 2015

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

[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

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

+1 Should be an easy change with a lot of benefits.

Florianschmidtwelzow (talk)12:54, 5 January 2015

YesY Done Api: and Skin: are now in the default namespaces (see Task T85807).

Florianschmidtwelzow (talk)20:22, 6 January 2015

Yep, makes sense; let's also include them in content namespaces if we didn't yet.

Nemo14:47, 6 January 2015

+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

Tracked in Task T86391

Florianschmidtwelzow (talk)01:30, 10 January 2015

YesY Done by Reedy :)

Florianschmidtwelzow (talk)21:34, 13 January 2015

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

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

Text missing but data available via edit function and database

A thread, Thread:Project:Current issues/Text missing but data available via edit function and database, was moved from here to Project:Support desk. This move was made by Ciencia Al Poder (talk | contribs) on 5 April 2015 at 18:48.

這個頁面應該是繁體中文(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

-- By LNDDYL. (Talk)06:50, 1 March 2015

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

This is bugzilla:20004.

Actually, some research option is available, but doesn't check where the thread is currently located.[1]

Nemo19:25, 3 April 2015

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 [1].

That's because now in phabricator, the project page goes to the workboard (see Task 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

FriedhelmW (talk)12:12, 28 March 2015

That doesn't work. It lists open tasks, but doesn't filter for that extension.

Ciencia Al Poder (talk)10:51, 29 March 2015

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.

Nemo13:01, 29 March 2015

As Nemo says. If you want to get a PHID of a project (e.g. Flow): Go to , enter ["Flow"] in names, get PHID-PROJ-ntg6sf6mfl2qm2e4qgxc.

AKlapper (WMF) (talk)10:13, 1 April 2015

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

Please assist - I am unable to access/log into my account:, 31 March 2015


(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

Proposal to convert LiquidThreads discussions to Flow

There is such a proposal, see [Wikitech-l] Starting conversion of LiquidThreads to Flow at This is the place where consensus for changes is checked, hence I'm opening the discussion here.

Also, some users have already started disabling LiquidThreads on some talk pages to use wikitext instead: what to do? Should that be done on more or less pages?

Nemo09:37, 18 March 2015

LiquidThreads was an unmitigated disaster, in my view, and has made the site worse for being here. History before it was enabled was lost (or, at least, very hard to find) the links in e-mails never take you to the thread they're supposed to, the UI is horrible and it is difficult to find things you are looking for. It actually makes the site harder to use for anyone at all experienced in wikis, not easier, and so should never have been enabled.

I haven't used Flow, so I don't know how it compares, but I would certainly vote for removing LiquidThreads! If Flow actually works in a wiki-like way (i.e. you can view history, see the state of the page before it was enabled, edit comments where necessary, etc.) then I might be persuaded that it is a good replacement, but given our experience with LiquidThreads I am fairly sceptical. For it to work it would have to be something that works inside existing wiki pages, rather than fighting against them. It would also be a requirement that all LT content can be 'migrated' to Flow so that it is not lost or broken. It is not acceptable for it to simply be shunted off to an 'old threads' namespace and abandoned - it needs to appear where it was originally posted.

The issue is as much about how the extension works behind-the-scenes and how well it integrates with the rest of the wiki, as about the interface it provides.

For example, I don't want to lose my current talk page, nor its history. If what is there can be converted seamlessly to Flow, without losing my ability to view old revisions of the page (pre-flow and post-flow), archive things in the way I have done in the past, include some non-thread-like content (e.g. introduction section) and link to specific items without the links breaking as items change (e.g. if they move to 'page 2' of the listings) then it might be viable. Otherwise, please just remove LiquidThreads and don't mess up the wiki with further incompatible plugins.

HappyDog (talk)10:09, 18 March 2015

PS - From reading the wikitech-l post, it looks like once again this is a decision being forced upon us without any kind of local consensus. should not be treated as a test site, without community buy-in. If you want people to be antagonistic towards Flow, and to resent its presence on the wiki, then that is a pretty good way of going about it.

HappyDog (talk)10:11, 18 March 2015

Also, I didn't realise quite how experimental/incomplete Flow currently is. Therefore, my vote is (for now at least) a firm no!

The comment from Risker/Anne sums things up pretty well, as far as I'm concerned.

Please just remove LiquidThreads and come back to us with a proposal for Flow when it is out of beta and feature-complete.

HappyDog (talk)10:15, 18 March 2015

Please no back to plain wikitext talk pages, at least for talk pages with hundreds of posts (like Current_issues and Support_desk). Wikitext talk pages are terrible to follow and archiving is as bad as the wikitext discussion format itself. I prefer LQT (in it's fairly bad state) before wikitext, but i welcome a move to Flow, after it is in a workable state (see, e.g., this mail).

See also[edit | edit source]

So, from my side: Support Support

Florianschmidtwelzow (talk)11:42, 18 March 2015

Is it possible to have a complete list of LQT pages on this wiki? That would help the discussion.

Certainly it makes sense to use modern discussion software on Project:Support desk, as that is a high-traffic forum-style page which is aimed at IT professionals and server administrators more than wiki users.

This, that and the other (talk)00:14, 19 March 2015

I agree that for the support desk, and maybe a couple of other support-related pages, a more forum-like approach is sensible.

However, one does have to question why we use the wiki for these purposes at all. We don't use the wiki for internal issue tracking, so I'm not sure why we are using it for support. I am not aware of any other company or open source project that would consider using a wiki for handling support issues - it is clearly the wrong tool for the job.

Perhaps a more sensible solution would be to use support desk software for handling the support desk, rather than trying to shoe-horn non-wiki-like tools into the wiki, which will inevitably bring unsatisfactory results (as has been shown with LQT).

HappyDog (talk)12:05, 19 March 2015

FWIW, there was such a proposal too: phabricator:T31923.

Search is pretty good at finding LQT talk pages: [1].

Nemo14:02, 19 March 2015

Special:PagesWithProp also works. [1] - currently LQT is on 1,639 pages - (I'm not sure why that number differs (1,567) from the search that Nemo linked?)

Re: existing posts - currently 52,526 individual posts. Of those: 24,897 of those are in Project:Support_desk; 1,269 in VisualEditor/Feedback.

I'm asking devs for help getting a more detailed listing of All pages ordered by size (number of posts).

[Update: A list of all pages with more than 10 posts, is now at phab:P417, and converted into an onwiki page with links at Flow/LQT pages.]

Quiddity (WMF) (talk)21:15, 19 March 2015

The Flow/LQT_pages are interesting, thanks. Just for fun I looked at the even (non-talk) namespace numbers: One entry in 90 might be odd (3 contributions counted as 12), and for the Project:Forum redirect I didn't get why it's counted as 94.

Be..anyone (talk)12:24, 20 March 2015
Edited by another user.
Last edit: 07:14, 24 March 2015

Note: We'll be holding an IRC office hour for Flow, this Monday at 19:30 UTC / 12:30 PDT. You can find information on how to get online, including a link to a webchat option if you don't have an IRC client, on the meta office hours page. The intended focus is for questions about the LQT -> Flow conversion here. Everyone is welcome for discussions and question answering. Logs will be posted on the meta office hour page afterwards. Thanks.

Quiddity (WMF) (talk)02:29, 21 March 2015

Few minutes of testing were enough to discover that

WMF, please ensure you table such proposals only after you've thoroughly tested the conversion. Thanks.

Nemo07:11, 24 March 2015

I don't know if it's just an unfortunate coincidence, or what, but since this announcement, the usability of LQT has degraded a lot...

First I reported that submitting a reply doesn't display the reply unless you refresh the page (Task T93374).

Today hitting "show preview" displays a confirmation dialog about leaving the page, and if you proceed, you end up submitting an edit to the underlying page and not on the message you was editing!

PD: Reported as Task T94089

Ciencia Al Poder (talk)10:57, 26 March 2015

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?

Ricordisamoa23:03, 21 March 2015

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".:tongue:

Be..anyone (talk)17:55, 22 March 2015

Api documentation bot


Just a quick notice, letting you know I'm currently working on a bot that get's documentation from the PHP classes (required rights, must be posted, parameter optional/required + description, examples etc.) into wikitext and saving to a wiki page.

Zak originally created something for this (example), but the source code remains unpublished and the format has changed a lot since then.

Roughly what I've got / aiming for (about 50% done)

  • Extract module name/class pairs from $mainApi = new ApiMain
  • Loop over and instantiate it: $module = new $class( $mainApi, $name );
  • Buid a documentation page in wikitext format: new ApiDoc4Wikitext( $module );
    • {{API-head}} with parameter values from getModulePrefix, mustBePosted etc.
    • Parameter section build with a function based on makeHelpMsgParameters but in wikitext format
    • Examples section based on array from getExamples, which is then dissected into parts for {{ApiEx}}, followed by an http request to exampleurl+format=xmlfm and output cleaned up and unescaped and fed to result-parameter of {{ApiEx}}.
    • Categories
  • Either write wikitext to a file and let another bot save to wiki, or write a simple wikibot and save right away.

To be done:

  • Example section
  • Saving mechanism

Any ideas / existing code I can look at ?

Krinkle09:02, 9 August 2011

The source code mentioned above is an empty svn folder. Is it hiding in an archived svn branch, or did it never see the light of day? This is now relatively easy to do with Pywikibot since I added a ParamInfo class. See API_talk:Main_page#Missing_documentation_pages for some basic code.

John Vandenberg (talk)01:47, 21 February 2015

Does anyone know who Zak is? And/or where this prototype code might be?

John Vandenberg (talk)00:04, 22 February 2015

Zak was probably the contractor that the foundation hired a few years ago, Once his contact ended he didn't return.

Peachey88 (talk)00:29, 22 February 2015

Zak hasn't been around for a while. I knew him when he was here (I had a chance to meet him in Gdansk) but since then he hasn't really been involved.

MarkAHershberger(talk)03:33, 22 February 2015

Thanks Peachey88 and Mark. Is his code lost? Can we contact him? phab:T31936 is related. I cant find much more about it.

John Vandenberg (talk)03:56, 22 February 2015

I sent him a message on FB. Let's see if he responds.

MarkAHershberger(talk)19:15, 22 February 2015

Greetings All,

Any source code that remains in sitting in storage about 8000km from where I am at the moment. :-/

However, I'm happy to look at source code and otherwise pitch in some.

Cheers! --zak

Zak08:04, 23 February 2015
Edited by another user.
Last edit: 08:34, 23 February 2015

Note that ApiHelp can now be transcluded, see an example at Extension:Flow/API. I think SPage has plans to start/propose using this feature more widely once it gets possible to select content language à la {{TNT}} (currently it's only possible via interface language change, e.g. [1]).

Nemo20:10, 22 February 2015

So far, Special:ApiHelp is extremely ugly (but better than nothing), and the details on Extension:Flow/API are not provided by Special:ApiHelp - they are added by hand. Also there is one aspect of the documentation which can't be generated (currently): information about previous releases. i.e. when each module & parameter was added, deprecated, & removed. Sadly there is not a lot of care for wikis running anything but the bleeding edge.

{{API-head}} has been improved to include a link to the API help module, so the current help is easy to get to, and that template has been added to most of the existing API pages.

John Vandenberg (talk)08:45, 23 February 2015

My proposal is phab:T89318, John Vandenberg and RobinHood70 raise excellent points. We'll have this tension with any generated documentation, so I mention it in phab:T93026 "remove wiki documentation that duplicates generated documentation (tracking)."

"It gets rebuilt from scratch on every code change" is a feature and a bug :)

SPage (WMF) (talk)06:22, 20 March 2015

"Now with mustache" logo

@Kaldari: uploaded a new version of File:Wiki.png today. I don't like it. In fact, I thought it was vandalism at first. Can we get this reverted?

Glaisher (talk)12:54, 27 February 2015

I like the idea of using special logos for special milestones and/or events and so on, but maybe it should be discussed first.

Florianschmidtwelzow (talk)13:28, 27 February 2015
MediaWiki logo with a mustache.png

Discussion, it's not directly related to Extension:SemanticMustacheFormat, but just in case I "rescued" it.:tongue:

Be..anyone (talk)19:26, 7 March 2015

It would be OK if it was explained somewhere... Most folks won't get such tech-jokes and therefore mistake them for vandalism or at least for a bad joke.

Patrick87 (talk)15:28, 27 February 2015

And this logo was used on too until a few minutes ago [1]... I'm also not completely against changing logos for special occassions but there is no explanation about why it was changed.. I've checked various places but I still can't find anything about this.

Glaisher (talk)16:17, 27 February 2015

Hmm, Okk but can we really have an explanation somewhere; maybe the logo's link could be changed..

Glaisher (talk)16:30, 27 February 2015

Thanks, it has been reverted now. Apparently, people came over to #mediawiki wondering whether the site was hacked.. Unfortunately, as Patrick said above, most users won't get such jokes. :/

Glaisher (talk)17:10, 27 February 2015

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

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

Has been fixed.

Temptuousinsolence (talk)12:28, 6 March 2015

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

A thread, Thread:Project:Current issues/error in update with by web browser in MediaWiki Language Extension Bundle, was moved from here to Project:Support desk. This move was made by Ciencia Al Poder (talk | contribs) on 1 March 2015 at 16:52.

Special:Translate not working

Edited by 2 users.
Last edit: 06:06, 26 February 2015

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:

TypeError: mw.config.get(...) is null" TypeError: mw.config.get(...) is null
Pelacakan susunan:
util.getUrl@ line 4 > eval:9:119
getTarget/targetPromise<@ line 4 > eval:53:1245
Uncaught TypeError: Cannot read property 'replace' of null
(anonymous function)load.php?debug=false&lang=id&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150107T1…:65

Anyone having this problem too?

William Surya Permana (talk)12:07, 9 January 2015

Yes, but not everyone. Thanks for reporting.

Nemo17:45, 9 January 2015
First page
First page
Previous page
Previous page
Last page
Last page