FlightGear wiki:Notes to administrators

From FlightGear wiki
Jump to navigation Jump to search


This is a collection of notes to administrators to help them with the maintenance that regular users cannot do. Please do extend/update this article so that others can more easily help with recurring tasks.

Common tasks

Interwiki data

  • Interwiki links (including translations interwikis) can be viewed and edited from Special:Interwiki.


See also {{delete}} and {{delete-sp}}.
  • Before deleting, check the page history.
  • An old page with lot of edits and views should probably not be deleted, but instead be turned into a redirect to a page that has a similar subject. Also, deleting a well-visited page can cause a lot of broken links on the forum or in the devel list archives

Dealing with spam

  • Newly-registered users whose first and only contribution clearly and unambiguously was spam can safely be blocked indefinitely and have their contributions deleted.
  • Make sure the edit summary does not contain the offending links and other content, just the word "spam" and possibly a few words more.
  • To add new blocking reasons, see MediaWiki:Ipbreason-dropdown
  • If the wiki is regularly being spammed with similar page titles, consider adding a regex to MediaWiki:Titleblacklist
  • Article protection reasons can be added via MediaWiki:Protect-dropdown

Maintenance categories

Periodically recurring tasks

Updating the sidebar


Note  This must also be done for the German translation.
  1. Proof read and cleanup last month's newsletter (this can also be done by normal users)
  2. Review/lock last month's newsletter
  3. Copy the newsletter template to the next draft newsletter
  4. Update/review the redirect at Next newsletter (should be automated)
  5. Update the table at FlightGear Newsletter

FlightGear releases

Note  For bugfix releases, you only need to:


  • Our custom Nasal syntax highlighting module is usually forgotten after MediaWiki software updates. Note that only Gijs (talk) and Hellosimon (talk), who have access to the server, can fix this issue.