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
"Now with mustache" logo517:10, 27 February 2015
error in update with by web browser in MediaWiki Language Extension Bundle014:54, 27 February 2015
Special:Translate not working106:06, 26 February 2015
Wikimedia Engineering reports621:21, 25 February 2015
Failed to mark for translation711:54, 26 February 2015
Api documentation bot908:45, 23 February 2015
[RESOLVED] API-head113:25, 22 February 2015
Change a red link007:47, 21 February 2015
MediaWiki:Noarticletext/zh-tw207:46, 21 February 2015
Fwd: Allow sysops to self-grant translation administrator008:23, 11 February 2015
Error upload Files in MediaWiki121:13, 4 February 2015
[RESOLVED] Include API: and Skin: in default search namespaces821:36, 13 January 2015
[RESOLVED] password115:31, 8 January 2015
Seach to a specific page/word013:42, 2 January 2015
Extension:CodeReview1018:56, 19 December 2014
[RESOLVED] MediaWiki:Titleblacklist720:29, 16 December 2014
Installation guide consolidation611:52, 16 December 2014
[RESOLVED] User:MisterLambda was blocked in error207:06, 15 December 2014
Index119:09, 6 December 2014
What spam are our captchas stopping?009:02, 5 December 2014
First page
First page
Previous page
Previous page
Last page
Last page

"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
 

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 https://www.wikimedia.org 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, https://gerrit.wikimedia.org/r/181708 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
 
 
 

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

We were dealing with a problem during installation MediaWiki Language Extension Bundle in step upadte database with by web browser

[f18f0cca] /mediawiki/mw-config/ Exception from line 341 of /home/mechir/domains/wikimech.org/public_html/mediawiki/includes/MagicWord.php: Error: invalid   magic word 'babel'
Backtrace:
#0 /home/mechir/domains/wikimech.org/public_html/mediawiki/includes/MagicWord.php(264): MagicWord->load(string)
#1 /home/mechir/domains/wikimech.org/public_html/mediawiki/includes/parser/Parser.php(5159): MagicWord::get(string)
#2 /home/mechir/domains/wikimech.org/public_html/extensions/Babel/BabelStatic.class.php(22): Parser->setFunctionHook(string, array)
#3 [internal function]: BabelStatic::onParserFirstCallInit(Parser)
#4 /home/mechir/domains/wikimech.org/public_html/mediawiki/includes/Hooks.php(206): call_user_func_array(string, array)
#5 /home/mechir/domains/wikimech.org/public_html/mediawiki/includes/GlobalFunctions.php(3995): Hooks::run(string, array, NULL)
#6 /home/mechir/domains/wikimech.org/public_html/mediawiki/includes/parser/Parser.php(279): wfRunHooks(string, array)
#7 /home/mechir/domains/wikimech.org/public_html/mediawiki/includes/parser/Parser.php(291): Parser->firstCallInit()
#8 /home/mechir/domains/wikimech.org/public_html/mediawiki/includes/parser/Parser.php(5000): Parser->clearState()
#9 /home/mechir/domains/wikimech.org/public_html/mediawiki/includes/parser/Parser.php(377): Parser->startParse(Title, ParserOptions, integer, boolean)
#10 /home/mechir/domains/wikimech.org/public_html/mediawiki/includes/installer/Installer.php(631): Parser->parse(string, Title, ParserOptions, boolean)
#11 /home/mechir/domains/wikimech.org/public_html/mediawiki/includes/installer/WebInstaller.php(676): Installer->parse(string, boolean)
#12 /home/mechir/domains/wikimech.org/public_html/mediawiki/includes/installer/WebInstallerPage.php(392): WebInstaller->getInfoBox(string)
#13 /home/mechir/domains/wikimech.org/public_html/mediawiki/includes/installer/WebInstallerPage.php(380): WebInstallerExistingWiki->showKeyForm()
#14 /home/mechir/domains/wikimech.org/public_html/mediawiki/includes/installer/WebInstaller.php(280): WebInstallerExistingWiki->execute()
#15 /home/mechir/domains/wikimech.org/public_html/mediawiki/mw-config/index.php(79): WebInstaller->execute(array)
#16 /home/mechir/domains/wikimech.org/public_html/mediawiki/mw-config/index.php(38): wfInstallerMain()
#17 {main}

