Project:Current issues

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

Current issues archive overview

Contents

Thread titleRepliesLast modified
Heartbleed308:51, 19 July 2014
No "LOG OUT" link007:27, 18 July 2014
Extensions not tagged with REL1_23112:32, 16 July 2014
insert "Vorlage" into a new mediawiki001:35, 13 July 2014
Broken link in user contributions footer613:54, 9 July 2014
Translate extension1408:28, 3 July 2014
left menu problem011:32, 2 July 2014
Honoring our volunteer devs614:45, 25 June 2014
Finding the correct version of an extension509:34, 20 June 2014
Not able to press the "Save Page" button019:17, 18 June 2014
Paid editing on this wiki319:42, 17 June 2014
Installation guide consolidation213:39, 14 June 2014
Leaflet For MediaWiki At Wikimania 2014014:16, 12 June 2014
Can't download extensions310:15, 3 June 2014
Add some Mediawiki pages for scribunto documentation109:32, 3 June 2014
Infobox not working007:22, 29 May 2014
Flow spam302:07, 29 May 2014
Missing messages in sidebar018:06, 23 May 2014
Page unprotect request218:15, 18 May 2014
block email-function for one user010:24, 30 April 2014
First page
First page
Previous page
Previous page
Last page
Last page

Heartbleed

Hi All, is Heartbleed security issue fixed? please confirm the version it got fixed.

148.188.243.25211:00, 16 April 2014

It's not a MediaWiki problem, but you may be interested in the Wikimedia projects handling: wmfblog:2014/04/10/wikimedias-response-to-the-heartbleed-security-vulnerability/.

Nemo15:22, 16 April 2014

Thank you Nemo, we have downloaded the MediaWiki app for internal wiki purpose, just want to know the version of wikimedia in which this bug was fixed...

148.188.243.25209:51, 17 April 2014

Heartbleed was a bug in OpenSSL, not in MediaWiki. The Wikimedia Foundation runs both on its sites, so it had to fix the OpenSSL problem; but there's no problem in MediaWiki. (MediaWiki and Wikimedia are two different things.)

Yaron Koren (talk)16:50, 14 May 2014
 
 
 

No "LOG OUT" link

A thread, Thread:Project:Current issues/No "LOG OUT" link, was moved from here to Extension talk:LDAP Authentication. This move was made by Florianschmidtwelzow (talk | contribs) on 18 July 2014 at 07:27.

Extensions not tagged with REL1_23

So far the repos were not tagged for MW 1.23. Thus it is not possible to select the "recommended version" for this release when using "Special:ExtensionDistributor". Not sure if there is something in the water.

[[kgh]] (talk)14:06, 10 July 2014

Ah, apparently there is indeed something in the water. Thanks for providing the links to Bugzilla.

[[kgh]] (talk)12:32, 16 July 2014
 

insert "Vorlage" into a new mediawiki

A thread, Thread:Project:Current issues/insert "Vorlage" into a new mediawiki, was moved from here to Project:Support desk. This move was made by Ciencia Al Poder (talk | contribs) on 13 July 2014 at 01:35.

Broken link in user contributions footer

It looks like the bottom of the "User contributions" page links to an edit counter which used to be hosted on toolserver. The link should be changed to link to some other edit counter.

APerson (talk)02:28, 9 July 2014

Which MediaWiki version do you run on your server that has this? Or is this about some Wikimedia website and not MediaWiki? Exact steps to reproduce welcome - I don't see any link to toolserver on my user contribution page on https://en.wikipedia.org/wiki/Special:Contributions

Malyacko (talk)07:29, 9 July 2014
 

I suggest he mean MW.org, which links to toolserver:

https://www.mediawiki.org/wiki/MediaWiki:Sp-contributions-footer

I think this isn't a bug report for bugzilla, but Support-Desk isn't the right place, too, i think. So move to talk page of Message or wait for mw.org admin? :)

Florianschmidtwelzow (talk)07:33, 9 July 2014
 

Done it. Thanks.

This, that and the other (talk)10:01, 9 July 2014

Thanks :) Now the question is: Wikipedia-project's uses supercount, mediawiki now uses xtools? Is that correct? :)

Florianschmidtwelzow (talk)10:25, 9 July 2014

