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

Start a new discussion

Contents

Thread titleRepliesLast modified
Replace full protection with FlaggedRevs1116:54, 29 October 2014
Wikimedia Engineering reports319:19, 28 October 2014
Toolserver wiki211:04, 19 October 2014
[RESOLVED] rapid-fire vandalism from Ekkentros109:19, 14 October 2014
[RESOLVED] vandalism from 2602:306:cc2e:efb0:59f:ad58:ff56:3a40022:46, 10 October 2014
Translation of the sidebar items106:35, 9 October 2014
Extension:CodeReview1019:12, 29 September 2014
[RESOLVED] MediaWiki:Gadget-externalsearch110:09, 28 September 2014
Some documentation needs clarified619:30, 26 September 2014
lock special sites010:22, 24 September 2014
ORCID316:41, 19 September 2014
Doesn't do anything015:46, 19 September 2014
New links not acknowledging that page exists006:12, 17 September 2014
Page creation glitch218:04, 11 September 2014
LQT search boxes on this site hit HTTP timeout atm.407:24, 8 September 2014
Email, watchlist, and notifications019:35, 6 September 2014
[RESOLVED] order reversed for Special:MyContributions?313:12, 5 September 2014
Enable DynamicPageList705:11, 1 September 2014
How to to get password reset for account on this site which has no email address706:10, 26 August 2014
left menu problem014:40, 14 August 2014
First page
First page
Previous page
Previous page
Last page
Last page

Replace full protection with FlaggedRevs

Some pages that are currently fully protected could benefit from a less rigid protection scheme using Flagged Revisions, allowing more editors to suggest edits without risking having highly visible pages contain potential gibberish. I propose changing the fully protected pages to Flagged Revision's "Require review for revisions from everyone except Reviewers" setting. That way people can suggest edits but these won't be publicly visible unless approved by a reviewer or administrator. Optionally, semi-protection can be added to prevent edits from unregistered or new accounts. What do you guys think?

Waldir (talk)15:51, 7 January 2013

The principle sounds interesting. What pages are you thinking of? Maybe it's easier to just report pages that should benefit from Flagged Revisions and change their status unless there is a good reason not to. Should we try with a just a few first?

Qgil (talk)18:13, 7 January 2013

There are 7 in ns0 (none worth unprotecting), one in Extension and none in Help or Manual. Waldir, what pages are you talking about?

Nemo19:12, 7 January 2013

I'm thinking all of them, really. It might be worth revisiting what we understand by "worth unprotecting". There is always a small detail (a typo, a minor rephrasing to make things clearer, etc.) that we will overlook — nothing's ever perfect, after all. As an example, just yesterday I noticed that the main page has a link to "How does MediaWiki work?", a redirect that can be replaced with its actual target, "Manual:What is MediaWiki?". Requiring edit requests makes the workload for such small edits triple. Besides, this wiki doesn't get much vandalism/spam (AFAIK), so it shouldn't be such a problem.