in main page by url www.wikimech.org/mediawiki The following message:

A database query error has occurred. This may indicate a bug in the software.
Wikimech org (talk)14:54, 27 February 2015

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@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
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

Yes, but not everyone. Thanks for reporting.

Nemo17:45, 9 January 2015
 

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

Hi, please let the first missing Wikimedia Engineering/Report/2015/January explain that the monthly reports are now finished for good, I still had a convoluted [[Wikimedia Engineering/Report/{{#time:Y/F|now-31days}}|Tech report]] for {{#time:F|now-31days}} rendered as "Tech report for January" on my user page.:tongue:

Be..anyone (talk)09:08, 24 February 2015

Thank you for following up: I'm waiting for the new system to be in place before announcing that the reports in their old format are officially been retired. See also T88468, T88470 and T24.

Guillaume (WMF) (talk)16:44, 24 February 2015

I've updated three related pages on this side:

  1. On Wikimedia Engineering/Report/2014 red link "2015" now goes to phabricator:tag/report/
  2. On Wikimedia Engineering/Report/2015/January phab:T88470 is flagged as "resolved".
  3. On draft m:Tech/News/2015/10 the issue is noted as "future change" announcing the tag.
Be..anyone (talk)21:21, 25 February 2015
 
 
 
 

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

Still happening... please file a bug, hopefully the WMF DB admin will help.

Nemo15:01, 26 January 2015

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.

Nemo21:55, 11 February 2015

> 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

The bug wasn't fixed yet. :(

Nemo07:55, 21 February 2015

Can someone search if a bug was filed? I saw something somewhere about clearGroup, but I can't find a thing in Phabricator.

Nemo13:58, 23 February 2015

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
 
 
 
 
 

Api documentation bot

Hi,

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
 
 

[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

It has been done.

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

Change a red link

A thread, Thread:Project:Current issues/Change a red link, was moved from here to Project:Support desk. This move was made by Nemo bis (talk | contribs) on 21 February 2015 at 07:47.

(很抱歉,我不會英語。)
translatewiki那邊早已修正錯誤了,為何這裡還沒有更新?請把搜索改成搜尋,謝謝!

-- By LNDDYL. (Talk)08:52, 20 February 2015

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
 
 

Fwd: Allow sysops to self-grant translation administrator

Proposed by Florian, MZMcBride, Glaisher and devunt at phabricator:T87797.

Nemo08:23, 11 February 2015

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/Thread:Project:Support_desk/The_file_you_uploaded_seems_to_be_empty_-_Windows_Server_2008_R2

Anyone can suggested how to resolve this problem?

170.252.72.6116:46, 4 February 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
 
 
 

[RESOLVED] password

Told my password was wrong, I reset it. Got new temp PW in email. Trying to log in with that. being told my password is wrong.

204.108.16.15918:26, 22 December 2014
Edited by 0 users.
Last edit: 18:28, 22 December 2014

finally able to log in. Nevermind

Dbrezenoff (talk)18:28, 22 December 2014
 

Seach to a specific page/word

A thread, Thread:Project:Current issues/Seach to a specific page/word, was moved from here to Project:Support desk. This move was made by Ciencia Al Poder (talk | contribs) on 2 January 2015 at 13:42.

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
 
 
 
 

Hi! There is a problem with one BlackList entry. This one:

#Allows creation of pages with titles too similar to existing pages
.*(е|а|о).*

It doesn't allow (new) users with cyrillic SUL name to login to MediaWiki site. Cause they usually contain these cyrillic (е|а|о) characters. You need to either remove this entry or improve it somehow.

Piramidion (talk)13:33, 4 December 2014

@Jasper Deng: Can you take a look?

Florianschmidtwelzow (talk)13:48, 4 December 2014

@Jasper Deng:@Florianschmidtwelzow: A week has passed. Anything? Our users still cannot enter MediaWiki site nor create their own user pages if their SUL usernames contain any of these 3 characters. The only exception is for those users with cyrillic SUL names who had registered here before this blacklist entry was enabled. Are you gonna do anything about that or should I address someone else to solve this problem?

Piramidion (talk)13:58, 11 December 2014

@Piramidion: I have commented out this rule for now, so it should work, if this is the real problem. Can you test it and give a response, if it works now?

@Jasper Deng: We should check, if we need this rule and should re-enable it with some adjustment?

Florianschmidtwelzow (talk)07:17, 15 December 2014

Thanks! I will tell the user(s) who couldn't enter MediaWiki under their own SUL login to try again. Earlier one user (now an administrator on ukwiki) had got the message that "this username is blacklisted on MediaWiki" or something like that. Now it should be fine. I will post the result here.

Piramidion (talk)19:14, 15 December 2014
 

Yes, it works! You can check it yourself :) Thanks again!

Piramidion (talk)19:31, 15 December 2014

Great :) YesY Done

Now we just need to figure out, how we can use this rule, without this behavior :P

Florianschmidtwelzow (talk)13:30, 16 December 2014
 
 
 
 
 

Installation guide consolidation

Edited by author.
Last edit: 11:48, 16 December 2014

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
 

I made Manual:LocalSettings.php translatable and expanded Manual:System administration by merging Manual:Configuration.

  • Manual:System administration could be useful if it becomes a reasonable index/step by step guide/tutoring of the really important pages in Category:MediaWiki for site admins (allowing to remove respective information from the general installation manual), but I'm not sure of its current role.
  • Manual:LocalSettings.php is very visited, but it's quite a mess. I doubt it kept anywhere close up to date, is it currently making a good service to users?
Nemo07:50, 9 August 2014

I wonder what's the purpose of making Manual:LocalSettings.php translatable if you doubt about the usefulness of that page or if you plan/propose to improve/restructure it.

Ciencia Al Poder (talk)18:36, 10 August 2014

The page is vastly correct and the strings contained in it look rather stable, so it's ok to translate it. It is my impression that some consolidation will be needed for that page (reducing total amount of text around), but not a rewriting.

Nemo19:10, 10 August 2014

I've tried to make the essential stuff transcludable, and I've trimmed some more pages.[1]

IMHO the direction is rather clear:

  • always defer to other sites for guides on how to set up PHP etc.;
  • keep all the steps internal to MediaWiki (like installer, config script, LocalSettings.php) in their own, shared manual pages;
  • in all the setup-specific pages, just transclude the former and maintain only:
    • information on packages available and how to use them (debatable, should be on their sites whenever possibles),
    • OS-specific instructions which can't be found anywhere else, like specific paths to put in MediaWiki config or RAM/suhosin requirements and the like.
Nemo11:52, 16 December 2014
 
 
 
 

[RESOLVED] User:MisterLambda was blocked in error

I am making this thread on his behalf.

User:MisterLambda is blocked for being a "vandalism-only account". From what I've observed, his account has not performed any vandalism, and his contributions include an extension.

Frozen Wind (talk)01:23, 15 December 2014

I'm not sure what happened, but I unblocked him.

Daniel Friesen (Dantman) (talk)02:57, 15 December 2014
 

What spam are our captchas stopping?

Some hours ago, FancyCaptcha was disabled on this wiki for 18 minutes. There was some more spam coming in as result, let's find out at Extension:ConfirmEdit/FancyCaptcha experiments exactly how much and what abusefilters can be set up to reliably stop it.

Nemo09:02, 5 December 2014
First page
First page
Previous page
Previous page
Last page
Last page