Difference between revisions of "FlightGear wiki:Village pump"

From FlightGear wiki
Jump to: navigation, search
(Aircraft Page Organization)
(Space shuttle screenshots category need cleanup: Added Category:Screenshots of Earthview to some of the relevant screenshots.)
 
(297 intermediate revisions by 16 users not shown)
Line 1: Line 1:
{{Archives|[[/Archive 2012|2012]], [[/Archive 2013|2013]], [[/Archive 2014|2014]]}}
+
{{Archives|[[/Archive 2012|2012]]|[[/Archive 2013|2013]]|[[/Archive 2014|2014]]|[[/Archive 2015|2015]]|[[/Archive 2016|2016]]|[[/Archive 2017|2017]]|[[/Archive 2018|2018]]|[[/Archive 2019|2019]]}}
 +
{{shortcut|FGW:VP}}
 +
 
 
Welcome to the '''Village Pump'''. This page is used to discuss the technical issues, operations and guidelines of the [[FlightGear wiki]].
 
Welcome to the '''Village Pump'''. This page is used to discuss the technical issues, operations and guidelines of the [[FlightGear wiki]].
  
: Please [{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics] to the '''bottom''' of this page.
+
Please <span class="plainlinks">[{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics]</span> to the '''bottom''' of this page.
 
+
: Old discussion should be moved to a [[FlightGear wiki:Village pump/Archive YEAR]]. These discussions can then be moved to a relevant talk page if appropriate.
+
 
+
----
+
 
+
== Navigation links added to FlightGear Newsletter header ==
+
 
+
As per [http://forum.flightgear.org/viewtopic.php?f=42&t=25104 request by Michat on the forum] I have now managed to add navigation links to the FlightGear Newsletter header, {{tl|Newsletter-header}}, pointing to the previous and next months newsletter.
+
 
+
So far I have only added it to the latest header though.
+
 
+
Happy browsing! :-)
+
 
+
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 19:48, 13 January 2015 (UTC)
+
 
+
== MediaWiki updated to 1.24.1 ==
+
  
I've updated MediaWiki to the latest stable release (1.24.1) today. There is a small issue with some of the extensions not displaying icons, so some of them have been disabled for the moment. I hope to have them re-enabled later today. Please report bugs if you find any. For a list of changes, see https://www.mediawiki.org/wiki/Release_notes/1.24
+
Old discussions should be moved to a [[FlightGear wiki:Village pump/Archive YEAR]]. These discussions can then be moved to a relevant talk page if appropriate.
  
[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 12:00, 1 February 2015 (EST)
+
== New Portal: Embedded or Hardware (02/2020) ==
 +
Suggestion: Dedicated portal for articles relating to embedded/hardware topics (which would be in line with numerous threads on the forum, as well as existing articles on the wiki). - [[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 11:59, 17 February 2020 (EST)
  
: It seems that Nasal syntax highlighting via Geshi is no longer working (I think it was Philosopher who came up with the module...)?
+
: That is slightly less complicated than you might think.  What you would do is to create a new page with the prefix <code>Portal:</code> and a suitable name, say for example [[Portal:Hardware development]], [[Portal:Cockpit hardware]] or [[Portal:DIY cockpit hardware]], or maybe [[Portal:Hardware]] if you would also like to see commercial hardware there, and then copy and modify the content from a similar portal.
: --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 15:58, 1 February 2015 (EST)
+
  
:: Ah, didn't move that one over. Should be fixed now.
+
: Hint: There is actually not a portal [[Help:Namespaces|namespace]], it is just a prefix. The portal pages are actually in the main namespaces, and thus function just like any other article page on the wiki.
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 16:19, 1 February 2015 (EST)
+
 +
: [[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 13:35, 10 March 2020 (EDT)
  
::: Confirmed fixed.  Thank you for the quick fix.  :-D
+
: Though I think your [[Portal:Embedded]] might be more diffuse than [[Portal:Hardware]] for people that do not know what {{wikipedia|embedded software}} is, I have still added it to the main page and added [[:Category:Portals]] to it.  It will get more use if people can find it. :-P
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 16:49, 1 February 2015 (EST)
+
  
== Support SVG file ==
+
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 04:16, 14 March 2020 (EDT)
  
Is there some securty issues/software limitations (no plugin's installed) why the wiki don't support uploads of SVG images?
+
== Use as few categories as possible ==
 +
Always use as few categories as possible.  Categories are a place in a structure rather than tags.  Putting each page in a lot of categories will put a lot of of pages in each category.  There is in particular no need to put a page in both a category and then in each category above that category.
  
[[User:Www2|Www2]] ([[User talk:Www2|talk]]) 21:02, 4 February 2015 (EST)
+
Please see advice in [[Help:Your first article#Categories]] and maybe also [[Help:categories]].
  
== If you find missing images ==
+
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 13:04, 15 March 2020 (EDT)
  
In case you find missing images have a look at this page: [[FlightGear wiki:Missing images]].
+
== Meta template and templates for commonly used logotypes and icons ==
 +
Through a placeholder page (ugh!) and a edit summary Hooray suggested making a template for commonly used logotypes.
  
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 23:51, 7 February 2015 (EST)
+
{{cquote|placeholder/stub for all sorts of wiki related logos that may need to be updated over time, but that are referenced on multiple pages - so that we don't need to edit each and every page here.|2=[http://wiki.flightgear.org/index.php?title=Template:Logo&oldid=123306 Hooray, 11 April 2020‎, 08:04]}}
 +
{{cquote|@Johan: could use your help with this, unless I can write the heuristics in Php or JavaScript ;-)|Hooray, 11 April 2020‎, 08:04}}
  
== Additional Portals ==
+
I would guess you also intend it to be used for icons as well, for example the [[:Category:Ready icons|ready icons]]? Logotype/icon templates might not be a bad idea. Less typing is almost always good.
Given the recent interest in doing embedded development related to FlightGear (Arduino/Rasberry PI), I was thinking that we might want to introduce dedicated portals for such use-casesto keep things neatly organized, but also to provide a place to grow this further - e.g. depending on how this goes, we could have portals covering:
+
* Embedded/Hardware (including cockpit building)
+
* UAVs
+
  
Equally, we may want to provide sub-forums for these two topics, which should help clean up the offtopic/development forum, too. Currently, the SUPPORT/HARDWARE forum is being used for many of these topics, even though that was originally intended for joysticks/yokes and pedals related stuff - not custom hardware, which would fit better under DEVELOPMENT in my opinon.
+
{{tl|logo}} should probably be a meta template, a template used by other templates in this case by logotype templates.  Meta templates are pretty common on MediaWiki wikis.
  
As far as I can tell there are roughly 10-15 contributors actively exploring embedded development including UAV stuff - so I guess it would be a good idea for the project (i.e. the forum and the wiki) to provide some structure to "house" such efforts.
+
Essentially, there could be a set of logotype and icon templates, for example {{tl|Compositor logo}}, {{tl|FGInterface logo}}, {{tl|Air refueling ready icon}} etc, that pass the image for the logotype, an alt text (for accessibility and when the image is not shown, for example due to browser settings) and a link to a relevant wiki page to {{tl|logo}}.  Possibly also optional parameters like other sizes etc.  The meta template would then add the boilerplate stuff around that and set the size.
  
thoughts/ideas ?
+
I would advise that having a suffix indicating the type of template, for example ''logo'', ''icon'' like mentioned above or ''navigation'' (for navigation boxes), in essence having less ambiguous names, is generally a good idea.
--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 06:17, 10 February 2015 (EST)
+
  
== Wiki extensions observations ==
+
I should mention that I am generally against placeholder pages.
  
Hi all,
+
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 06:44, 12 April 2020 (EDT)
  
Recently I was looking at the [[Special:Version#Installed extensions|installed extensions]], and noticed the below:
+
== UTF-8 language pages cannot be edited (cont. from 2015) ==
  
; [http://www.mediawiki.org/wiki/Extension:SmoothGallery SmoothGallery]
+
While migrating my own unrelated MediaWiki instance, I may have stumbled upon "a" SQL issue blocking the creation of pages with non-latin characters in their titles. See:
: It appears that it doesn't work anymore on this wiki.  For instance, the below code …
+
  <nowiki><sgallery>
+
Glass01.jpg
+
Glass07.jpg
+
Glass11.jpg
+
</sgallery></nowiki>
+
: … causes the following error:
+
  
: Notice: Undefined variable: args in /home/wiki/wiki/extensions/SmoothGallery/SmoothGallery.php on line 113 Fatal error: Call to undefined method LocalFile::getThumbnail() in /home/wiki/wiki/extensions/SmoothGallery/SmoothGalleryParser.php on line 208
+
* [[FlightGear wiki:Village pump/Archive 2015#UTF-8 language pages cannot be edited]]
 +
* [[FlightGear wiki:Village pump/Archive 2016#UTF-8 language pages cannot be edited]]
 +
* [[FlightGear wiki:Village pump/Archive 2019#Language flags on the main page]]
  
: This could be related to extension's [http://www.mediawiki.org/wiki/Extension:SmoothGallery#Fixing_bugs bugs].
+
If someone has access to the MySQL backend (command line or phpMyAdmin), could you check what the "Collation" of our database is set to?  For example:
  
: I suggest this extension be removed because
+
<syntaxhighlight lang="sql">
# As far as I know, it's not used on any of the wiki's pages.
+
USE dbname;
# Is it needed?
+
SELECT @@character_set_database, @@collation_database;
# Its ''unstable'' as of 22 March, 2015, which means it's broken and shouldn't be used ([http://www.mediawiki.org/wiki/Extension_status link]).
+
</syntaxhighlight>
  
; [http://www.mediawiki.org/wiki/Extension:EmbedVideo EmbedVideo]
+
Or in phpMyAdmin the collation is given in the database listingMy guess is that we are not using UTF-8.  That can be changed (after a backup) with:
: According to the [http://www.mediawiki.org/w/index.php?title=Extension:EmbedVideo&oldid=1447164 page revision as of 16 March 2015], there were XSS flaws in version 2.2.4 and earlier of the extensionIt should probably be updated to the latest revision.
+
  
[[User:Red_Leader|<span style="color:red">'''''Red Leader'''''</span>]] ([[User_talk:Red_Leader|Talk]], [[Special:Contributions/Red_Leader|contribs]]) 14:08, 22 March 2015 (EDT)
+
<syntaxhighlight lang="sql">
 +
ALTER DATABASE dbname CHARACTER SET utf8 COLLATE utf8_general_ci;
 +
</syntaxhighlight>
  
: Both are done. Thanks for reporting!
+
Or in phpMyAdmin, select the databse of this wiki, click on the "Operations" tab, in the "Collation" box select "utf8_general_ci", and finally click on "Go".  Hopefully this is the cause of this long standing and painful issue.
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 17:21, 24 March 2015 (EDT)
+
  
== Boeing 777 Cleanup ==
+
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 03:33, 9 September 2020 (EDT)
  
Just wrapping up cleaning up Boeing 777 articles that I discussed a full year ago. All now redirect centrally to that page. This makes for a lot less segregated wiki. Looking at it, it would appear that very little happens on the individual pages and the content on them is relatively insignificant. The stuff that is needed I copied over to the main page. Will try to add some pictures as well.
+
: Hi Edward,
 +
: I somehow missed all these previous reports :-( Sorry!
 +
: You're right. The database is in latin1. We're actually currently in the process of migrating some of our server work and updating. I will take care of setting the correct collation on that occasion.
 +
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 04:24, 9 September 2020 (EDT)
  
If anybody has any objections, speak up :)
+
:: Great, that sounds exactly like this problem.  Only pages with 'latin1' characters in their names can be edited.  I really hope switching the collation to UTF-8 will fix the problem.  There must have been a MySQL server migration many years ago where the old database was UTF-8 and the import automatically changed the language to the server default of 'latin1', as many pages were created on this wiki with non-latin1 characters in the past.  I see this with my MySQL database too - I have to switch back to UTF-8 after import into the new SQL database.
  
 +
:: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 06:00, 9 September 2020 (EDT)
  
: It would be really useful to merge the pages ''if'' the aircraft are similar in many ways, for example:
+
== Needing an extra pair of eyes ==
:* All part of the same aircraft package
+
There is a problem with automatic categorization in {{tl|Autoflight Navigation}} that I can not seem to solve.
:* Same or similar usage, for example
+
:** Keyboard shortcuts
+
:** Custom dialogs
+
:** Clickable cockpit interfaces
+
:* Same levels of system modeling
+
  
: If they could be handled pretty much the same way and was part of the same aircraft package I don't think I would have any objections.
+
For details see [[Template talk:Autoflight Navigation#Automatic categorization seem broken]].
  
: However, if they differ a lot in the areas mentioned above I think it would not be a good idea to merge the pages; the aircraft would be dissimilar enough that the page would have to be uncomfortably long and possibly confusing if it were to describe the different workings.
+
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:26, 10 September 2020 (EDT)
  
: If they are not part of the same aircraft package, looking into the similarities and differences and slowly work towards integrating them into the same aircraft package could also bee a good idea.
+
: All done!  In summary, the {{tl|howto other}} template logic was completely broken and was operating as the {{tl|main other}} template instead!  Checking if the {{obr}}NAMESPACE{{cbr}} is set to {{obr}}ns:0{{cbr}} is not how you check for the "Howto" namespace.  As I don't know the numeric value of this namespace, I switched to comparing {{obr}}NAMESPACE{{cbr}} to the simple string 'Howto'.  So the template is now fixed.  We should see a lot of auto-categorisation additions and fixes now.  I also switched {{tl|Autoflight Navigation}} to use {{tl|namespace detect}} to simplify its logic.
  
: [[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 07:48, 5 May 2015 (EDT)
+
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 06:14, 11 September 2020 (EDT)
  
== Aircraft Page Organization ==
+
:: Thank you som much for fixing that. :-)
I just started a [http://forum.flightgear.org/viewtopic.php?f=72&t=26161 topic] over on the forum on how posts are organized if somebody has input.
+
:: Did not think of comparing the namespace numbers between the templates.
 +
:: I was wondering where I found the numbers, but could not quite remember.  If I figure it out I will probably add the source for those at a suitable place, like under ''Technical details'' in ducumentation for {{tl|namespace detect}} or something like that, though using full names of the namespaces is probably the safer option.
 +
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 02:07, 12 September 2020 (EDT)
  
{{unsigned|11:45, 5 May 2015|Manfred}}
+
== The Howto namespace ==
 +
: ''Copied here from [[Template talk:Autoflight Navigation]].''
  
 +
To be honest, from the start I have considered the Howto namespace to be an abomination.  There is absolutely no need for it, as one could simply have articles in the main namespace with a Howto: prefix (IIRC they call this "user administered namespaces" or "pseudo namespaces" on Wikipedia). To not have to type the prefix, one could simply create redirects.  Creating a separate Howto namespace have caused issues in the past, like that the search function per default only looks for articles in the Main namespace.  It is not entirely unlikely that what we see here might be some configuration issue as well.
  
: I think it would probably be better to discuss the quality and organization of the wiki right here (on this very page) than on the forum.
+
Sorry for the rant. And thanks again.
  
: The main two reasons for that is (1) to keep the wiki quality discussions here and (2) that it would be a bit more transparent to do it that way.
+
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 06:29, 11 September 2020 (EDT)
  
: The transparency is important in that it would make it easier to later look into ''why'' things were decided to be in a certain way and ''who'' said ''what'' and ''when''.
+
: I wouldn't call that a rant.  It would be better on [[FlightGear wiki:Village pump]] though.  To me 'Howto' here is simply a categorisation.  Why is that categorisation even needed in the page title?  I never liked this namespace, specifically because the default search misses it, and there is a significant grey area of what you would categorise as a 'howto' or not.  I think it would be better managed with a basic {{tl|howto}} template at the start of each of these articles which automatically adds [[:Category:Howto]].  If you take your discussion above over to the village pump, I'll copy this over there as well.
  
: [[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 08:07, 5 May 2015 (EDT)
+
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 07:56, 11 September 2020 (EDT)
  
Alright, so here goes:
+
== Space shuttle screenshots category need cleanup ==
 +
There currently are quite a number of misplaced files in the [[Special:CategoryTree/Space Shuttle screenshots|Space Shuttle screenshot categories]], possibly making it harder to find screenshots and other images. For example external screenshots in the [[:Category:Space Shuttle cockpit detail screenshots|cockpit detail category]], that preferably should be closeup images of panels and displays, and screenshots of large portions of the cockpit in the cockpit detail category.
  
By the nature of FlightGear, multiple people might work on different projects covering the same areas. For instance, there are 2 different projects covering the Boeing 787. This makes overview and indexing very difficult. Wikipedia is designed to only really have one article on a topic (i.e. aircraft) that can be extended.
+
I do expect some overlap between the cockpit categories and the custom dialog categories as dialogs are featured in a lot of those.
  
For instance:
+
There are also a lot of diagrams with no part of the Space Shuttle at all in the screenshot categories, those are more at home in the [[:Category:Space Shuttle diagrams|Space Shuttle diagrams]] category.
  
{{Airbus}}
+
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 20:10, 3 November 2020 (EST)
  
It is dreadfully unclear on the overview of aircraft. In my opinion, it would make more sense to get an disambiguation page on the various 'packages' that contain the A319 for instance. The multiple entries greatly diminishes the value of the list.
+
Have done a little cleanup, a lot left to do.
  
Here are a few ideas:
+
If my recategorization edits fill up [[Special:RecentChanges|recent changes]], click ''Hide minor edits''. When (re)categorizing, I mark my edits as minor edit so they can be filtered away if they fill up recent changes (I have gotten frustrated comments on my edits filling up recent changes before).
* '''Give aircraft a codeword or project name.''' For instance, the Boeing 787 (Dream Project) or Boeing 787 (GPL Project) to distinguish between them. Then list them like that in the index as well. When you both have a --aircraft= A319 and A319-131, what are you going to do when the next person comes around and wants to design an A319? It would make more sense to migrate to a structure of say B787-8-Dream and B787-8-GPL. If you make a piece of software, you're not going to go calling your software 'Conference Manager', with the next person making the similar stuff calling it 'Conference Manager 2', but rather ConferenceTime and and ConferenceMaster. Naming your work after aircraft in the current way gets bloody confusing.
+
  
* I imagine that perhaps as a bit of a continuation of the above, '''people try to distinguish between their models by giving them very specific names, such as Boeing 707-338'''. I realize that people want to work on it themselves, but from a broader perspective, how much technical difference is there really between these? The A319 should also work with the corresponding changes as a A320- it is an identical cockpit and much the same fuselage. IMHO, it should have been filed as an A320 instead with only one model, an A319. As for the Boeing, give it a codeword, such as Boeing 707 (Qantas Project). It even makes it more marketable.
+
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 21:23, 3 November 2020 (EST)
  
* '''Clearly distinguish between current and past development in the template''', i.e. add a new index on the left that contains both categories. I find that not doing any work on the model in five years qualifies for past development.
+
Also added [[:Category:Screenshots of Earthview]] to relevant Space Shuttle screenshots up to and including [[:File:Shuttle-tutorial2-01.jpg]].
  
The ability to grow is proportional to the ability to handle the increase in information. While this perhaps happens mostly on aircraft articles, what happens if somebody wants a fresh start on that airport scenery? How does he name the page and organize it in relation to the current one? It would have been easier to name both after some town landmark so one the second one came around, you could easily categorise them.
+
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 05:08, 6 November 2020 (EST)

Latest revision as of 05:08, 6 November 2020


Archives
2012, 2013
2014, 2015
2016, 2017
2018, 2019

Shortcut
FGW:VP

Welcome to the Village Pump. This page is used to discuss the technical issues, operations and guidelines of the FlightGear wiki.

Please add new topics to the bottom of this page.

Old discussions should be moved to a FlightGear wiki:Village pump/Archive YEAR. These discussions can then be moved to a relevant talk page if appropriate.

New Portal: Embedded or Hardware (02/2020)

Suggestion: Dedicated portal for articles relating to embedded/hardware topics (which would be in line with numerous threads on the forum, as well as existing articles on the wiki). - Hooray (talk) 11:59, 17 February 2020 (EST)

That is slightly less complicated than you might think. What you would do is to create a new page with the prefix Portal: and a suitable name, say for example Portal:Hardware development, Portal:Cockpit hardware or Portal:DIY cockpit hardware, or maybe Portal:Hardware if you would also like to see commercial hardware there, and then copy and modify the content from a similar portal.
Hint: There is actually not a portal namespace, it is just a prefix. The portal pages are actually in the main namespaces, and thus function just like any other article page on the wiki.
Johan G (Talk | contribs) 13:35, 10 March 2020 (EDT)
Though I think your Portal:Embedded might be more diffuse than Portal:Hardware for people that do not know what embedded software This is a link to a Wikipedia article is, I have still added it to the main page and added Category:Portals to it. It will get more use if people can find it. :-P
Johan G (Talk | contribs) 04:16, 14 March 2020 (EDT)

Use as few categories as possible

Always use as few categories as possible. Categories are a place in a structure rather than tags. Putting each page in a lot of categories will put a lot of of pages in each category. There is in particular no need to put a page in both a category and then in each category above that category.

Please see advice in Help:Your first article#Categories and maybe also Help:categories.

Johan G (Talk | contribs) 13:04, 15 March 2020 (EDT)

Meta template and templates for commonly used logotypes and icons

Through a placeholder page (ugh!) and a edit summary Hooray suggested making a template for commonly used logotypes.

Cquote1.png placeholder/stub for all sorts of wiki related logos that may need to be updated over time, but that are referenced on multiple pages - so that we don't need to edit each and every page here.
Cquote2.png
Cquote1.png @Johan: could use your help with this, unless I can write the heuristics in Php or JavaScript ;-)
— Hooray, 11 April 2020‎, 08:04
Cquote2.png

I would guess you also intend it to be used for icons as well, for example the ready icons? Logotype/icon templates might not be a bad idea. Less typing is almost always good.

{{logo}} should probably be a meta template, a template used by other templates in this case by logotype templates. Meta templates are pretty common on MediaWiki wikis.

Essentially, there could be a set of logotype and icon templates, for example {{Compositor logo}}, {{FGInterface logo}}, {{Air refueling ready icon}} etc, that pass the image for the logotype, an alt text (for accessibility and when the image is not shown, for example due to browser settings) and a link to a relevant wiki page to {{logo}}. Possibly also optional parameters like other sizes etc. The meta template would then add the boilerplate stuff around that and set the size.

I would advise that having a suffix indicating the type of template, for example logo, icon like mentioned above or navigation (for navigation boxes), in essence having less ambiguous names, is generally a good idea.

I should mention that I am generally against placeholder pages.

Johan G (Talk | contribs) 06:44, 12 April 2020 (EDT)

UTF-8 language pages cannot be edited (cont. from 2015)

While migrating my own unrelated MediaWiki instance, I may have stumbled upon "a" SQL issue blocking the creation of pages with non-latin characters in their titles. See:

If someone has access to the MySQL backend (command line or phpMyAdmin), could you check what the "Collation" of our database is set to? For example:

USE dbname;
SELECT @@character_set_database, @@collation_database;

Or in phpMyAdmin the collation is given in the database listing. My guess is that we are not using UTF-8. That can be changed (after a backup) with:

ALTER DATABASE dbname CHARACTER SET utf8 COLLATE utf8_general_ci;

Or in phpMyAdmin, select the databse of this wiki, click on the "Operations" tab, in the "Collation" box select "utf8_general_ci", and finally click on "Go". Hopefully this is the cause of this long standing and painful issue.

Bugman (talk) 03:33, 9 September 2020 (EDT)

Hi Edward,
I somehow missed all these previous reports :-( Sorry!
You're right. The database is in latin1. We're actually currently in the process of migrating some of our server work and updating. I will take care of setting the correct collation on that occasion.
Gijs (talk) 04:24, 9 September 2020 (EDT)
Great, that sounds exactly like this problem. Only pages with 'latin1' characters in their names can be edited. I really hope switching the collation to UTF-8 will fix the problem. There must have been a MySQL server migration many years ago where the old database was UTF-8 and the import automatically changed the language to the server default of 'latin1', as many pages were created on this wiki with non-latin1 characters in the past. I see this with my MySQL database too - I have to switch back to UTF-8 after import into the new SQL database.
Bugman (talk) 06:00, 9 September 2020 (EDT)

Needing an extra pair of eyes

There is a problem with automatic categorization in {{Autoflight Navigation}} that I can not seem to solve.

For details see Template talk:Autoflight Navigation#Automatic categorization seem broken.

Johan G (Talk | contribs) 10:26, 10 September 2020 (EDT)

All done! In summary, the {{howto other}} template logic was completely broken and was operating as the {{main other}} template instead! Checking if the {{NAMESPACE}} is set to {{ns:0}} is not how you check for the "Howto" namespace. As I don't know the numeric value of this namespace, I switched to comparing {{NAMESPACE}} to the simple string 'Howto'. So the template is now fixed. We should see a lot of auto-categorisation additions and fixes now. I also switched {{Autoflight Navigation}} to use {{namespace detect}} to simplify its logic.
Bugman (talk) 06:14, 11 September 2020 (EDT)
Thank you som much for fixing that. :-)
Did not think of comparing the namespace numbers between the templates.
I was wondering where I found the numbers, but could not quite remember. If I figure it out I will probably add the source for those at a suitable place, like under Technical details in ducumentation for {{namespace detect}} or something like that, though using full names of the namespaces is probably the safer option.
Johan G (Talk | contribs) 02:07, 12 September 2020 (EDT)

The Howto namespace

Copied here from Template talk:Autoflight Navigation.

To be honest, from the start I have considered the Howto namespace to be an abomination. There is absolutely no need for it, as one could simply have articles in the main namespace with a Howto: prefix (IIRC they call this "user administered namespaces" or "pseudo namespaces" on Wikipedia). To not have to type the prefix, one could simply create redirects. Creating a separate Howto namespace have caused issues in the past, like that the search function per default only looks for articles in the Main namespace. It is not entirely unlikely that what we see here might be some configuration issue as well.

Sorry for the rant. And thanks again.

Johan G (Talk | contribs) 06:29, 11 September 2020 (EDT)

I wouldn't call that a rant. It would be better on FlightGear wiki:Village pump though. To me 'Howto' here is simply a categorisation. Why is that categorisation even needed in the page title? I never liked this namespace, specifically because the default search misses it, and there is a significant grey area of what you would categorise as a 'howto' or not. I think it would be better managed with a basic {{howto}} template at the start of each of these articles which automatically adds Category:Howto. If you take your discussion above over to the village pump, I'll copy this over there as well.
Bugman (talk) 07:56, 11 September 2020 (EDT)

Space shuttle screenshots category need cleanup

There currently are quite a number of misplaced files in the Space Shuttle screenshot categories, possibly making it harder to find screenshots and other images. For example external screenshots in the cockpit detail category, that preferably should be closeup images of panels and displays, and screenshots of large portions of the cockpit in the cockpit detail category.

I do expect some overlap between the cockpit categories and the custom dialog categories as dialogs are featured in a lot of those.

There are also a lot of diagrams with no part of the Space Shuttle at all in the screenshot categories, those are more at home in the Space Shuttle diagrams category.

Johan G (Talk | contribs) 20:10, 3 November 2020 (EST)

Have done a little cleanup, a lot left to do.

If my recategorization edits fill up recent changes, click Hide minor edits. When (re)categorizing, I mark my edits as minor edit so they can be filtered away if they fill up recent changes (I have gotten frustrated comments on my edits filling up recent changes before).

Johan G (Talk | contribs) 21:23, 3 November 2020 (EST)

Also added Category:Screenshots of Earthview to relevant Space Shuttle screenshots up to and including File:Shuttle-tutorial2-01.jpg.

Johan G (Talk | contribs) 05:08, 6 November 2020 (EST)