In any case, we can certainly try it with one or two pages and reassess after a month or two. Any edits will only be visible immediately if made by reviewers or admins, and should any of them screw up (which is rather unlikely to happen, as you might imagine), the right can easily be removed; at the same time, autoconfirmed users will be empowered to suggest edits (to make a git analogy, that's kind of a pull request rather than a patch, where the final repository gets the actual authorship in the version history). So what do you say about a test trive?

Waldir (talk)13:30, 8 January 2013

It's no big deal. If it's just those 7 pages (I'm excuding the main page and Visual editor/Feedback which might still be linked in edit view from somewhere) I can do it immediately.

Nemo15:00, 8 January 2013

Great, please do. Just one question: what do you mean by "which might still be linked *in edit view* from somewhere"? a url with action=edit?

Waldir (talk)17:19, 9 January 2013
 
 
 
 

I thing this is a very good idea.

Countless times, I have wanted to improve - most often correct - a page or a template, and I gave up, because it was locked. → The wiki gets no gain.

Countless times also, I have edited a page, or a part of the home page, with flagged revisions, and my edit went live after a few hours or days. → The wiki gets improved.

However, in the proposal by Waldir, there is one thing I don't like : the part "except Reviewers". If we place a barrier in front of content editing, why would reviewers have a passe-droit ? Admins behaving "above the law" are a chronic disease in Wikipedia communities. If there is a good reason to allow reviewers to edit directly, then there is a good reason to allow everyone to edit directly.

Nnemo (talk)15:44, 21 October 2014

This is a dead horse, FlaggedRevs has been removed from MediaWiki.org.

Nemo05:27, 22 October 2014

If one has removed this, then one can put it back.

Nnemo (talk)14:00, 23 October 2014

But we aren't going to. Failed technologies need to be allowed to die.

Jdforrester (WMF) (talk)16:54, 29 October 2014
 
 
 
 

Wikimedia Engineering reports

The Wikimedia Engineering report for August is still a draft, the link to the September summary is a red link, and {{SoFixIt}} is not applicable. But WP:BRION is alive and kicking again.

Be..anyone (talk)07:43, 13 October 2014
Edited by author.
Last edit: 07:19, 16 October 2014

You gotta be kidding, "Previous reports" in the footer has three red links. :) m:Tech/News mostly replaced BRION. WMF reports are lagging behind due to some work shifts in their maintainers, AFAICS.

Nemo11:52, 14 October 2014

Well, those links worked seven years ago, before somebody intentinally "lost" his m+w passwords. :-| The new m:Tech/News/Latest is fine, I have a link to it on my user page.

Be..anyone (talk)17:17, 15 October 2014
 

The engineering reports have traditionally been published within two weeks after the end of a month. The reports for August and September were delayed due to several reasons, but the August report has now been published, and the September report is being drafted and will be published shortly.

That said, it's true that the engineering reports are very labor-intensive, and that's why we're considering replacing them by a more consistent combination of timely updates (in the form of Tech News and status updates) and quarterly retrospectives. See also the last paragraph of this wikitech-l email.

Guillaume (WMF) (talk)19:15, 28 October 2014
 

Toolserver wiki

I'd like to import several Toolserver wiki pages on this wiki, with some regex cleanup. I lean towards:

  • changing titles to pseudo-namespace format as we did for API etc., Toolserver:;
  • regex change of internal links (but not templates) so that they keep working;
  • run AnankeBot to add a template similar to Template:MoveToMediaWiki on top;
  • perhaps manually fix some active usernames to match this wiki (e.g. 'nemobis' -> 'Nemo bis').

Ideas?

Nemo09:33, 19 October 2014

What content specifically are you looking to import?

Peachey88 (talk)09:36, 19 October 2014

Toolserver wiki's.

Nemo11:04, 19 October 2014
 
 

[RESOLVED] rapid-fire vandalism from Ekkentros

Ekkentros (talk · contribs) is creating lots of nonsense pages. Could an admin please delete all of them?

Ixfd64 (talk)18:46, 13 October 2014

YesY Done by Tegel

The user is blocked with an expiry time of indefinite.

Florianschmidtwelzow (talk)20:42, 13 October 2014
 

[RESOLVED] vandalism from 2602:306:cc2e:efb0:59f:ad58:ff56:3a40

I'm not sure if this is the correct place to report vandalism, but 2602:306:cc2e:efb0:59f:ad58:ff56:3a40 (talk · contribs) keeps vandalizing Help:Templates.

Ixfd64 (talk)23:13, 1 October 2014

Hello!

Thanks for reporting this. The IP adress is actually blocked :)

Florianschmidtwelzow (talk)06:33, 2 October 2014
 

Translation of the sidebar items

I'm trying to translate the home MediaWiki sidebar, i. e. "Contribute". But the creation of MediaWiki:Mw-contribute/ca is blocked!?, only exists MediaWiki:Mw-contribute/ru for other language.

Jmarchn (talk)05:56, 9 October 2014

For interface messages you need the right "editinterface" to edit them. On mediawiki.org, only administrators have this right: Special:ListGroupRights :)

You can request user rights here (read the opener!).

Florianschmidtwelzow (talk)06:33, 9 October 2014
 

I don't think this deprecated function should still be installed at MediaWiki.org. Why not move all data of Special:Code to Phabricator and remove this extension from MediaWiki.org?

GZWDer (talk)08:14, 27 September 2014

Won't that create a lot of dead links?

If it can be done in a way that (a) doesn't break the web; and (b) means the content is still fully accessible then I don't have an objection, however if either of these is not possible then I strongly urge that it not be removed.

Perhaps a simpler answer would be to remove code-reviewing rights from everyone, so the pages remain but are no longer editable by anyone?

HappyDog (talk)08:46, 27 September 2014
 

