Page MenuHomeMiraheze

Clean up and generalise Miraheze Extensions
Closed, ResolvedPublic

Description

Currently we develop 4 independent... dependent extensions. Each extension should be designed to work as add one to the CreateWiki extension (as they are) but should explicitly be built on. We shouldn’t dupe extension code across multiple extensions or config variables.

This also will track using wg config more so any wiki farm could in theory use our extensions with little to no problems.

TODO list:

  • CreateWiki: Make the extension directory look nice (includes, maintenance, sql, i18n directories etc.)
  • CreateWiki: Alphabetise extension.json and document settings.
  • CreateWiki: Drop pre-1.25 support.
  • CreateWiki: clean up DBListGenerator.php and add support for modular config of wiki configuration (e.g. inactive, closed, settings etc.)
  • CreateWiki: Make Private wikis modular.
  • CreateWiki: Make closed wikis modular.
  • CreateWiki: Handle subdomain only cases.
  • CreateWiki: Make sending emails a modular config.
  • CreateWiki: Make creation email less Miraheze specific.
  • CreateWiki: Make custom domain a modular config.
  • MirahezeMagic: Move RemoteWiki.php to CreateWiki (we use it too much for it to be an "us" thing anymore, makes all extensions unusable without our custom stuff forced on everyone else)
  • MirahezeMagic: see if we can move any other stuff from this into any of the other extensions as appropriate.
  • ManageWiki: Double check we employ modular config correctly for settings.
  • ManageWiki: Use new modular configs for private and so on.
  • WikiDiscover: Modularise the extension a bit more, it's all nice and neat but lacks more control.

Event Timeline

John triaged this task as Normal priority.Jun 5 2018, 02:52
John created this task.

This should also include better docs which I’ll also cover in the extensions. We may want to follow code coverage standards too?

John moved this task from Backlog to MediaWiki on the Goal-2018-Jan-Jun board.
John moved this task from Requires a developer to Being worked on on the Developer board.

Re: moving RemoteWiki, it was moved to MirahezeMagic by SPF for some reason

Re: moving RemoteWiki, it was moved to MirahezeMagic by SPF for some reason

Because it's Miraheze specific. But I'm fixing it and moving it back.

I'm going to keep all the backend code full, but change the front end code to obey config. It's easier then it means people can enable certain features later without having to do work to let says populate categories and stuff for everything as "uncategorised" and so on.

Please use Special:ManageWiki on your wiki to change these settings.

This is an automatic edit, if there is a false positive, please reopen the task.

Thanks Herald but I know this can't be done through Special:ManageWiki.