Template talk:DownloadMediaWiki

About this board

41.200.126.234 (talkcontribs)

Please add a text telling that MediaWiki 1.36 is no longer supported. Thanks.

41.200.126.234 (talkcontribs)

It will help.

Shirayuki (talkcontribs)

Yes Done

Managing "versions" is painful

3
Reedy (talkcontribs)

We ended up in a situation where the template was saying 1.36 is an LTS... This isn't true.

To users of MediaWiki versions version 1.34 and earlier: These versions are no longer supported. Please update to a newer version of MediaWiki:

    MediaWiki 1.37.0 (download .zip, download .tar.gz) - stable
    MediaWiki 1.36.2 (download .zip, download .tar.gz) - current long-term support (LTS)

This weird way of using commented templates, use of void, HTML comments etc is painful to manage. Why "legacy release" was used for LTS... I have no idea

* MediaWiki {{MW legacy release number}} ({{MW legacy release link zip|1=<translate><!--T:40--> download <tvar name=1>.zip</tvar></translate>}}, {{MW legacy release link|1=<translate><!--T:41--> download <tvar name=1>.tar.gz</tvar></translate>}}) - <translate><!--T:49--> current long-term support (LTS)</translate>

Never mind there seems to be numerous duplicates...

Jdforrester (WMF) (talkcontribs)

I just re-implemented the equivalent logic for MWReleases; clearly we should have this as a single Module we can just call to output a list of currently-supported branches, linking either to their download targets or release pages or something else…?

Ciencia Al Poder (talkcontribs)

The idea of the templates and logic was to preserve the translation units, so things don't have to be re-translated again for new releases, because sometimes a legacy lts doesn't appear and sometimes it's present.

Maybe a module would be a good idea, and add the translatable text as invocation parameters so they can be used when generating the output, even if sometimes they're not used

Reply to "Managing "versions" is painful"

current long-term support and legacy long-term support

2
Reedy (talkcontribs)

Having both current long-term support and legacy long-term support looks a bit odd.

We should hidelegacy long-term support until we have 1.39 released...

Ciencia Al Poder (talkcontribs)

Yes Done

Reedy (talkcontribs)

Download is looking a bit broken, template and translate syntax appearing...

Ата (talkcontribs)

Commenting code doesn't quite work when you have already commented text inside. <!--something <!--something else--> here--> will produce here-->, only whatever is inside first<!-- and first --> will be commented.

I added more comment markup to make it work, though it will be a bit harder now, I assume, to uncomment the code when needed.

Reedy (talkcontribs)
Shirayuki (talkcontribs)

Yes Done by using display:none. But hiding content with display:none may cause accessibility issues.

MacFan4000 (talkcontribs)

Could someone please mark this page for translation?

Mglaser (talkcontribs)
MacFan4000 (talkcontribs)

The current version hasn't been marked though.

Proposal to add note to not use The Unarchiver on MacOS

2
Andrujhon (talkcontribs)

The Unarchiver on MacOS is a very popular archive utility due to it's support of a very wide range of archive formats.

Unfortunately the tar-gzip decompression incorrectly truncates filenames (See https://phabricator.wikimedia.org/T258716) causing subtle but significant errors in the installation - certain front-end features fail due to missing resources.

Since The Unarchiver is a very popular utility for many MacOS users, it might be justified to add a note alongside the suggestion that windows users use 7-Zip that MacOS users should not use The Unarchiver.

I've added an edit to the page, but it's protected so I thought it wise to also drop a note here explaining my addition.

Ciencia Al Poder (talkcontribs)

Closing this, as it has been added already but with a warning that it corrupts the extracted files due to phab:T258716

There are no older topics