Some pages use

 
<languages /> (as https://www.mediawiki.org/wiki/Manual:Interface/Sidebar) 
<languages /> (as https://www.mediawiki.org/wiki/Extension:CodeMirror)
{{languages}} (as https://www.mediawiki.org/wiki/Manual:Code). 

what is the difference ? when and what to use really ? thank you.

Christian Wia (talk) 09:37, 1 August 2019 (UTC)

Manual:Code is not marked for translation. I think you get the point. Shirayuki (talk) 14:03, 1 August 2019 (UTC)

Template form is old system before extension:translate installed. The extension comes with new translation method and adds this tag to automatic generate list of languages. On pages marked to use new system you should use tag. wargo (talk) 09:06, 4 August 2019 (UTC)

Hi all, on page https://www.mediawiki.org/wiki/Help:System_message , after T10="Finding messages and documentation" i.e. in T11, the link complete documentation in the qqq pseudo-language leads to a number of items to reread in translatewiki (...strange?) where translation language = 'documentation of the message'  ; please can anyone correct ?

How each message is used by MediaWiki, variables available, parameters used, limitations, et cetera is explained with the [<tvar|twn>//translatewiki.net/w/i.php?title=Special%3ATranslate&task=reviewall&group=core&language=qqq&limit=5000&tux=0</> complete documentation in the qqq pseudo-language] files,....

Christian Wia (talk) 12:16, 3 August 2019 (UTC)

Done. "action=page" and explicit "page=" are required. Shirayuki (talk) 12:49, 3 August 2019 (UTC)

Hi all, on page https://www.mediawiki.org/wiki/Help:Magic_words parser functions speak of {{#foo:...}} but for my translations I often met following format with a pipe {{int|whatlinkshere} Is then 'int' still a magic word ? Manuals says adding the possible MediaWiki: prefix, but page "https://www.mediawiki.org/wiki/MediaWiki:Whatlinkshere" used to exist and has been suppressed. I m a bit lost. Where can I find the documentation to understand which parameters of 'int' are recognized or not ? Thank you.

Christian Wia (talk) 14:17, 3 August 2019 (UTC)

The pipe version is Template:Int which is actually wrapping the colon version which is the global magic word. The pipe version does work only on a wiki where such template is defined, while the magic word is always available.

Basically both approaches lead to the same result, but in some edge cases the template is more comfortable.

There are thousands over thousands of possible keywords, and every week some dozens are added and some dozens become invalid.

You may visit translatewiki: and filter for MediaWiki messages. PerfektesChaos (talk) 17:03, 3 August 2019 (UTC)

ok so for everyone to understand when you see the pipe, you go to translatewiki, hit on the 'MediaWikiproject', hit 'Translate' button, select 'ALL messages', enter your text i.e. 'whatlinkshere' in the filter box, wait among the 34700 messages .... and wait .... and wait ....

At the end you have all messages containing the string 'whatlinkshere' (today 6 occurences) so I expected to found my single word alone somewhere with its equivalent but there is no such match!

So again Question: => please can someone explain how to reach the translated text starting from the int| parameter ?

One can also request about what is the result of the template for a not translatable text. Let us say we make a mistake and write the improbable 'int|whatlinxhere' . I have made the test and reply is '⧼whatlinxhere⧽'.

Christian Wia (talk) 07:04, 4 August 2019 (UTC)

This is message name started with mediawiki: prefix. On translatewiki you can also view specific "page" for message(s) and with langcode subpage. For example: Mediawiki:whatlinkshere. wargo (talk) 09:02, 4 August 2019 (UTC)

As I said in the subject, the Mediawiki:whatlinkshere has a banner 'this page has been suppressed'. ....so what must the reader understand  ?

Cette page a été supprimée. Les journaux des suppressions, protections et déplacements pour la page sont fournis ci-dessous pour référence.

1 mars 2009 à 15:17 Toliño a supprimé la page MediaWiki:Whatlinkshere (content was: 'Was gleicht do ane?' (and the only contributor was 'Strommops'): that's not English) (remercier)

5 janvier 2007 à 23:56 MediaWiki default a supprimé la page MediaWiki:Whatlinkshere (No longer required) Christian 🇫🇷 FR 🚨 (talk) 09:18, 4 August 2019 (UTC)

Pages in the MediaWiki namespace are special. If the page does not exist or has been deleted, then it may still have content if there's a message associated with it, and it will display the default message in the wiki's content language.

As you can see, even deleted, the page displays some text. Ciencia Al Poder (talk) 09:25, 4 August 2019 (UTC)

Ok I see SOLUTION: you must NOT go on https://translatewiki.net/wiki/Mediawiki:whatlinkshere but stay on mediawiki.org.

In this case I have https://www.mediawiki.org/wiki/MediaWiki:Whatlinkshere/fr where I get "Pages liées" which is the correct answer.

... a beer now 🍺 ! Christian 🇫🇷 FR 🚨 (talk) 09:34, 4 August 2019 (UTC)

The colon version uses the user interface language .

But the pipe version always follows the page content language (for documentation use). Shirayuki (talk) 22:25, 3 August 2019 (UTC)

Hello everyone, As part of my Google Summer of Code project, I have developed code snippets in PHP, Python and MediaWiki Javascript to demonstrate the use of MediaWiki Action API modules. All these code samples will be shown in a tabbed window in all the API module pages on MediaWiki.org like in https://test.wikipedia.org/wiki/API:Sandbox via a Gadget. This Gadget also deployed in MediaWiki.org. But it is not done yet for non-login users. For Login users, you can enable it from Special:Preferences-> Gadgets.

1. API:Tokens
2. API:Opensearch

After enabling the gadget, you can checkout above pages. I am looking for your suggestions and feedback to enable it for non-login users as well. So that we can do on-wiki API documentation. Thank you :) Jayprakash12345 (talk) 13:48, 4 August 2019 (UTC)

Combining the different languages into a single section on the page is a good idea since it takes up less space. ☠MarkAHershberger☢(talk)☣ 02:35, 5 August 2019 (UTC)

A couple of issues:

The table of contents of the page has now this structure:

2 Example
2.1 GET request
2.2 Response
2.3 Sample code
2.4 Python
2.5 PHP
2.6 Javascript
2.7 MediaWiki JS

• 2.4 through 2.7 should probably be nested as child of 2.3
• When clicking the link from the TOC to those tabbed sections, the link doesn't work. It would be good to scroll and switch to the corresponding tab, or if that's not possible, at least scroll to the section. Ciencia Al Poder (talk) 09:08, 5 August 2019 (UTC)

Weird, We have already removing the TOC link like Python, PHP and Javascript etc by the gadget as OOUI does not support to set the id of tab directly. Can you check again with hard reset? Jayprakash12345 (talk) 01:49, 6 August 2019 (UTC)

Still the same. I'm using Firefox Ciencia Al Poder (talk) 09:15, 6 August 2019 (UTC)

I don't normally use Chrome, so I visited the page in Chrome (77.0.3865.10 (Official Build) dev (64-bit)) and saw that 2.4-2.7 were still there. ☠MarkAHershberger☢(talk)☣ 16:28, 6 August 2019 (UTC)

I tested the Gadget in three different browsers, and I don't see section 2.4-2.7 show up in the TOC. More info on the browser versions:

• Firefox: 68.0.1 (64-bit)
• Chrome: 75.0.3770.142 (Official Build) (64-bit)
• Safari: 12.1.1

@MarkAHershberger @Ciencia Al Poder I'm wondering if you were logged in when you tried to view the API:Tokens or API:Opensearch page in your browser. As this Gadget is not set as default / enabled for everyone, it won't work as expected if you are not logged in. User:SSethi_(WMF) 00:05, 8 August 2019 (UTC)

Yes, I'm logged in because otherwise the gadget won't run :)

Screenshots:

• https://snag.gy/kDioh4.jpg
• https://snag.gy/c4bGmr.jpg Ciencia Al Poder (talk) 09:16, 8 August 2019 (UTC)

"Yes, I'm logged in because otherwise the gadget won't run :)"

Aha! You maybe be happy to learn, that it is possible to test gadgets whilst logged-out. See Snippets/Load JS and CSS by URL. For example https://en.wikipedia.org/wiki/Foobar?withCSS=MediaWiki:Gadget-Blackskin.css  :) –Quiddity (talk) 16:24, 8 August 2019 (UTC)

Good to know! That would have ruled out problems with gadgets by opening it as a private window :)

https://www.mediawiki.org/wiki/API:Tokens?withJS=MediaWiki:Gadget-tabbedwindow.js Ciencia Al Poder (talk) 21:10, 8 August 2019 (UTC)

Just one question more, Can you see your web console error and warnings And paste here if any? Jayprakash12345 (talk) 11:26, 8 August 2019 (UTC)

Nothing relevant.

Being curious as to what could be failing, I reviewed the code and found that my section headers had a slightly different structure than what the script expects. Then I remembered having the HeadAnchor gadget active, which is what's causing the script to not function properly. If I deactivate that gadget, it works as you described. Sorry for the confusion! Ciencia Al Poder (talk) 15:32, 8 August 2019 (UTC)

On page https://www.mediawiki.org/wiki/Manual:Recentchanges_table/fr#rc_namespace , there is a floating text in english not translated : "(Incorrect. redirect table records redirect to special pages in this way as well.)" . We cannot detail a topic and declare that what we say is incorrect. Either it should be a lost comment of the ENglish page for a further documentation, or it should be translated but article need to be reformulated. Can someone clarify please ?

Christian Wia (talk) 14:35, 5 August 2019 (UTC)

I've removed that, which isn't really useful information Ciencia Al Poder (talk) 18:45, 5 August 2019 (UTC)

please see https://www.mediawiki.org/wiki/Skin%20talk%3AMinerva%20Neue/2019#h-Rereading%3A_red_link_found_for_MediaWiki%3ARandom-url-2019-08-11T11%3A30%3A00.000Z Christian 🇫🇷 FR 🚨 (talk) 11:40, 11 August 2019 (UTC)

Hi all. Following page rereading I see a red link on 'suphp' of "If using suphp, make sure...." at paragraph https://www.mediawiki.org/wiki/Manual:Configuring_file_uploads#Check_directory_security

Is that rather 'suPHP' ? but how can we correct ? redirect ? suppress ? Thank you. Christian 🇫🇷 FR 🚨 (talk) 12:21, 11 August 2019 (UTC)

suPHP is no longer maintained (since 2013!). Although there's a fork, I doubt people are actually using it. So I've removed all references to it Ciencia Al Poder (talk) 18:05, 11 August 2019 (UTC)

Hi all, re-reading page

https://www.mediawiki.org/wiki/Manual_talk:Configuring_file_uploads

(or other more generic to uploads) I dont see where is described the action following the upload of a too big file: is the upload rejected ? (with failure return code) or is it done with truncation to the limit size ? or is there a dialogue with user to transfer till limit or abort for this file? or ... ? Even if the answer is obvious it 'd be nice to have one simple sentence about that. Thanks.

Christian Wia (talk) 21:33, 11 August 2019 (UTC)

If the upload is too big, it is rejected. The server can often do this before any of the file is transmitted because the browser will tell the server the size before it actually sends the file. ☠MarkAHershberger☢(talk)☣ 01:23, 12 August 2019 (UTC)

By "The server can often do this" you probably wanted to say "The browser can often do this".

When it fails, the server can give multiple errors depending at which layer the limit was imposed: If it's a server limit (nginx, apache) on the maximum amount of transmitted data, it may simply fail with a HTTP 500 error or HTTP 413 – Request entity too large.

If the limit it's at the PHP level, if post_max_size is hit, you may get a generic HTTP 500 error (or simply a blank page). Otherwise, MediaWiki should give a more meaningful error message Ciencia Al Poder (talk) 09:04, 12 August 2019 (UTC)

I wait a bit and I will try to sum up all these informations ... Christian 🇫🇷 FR 🚨 (talk) 11:04, 12 August 2019 (UTC)

ok sum up as:

Browsers tell the server the size of the file to be uploaded before it actually sends the file.
If the upload is too big, it is rejected by the target (server) and the upload fails providing multiple errors depending at which layer the limit was imposed: 
* If it's a server limit (nginx, Apache) on the maximum amount of transmitted data, it may simply fail with a HTTP 500 error or HTTP 413 – Request entity too large.
* If the limit it's at the PHP level, if post_max_size is hit, you may get a generic HTTP 500 error (or simply a blank page) otherwise, MediaWiki should give a more meaningful error message.

Christian 🇫🇷 FR 🚨 (talk) 13:08, 24 August 2019 (UTC)

So they decided at Commons to unify files or whatever without considering that this will break a heavily used template here. I tried to fix with this edits however I obviously still do not master the TemplateStyles extensions mechanics. I figured switching to the existing file is enough. Purging and whatever does not help either. Dunno what to do?? To me this appears to be a 2 second task and yet again I already spend 10 minutes on this. I am super grumpy and look for help. Thanks [[kgh]] (talk) 23:20, 15 August 2019 (UTC)

It worked on the actual styles page (not sandbox). Maybe the sandbox doesn't work for styles? Ciencia Al Poder (talk) 09:20, 16 August 2019 (UTC)

Ah, ok, not I get this. Thanks a ton for your help! [[kgh]] (talk) 12:23, 16 August 2019 (UTC)

On page https://www.mediawiki.org/wiki/Manual:Cache

when accessing at bottom the link "Guide about object cache with Saetta Web Server and MediaWiki" (=> http://blog.izysoftware.com/?p=28 ) then the target is no longer existing:

blog.izysoftware.com/?p=28 =>  This Domain Has Expired, To Renew Please Contact Your Provider.

Shall I remove the reference ?

Christian Wia (talk) 18:14, 22 August 2019 (UTC)

sounds appropriate, yes. ☠MarkAHershberger☢(talk)☣ 18:48, 22 August 2019 (UTC)

Hi all, on page https://www.mediawiki.org/wiki/Manual:File_cache we say at the beginning "Any subsequent requests from anonymous users are met not by rendering the page again, but by simply sending the stored HTML version which is on the disk. This saves time." but there is no explaination for what happens with connected users. Why this 'advantage' is reserved for anonymous users? do connected users also use the cache? (I hope so) and what is the process for them ? Can someone develop this to complement the paragraph? Thanks.

Christian Wia (talk) 14:20, 23 August 2019 (UTC)

Logged-in users don't benefit from this cache. Basically, because this cache consists of the entire HTML of the page. Logged-in users have difference in the HTML. The main reason is the user name present at the user links (user page, talk, etc, on vector and monobook they're at the top-right corner), and also user preferences like the selected skin, etc. Only anonymous users have the same HTML rendered, that's why this only applies to them. Ciencia Al Poder (talk) 16:34, 23 August 2019 (UTC)

marvellous ! sumed up as "The file cache serves anonymous users only and they see the same HTML rendered. Logged-in users don't benefit from this cache because their page contains user name, selected skin, etc." Christian 🇫🇷 FR 🚨 (talk) 12:37, 24 August 2019 (UTC)

When accessing paragraph 'Examples' in https://www.mediawiki.org/wiki/Manual:Language#Page_content_language , link https://translatewiki.net/wiki/Project_list/ar leads to the root of site translatewiki.net , instead of prodiving the list of projects in arabic. How we can transform the URL to get that ? Thanks.

Christian Wia (talk) 10:58, 27 August 2019 (UTC)

It is a redirect.

https://translatewiki.net/wiki/Project_list/ar?action=edit Shirayuki (talk) 11:15, 27 August 2019 (UTC)

Have you tried at least ?

In text "See translatewiki:Project list/ar as a translation of translatewiki:Project list. The directionality of the page is thus correctly set to right-to-left for Arabic."

the first link shows => https://translatewiki.net/wiki/Project_list/ar which is the logon page of https://translatewiki.net/

The second link acts the same way. May be some one provide a simpler example for a case always working to illustrate the topic ? Thanks. Christian 🇫🇷 FR 🚨 (talk) 11:36, 27 August 2019 (UTC)

https://translatewiki.net/wiki/Project_list?action=edit is also a redirect.

These pages were removed from translation on June 6, 2018. Shirayuki (talk) 11:42, 27 August 2019 (UTC)

The topic of the paragraph is not about redirections. The question is to provide to our readers concrete examples of what we say and not to drive them into a dead end. Please dont hurry, may be some one will provide a simpler example for a case always working to illustrate the topic ? Thanks. Christian 🇫🇷 FR 🚨 (talk) 16:39, 27 August 2019 (UTC)

EMWCon Spring 2019/Dockerizing MediaWiki Setup has an incorrect link to a docker-compose.yml.j2 file. It looks like the correct link is https://github.com/dataspects/dataspectsSystem/blob/master/ansible_templates/docker-compose.yml.j2, but an abusefilter prevented the edit. 90.246.247.96 (talk) 09:01, 28 August 2019 (UTC)

Done Shirayuki (talk) 09:12, 28 August 2019 (UTC)

From page https://www.mediawiki.org/wiki/Manual:Title.php/fr I try to click on link {{PAGENAME}}.

Original form of {{PAGENAME}} is #REDIRECT Help:Magic_words#Page_names which leads to corresponding section of EN page.

I want to skip to the equivalent section but of the translated FR page.

I try #REDIRECT [[{{ll|Help:Magic_words#Page_names}}]] but it doesnt redirect.

I try #REDIRECT [[Special:myLanguage/Help:Magic_words#Page_names]] which is accepted as a redirection but doesnot jump.

What is the most clever form working ? Thanks.

Christian Wia (talk) 16:49, 29 August 2019 (UTC)

It jumps for me (opening Help:Magic_words/fr#Page_names works as expected) Ciencia Al Poder (talk) 19:26, 29 August 2019 (UTC)

I redo - and I m sorry but if I take PAGENAME in https://www.mediawiki.org/wiki/Manual:Title.php/fr as example just before getDBKey : ....y a après. Voir le mot magique {{PAGENAME}}. getDBKey()

it links to "https://www.mediawiki.org/wiki/Help:Magic_words#Page_names" and not in the FR. Can you explain what you have done ?

In other words if the contents of the redirection is "Help:Magic words#Page names" how do you explain you can access to "Help:Magic words/fr#Page names" without additional conversion ?

In clear I wish to code #REDIRECT [[{{ll|Help:Magic_words#Page_names}}]] but it is not redirecting although {{ll|Help:Magic_words#Page_names}} provides the right target. Christian 🇫🇷 FR 🚨 (talk) 19:49, 29 August 2019 (UTC)

I have fixed Manual:Title.php and Help:Magic words.

#REDIRECT does not support Special:MyLanguage. Shirayuki (talk) 22:11, 29 August 2019 (UTC)

yes better to get rid of the redirection (...) if we know directly where we are going.

I document bit this aspect of not working redirections, on page https://www.mediawiki.org/wiki/Help:Redirects Christian 🇫🇷 FR 🚨 (talk) 22:26, 29 August 2019 (UTC)