Well, no-one said which one they wanted, so I just added a "link to some other edit counter". What's the difference between the two?

This, that and the other (talk)11:38, 9 July 2014

I don't know, i only saw the difference :) For me it's ok with this one.

Florianschmidtwelzow (talk)13:54, 9 July 2014
 
 
 
 

We've been using the translate extension for a while now on this wiki, which definitely needs more multilingual support, so I think we should greatly expand its usage, by deciding where to start. The aim is to reach more MediaWiki users (rather than developers); benefits have to be balanced by costs, and in some areas the extension is easier to use than in others (or even easier than continuing with {{Languages}} and so on). Some ideas:

  1. Most viewed pages: I've done some, but they often need an update/revamp in English too.
  2. Configuration variables: hundreds of them have the corresponding Manual: page translated and can be assumed of interest. The pages use a common pattern and most important info is in the template, so – in principle – translations can be moved to the new system (semi)automatically.
  3. Help pages would be the most useful in theory, but those we have here are very specific and limited. It makes no sense to translate most of them, because the "real help pages" and their translations are in fact on Meta or scattered among Wikipedias (or other Wikimedia projects.
Nemo09:23, 21 October 2012
Edited by another user.
Last edit: 13:31, 21 October 2012

About #3: What about the users of non-WMF wikis? Wouldn't translated help pages be helpful for them?

Leucosticte (talk)13:31, 21 October 2012

Yes but one should first move the up-to-date and complete English pages here from Meta and other wikis (finding a solution for licensing problems and also convincing them not to keep outdated copies around), which is not going to happen.

Nemo14:01, 21 October 2012
Edited by 0 users.
Last edit: 16:53, 21 October 2012

You may be right. I think it was a mistake to insist on public domain Help pages, and that we are reaping the harmful consequences of that decision. But to fix it would require acknowledging that a mistake was made, and sometimes people are resistant to that.

Leucosticte (talk)16:53, 21 October 2012

I disagree - PD help pages are a very good idea. However, it is a mistake to think they will be of any real use until we provide a workable method of distibuting them. I think it is a fairly safe assumption that if there was an easy way to import the default help pages into your local wiki, in the appropriate language(s), then that would be sufficient encouragement for the current pages to be tidied up (if, indeed, that is necessary - I haven't looked at them for a while) and, more importantly, widely translated.

I don't think think the solution here is to import existing non-English help content from elsewhere, or to try and encourage a translation drive for the help content, without having an export process in place.

HappyDog (talk)18:22, 21 October 2012

Seems we can all agree on this, so we're left with #1 and #2 for now.

Nemo08:26, 22 October 2012
 
 
 
 
Edited by 2 users.
Last edit: 18:21, 1 January 2013

Configuration settings summaries have over 23 thousands translations for the Configure extension; it would be nice to find a way to use them on wiki. I've opened bugzilla:43380 to see what's technically feasible.

Nemo11:06, 24 December 2012
 

I'm not familiar with the Translate extension, although I'm looking for an excuse to finally give it a try.  :) Is it possible to promote a set of pages where translation is prioritized? Using a category, for instance.

Trying to translate the whole mediawiki.org is pointless and actually counterproductive, but there is a bunch of pages that would really welcome more translations, and a formal request to be translated. It would be useful for the project and for translator to identify those, and if possible get those nice stats telling that Japanese is 100% up to date, Italian is 83%, Arabic is 12% and so on.

There are two types of translatable pages based on motivation:

  1. Promotion: local languages are good to reach out to new users and contributors. Homepage, the hubs, How to contribute, the local Groups (mainly in their respective native languages)...
  2. Support: essential pages for users of MediaWiki and our technical infrastructure. The most basic and required pages of the manual, how bugzilla works how to get developer access...

Maybe it's worth having both translatable categories separate? Maybe some languages make total sense for Promotion but less so for Support (no specific examples, although I can imagine Indic or Latin languages speakers needing those translations more for Promotion than Support, since the average sysadmin / developer of those languages is used to deal with English documentation).

It is clear that the deeper you get into both categories the clearer is the need to manage some English, at least in our current reality. We could probably define a VERY LIMITED set of pages translatable here and now in both categories and then consider the addition of new pages based on actual need.

And I agree with Nemo that those pages need a review in the canonical English version before making big calls for translation. But maybe this is a feature? It forces us to go through identified pages, mark them as translatable progressively and giving more time to translators to deal with new content. For instance, we could start focusing in How to contribute and Help:Formatting, and do a first test with these pages.

Qgil (talk)17:00, 24 December 2012

Yes, it's possible to "categorize" requests for translations, see for instance m:Special:AggregateGroups. It's also possible to define priority languages and even to disable translations in some languages, but this makes little sense on this wiki. In general, people will always translate what they're interested in, not what you'd most like to have translated, therefore if something would use translations it should be translatable, while for focused translation recruitement you can have a specific priority group of translatable pages.

In short, I don't like that "very limited" in all caps, unless you consider (like me) that e.g. 600 configuration settings pages (out of ten thousands content pages) would be a "very limited" set of translatable pages. ;-) Specific pages ready for translation should made translatable immediately: I'll comment on those two on talk.

Nemo17:49, 24 December 2012

Ok, got your point. I just find useful to have a set of pages identified for volunteer translators without own itch or agenda. "I want to start translating MediaWiki content to Catalan: where should I start? Thank you."

Qgil (talk)18:08, 24 December 2012

I've created a high priority group now.

Nemo18:46, 24 December 2012
 
 
 

http://stats.grok.se/www.w/top was updated; the Help: and Manual: pages in the top-1000 list should probably be made translatable. Who's willing to help me?

Nemo08:38, 24 May 2013

Thank you for this useful link!

Qgil (talk)14:41, 24 May 2013
 
 

left menu problem

Hello. Left menu in other language is not correctly. Such as, User help link leads to English only, not to other languages. I think that link must be /wiki/Special:MyLanguage/Help:Contents.

Category:Extensions is too.

Please fix this or tell me how to fix it.

Meshkov.a (talk)11:32, 2 July 2014

Honoring our volunteer devs

I've been a little frustrated recently by a couple of users who don't seem to understand how important our volunteer devs are. It's not entirely their fault; they're just so new, compared to MediaWiki's existence, that they have no idea that the entire concept of MediaWiki software was a volunteer achievement. The WMF devs are working on some large, high-profile projects, and the result is that "volunteer dev" sounds like "second-class dev" to these new folks.

So I have just started a page, How to become a MediaWiki hacker/Volunteer achievements, on which I've listed a couple of obvious, user-facing changes that were written by volunteer devs (even if said devs were later paid to work on MediaWiki).

I'm secretly hoping someone will tell me "No, that's just a poor duplicate of <this much, much better page>", but, failing that, if there's anything that you did, or that you know someone else did as a volunteer, please expand. I'd like people who are interested in become hackers to know that volunteer devs can do real things here, and for non-technical users to be able to see that volunteer devs have created many of the things that they use and rely on every single time they read or edit the site.

Thank you–to all the volunteer devs, for doing your work, and to anyone who can help me expand this page, for helping honor that good work and educate the next generation of users about our debt to the volunteer devs.

WhatamIdoing (talk)18:31, 18 June 2014

This is a great idea. Could you post this to the mediawiki-l and wikitech-l mailing lists? If you can't, would you mind if I post your message there?

MarkAHershberger(talk)18:45, 18 June 2014

I've added a link there. Usually, I do this on the MediaWiki release pages: you'll notice that most stuff on 1.21, 1.22, 1.23, 1.24 is done by volunteers.

I'm not sure how to expose such information without duplications nor ghettos, there would be two extremes:

  • highlighting volunteer contributions on MediaWiki history: could only be very high level (as your stub currently is);
  • filling in the "assignee" field on bugzilla for hundreds of particularly important bugs: very atomic, not super-readable.

As an aside, it's easy to find the conversation you probably had in mind and I'm not sure the person meant to depreciate volunteer work, rather the opposite.

Nemo19:24, 18 June 2014

I've seen more than one of these conversations in the last year or two, and different users have different views. Some agree with me that it's awesome that volunteer devs do so much. Some seem to be dismayed that critical infrastructure is left to mere volunteers.


Mark, you should feel free to post a link to the page any place that you'd like.

WhatamIdoing (talk)05:13, 20 June 2014

I would disagree that critical parts of the infrastructure are "left to mere volunteers". If a volunteer fills a need, the Foundation doesn't necessarily look to replace them with a paid employee. There have bee critical bits of infrastructure that have been handled by volunteers, but many of them have been hired as full time employees.

MarkAHershberger(talk)18:10, 21 June 2014

I think that your idea of what constitutes "critical infrastructure" might be narrower than some other people's.  ;-)

Whatamidoing (WMF) (talk)18:54, 23 June 2014
 
 
 
 
 

Finding the correct version of an extension

When I was here the last time, it was easy to find the correct version of an extension for my mediawikiversion - which is 1.17.0 - as than subversion was used to download snapshots. Now it is almost impossible to find the correct version as GIT ist used and only the newest snapshot is easyly found, while the correct old versions are almost impossible to identify.

Now I need Extension:ConfirmEdit to block spam and the newest snapshot doesn't work and I don't know if this is because it is not the correct version.

Kersti (talk)10:38, 2 December 2012

Yes, there's currently no way to reliably download extensions. This is very unsatisfactory and has been discussed several times on this wiki, bugzilla, wikitech-l and mediawiki-l but there's no solution on sight coming from the devs; try reading/joining those discussions to find partial solutions...

Additionally, 1.17 is unsupported and 1.18 will be soon the next, so I think you're really supposed to upgrade to 1.19 or 1.20.

Nemo11:45, 3 December 2012

Actually 1.18 is already EOL.

Daniel Friesen (Dantman) (talk)12:49, 3 December 2012

Sorry, but it is not possible for me to upgrade that often. And there may be good reasons why someone is not able to upgrade to a newer version, for example because he is running Mediawiki at home and has an old Computer.

Kersti (talk)11:47, 13 August 2013

That's really not a good reason.

Krenair (talkcontribs)13:31, 13 August 2013

I think, ab big site als Wikipedia or a Wiki which has 20 Contributors or more schould upgarde regularly whenever there is a new version.

But in cases where upgrading for itself is more work than I do on the contents of the Wiki, than this is a very good reason, to reduce upgrading to a sensible niveau! And in this case it is really impossible to upgrade that often, as I simply don't have the time to upgrade once a year!

Kersti (talk)09:34, 20 June 2014
 
 
 
 
 

Not able to press the "Save Page" button

A thread, Thread:Project:Current issues/Not able to press the "Save Page" button, was moved from here to Project:Support desk. This move was made by Ciencia Al Poder (talk | contribs) on 18 June 2014 at 19:17.

Paid editing on this wiki

Since the proposal affects this wiki (as well as the "software" project), please see Requests for comment/Alternate disclosure policy for a proposal to not require disclosure of compensation for editing actions.

Bawolff (talk)18:16, 17 June 2014

Could you please clarify what you're talking about? I assume it has something to do with the Release Management RFP but I'm not sure exactly what.

MarkAHershberger(talk)18:31, 17 June 2014

It affects anyone who touches MediaWiki for work.

Nemo19:17, 17 June 2014

Thanks, just read the text in Bawolff's original link. NOW I understand

MarkAHershberger(talk)19:42, 17 June 2014
 
 
 

Installation guide consolidation

Manual:Installation guide has one section with a 400 words summary, but then links to a "Main installation guide" composed of 4+4 more pages. None of these pages is translatable. Can we consolidate truly important information and make it translatable? Currently one is supposed to find the following logical steps.

  1. Download
  2. Requirements
  3. The actual installation
  4. Misc troubleshooting and alternatives if something went wrong
  5. Configuration
  6. Maintenance
  7. Informative material

The pages in bold are part of the official Template:InstallationNav (which complements Template:MediaWiki Introduction): they are supposed to be the official path and need special care and coordination.

Nemo14:17, 27 May 2014

Given Chad's comment, I'm also going to tag all "platform-specific" manual pages for merge to the main ones. Common parts can be merged and transcluded on the specific pages, while really platform-specific additional information can be left there. P.s.: for a start, I removed 5 guides on obsoleted systems and marked the others for merge.

Nemo09:51, 14 June 2014

Thank you for this!

MarkAHershberger(talk)13:39, 14 June 2014
 
 

Leaflet For MediaWiki At Wikimania 2014

Are you looking to recruit more contributors to your project?
We are offering to design and print physical paper leaflets to be distributed at Wikimania 2014 for all projects that apply.
For more information, click the link below.
Project leaflets

Adikhajuria (talk)14:10, 12 June 2014

Can't download extensions

Whenever I try to download an extension through Special:ExtensionDistributer I get a blank select box for the MW version and when I click contiune no download starts.....

Any other way I can get MaintenanceShell?

LK901 (talk)16:51, 21 May 2014
Edited by 3 users.
Last edit: 00:09, 3 June 2014

Yes, you can click the link next to it: [1]. Not sure why ED is not working, branches exist.[2]

Nemo bis17:01, 21 May 2014

Thanks,
Seems to be working now :)