Would you like to work on the migration code to move all data of Special:Code to Phabricator?

AKlapper (WMF) (talk)14:03, 27 September 2014

Not really, no.

HappyDog (talk)11:03, 28 September 2014

Oh, I didn't mean you, more the original requestor and her/his question "Why not move all data". :)

AKlapper (WMF) (talk)13:47, 28 September 2014
-)

Should have paid more attention to the indentation!

HappyDog (talk)13:57, 28 September 2014
 
 
 

Special:Code is very pretty and useful and it shouldn't be replaced without a clear benefit. In fact, some days ago I wanted to reply to a thread and I couldn't because it was frozen: which is okay and makes sense, but a bit against WikiNow.

Nemo20:45, 27 September 2014
 

I also have no time to write the code. However, is it possible to move data after data from gerrit is moved?

Maybe we should remove coder and svnadmin group from Mediawiki.org. It currently does nothing about CodeReview (though coder sill have autopatrol right). Extension:CodeReview can be on hold. But I still concern that keeping CodeReview is a risk if there're bugs in extension and this probably can be used by hackers.

GZWDer (talk)14:32, 28 September 2014

Phabricator will not even have comments from gerrit: http://fab.wmflabs.org/T42#46 I'd rather support importing gerrit comments into the CodeReview extension. ;-)

Nemo08:24, 29 September 2014

fyi, fab.wmflabs.org is closed.

GZWDer (talk)12:11, 29 September 2014

Which shows my point. ;-) Hopefully you can reach the place where my link went; if not, add to the reasons to keep CodeReview.

Nemo19:12, 29 September 2014
 
 
 
 

Please could someone change the URL to HTTPS or protocol-relative?

It Is Me Here t / c13:38, 27 September 2014

Done, thanks for the report.

Nemo20:42, 27 September 2014
 

Some documentation needs clarified

Sorry, but couldn't find any but seeming mutually contradictory information on the replace string extension. Is it alive on en.Wikibooks (meaning I have a likely precedence flaw) or not is WAS my 'Need'... but I answered my own question remembering I used it successfully a couple of months ago in another template.  

I'm continuing because...
the one reference page has two box headers which seem to contradict themselves at the very page top, and the bugzilla linked there seems to be open and unresolved--but with a mention that everything there was now incorporated into the wiki magicword system, but that and one other.

If I'm making the right mappings from my history:

  1. Extension:Replace Text probably has the two warring box notices right up top... as I went to Bugzilla from there.
  2. Wikitext parser/Core parser functions - says it should work (but someone ought to reconcile these!)
  3. Extension:String Functions#replace is a very unhelpful section header with an apparently included empty sub-page.

I'd take it on, but making sure of my ground in this realm of computer science geeks is like translating German to English to read how an Electrical geek like me has to use it! best regards,

FrankB23:25, 22 August 2014

Is it correct that you have not asked a question?

88.130.104.21723:32, 22 August 2014

Well a truly discerning read, especially of the links would have detected the message that there needs be a clarification, specifically on the string extensions of the parser functions. So no, my communication was more along the lines of a statement that this was a terrible situation that stinks!

  • However, it would appear here at least, programming standards apparently no longer include the ethic that No job is done until the paperwork is finished, so I'll just take me hits on my leisure time as a lesson, and further just finished donating a bit more of that scarce resource just so others don't get screwed over by that same lack of professional ethics. Please enjoy the embedded pic, which sums it up almost as good as an icon with someone holding their nose.
  • Lua scripts and CSS measures don't fix misleading references for a world wide audience that depends on these pages for reliable information. Sigh.
  • Further, the one thing apparently not fixed is the ability to replace spaces with underscores to reliably construct either a Wikimarkup section link, or a usable externally linkable url in templates, both of which I have need of in Wikibooks pages involving keyword-keyword pairs or keyword-phrase pairs—who'd have thought a space could turn into such a nasty enemy to productivity! // FrankB 18:53, 25 September 2014 (UTC)
FrankB18:53, 25 September 2014
No job is done until the paperwork is finished

Being involved in the documentation of Open Source projects myself, I can only agree. However, it is an obvious truth that developers do not like writing manuals nor documenting features. Basically, if you found something to be improved, I recommend: Go ahead and just do it! Chances are people will just be fine with it (which often means you never hear a word, but that is yet another topic).

As for the space issue, if you consider this a bug, you might want to file a BUGREPORT!

