Template talk:Main page

Archives: 1 · 2 · 3 · 4 · 5 · 6

Previous page history was archived for backup purposes at Talk:MediaWiki/LQT Archive 1 on 2015-07-10

Done in Special:Diff/6463985

Please replace "Manual:Installation guide" and "Manual:Errors and symptoms" to their redirect targets, because "Special:MyLanguage" will not follow the redirection, preventing users get redirected to their language.

Thank you!

 Done Special:Diff/6463985

{{Edit Protected}}  Done

Hello, currently rtl (right to left) languages display as ltr (left to right) on the main page (See lang=he) Can the changes I have made at MediaWiki/sandbox and Template:Main page/sandbox be implemented so that these languages can display as rtl.

Thanks, Terasail

Ping @Quiddity as they originally asked about this.

Implemented! It looks like that's fixed it. Thanks again for noticing, researching, and preparing the fixes, both here and at Wikifunctions.

What is the id="lang_dir" bit for?

Instead of {{{1|{{PAGELANGUAGE}}}}}, you could use {{#invoke:Caller title|lang|base=Template:Main page}} (see Module:Caller title), avoiding the need for passing the language code from MediaWiki.

The id has no real use, it comes from when I copied the solution from the Wikifunctions main page. I personally know nothing about Module:Caller title, if it is a better way of doing things then I support it being used. I just made the edit request with the solution that I had originally found for this problem so that it might stop being a problem. (There are many ways to cook an egg and all that).

I believe Module:Caller title is better, although I have to add the disclaimer that I’m the original author it (I think I originally authored it on Commons), so it’s not surprising. 🙂 (I seem not to have been attributed on mediawiki.org.) Now MediaWiki tells Template:Main page in which language the latter will appear in, but Template:Main page decides the language it will actually appear in, which can easily lead to inconsistencies.

Link added

Although the Wikimedia Developer Portal is a great entry point for people interested in Wikimedia technical projects in general, this page should also provide a link to the developer documentation specific to MediaWiki. Instead of linking to both Manual:Contents and Developer hub, as this page did previously, I'd suggest linking to just Developer hub since it is more comprehensive and includes a link to Manual:Contents.

Proposed change:

		<h3><span class="header_icon" aria-hidden="true" role="presentation">[[File:OOjs UI icon chem.svg|20px|middle|link=]]</span><span><translate><!--T:3--> Develop and extend code</translate></span></h3>
		<div id="mainpage-devs" title="<translate nowrap><!--T:15--> Developers</translate>" class="items">
* <translate>Read the MediaWiki [[<tvar name=1>Special:MyLanguage/Developer hub</tvar>|developer documentation]]</translate>
* <translate><!--T:41--> Visit the [<tvar name=1>https://developer.wikimedia.org</tvar> Wikimedia Developer Portal]</translate>

Sounds good to me

IIUC, this is what was wanted? https://www.mediawiki.org/w/index.php?title=Template%3AMain_page&diff=5712915&oldid=5301280&diffmode=source

(I boldly edited, as the page is fully-protected, and APaskulin is not currently an admin. :) )

Perfect. Thank you, @Quiddity (WMF)!

If I am correct, T297019 makes it possible to blank the title by introducing the two new system messages, MediaWiki:Mainpage-title and MediaWiki:Mainpage-title-loggedin. So {{DISPLAYTITLE:<span style="opacity:0;position:absolute;">{{FULLPAGENAME}}</span>}} should be replaced, right?

Please add Manual:How_to_make_a_MediaWiki_skin to the develop and extend code section. It's a great way for volunteers to get involved!

Done

Hmm, I don't think we should link to this. Making skins is a very arduous and not very well supported area still, despite Jon's excellent work of late…

Could you be more specific here about what is arduous in the process? To be clear I think we are talking about creating a skin for fun, not for use on Wikimedia servers, which is a very different thing.

I think creating a skin should be a lot easier now with the additional abstractions, and I want us to support it better to make it easier to maintain our own skins, and if it's not I'm keen to hear about what specifically doesn't make sense. I can't hear that feedback unless people are encouraged to develop skins... :-)

This is the very top level of prompts for something a new developer might want to do. Indeed, it was inserted above the previous single prompt of working on core itself, or on extensions; it should be added to that page, not re-prioritising such a thing so much.

1) The entire content is collapsed under a single heading on the page "MediaWiki is a collaboration and documentation platform brought to you by a vibrant community.".

Solution: wrap the whole content in a DIV this will disable section collapsing on mobile and make the page more usable.

2) The talk button is inaccessible

The title is hacked with opacity:0;position:absolute; which impacts the talk tab. There should be no need to do this - the template is used on the main page not here.

Please remove this code: {{DISPLAYTITLE:<span style="opacity:0;position:absolute;">{{FULLPAGENAME}}</span>}}

Regarding: 2) Does (some of) the | #default= {{#invoke:Template translation|renderTranslatedTemplate|template=Template:Main page|noshift=1|uselang={{{1|{{int:lang}}}}}}}<!-- -->{{#ifeq:{{NAMESPACE}}||{{languages|Template:Main page}}}} }} part at the bottom also need removal? I obviously have no idea why that's here or what needs to be done.

Someone feel free to go ahead.

There should be no need to do this - the template is used on the main page not here.

