If need be, I don't think there would be any legal reason you couldn't provide a copy of the scripts on your wiki, provided that the licensing information (which is in a comment at the top of the script) is kept intact, and that you supply the URL of the original copy.

Did you name the talk namespace? This doesn't happen automatically, and will disallow you from submitting the form.

@Paladox @Reception123 ^

In T3861#76112, @Void wrote:

Task has been resolved upstream for a month.

Correction, Special:ListFiles has been fixed. Is there an upstream task for Extension:Editcount?

Content translation was previously removed because it requires a service we don't have. See T784#12341. I'm guessing someone just forgot to remove the extension submodule.

We don't maintain the translations of other extensions.

Caused by broken translations. I've adjusted them.

In T4010#76825, @MikeV wrote:

I managed to do it after getting him to browse to ndg.nenawiki after logging on to nenawiki.

Yup, that's what you need to do.

A global account already exists.
https://meta.miraheze.org/wiki/Special:CentralAuth/TomBreen

Fixed by @Paladox. Should be working now.

Nope, you should just be able to create a link like that. There are a few more details here.

Looks like this is affecting all wikis.

This should be possible if the current namespaces existed in the ManageWikiNamespaces. I guess there are a number of wikis that don't have the mw_namespaces table populated, which should get fixed.

You could try using the new global interwiki feature, by linking to [[mh:nenawiki:Page]]. In theory, the link should always point to the same place.

If you have any questions about the process, please direct them to the community noticeboard, unless you are getting an error when trying to import.

You should be able to use the upload form normally. What issues are you getting?

This can be accomplished using Special:ManageWikiPermissions.

Per above, and the fact that Extension:EmailForm is not compatible with the most recent version(s) of MediaWiki.

It appears that the user Topology is the bureaucrat of that wiki, just FYI. I've opened up the wiki.
If you can't open a wiki, the request should be on Requests for adoption.

You could load it in as a gadget, by moving MediaWiki:Slick.js and MediaWiki:Slick.css to MediaWiki:Gadget-Slick.js and MediaWiki:Gadget-Slick.css. Then add the following to MediaWiki:Gadgets-definition:
* Slick[ResourceLoader]|default|Slick.js|Slick.css
Then, you could create MediaWiki:Gadget-Slick with information on what it does.

Is this still an issue?

Done in https://git.io/fhZzq

Task has been resolved upstream for a month.

The ability to delete namespaces has been added as of T3949.

I've worked on this in https://git.io/fhs1Z

cw_user was using a SMALLINT, which has a max size of 32767

I doubt there's any compromising going on here, otherwise this would be a security task. The original requester is still visible in the farmer log, so that does help.

This issue seems to affect all users created after Hearth to matilda was added to meta.

A user's contributions can still be attached to their account, without the need to delete and re-import content. However, it will require the use of a maintenance script. In terms of attribution, we believe that, as long as the full history of the pages is preserved, attribution is satisfied. We do not believe it to be within reason to require that all pages that were imported from another source link back to the original page.

Confirmed working on publictestwiki.com

I believe https://git.io/fhIPq will add default permissions for all extensions we currently have.

I've unlocked the accounts, they had appeared to be connected to another user, but the lock should never have been made. If they have any other difficulties editing as a result of a block or lock, let me know on my talk page.

Should the value be modifiable by Special:ManageWiki?

Per above

Works on all wikis I checked

Global issue

Per above

You should be all set now.

Hmm, I got an internal error on visiting the wiki and was logged out across all wikis.

Is the page currently in a namespace where subpages are enabled?

Subpages need to be enabled on any namespace you want them to be on.

You can either see if the extension Popups does what is required, or you will need to create the following pages.

We don't add unmaintained extensions.

Still an issue

What extension is this?

I don't think it is possible to create a script that runs any faster without risking causing a DOS-like event. I can make it easy to change the reason supplied (you can do this by changing both lines that begin with reason: in the script before running it), and maybe I'll create a fake special page to make the input look nicer.

1. OS is done.
2. Warning is going anyway.
3. List should possibly be here.

We do have MediaWikiChat installed, but I'm not too sure why it's not available for ManageWiki.

We currently have no way to prevent anyone from being able to read any page on a wiki unless the whole wiki is made private. In other words, there is no way to make only certain pages or namespaces only visible to certain users in a secure manner. We can create a private wiki for you where you can store the pages you want to be private and you can give access to those who are supposed to read.

We can up the limit on the time out too, but there's no real way to get rid of it entirely.

Hmm, from the looks of things, the extension only assigns the edit permission to admins but never grants the group any of the other permissions it revokes. It could be worth an upstream ticket, but we could easily assign the permission (createpage) to admins on request.

Aside from writing up a brand new extension, we could possibly pull this off by creating a wiki (called interwikiwiki or something), add a link to it in the global interwiki, and then in the interwikiwiki interwiki, add interwiki links to all wikis (probably using a bot to scan WikiDiscover). Then, it should be possible to interwiki to interwikiwiki, which then would redirect you to the wiki from your link. Hope that makes sense!

If you still need assistance with this, I'd recommend taking it to my talkpage. Unless you want to do an import from wikia.

Looks better already. If you want it collapsible, you'll be needing to add MediaWiki:Common.js from enwikipedia as well.

The Translate extension is enabled on your wiki. Please see Extension:Translate and Help:Extension:Translate on mediawiki.org for instructions on use.

Yup, I've assigned the right to sysop for now, please let me know if you want that changed.

Done

Done

Hi, sorry for the delay in handling your request. Is Extension:Translate sufficient for your purposes, or do you still require this additional feature?

Hi, sorry for the delay in getting to your request. Would it break or otherwise interfere with your wiki's functionality if these namespaces did not have the same namespace ID (number) as requested?

Sorry for the delay. I've enabled VisualEditor, but I'd prefer not to touch the ReCaptcha settings myself.

Is this namespace still needed, or can this task be closed?

Done

Also, please be aware that we do not support the use of EmbedVideo for security reasons, we do however support the use of TimedMediaHandler and/or Youtube.

Hi, please use Special:ManageWiki to add these extensions yourself.