I also faced this issue recently and found that ignoring the issue is the solution for now! (https://www.mediawiki.org/wiki/Topic:Wajxsp05c7gsnf6r)

I think zip should be the primary, at least till the tar issue has been resolved. Another reason is zip works on every platform without any issue and without any extra tool. Windows default extract tool is a littler slower than the 7zip and WinRar but it works. This a major advantage over the tar format.

I tried to updated the mediawiki download template (https://www.mediawiki.org/wiki/Template:DownloadMediaWiki) and found that it uses https://www.mediawiki.org/wiki/Template:MW_stable_release_link to show the download link which a protected page. Can anyone update that link for zip

7zip shows warnings that it is going to replace files. If it extracts without any warning, then I assume 7zip fixed the issue. I use 19.00 and it shows warnings as following.
.

@Jdlrobson I used tar archive to install mediawiki and i did not run any composer update. I did not see any error on console or network tab. So here I am sharing the some screenshots again

@Psychonaut did you find any solution to add those tags? I am also facing the same issue on my site.

Is there any to control if I want to show the Toolbox or not? Can you please update the Sidebar doc on the mediawiki so that others can use it for their own purpose. For example I might want to show the Toolbar only for the logged in users. how can i do that?

is there any estimated time to fix this issue? already one month gone till the date of reporting the issue. Can you tell me how should I continue the installation?

Thanks. As it was not mentioned at the time i started the skin development I started to use a stable release.

@Jdlrobson thank you for looking into the issue.

Can we make MW archives available in such formats where we will not need to have additional/ special tools just to extract that?

This issue was created on Jul 4 2020, 3:03 PM. So it exists more than 6 months. This is the very first step of the installation and it is known that it can be failed. That is why I think it has been ignored.

No. It was showing two error and I expanded the first one. I have uploaded the screenshot for you understanding.

Is there any specific reason of releasing MW only as a tarball ? Why we can not release a zip file along with the tar file?

Thanks. created two new bugs for example skin.

Thanks for your quick response.

@Aklapper thanks for looking into this project.
I am not working on this project right now. But may be work on it again.

It is not blocked by any other issue. Rather it will need some additional codding assistance. At the time of of opening the issue it was planned to engage some additional resources.
I started to work on this project again hopefully i will be able to post some updates soon.

When I got the news of this extension the first thing came to my mind is that if we get the list of most search keywords on my wiki. We will be able to work on the missing articles. It would be a huge help to get more readers.

@Aklapper i am sorry, i should mention that i updated the description. Actually i mentioned this in an another issue and forgot to mention here.

@Qgil can you please check the description and help me to move it to on track

@Lokal_Profil thanks for your valuable comment and explanation.

There is no direct relation with the OpenBadges and there are some major differences with that. For example this tool will be a standalone one rather be an extension/core part of the Mediawiki. This tool will check and store the user contribution stat (if user wants to) and the badges the user received and about to receive. It also have an option to display the badges centrally. Along with this @Lokal_Profil also mentioned some points.

If i want to release my images in CC 4.0 license and want to use the basic uploader, then what would be the way to do that?

Hi @Qgil i am interested to be the org admin. Can you please inform me more?

Added 2 characters and changed the order at https://en.wikisource.org/wiki/User:AuFCL/specialcharacters.json and i think there are no change needed

I checked the Bengali Wikipedia WikiEditor character set and all the characters are not usable. I can click on some of the characters but not all. Even the English Wikisource CharInsert set are not complete, can you please tell me where can i update the set?

@Nikerabbit is there any plan to implement HTML emails in core? then it might be easier to resolve this and present the text in a more formatted way.

Most of the time plain text emails can not create links for non-latin ULRs. I think HTML email would be the solution. Is there any pan to do so in future roadmap?

@Mattflaschen thanks for looking into the issue. Do you have any idea how this can be resolved?

@Nemo_bis
so, what should be the proposed solution for this?

Is there any update on this issue?

Is there any update on this issue?