LK901 (talk)18:07, 21 May 2014
Edited by 2 users.
Last edit: 00:15, 3 June 2014

ExtensionDistributor has a lot of problems. In the future, it's always easier to download from git.

GeorgeBarnick (talk)18:43, 21 May 2014
 
 
 

Add some Mediawiki pages for scribunto documentation

Edited by 2 users.
Last edit: 00:08, 3 June 2014

Please add this page to Mediawiki MediaWiki:Scribunto-doc-page-show with the code

{{documentation|{{#ifexist:{{FULLPAGENAME}}/doc|{{FULLPAGENAME}}/doc|{{NAMESPACE}}:{{BASEPAGENAME}}/doc}}}}     
<span id="code"></span>

And please also add MediaWiki:Scribunto-doc-page-does-not-exist with the code

{{#ifeq: {{SUBPAGENAME}} | testcases    
 | {{module test cases notice}} 
 | {{documentation}}    
}}

Please also add MediaWiki:Scribunto-doc-page-header With code

{{#ifeq:{{#titleparts:{{PAGENAME}}|1|2}}|documentation||{{documentation subpage}}}}

Please

20:48, 11 March 2014
Edited by 2 users.
Last edit: 00:16, 3 June 2014

Ring

110.146.151.5014:22, 2 June 2014
 

Infobox not working

A thread, Thread:Project:Current issues/Infobox not working, was moved from here to Project:Support desk. This move was made by Nemo bis (talk | contribs) on 29 May 2014 at 07:22.

Talk:Flow and Talk:Beta Features/Hovercards have been hit with massive spam attacks. Some blocks and perhaps website blacklisting seem to be needed, as well as deletion of the Flow posts.

Jay8g (talk)17:13, 26 May 2014

I've added 16 more domains to MediaWiki:Spam-blacklist, and will delete the topics that are still visible or just hidden. I've emailed the Flow dev team, to emphasize the priority of confirmedit integration.

Thanks again, for everyone's help with this.

Quiddity (WMF) (talk)20:25, 26 May 2014

It's back (on Talk:Beta Features/Hovercards only this time). More IPs to block, posts to delete, and perhaps websites to blacklist.

Jay8g (talk)01:15, 28 May 2014
 

Also note header spam.

Jay8g (talk)01:36, 28 May 2014

Jorm has semi-protected the page, whilst the developers work on the extension-integration. I've added some more domains to the blacklist, and deleted the posts. Most of the IPs only make a single post, so blocks probably wouldn't help. Thanks again.

Quiddity (WMF) (talk)02:07, 29 May 2014
 
 
 

Missing messages in sidebar

Causes some entries to not even show up.

137.147.156.916:14, 23 May 2014

Page unprotect request

Hi, I'm in charge of the Semantic Bundle. The page Talk:Semantic_Bundle/Discussion_archive is currently protected, but I want to edit it, to add more to the archive. Can someone please unprotect it?

Yaron Koren (talk)16:47, 14 May 2014

I've removed the protection so you can update it. Let me know when I can restore it.

MarkAHershberger(talk)13:38, 15 May 2014

Thanks, I moved the discussion text over. However, I don't know if there's a need to re-protect the page - none of my extensions' archive pages are protected, and that doesn't seem to have led to any problems...

Yaron Koren (talk)18:15, 18 May 2014
 
 

block email-function for one user

A thread, Thread:Project:Current issues/block email-function for one user, was moved from here to Project:Support desk. This move was made by Nemo bis (talk | contribs) on 30 April 2014 at 10:24.
First page
First page
Previous page
Previous page
Last page
Last page