FlightGear wiki:Plugin Requests

From FlightGear wiki
Jump to: navigation, search


Hook for parsing articles when saving

could we discuss adding a check to automatically detect/fix up links for which we have helper templates like Template:Repo link ? The point being, new/updated articles should no longer contain absolute links to github, sourceforge, gitorious etc, but instead use these templates. For example, it seems we could register a "MultiContentSave" hook to specifically look for such links [1] ? We could probably also run a Python script/bot to update existing articles semi-automatically, or at least add them to category for review ? -Hooray (talk) 06:44, 25 April 2020 (EDT)

Alternatively, we could extend the mediawiki editor to add buttons for special/FlightGear specific templates like these, so that users can more easily build links that are in line with the template ?

See also:

Regarding an editor toolbar, a few years back on Wikipedia (in essence when Wikipedia used about the same version of MediaWiki as this wiki), there was a bar between the text editing box and the edit summary box with some useful stuff, like the <reference /> tag, commonly used characters (I particularly miss a quick forward arrow, ) and some often used templates. I have not taken myself to look into that though.
Regarding hooks and bots to catch links, even such a seemingly simple thing as manually trying to catch only most forum links was a bit of a headache (see in particular FlightGear wiki:Village pump/Archive 2019#Conversion of direct forum links and URLs to templates). Catching them and recommending a template might work, but trying to automatically convert links to templates might be trickier (and in addition would need administrators to maintain such bots for conversion if the templates are edited).
Unfortunately, my experience is that most people do not like reading documentation, but if they did, a very brief summary of which templates to use for the very most common cases could be useful. I struggle a bit with the current documentation as I do not use those templates all that often and have sometimes found myself spending several minutes trying to figure out which use case and what parameter names I should use. Which probably speaks for a tool bar or automation, or just more specific templates (in essence templates for only a few use cases).
Johan G (Talk | contribs) 12:15, 25 April 2020 (EDT)
Looking at the mediawiki docs, a client/browser-side extension would be fairly easy to implement, i.e. to extending the editor to add a button for some of the more common/useful project-specific templates, and showing a corresponding "template configurator", e.g. the repo link stuff would show a checkbox/dropdown menu to select different options and then configure the template, analogous to how tables can be created using a really simple wizard. I think you've got a point, I also tend to be unaware of existing templates for specific purposes, so running some heuristics (e.g. check for forum link, mailing list link or git link) and then suggest a template configurator/wizard, while showing a suggestion that can be approved/customized would probably suffice. I am not sure if there are existing solutions/plugins for this specific purpose, but it would be fairly easy to implement and maintain by wiki admins, even client-side (i.e. using JavaScript). I just think we need to get Gijs involved, because most of the other admins won't have sufficient privileges to extend the editor (?)-Hooray (talk) 12:23, 25 April 2020 (EDT)


  • the file upload wizard seems to be gone ?
    Fixed now. Not really sure what went wrong, but we had to disable it after we restored the wiki last week. Gijs (talk) 17:44, 31 January 2015 (EST)
  • Thank you --Hooray (talk) 15:58, 1 February 2015 (EST)


  • support for forking/branching articles to more easily maintain articles for different versions of FlightGear, so that new features can be documented, without affecting old documentation and vice versa [2]


  • LaTex support, so that wiki articles may contain embedded LaTex sections (this does not just need an extension, but server-side support, i.e. the LaTex toolchain)
  • we still need to provide additional GeSHi (syntax highlighting) schemes for Nasal and GLSL


Section inclusion

Gijs & Hooray talked about using this to automate writing changelogs, based on extracting sections from the monthly newsletter: mw:Extension:Labeled Section Transclusion


MediaWiki Extension Requests against SPAMING

Every day a new spam are edit on this WIKI, It's so Boring. Personnaly i havn't right to delete account, and can only delete the Spam. But if administrator of the wiki can install some of this extension to prevent spamming, it could be very nice... I know there some Capcha installed, apparently is not enough

and please read this page mw:Manual:Combating spam

Thanks. --Lolalilo 01:58, 11 February 2011 (EST)


MediaWiki Extension Requests

—This unsigned comment was added by MILSTD (talkchanges) 17:01, 20 February 2010 (UTC)