The displaytitle code exists to hide the page title on the main page. Removing this code would make it no longer do that. I'm not sure in what way Template vs Main page matters, except that the rendering of the main page seems more important than this individual template page, so let's not just remove this :) Perhaps you can suggest an alternative way instead?

The main page title can be hidden using MediaWiki:Common.css - that's how most of wikis tend to do it. Mobile doesn't render the heading on main pages (that should probably be the default on desktop too but it isn't).

1) is now  Done. 2) needs an IAdmin to complete, maybe @DannyS712 can help us here?

Sure - do I understand correctly that the request (from me) is to use Common.css to hide the title from being displayed on the main page? If so, adding

.action-view.page-MediaWiki {
	display: none !important;
}

to common.css should be enough

Uhhh, not sure if that's enough. The same treatment should be applied to all translated versions.

Then I'll also apply it to .rootpage-Template_Main_page which will cover the translations

This template tries to transclude Template:MediaWiki News when there’s no translation of that template in the desired language, which is broken because of the translate markup. Either this template should transclude Template:MediaWiki News/en instead, or Template:MediaWiki News should autotranslate itself.

We should re-translate Template:MediaWiki News.

I don’t understand you. What should we re-translate? How would that resolve this issue? As long as <translate> tags are transcluded, it will be broken.

Sorry.

@Iniquity @Base Can you determine what the problem is here? See e.g. Template:Main_page/nl in contrast to Template:Main_page/de.

(For others, see context at Topic:Vsvbc8ui8hv55lws)

Fixed. --Base (talk) 17:14, 14 September 2020 (UTC)

Thank you!

Php7.4 is what I use so is there a beta version for mediawiki compatible with php 7.4

Off topic for this page which is for discussion of the MediaWiki page content and not the general software product. Project:Support desk is potentially a better place to ask. I imagine the answer will be "we don't know", but I might be wrong. :)

The Main page template is used with the parameter 1 set to en which prevents translated content from being shown on the Main Page. The parameter should be removed. (Invalid parameters will lead to the page being shown in English, so there wouldn't be a resulting problem.)

 Done

Thank you!

I note that you performed that exact opposite edit at Template talk:Main page#Display preferred language due to a request by Wargo. A decision should be made here, rather than there being hodgepodge oscillations at the request of individual users.

The edit at MediaWiki was wrong and unrelated to the request. At that time I should do this edit at Template:Main page.

Is there a good convincing reason as to why the latest stable builds are no longer listed on mediawiki wiki's main page?

Why is it important to you to see the specific numbers of the latest stable builds on the main page?

It was both convenient to download and track the latest stable and LTS builds. By the way I'm talking about this box: https://i.imgur.com/7WNmVzY.png that was still there not long ago (a few months ago at most).

If you want to download and track latest builds, feel free to bookmark Download.

I see no reason for such information to waste space on the front page. See "If people want to download MediaWiki they should go to the Download page" on MediaWiki/Homepage improvements 2018.

Who decides what wastes space on the main page and what doesn't? Was there a discussion where the majority agreed that the box that's been there for years is no longer relevant? All I see on the project you linked that it was decided (probably by you) that the box should be removed and that's that. The discussion page on that same project has little to no reference or actual discussion on this topic.

I quote from the source you linked: "I doubt anyone informs themselves about a need for an upgrade of their installation by visiting the front page and then manually comparing with their version."

"I doubt" - you doubt so that automatically means that no one does that. Well I did exactly that and I'm more than confident that there were a lot of people who did exactly that as well, but obviously they aren't being so vocal about it. For most of the people this wiki is a resource for the software.

@Lyrixn: Sure there was. See the three "Announcements / call for comments" sections on MediaWiki/Homepage improvements 2018 how you could have gotten aware.

I do see you being the only participant in these, unless I'm missing something.

If that was true (it is not), what would be the problem with that? Nobody can force anyone to take part in discussions...

The discussions can be found in Talk:MediaWiki/Homepage improvements 2018 and Talk:MediaWiki/Homepage improvements 2018/Proposal as linked from the three "call for comments" sections that I already linked in my previous comment. Anyone interested was welcome to provide input.

I'm not sure I totally understand but if I do, then you're asking for what is in the "News" card in https://www.mediawiki.org/wiki/MediaWiki? I do see latest stable builds/releases of MW on the "News" card, which if you click on "more news", you'll be taken to: https://www.mediawiki.org/wiki/News.

Does that help? Thanks!

I mean the "current version" box. https://web.archive.org/web/20190101022620/https://www.mediawiki.org/wiki/MediaWiki

I have the following table on my corp wiki - use the source editor to actually read it:

{{#get_web_data:url=https://en.wikipedia.org/w/api.php?action=query&meta=siteinfo&format=json
|format=JSON
|data=wp_servername=servername,wp_generator=generator
|cache seconds=21600}}
 {{#get_web_data:url=https://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&format=json
|format=JSON
|data=mw_servername=servername,mw_generator=generator
|cache seconds=21600}}

{{#external_value:mw_servername}}: {{#external_value:mw_generator}}

{{#external_value:wp_servername}}: {{#external_value:wp_generator}}

www.mediawiki.org: 1.35.0-wmf.30 (765c95b)

It might come in handy.