88.130.113.019:30, 25 September 2014

Given the bugzilla length, and the related (and reading between the lines, there are several that merged) I don't know how another might help. Further, that was why I posted here. Someone with a better handle on developments the last four years (not to mention scripting mysteries) needs to evaluate this and make that kind of call.

I will be glad to document trials of several templates where I'd expected b:template:Underscores to work the task, but it's no longer 'called' and I'd have to examine my saves (and contribs) and whatnot to refigure the trials. I'd not likely saved more than once or twice, then had to revert, so there will be some small trail. Mostly I debug in preview, so... those won't be visible. I might have an offline file or two as well. I use a programmers editor to match up curly-braces et.al. and other nesting in such templates. Easy peasey and saves a lot of grief. The rare revert will show up about that date though, so we could tell a sensible tale. //

FrankB02:12, 26 September 2014
 
 
 
 

lock special sites

A thread, Thread:Project:Current issues/lock special sites, was moved from here to Project:Support desk. This move was made by Ciencia Al Poder (talk | contribs) on 24 September 2014 at 10:22.

I've created a userbox, {{User ORCID}} for users who have an ORCID identifier. You can see it in use on my user page. ORCID identifiers disambiguate contributors with similar names, and unify the works of people who have published under different names. Anyone may sign up for one, free, and I encourage you to do so, and to display it using this template. More information on the use of ORCID identifiers by Wikimedia project editors may be found at w:en:WP:ORCID.

Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits20:40, 18 September 2014

But this isn't an issue, am i right?

Florianschmidtwelzow (talk)15:28, 19 September 2014

I guess it's just an "announcement", but there isn't a place for internal announcements here so this seems to be the best place ATM

Ciencia Al Poder (talk)15:46, 19 September 2014

Argh, it's Current_issues, i thought it is Support_desk :) Thx for the hint Ciencia Al Poder.

Florianschmidtwelzow (talk)16:41, 19 September 2014
 
 
 

Doesn't do anything

A thread, Thread:Project:Current issues/Doesn't do anything, was moved from here to Project:Support desk. This move was made by Ciencia Al Poder (talk | contribs) on 19 September 2014 at 15:46.

New links not acknowledging that page exists

A thread, Thread:Project:Current issues/New links not acknowledging that page exists, was moved from here to Project:Support desk. This move was made by Nemo bis (talk | contribs) on 17 September 2014 at 06:12.

Page creation glitch

When I tried to create a new userpage, I got this peculiar problem: File:Bobrayner pagecreation problem.jpg

  • MediaWiki is trying to warn me that I'm creating a new page, but this notice can seemingly only be triggered by users who willingly click on the "Create" link or similar (not just by navigating to a currently-redlinked page), so why is a warning necessary?
  • The notice is malformed and unreadable, apparently due to being put inside a narrow frame which takes up the left half of the notice area, and the leftmost strip of the warning is devoted to a pointless image which only takes a small % of the vertical height.
  • Also, on trying to search this page for any related issue, I get "An error has occurred while searching: HTTP request timed out.". Sorry if this is a duplicate.

Any suggestions?

Bobrayner (talk)18:29, 6 September 2014

The first two appear to be some VisualEditor issue. The other is about the old search system which is being discountinued (see Search) but still has some leftovers: please use Special:Search instead.

Nemo22:24, 6 September 2014
 

The first (the warning) is triggered when you navigate to a redlink. Go to Special:RecentChanges and click on any red-linked username, and you'll get the same message at the top of the wikitext editing window.

The second is a problem with the design of the template. It was designed to be displayed on a particular shape of a screen. You'll see the same mess in the wikitext editor if you have a very narrow screen (e.g., anyone using a smartphone over Mobile web, or if you drag your browser window to be narrow). It should be possible to make the text wrap around the icon, but the person designing it (years ago) was only thinking about how it would display for desktop users using the wikitext editor (because that's pretty much all there was back then).

Whatamidoing (WMF) (talk)18:04, 11 September 2014
 

LQT search boxes on this site hit HTTP timeout atm.

I'm using HTTPS and experience this issue. That is all.

Gryllida10:54, 31 August 2014

Someone added a topic summary, but I don't see who. Thanks though for identifying the issue and reporting it!

Gryllida12:15, 4 September 2014

It's still silly to link a dead feature and newbies were getting confused, so I hid the search box: [1]. Surely there is some configuration setting or hook to do it properly?

Nemo05:35, 7 September 2014

Best configuration remedy for this would be to disable LQT.

Max Semenik (talk)07:51, 7 September 2014
 
 

Email, watchlist, and notifications

A thread, Thread:Project:Current issues/Email, watchlist, and notifications, was moved from here to Project:Support desk. This move was made by Nemo bis (talk | contribs) on 6 September 2014 at 19:35.

[RESOLVED] order reversed for Special:MyContributions?

I don't remember changing any of my personal preferences, but when I look at my contributions (Special:MyContributions) the list starts with the earliest edits and there's no way to reverse the order. (The watchlist, on the other hand, still looks the same to me)

Cavila (MW 1.22, MySQL 5.5.37-0, Php 5.4.4-14 squeeze, SMW 1.9.2, SF 2.7)22:27, 4 September 2014

Things are back to normal, so the (temporary) changes must have been restored.

Cavila (MW 1.22, MySQL 5.5.37-0, Php 5.4.4-14 squeeze, SMW 1.9.2, SF 2.7)06:46, 5 September 2014
 

Just for information: This was a bug in new MediaWiki 1.24wmf20 tracked in bug 70413. It was hot fixed for mediawiki.org and testwiki yesterday :) So that's why all is ok now :)

Florianschmidtwelzow (talk)11:10, 5 September 2014

Alright, thanks for the explanation.

Cavila (MW 1.22, MySQL 5.5.37-0, Php 5.4.4-14 squeeze, SMW 1.9.2, SF 2.7)13:12, 5 September 2014
 
 

Enable DynamicPageList

Meta-Wiki, along with hundreds Wikimedia projects, has DynamicPageList enabled. It's trivial to enable it here as well, but it wasn't done yet, yet e.g. I need it on Project:Language_policy/Migration_list to intersect 1 with non-2.

So I ask the MediaWiki.org community: any objection to enabling it here?

Nemo14:55, 8 August 2014

+1!

Florianschmidtwelzow (talk)16:51, 8 August 2014

What would be the purpose? Can you give some examples of how it might be useful on this wiki?

HappyDog (talk)10:17, 9 August 2014

I gave one in the first message. You can also click edit on that page to see the syntax.

Nemo10:55, 9 August 2014

Oops - yes, silly me!

Sounds like it is not something we generally need, but which might have the odd occasional use such as this. I don't have any objection to it being enabled.

HappyDog (talk)07:55, 10 August 2014
 
 
 

+1!

Gryllida09:56, 25 August 2014
Edited by 2 users.
Last edit: 00:25, 1 September 2014

Done!

Nemo04:55, 29 August 2014

<3!

Gryllida10:53, 31 August 2014
 
 
 

How to to get password reset for account on this site which has no email address

I've got an account here which I started back in 2006, but I forgot my password and it seems that in this case I neglected to set up an email address for my username. Thus the Reset Password page just says: "There is no email address recorded for user <xxxxx>". Oops!

So I'd like a password reset sent to the email address I use for the same username on several other Wikipedia projects. I can think of several ways to demonstrate that I'm the same person. Is there a way to privately submit a request to the admins here? Or some other option? Thanks!

24.9.62.24116:12, 6 August 2014

If the account is the same as Wikipedia, the password should also be the same. You should check Special:CentralAuth/YourAccountName and see if the MediaWiki.org account is linked.

Ricordisamoa23:39, 6 August 2014

Thanks for the quick response. This account was set up before there was that sort of linking of accounts. They are not linked, and the password is different. So I'm still looking for some help here.

24.9.62.24121:56, 7 August 2014

I'm sorry, but there's nothing we can do about that. If you don't have the email address and you don't remember the password, we cannot retrieve the account for you.

Jorm (WMF) (talk)02:32, 14 August 2014

Well, almost. On the off chance you set up a committed identity (if you don't know what that is, then you didn't), you can use that to prove you own the account and get it back.

Jackmcbarn (talk)02:56, 14 August 2014

I would like to know what it is, please.

Gryllida09:55, 25 August 2014
 
 
 
 
 

left menu problem

A thread, Thread:Project:Current issues/left menu problem, was moved from here to MediaWiki talk:Sidebar. This move was made by Qgil-WMF (talk | contribs) on 14 August 2014 at 14:40.
First page
First page
Previous page
Previous page
Last page
Last page