mw.mh370.wiki - User contributions [en]

https://mw.mh370.wiki/w/api.php?action=feedcontributions&feedformat=atom&user=GrantM mw.mh370.wiki - User contributions [en] 2026-04-17T12:26:55Z User contributions MediaWiki 1.43.1 https://mw.mh370.wiki/w/index.php?title=MediaWiki:Common.css&diff=2462 MediaWiki:Common.css 2025-12-24T10:55:27Z

<p>GrantM: </p> <hr /> <div>/* CSS placed here will be applied to all skins */<br /> <br /> <br /> /* #ca-nstab-ns_3400 { display:none !important; } */<br /> <br /> /* body.ns-0 #ca-talk { display:none !important; } */ /* this works */<br /> <br /> /* body.ns-0 #ca-nstab { display:none !important; } doesn't work */<br /> <br /> body.ns-3400 #ca-talk { display:none !important; } /* this works */<br /> <br /> body.ns-3400 #ca-nstab-snippets { display:none !important; }<br /> <br /> <br /> <br /> /* 5 August 2025 Added Colors for use in Sidebar and MediaWiki interface */<br /> <br /> /* Steel Blue */<br /> :root { --SteelBlue-80: #B6CEE2;<br /> --SteelBlue-70: #91B6D4;<br /> --SteelBlue-60: #6C9DC6;<br /> --SteelBlue-50: #4785B8;<br /> --SteelBlue-40: #396A93;<br /> } /* End Steel Blue */<br /> <br /> /* Tan */<br /> :root { --Tan-90: #F1E7DA;<br /> --Tan-80: #E2CFB6;<br /> --Tan-70: #D4B791;<br /> --Tan-60: #C69F6C;<br /> --Tan-50: #B88747;<br /> --Tan-40: #936C39;<br /> } /* End Tan */<br /> <br /> /* 10 Dec 2025 added shades of Light Steel Blue #b0c4de (for catlinks) */<br /> :root { --LightSteelBlue: #B0C4DE;<br /> --LightSteelBlue-80: #B7C9E1;<br /> --LightSteelBlue-85: #C9D7E8;<br /> --LightSteelBlue-90: #DBE4F0;<br /> } /* End Light Steel Blue */<br /> <br /> /* 10 Dec 2025 added shades of Light Sky Blue #99CCEF for use in page headers */<br /> :root { --LightSkyBlue: #99CCFF;<br /> } /* End Light Sky Blue */<br /> <br /> <br /> /* 10 Dec 2025 added variables for greys */<br /> :root { --PageBackground: #F2F2F2;<br /> --QuoteBackground: #FAFAFA;<br /> --BlackText: #000000;<br /> }<br /> <br /> /* Black and White as used on MH370 site for tables */<br /> :root { --clr-white: #FFFFFF;<br /> --clr-black: #000000;<br /> }<br /> <br /> :root { --clr-grey-base-50: #808080; } /* exactly half way between black and white */<br /> <br /> <br /> <br /> <br /> /* Items sorted with lightest color shade first, approximating a Z order */<br /> <br /> #mw-head { background-color: var(--SteelBlue-80); } /* full width at top of screen, behind logo */<br /> <br /> /* mw-body-content is in front of mw-body */<br /> .mw-body-content { background-color: var(--PageBackground); border-radius: 1em; padding-top:2em; padding-bottom:2em; padding-left:2.5em; padding-right:2.5em; } <br /> <br /> .mw-body { background-color: var(--SteelBlue-70); } /* is background for everything below header and right of left panel and down to footer */<br /> <br /> .mw-footer { background-color: var(--SteelBlue-60); } /* does not extend to bottom of the screen */<br /> .mw-footer { padding-bottom:2em; } /* added 24 Dec 2025 */<br /> <br /> #mw-panel.vector-legacy-sidebar.collapsible-nav { background-color: var(--SteelBlue-50); } /* background for menu but extends to top of screen and behind logo and in front of header */<br /> <br /> body { background-color: var(--SteelBlue-40); } /* everything below mw-head, full width of screen, to bottom of screen */<br /> <br /> .catlinks { background-color: var(--LightSteelBlue); } /* border on category row. was #bdccdb */<br /> .mw-normal-catlinks { background-color: var(--LightSteelBlue-90); padding-left:20px; } /* was #ced8e4 */<br /> <br /> <br /> /* 17 Sept 2025 added classes for different background color pages */<br /> .BluePage { color: #9900CC; } /* Purple text on blue background */<br /> .GreenPage { color: #000099; } /* Blue text on green background */<br /> <br /> .mw-body-content:has(.BluePage) { background-color: #E6F5FF; }<br /> .mw-body-content:has(.GreenPage) { background-color: #E6FFF2; }<br /> <br /> <br /> <br /> <br /> <br /> /* 2 August added class to standardised margins when displaying a category tree */<br /> .displayCatTree { margin-left:4em; }<br /> <br /> <br /> <br /> /* 1 August 2025 Added a class to standardise page headers, plus a variant for category pages */<br /> <br /> .header { width:90%; <br /> margin-left:auto; margin-right:auto; margin-bottom:1em; padding-top:10px; padding-bottom:10px; <br /> text-align:justify;<br /> background-color: var(--LightSkyBlue); border-color: var(--LightSkyBlue); border-radius: 10px;<br /> } /* colors were #cce6ff */<br /> <br /> .cat { background-color: var(--LightSteelBlue-85); border-color: var(--LightSteelBlue-85); } /* pale shade of blue for header on category pages. was #e8f2fc */<br /> <br /> <br /> <br /> /* 28 July 2025 attempt to indent unordered lists */<br /> .mw-body-content ul { display:block; position:relative; left:1em; overflow-wrap: normal; word-wrap: normal; max-width:90%; text-align:justify; } /* mw-body-content limits scope */<br /> /* .ulNormal { display:block; position:relative; left:2vw; overflow-wrap: normal; word-wrap: normal; max-width:90%; text-align:justify; } */<br /> <br /> <br /> /* 28 July 2025 added style for quoted text, adapted from mh370wiki.net, used instead of blockquote */<br /> <br /> .quote { width: 90%; background: var(--QuoteBackground); /* contrast against page background */<br /> padding-left: 1em;; padding-right: 1em; padding-top: 0.5em; padding-bottom: 0.5em; /* was px */<br /> margin-left:auto; margin-right:auto; margin-top:0.5em; margin-bottom:0.5em; <br /> text-align:justify; color: var(--BlackText); /* black */<br /> }<br /> <br /> <br /> /* 27 July 2025 added left margin to images */<br /> .mw-default-size { margin-left: 2em; } /* this is the container. applies to all images */<br /> <br /> <br /> <br /> <br /> /* 25 July 2025 added style to indent <pre> Note: No dot required before pre */<br /> <br /> pre { width: 90%; margin-left: auto; margin-right: auto; }<br /> <br /> <br /> <br /> /* 22 July 2025 Added style to enlarge fonts on Tooltips but currently unable to change tooltip width */<br /> <br /> .mw-lingo-definition-text { font-size:125%; } /* Tooltip is also styled as a qtip in jquery.qtip.css */<br /> <br /> /* _________________________________________________________________________________________________________________________*/<br /> <br /> <br /> /* 20 July 2025 Fluid Typography and Font Variables */<br /> /* Copied from mh370wiki.net and adapted for use here */<br /> <br /> /* Fluid Typography - see Responsive And Fluid Typography With vh And vw Units<br /> https://www.smashingmagazine.com/2016/05/fluid-typography/ <br /> Unlike responsive typography, which changes only at set breakpoints,<br /> fluid typography resizes smoothly to match any device width.<br /> */<br /> /* Variables for font size ( to be used in Vector.css ) see https://foxland.fi/naming-typography-css-variables/ */<br /> <br /> /* Clamp() for min, preferred, max font size see https://developer.mozilla.org/en-US/docs/Web/CSS/clamp() */<br /> /* Notes on font sizes<br /> The default text size in browsers is 16px. So, the default size of 1em is 16px.<br /> rem (root em) references the base font size of the document.<br /> Assuming that the base font size is 16px, we get the following values:<br /> 1rem = 16px<br /> 1.5rem = 24px<br /> 0.5rem = 8px<br /> */<br /> <br /> /* Use clamp ( min preferred max ) */<br /> :root { font-size: clamp( 1vw, 1.05rem, 1.2vw ); } <br /> <br /> /* Font sizes using variables from https://foxland.fi/naming-typography-css-variables/ */<br /> /* Example font-size: var(--font-size-100); */<br /> :root { --font-size-625: 62.5%; /* 62.5% of root font size */<br /> --font-size-875: 87.5%; /* 87.5% x root font size */<br /> --font-size-090: 90%; /* 90% x root font size */<br /> --font-size-095: 95%; /* 95% x root font size */<br /> --font-size-100: 100%; /* 100% = root font size */<br /> --font-size-105: 105%; /* 105% x root font size */<br /> --font-size-110: 110%; /* 110% x root font size */<br /> --font-size-115: 115%; /* 115% x root font size */<br /> --font-size-120: 120%; /* 120% x root font size */ <br /> --font-size-125: 125%; /* 125% x root font size */<br /> }<br /> <br /> /* _________________________________________________________________________________________________________________________*/<br /> <br /> /* Text Styles using Font Variables */<br /> <br /> /* Font Sizes */<br /> body { font-size: var(--font-size-100); }<br /> p { font-size: var(--font-size-100); }<br /> dl dt dd { font-size: var(--font-size-100); }<br /> dd { margin-bottom: 1em; } /* added 11 Oct 2022 to space between a dd and the next dt */<br /> /* ul ol li { font-size: var(--font-size-100); } */<br /> <br /> /* Headings are sized by percentage over the base font and also resize based on viewport width */<br /> h1 {font-size: var(--font-size-125);} <br /> h2 {font-size: var(--font-size-120);} /* h2 was previously not defined */<br /> h3 {font-size: var(--font-size-115);}<br /> h4 {font-size: var(--font-size-110);}<br /> h5 {font-size: var(--font-size-105);}<br /> /* h6 {font-size: var(--font-size-100);} modified 4 Jan 2025 */<br /> h6 {font-size: var(--font-size-090);}<br /> <br /> h1, h3, h4, h5, h6 {<br /> font-family: Arial, Helvetica, sans-serif;<br /> color: var(--clr-DeepPurple-base-30); <br /> font-weight: 600;<br /> }<br /> <br /> /* _________________________________________________________________________________________________________________________*/<br /> <br /> /* Text layout using padding - use vw for responsive */<br /> /* 10px = 0.625rem; 20px = 1.25rem; 30px = 1.875rem; 40px = 2.5rem; */<br /> /* h1, h2, h3 align with left of page. h4 is rarely used */<br /> /* h1, h2, h3 align with left of page. h4 is rarely used */<br /> h5 { padding-left: 0.5vw; } <br /> h6 { padding-left: 0.5vw; } <br /> p { padding-left: 1vw; padding-right:1vw; } <br /> <br /> /* Margin above, added 14 Dec 2025 to avoid need for <br /> before a major heading (h3) */<br /> h3 { margin-top: 0.2vh; } /* started with .5vw */<br /> <br /> /* padding below added 15 Dec 2025 */<br /> li { padding-bottom: 0.2vh; }<br /> <br /> <br /> <br /> /* ordered list ol and altered padding for a nested list */<br /> ol { display:block; position:relative; left:0.9vw; overflow-wrap: normal; word-wrap: normal; max-width:90%; padding-right:0.9vw; <br /> & ol { display:block; position:relative; left:-0.9vw; overflow-wrap: normal; word-wrap: normal; max-width:90%; list-style-type:lower-roman; }<br /> } <br /> <br /> /* Definition List */<br /> dl { padding-left: 2.5vw; padding-right:2.5vw; } <br /> dt { padding:right:2.5vw; padding-right:2.5vw; text-align:justify; }<br /> dd { padding:right:2.5vw; padding-right:2.5vw; text-align:justify; }<br /> <br /> <br /> /* _________________________________________________________________________________________________________________________*/<br /> <br /> /* 11 July 2025 Rows and Columns */<br /> <br /> /* 26 July 2020 New row/column layout */<br /> /* July 2025 Copied from www.mh370wiki.net ( with minor adjustments ) */<br /> .Row { display: flex; flex-flow: row nowrap; justify-content: flex-start; justify-content: space-between; width: 100%; } <br /> .row { display: flex; flex-flow: row nowrap; justify-content: flex-start; justify-content: space-between; width: 100%; } <br /> .column-left { display: flex; flex-flow: column; flex-grow: 1; flex-shrink: 1; padding-right: 1em; }<br /> .column-center {display: flex; flex-flow: column; flex-grow: 1; flex-shrink: 1; margin-left: 1em; margin-right: 1em; }<br /> .column-right {display: flex; flex-flow: column; flex-grow: 1; flex-shrink: 1; padding-left: 1em; }<br /> <br /> /* flex-basis determines column width */ <br /> .col-width-75 { flex-basis: 75%; flex-shrink: 15;} /* usually main column 75% and Comments or Notes 25% */<br /> .col-width-70 { flex-basis: 65%; flex-shrink: 13;} /* added 28 Oct 2020 to use with col-width-30 even though that is actually 33% */<br /> .col-width-60 { flex-basis: 60%; flex-shrink: 12;} /* two columns in ratio 3:2 */<br /> .col-width-50 { flex-basis: 50%; flex-shrink: 10;} /* two equal columns */<br /> .col-width-40 { flex-basis: 40%; flex-shrink: 8;} <br /> /*.col-width-30 { flex-basis: 33%; flex-shrink: 7;} */<br /> /* .col-width-30 { flex: 1 1 0;} /* 16 Nov 2020 If columns are equal then flex should be 1 1 0 */<br /> .col-width-30 { flex-basis: 0; }<br /> .col-width-25 { flex-basis: 25%; flex-shrink: 5;} /* usually right column */<br /> <br /> <br /> /* _________________________________________________________________________________________________________________________*/<br /> /* Tables - adapted from MH370 site 10 Dec 2025 */<br /> /* flex-font-base removed */<br /> <br /> <br /> th { font-weight:bold; }<br /> <br /> th, td { padding-left: 0.6em; padding-right: 0.6em; } /* added 29 Oct 2020. will apply to all types of table */ <br /> th, td { vertical-align: top; } /* added 31 Oct 2020. will apply to all types of table */<br /> /* Custom Tables */<br /> /* w=width Use class in conjunction with tbl or tblB */<br /> .w100 { width: 100%; } /* Table width 100% with no margins */<br /> .w90 { width: 90%; margin-left: auto; margin-right: auto; } /* Table width 90% centred */<br /> .w80 { width: 80%; margin-left: auto; margin-right: auto; } /* Table width 80% centred */<br /> .w75 { width: 75%; margin-left: auto; margin-right: auto; } /* Table width 75% centred */<br /> .w70 { width: 70%; margin-left: auto; margin-right: auto; } /* Table width 70% centred */<br /> .w60 { width: 60%; margin-left: auto; margin-right: auto; } /* Table width 60% centred */<br /> .w50 { width: 50%; margin-left: auto; margin-right: auto; } /* Table width 50% centred */<br /> .w40 { width: 40%; margin-left: auto; margin-right: auto; } /* Table width 40% centred */<br /> .w30 { width: 30%; margin-left: auto; margin-right: auto; } /* Table width 30%centred */<br /> .w25 { width: 25%; margin-left: auto; margin-right: auto; } /* Table width 25% centred */<br /> .w20 { width: 20%; margin-left: auto; margin-right: auto; } /* Table width 20% centred */<br /> .wauto { margin-left: auto; margin-right: auto; } <br /> <br /> /* Table centred */<br /> /* tbl = table. B=bordered. tblB is a bordered table with white background */<br /> /* tblBcenter = table with border and columns centered */<br /> <br /> .tbl { background-color: var(--clr-white); color: var(--clr-black); /* Background is white for a table with no borders. */<br /> vertical-align: top; }<br /> .tbl th td { background-color: var(--clr-white); color: var(--clr-black);<br /> text-align: left; font-weight: bold; vertical-align: top; }<br /> .tbl td { background-color: var(--clr-white); color: var(--clr-black);<br /> text-align: left; vertical-align: top; }<br /> <br /> .tbl tr:nth-child(even) { background-color: var(--clr-white); } /* overwrite the zebra striping default */<br /> .tbl tr:nth-child(odd) { background-color: var(--clr-white); } /* overwrite the zebra striping default */<br /> <br /> .tblB { background-color: var(--clr-white); color: var(--clr-black); <br /> border-collapse: collapse; <br /> border: 1px solid var(--clr-grey-base-50); }<br /> <br /> .tblB th { background-color: var(--clr-white); color: var(--clr-black);<br /> border-collapse: collapse; border: 1px solid; border-color: var(--clr-grey-base-50);<br /> text-align: left; font-weight: bold; }<br /> <br /> .tblB td { background-color: var(--clr-white); color: var(--clr-black);<br /> border-collapse: collapse; border: 1px solid var(--clr-grey-base-50);<br /> text-align: left; }<br /> <br /> .tblB tr:nth-child(even) { background-color: var(--clr-white); } /* overwrite the zebra striping default */<br /> .tblB tr:nth-child(odd) { background-color: var(--clr-white); } /* overwrite the zebra striping default */<br /> <br /> <br /> .tblBcenter { background-color: var(--clr-white); color: var(--clr-black); <br /> border-collapse: collapse; border: 1px solid; border-color: var(--clr-grey-base-50); }<br /> <br /> .tblBcenter th { background-color: var(--clr-white); color: var(--clr-black);<br /> border-collapse: collapse; border: 1px solid; border-color: var(--clr-grey-base-50);<br /> text-align: center; font-weight: bold; }<br /> <br /> .tblBcenter td { background-color: var(--clr-white); color: var(--clr-black);<br /> border-collapse: collapse; border: 1px solid; border-color: var(--clr-grey-base-50);<br /> text-align: center; }<br /> <br /> .tblBcenter tr:nth-child(even) { background-color: var(--clr-white); } /* overwrite the zebra striping default */<br /> .tblBcenter tr:nth-child(odd) { background-color: var(--clr-white); } /* overwrite the zebra striping default */<br /> <br /> <br /> <br /> /* Overflow for Custom Tables - added 30 Dec 2020 */<br /> .table { overflow-x: auto; } /* this works */<br /> /* .tbl .tblB .tblBcenter { overflow-x: auto; } /* should not show vertical scrollbar and horizontal only when needed */<br /> .tblB { overflow-x: auto; }</div>

GrantM https://mw.mh370.wiki/w/index.php?title=MediaWiki:Common.css&diff=2461 MediaWiki:Common.css 2025-12-24T10:53:59Z

<p>GrantM: </p> <hr /> <div>/* CSS placed here will be applied to all skins */<br /> <br /> <br /> /* #ca-nstab-ns_3400 { display:none !important; } */<br /> <br /> /* body.ns-0 #ca-talk { display:none !important; } */ /* this works */<br /> <br /> /* body.ns-0 #ca-nstab { display:none !important; } doesn't work */<br /> <br /> body.ns-3400 #ca-talk { display:none !important; } /* this works */<br /> <br /> body.ns-3400 #ca-nstab-snippets { display:none !important; }<br /> <br /> <br /> <br /> /* 5 August 2025 Added Colors for use in Sidebar and MediaWiki interface */<br /> <br /> /* Steel Blue */<br /> :root { --SteelBlue-80: #B6CEE2;<br /> --SteelBlue-70: #91B6D4;<br /> --SteelBlue-60: #6C9DC6;<br /> --SteelBlue-50: #4785B8;<br /> --SteelBlue-40: #396A93;<br /> } /* End Steel Blue */<br /> <br /> /* Tan */<br /> :root { --Tan-90: #F1E7DA;<br /> --Tan-80: #E2CFB6;<br /> --Tan-70: #D4B791;<br /> --Tan-60: #C69F6C;<br /> --Tan-50: #B88747;<br /> --Tan-40: #936C39;<br /> } /* End Tan */<br /> <br /> /* 10 Dec 2025 added shades of Light Steel Blue #b0c4de (for catlinks) */<br /> :root { --LightSteelBlue: #B0C4DE;<br /> --LightSteelBlue-80: #B7C9E1;<br /> --LightSteelBlue-85: #C9D7E8;<br /> --LightSteelBlue-90: #DBE4F0;<br /> } /* End Light Steel Blue */<br /> <br /> /* 10 Dec 2025 added shades of Light Sky Blue #99CCEF for use in page headers */<br /> :root { --LightSkyBlue: #99CCFF;<br /> } /* End Light Sky Blue */<br /> <br /> <br /> /* 10 Dec 2025 added variables for greys */<br /> :root { --PageBackground: #F2F2F2;<br /> --QuoteBackground: #FAFAFA;<br /> --BlackText: #000000;<br /> }<br /> <br /> /* Black and White as used on MH370 site for tables */<br /> :root { --clr-white: #FFFFFF;<br /> --clr-black: #000000;<br /> }<br /> <br /> :root { --clr-grey-base-50: #808080; } /* exactly half way between black and white */<br /> <br /> <br /> <br /> <br /> /* Items sorted with lightest color shade first, approximating a Z order */<br /> <br /> #mw-head { background-color: var(--SteelBlue-80); } /* full width at top of screen, behind logo */<br /> <br /> /* mw-body-content is in front of mw-body */<br /> .mw-body-content { background-color: var(--PageBackground); border-radius: 1em; padding-top:2em; padding-bottom:2em; padding-left:2.5em; padding-right:2.5em; } <br /> <br /> .mw-body { background-color: var(--SteelBlue-70); } /* is background for everything below header and right of left panel and down to footer */<br /> <br /> .mw-footer { background-color: var(--SteelBlue-60); } /* does not extend to bottom of the screen */<br /> .mw-footer { padding-bottom:20px; } /* added 24 Dec 2025 */<br /> <br /> #mw-panel.vector-legacy-sidebar.collapsible-nav { background-color: var(--SteelBlue-50); } /* background for menu but extends to top of screen and behind logo and in front of header */<br /> <br /> body { background-color: var(--SteelBlue-40); } /* everything below mw-head, full width of screen, to bottom of screen */<br /> <br /> .catlinks { background-color: var(--LightSteelBlue); } /* border on category row. was #bdccdb */<br /> .mw-normal-catlinks { background-color: var(--LightSteelBlue-90); padding-left:20px; } /* was #ced8e4 */<br /> <br /> <br /> /* 17 Sept 2025 added classes for different background color pages */<br /> .BluePage { color: #9900CC; } /* Purple text on blue background */<br /> .GreenPage { color: #000099; } /* Blue text on green background */<br /> <br /> .mw-body-content:has(.BluePage) { background-color: #E6F5FF; }<br /> .mw-body-content:has(.GreenPage) { background-color: #E6FFF2; }<br /> <br /> <br /> <br /> <br /> <br /> /* 2 August added class to standardised margins when displaying a category tree */<br /> .displayCatTree { margin-left:4em; }<br /> <br /> <br /> <br /> /* 1 August 2025 Added a class to standardise page headers, plus a variant for category pages */<br /> <br /> .header { width:90%; <br /> margin-left:auto; margin-right:auto; margin-bottom:1em; padding-top:10px; padding-bottom:10px; <br /> text-align:justify;<br /> background-color: var(--LightSkyBlue); border-color: var(--LightSkyBlue); border-radius: 10px;<br /> } /* colors were #cce6ff */<br /> <br /> .cat { background-color: var(--LightSteelBlue-85); border-color: var(--LightSteelBlue-85); } /* pale shade of blue for header on category pages. was #e8f2fc */<br /> <br /> <br /> <br /> /* 28 July 2025 attempt to indent unordered lists */<br /> .mw-body-content ul { display:block; position:relative; left:1em; overflow-wrap: normal; word-wrap: normal; max-width:90%; text-align:justify; } /* mw-body-content limits scope */<br /> /* .ulNormal { display:block; position:relative; left:2vw; overflow-wrap: normal; word-wrap: normal; max-width:90%; text-align:justify; } */<br /> <br /> <br /> /* 28 July 2025 added style for quoted text, adapted from mh370wiki.net, used instead of blockquote */<br /> <br /> .quote { width: 90%; background: var(--QuoteBackground); /* contrast against page background */<br /> padding-left: 1em;; padding-right: 1em; padding-top: 0.5em; padding-bottom: 0.5em; /* was px */<br /> margin-left:auto; margin-right:auto; margin-top:0.5em; margin-bottom:0.5em; <br /> text-align:justify; color: var(--BlackText); /* black */<br /> }<br /> <br /> <br /> /* 27 July 2025 added left margin to images */<br /> .mw-default-size { margin-left: 2em; } /* this is the container. applies to all images */<br /> <br /> <br /> <br /> <br /> /* 25 July 2025 added style to indent <pre> Note: No dot required before pre */<br /> <br /> pre { width: 90%; margin-left: auto; margin-right: auto; }<br /> <br /> <br /> <br /> /* 22 July 2025 Added style to enlarge fonts on Tooltips but currently unable to change tooltip width */<br /> <br /> .mw-lingo-definition-text { font-size:125%; } /* Tooltip is also styled as a qtip in jquery.qtip.css */<br /> <br /> /* _________________________________________________________________________________________________________________________*/<br /> <br /> <br /> /* 20 July 2025 Fluid Typography and Font Variables */<br /> /* Copied from mh370wiki.net and adapted for use here */<br /> <br /> /* Fluid Typography - see Responsive And Fluid Typography With vh And vw Units<br /> https://www.smashingmagazine.com/2016/05/fluid-typography/ <br /> Unlike responsive typography, which changes only at set breakpoints,<br /> fluid typography resizes smoothly to match any device width.<br /> */<br /> /* Variables for font size ( to be used in Vector.css ) see https://foxland.fi/naming-typography-css-variables/ */<br /> <br /> /* Clamp() for min, preferred, max font size see https://developer.mozilla.org/en-US/docs/Web/CSS/clamp() */<br /> /* Notes on font sizes<br /> The default text size in browsers is 16px. So, the default size of 1em is 16px.<br /> rem (root em) references the base font size of the document.<br /> Assuming that the base font size is 16px, we get the following values:<br /> 1rem = 16px<br /> 1.5rem = 24px<br /> 0.5rem = 8px<br /> */<br /> <br /> /* Use clamp ( min preferred max ) */<br /> :root { font-size: clamp( 1vw, 1.05rem, 1.2vw ); } <br /> <br /> /* Font sizes using variables from https://foxland.fi/naming-typography-css-variables/ */<br /> /* Example font-size: var(--font-size-100); */<br /> :root { --font-size-625: 62.5%; /* 62.5% of root font size */<br /> --font-size-875: 87.5%; /* 87.5% x root font size */<br /> --font-size-090: 90%; /* 90% x root font size */<br /> --font-size-095: 95%; /* 95% x root font size */<br /> --font-size-100: 100%; /* 100% = root font size */<br /> --font-size-105: 105%; /* 105% x root font size */<br /> --font-size-110: 110%; /* 110% x root font size */<br /> --font-size-115: 115%; /* 115% x root font size */<br /> --font-size-120: 120%; /* 120% x root font size */ <br /> --font-size-125: 125%; /* 125% x root font size */<br /> }<br /> <br /> /* _________________________________________________________________________________________________________________________*/<br /> <br /> /* Text Styles using Font Variables */<br /> <br /> /* Font Sizes */<br /> body { font-size: var(--font-size-100); }<br /> p { font-size: var(--font-size-100); }<br /> dl dt dd { font-size: var(--font-size-100); }<br /> dd { margin-bottom: 1em; } /* added 11 Oct 2022 to space between a dd and the next dt */<br /> /* ul ol li { font-size: var(--font-size-100); } */<br /> <br /> /* Headings are sized by percentage over the base font and also resize based on viewport width */<br /> h1 {font-size: var(--font-size-125);} <br /> h2 {font-size: var(--font-size-120);} /* h2 was previously not defined */<br /> h3 {font-size: var(--font-size-115);}<br /> h4 {font-size: var(--font-size-110);}<br /> h5 {font-size: var(--font-size-105);}<br /> /* h6 {font-size: var(--font-size-100);} modified 4 Jan 2025 */<br /> h6 {font-size: var(--font-size-090);}<br /> <br /> h1, h3, h4, h5, h6 {<br /> font-family: Arial, Helvetica, sans-serif;<br /> color: var(--clr-DeepPurple-base-30); <br /> font-weight: 600;<br /> }<br /> <br /> /* _________________________________________________________________________________________________________________________*/<br /> <br /> /* Text layout using padding - use vw for responsive */<br /> /* 10px = 0.625rem; 20px = 1.25rem; 30px = 1.875rem; 40px = 2.5rem; */<br /> /* h1, h2, h3 align with left of page. h4 is rarely used */<br /> /* h1, h2, h3 align with left of page. h4 is rarely used */<br /> h5 { padding-left: 0.5vw; } <br /> h6 { padding-left: 0.5vw; } <br /> p { padding-left: 1vw; padding-right:1vw; } <br /> <br /> /* Margin above, added 14 Dec 2025 to avoid need for <br /> before a major heading (h3) */<br /> h3 { margin-top: 0.2vh; } /* started with .5vw */<br /> <br /> /* padding below added 15 Dec 2025 */<br /> li { padding-bottom: 0.2vh; }<br /> <br /> <br /> <br /> /* ordered list ol and altered padding for a nested list */<br /> ol { display:block; position:relative; left:0.9vw; overflow-wrap: normal; word-wrap: normal; max-width:90%; padding-right:0.9vw; <br /> & ol { display:block; position:relative; left:-0.9vw; overflow-wrap: normal; word-wrap: normal; max-width:90%; list-style-type:lower-roman; }<br /> } <br /> <br /> /* Definition List */<br /> dl { padding-left: 2.5vw; padding-right:2.5vw; } <br /> dt { padding:right:2.5vw; padding-right:2.5vw; text-align:justify; }<br /> dd { padding:right:2.5vw; padding-right:2.5vw; text-align:justify; }<br /> <br /> <br /> /* _________________________________________________________________________________________________________________________*/<br /> <br /> /* 11 July 2025 Rows and Columns */<br /> <br /> /* 26 July 2020 New row/column layout */<br /> /* July 2025 Copied from www.mh370wiki.net ( with minor adjustments ) */<br /> .Row { display: flex; flex-flow: row nowrap; justify-content: flex-start; justify-content: space-between; width: 100%; } <br /> .row { display: flex; flex-flow: row nowrap; justify-content: flex-start; justify-content: space-between; width: 100%; } <br /> .column-left { display: flex; flex-flow: column; flex-grow: 1; flex-shrink: 1; padding-right: 1em; }<br /> .column-center {display: flex; flex-flow: column; flex-grow: 1; flex-shrink: 1; margin-left: 1em; margin-right: 1em; }<br /> .column-right {display: flex; flex-flow: column; flex-grow: 1; flex-shrink: 1; padding-left: 1em; }<br /> <br /> /* flex-basis determines column width */ <br /> .col-width-75 { flex-basis: 75%; flex-shrink: 15;} /* usually main column 75% and Comments or Notes 25% */<br /> .col-width-70 { flex-basis: 65%; flex-shrink: 13;} /* added 28 Oct 2020 to use with col-width-30 even though that is actually 33% */<br /> .col-width-60 { flex-basis: 60%; flex-shrink: 12;} /* two columns in ratio 3:2 */<br /> .col-width-50 { flex-basis: 50%; flex-shrink: 10;} /* two equal columns */<br /> .col-width-40 { flex-basis: 40%; flex-shrink: 8;} <br /> /*.col-width-30 { flex-basis: 33%; flex-shrink: 7;} */<br /> /* .col-width-30 { flex: 1 1 0;} /* 16 Nov 2020 If columns are equal then flex should be 1 1 0 */<br /> .col-width-30 { flex-basis: 0; }<br /> .col-width-25 { flex-basis: 25%; flex-shrink: 5;} /* usually right column */<br /> <br /> <br /> /* _________________________________________________________________________________________________________________________*/<br /> /* Tables - adapted from MH370 site 10 Dec 2025 */<br /> /* flex-font-base removed */<br /> <br /> <br /> th { font-weight:bold; }<br /> <br /> th, td { padding-left: 0.6em; padding-right: 0.6em; } /* added 29 Oct 2020. will apply to all types of table */ <br /> th, td { vertical-align: top; } /* added 31 Oct 2020. will apply to all types of table */<br /> /* Custom Tables */<br /> /* w=width Use class in conjunction with tbl or tblB */<br /> .w100 { width: 100%; } /* Table width 100% with no margins */<br /> .w90 { width: 90%; margin-left: auto; margin-right: auto; } /* Table width 90% centred */<br /> .w80 { width: 80%; margin-left: auto; margin-right: auto; } /* Table width 80% centred */<br /> .w75 { width: 75%; margin-left: auto; margin-right: auto; } /* Table width 75% centred */<br /> .w70 { width: 70%; margin-left: auto; margin-right: auto; } /* Table width 70% centred */<br /> .w60 { width: 60%; margin-left: auto; margin-right: auto; } /* Table width 60% centred */<br /> .w50 { width: 50%; margin-left: auto; margin-right: auto; } /* Table width 50% centred */<br /> .w40 { width: 40%; margin-left: auto; margin-right: auto; } /* Table width 40% centred */<br /> .w30 { width: 30%; margin-left: auto; margin-right: auto; } /* Table width 30%centred */<br /> .w25 { width: 25%; margin-left: auto; margin-right: auto; } /* Table width 25% centred */<br /> .w20 { width: 20%; margin-left: auto; margin-right: auto; } /* Table width 20% centred */<br /> .wauto { margin-left: auto; margin-right: auto; } <br /> <br /> /* Table centred */<br /> /* tbl = table. B=bordered. tblB is a bordered table with white background */<br /> /* tblBcenter = table with border and columns centered */<br /> <br /> .tbl { background-color: var(--clr-white); color: var(--clr-black); /* Background is white for a table with no borders. */<br /> vertical-align: top; }<br /> .tbl th td { background-color: var(--clr-white); color: var(--clr-black);<br /> text-align: left; font-weight: bold; vertical-align: top; }<br /> .tbl td { background-color: var(--clr-white); color: var(--clr-black);<br /> text-align: left; vertical-align: top; }<br /> <br /> .tbl tr:nth-child(even) { background-color: var(--clr-white); } /* overwrite the zebra striping default */<br /> .tbl tr:nth-child(odd) { background-color: var(--clr-white); } /* overwrite the zebra striping default */<br /> <br /> .tblB { background-color: var(--clr-white); color: var(--clr-black); <br /> border-collapse: collapse; <br /> border: 1px solid var(--clr-grey-base-50); }<br /> <br /> .tblB th { background-color: var(--clr-white); color: var(--clr-black);<br /> border-collapse: collapse; border: 1px solid; border-color: var(--clr-grey-base-50);<br /> text-align: left; font-weight: bold; }<br /> <br /> .tblB td { background-color: var(--clr-white); color: var(--clr-black);<br /> border-collapse: collapse; border: 1px solid var(--clr-grey-base-50);<br /> text-align: left; }<br /> <br /> .tblB tr:nth-child(even) { background-color: var(--clr-white); } /* overwrite the zebra striping default */<br /> .tblB tr:nth-child(odd) { background-color: var(--clr-white); } /* overwrite the zebra striping default */<br /> <br /> <br /> .tblBcenter { background-color: var(--clr-white); color: var(--clr-black); <br /> border-collapse: collapse; border: 1px solid; border-color: var(--clr-grey-base-50); }<br /> <br /> .tblBcenter th { background-color: var(--clr-white); color: var(--clr-black);<br /> border-collapse: collapse; border: 1px solid; border-color: var(--clr-grey-base-50);<br /> text-align: center; font-weight: bold; }<br /> <br /> .tblBcenter td { background-color: var(--clr-white); color: var(--clr-black);<br /> border-collapse: collapse; border: 1px solid; border-color: var(--clr-grey-base-50);<br /> text-align: center; }<br /> <br /> .tblBcenter tr:nth-child(even) { background-color: var(--clr-white); } /* overwrite the zebra striping default */<br /> .tblBcenter tr:nth-child(odd) { background-color: var(--clr-white); } /* overwrite the zebra striping default */<br /> <br /> <br /> <br /> /* Overflow for Custom Tables - added 30 Dec 2020 */<br /> .table { overflow-x: auto; } /* this works */<br /> /* .tbl .tblB .tblBcenter { overflow-x: auto; } /* should not show vertical scrollbar and horizontal only when needed */<br /> .tblB { overflow-x: auto; }</div>

GrantM https://mw.mh370.wiki/w/index.php?title=MediaWiki:Common.css&diff=2460 MediaWiki:Common.css 2025-12-24T10:53:22Z

<p>GrantM: </p> <hr /> <div>/* CSS placed here will be applied to all skins */<br /> <br /> <br /> /* #ca-nstab-ns_3400 { display:none !important; } */<br /> <br /> /* body.ns-0 #ca-talk { display:none !important; } */ /* this works */<br /> <br /> /* body.ns-0 #ca-nstab { display:none !important; } doesn't work */<br /> <br /> body.ns-3400 #ca-talk { display:none !important; } /* this works */<br /> <br /> body.ns-3400 #ca-nstab-snippets { display:none !important; }<br /> <br /> <br /> <br /> /* 5 August 2025 Added Colors for use in Sidebar and MediaWiki interface */<br /> <br /> /* Steel Blue */<br /> :root { --SteelBlue-80: #B6CEE2;<br /> --SteelBlue-70: #91B6D4;<br /> --SteelBlue-60: #6C9DC6;<br /> --SteelBlue-50: #4785B8;<br /> --SteelBlue-40: #396A93;<br /> } /* End Steel Blue */<br /> <br /> /* Tan */<br /> :root { --Tan-90: #F1E7DA;<br /> --Tan-80: #E2CFB6;<br /> --Tan-70: #D4B791;<br /> --Tan-60: #C69F6C;<br /> --Tan-50: #B88747;<br /> --Tan-40: #936C39;<br /> } /* End Tan */<br /> <br /> /* 10 Dec 2025 added shades of Light Steel Blue #b0c4de (for catlinks) */<br /> :root { --LightSteelBlue: #B0C4DE;<br /> --LightSteelBlue-80: #B7C9E1;<br /> --LightSteelBlue-85: #C9D7E8;<br /> --LightSteelBlue-90: #DBE4F0;<br /> } /* End Light Steel Blue */<br /> <br /> /* 10 Dec 2025 added shades of Light Sky Blue #99CCEF for use in page headers */<br /> :root { --LightSkyBlue: #99CCFF;<br /> } /* End Light Sky Blue */<br /> <br /> <br /> /* 10 Dec 2025 added variables for greys */<br /> :root { --PageBackground: #F2F2F2;<br /> --QuoteBackground: #FAFAFA;<br /> --BlackText: #000000;<br /> }<br /> <br /> /* Black and White as used on MH370 site for tables */<br /> :root { --clr-white: #FFFFFF;<br /> --clr-black: #000000;<br /> }<br /> <br /> :root { --clr-grey-base-50: #808080; } /* exactly half way between black and white */<br /> <br /> <br /> <br /> <br /> /* Items sorted with lightest color shade first, approximating a Z order */<br /> <br /> #mw-head { background-color: var(--SteelBlue-80); } /* full width at top of screen, behind logo */<br /> <br /> /* mw-body-content is in front of mw-body */<br /> .mw-body-content { background-color: var(--PageBackground); border-radius: 1em; padding-top:2em; padding-bottom:2em; padding-left:2.5em; padding-right:2.5em; } <br /> <br /> .mw-body { background-color: var(--SteelBlue-70); } /* is background for everything below header and right of left panel and down to footer */<br /> <br /> .mw-footer { background-color: var(--SteelBlue-60); } /* does not extend to bottom of the screen */<br /> .mw-footer { margin-bottom:20px; } /* added 24 Dec 2025 */<br /> <br /> #mw-panel.vector-legacy-sidebar.collapsible-nav { background-color: var(--SteelBlue-50); } /* background for menu but extends to top of screen and behind logo and in front of header */<br /> <br /> body { background-color: var(--SteelBlue-40); } /* everything below mw-head, full width of screen, to bottom of screen */<br /> <br /> .catlinks { background-color: var(--LightSteelBlue); } /* border on category row. was #bdccdb */<br /> .mw-normal-catlinks { background-color: var(--LightSteelBlue-90); padding-left:20px; } /* was #ced8e4 */<br /> <br /> <br /> /* 17 Sept 2025 added classes for different background color pages */<br /> .BluePage { color: #9900CC; } /* Purple text on blue background */<br /> .GreenPage { color: #000099; } /* Blue text on green background */<br /> <br /> .mw-body-content:has(.BluePage) { background-color: #E6F5FF; }<br /> .mw-body-content:has(.GreenPage) { background-color: #E6FFF2; }<br /> <br /> <br /> <br /> <br /> <br /> /* 2 August added class to standardised margins when displaying a category tree */<br /> .displayCatTree { margin-left:4em; }<br /> <br /> <br /> <br /> /* 1 August 2025 Added a class to standardise page headers, plus a variant for category pages */<br /> <br /> .header { width:90%; <br /> margin-left:auto; margin-right:auto; margin-bottom:1em; padding-top:10px; padding-bottom:10px; <br /> text-align:justify;<br /> background-color: var(--LightSkyBlue); border-color: var(--LightSkyBlue); border-radius: 10px;<br /> } /* colors were #cce6ff */<br /> <br /> .cat { background-color: var(--LightSteelBlue-85); border-color: var(--LightSteelBlue-85); } /* pale shade of blue for header on category pages. was #e8f2fc */<br /> <br /> <br /> <br /> /* 28 July 2025 attempt to indent unordered lists */<br /> .mw-body-content ul { display:block; position:relative; left:1em; overflow-wrap: normal; word-wrap: normal; max-width:90%; text-align:justify; } /* mw-body-content limits scope */<br /> /* .ulNormal { display:block; position:relative; left:2vw; overflow-wrap: normal; word-wrap: normal; max-width:90%; text-align:justify; } */<br /> <br /> <br /> /* 28 July 2025 added style for quoted text, adapted from mh370wiki.net, used instead of blockquote */<br /> <br /> .quote { width: 90%; background: var(--QuoteBackground); /* contrast against page background */<br /> padding-left: 1em;; padding-right: 1em; padding-top: 0.5em; padding-bottom: 0.5em; /* was px */<br /> margin-left:auto; margin-right:auto; margin-top:0.5em; margin-bottom:0.5em; <br /> text-align:justify; color: var(--BlackText); /* black */<br /> }<br /> <br /> <br /> /* 27 July 2025 added left margin to images */<br /> .mw-default-size { margin-left: 2em; } /* this is the container. applies to all images */<br /> <br /> <br /> <br /> <br /> /* 25 July 2025 added style to indent <pre> Note: No dot required before pre */<br /> <br /> pre { width: 90%; margin-left: auto; margin-right: auto; }<br /> <br /> <br /> <br /> /* 22 July 2025 Added style to enlarge fonts on Tooltips but currently unable to change tooltip width */<br /> <br /> .mw-lingo-definition-text { font-size:125%; } /* Tooltip is also styled as a qtip in jquery.qtip.css */<br /> <br /> /* _________________________________________________________________________________________________________________________*/<br /> <br /> <br /> /* 20 July 2025 Fluid Typography and Font Variables */<br /> /* Copied from mh370wiki.net and adapted for use here */<br /> <br /> /* Fluid Typography - see Responsive And Fluid Typography With vh And vw Units<br /> https://www.smashingmagazine.com/2016/05/fluid-typography/ <br /> Unlike responsive typography, which changes only at set breakpoints,<br /> fluid typography resizes smoothly to match any device width.<br /> */<br /> /* Variables for font size ( to be used in Vector.css ) see https://foxland.fi/naming-typography-css-variables/ */<br /> <br /> /* Clamp() for min, preferred, max font size see https://developer.mozilla.org/en-US/docs/Web/CSS/clamp() */<br /> /* Notes on font sizes<br /> The default text size in browsers is 16px. So, the default size of 1em is 16px.<br /> rem (root em) references the base font size of the document.<br /> Assuming that the base font size is 16px, we get the following values:<br /> 1rem = 16px<br /> 1.5rem = 24px<br /> 0.5rem = 8px<br /> */<br /> <br /> /* Use clamp ( min preferred max ) */<br /> :root { font-size: clamp( 1vw, 1.05rem, 1.2vw ); } <br /> <br /> /* Font sizes using variables from https://foxland.fi/naming-typography-css-variables/ */<br /> /* Example font-size: var(--font-size-100); */<br /> :root { --font-size-625: 62.5%; /* 62.5% of root font size */<br /> --font-size-875: 87.5%; /* 87.5% x root font size */<br /> --font-size-090: 90%; /* 90% x root font size */<br /> --font-size-095: 95%; /* 95% x root font size */<br /> --font-size-100: 100%; /* 100% = root font size */<br /> --font-size-105: 105%; /* 105% x root font size */<br /> --font-size-110: 110%; /* 110% x root font size */<br /> --font-size-115: 115%; /* 115% x root font size */<br /> --font-size-120: 120%; /* 120% x root font size */ <br /> --font-size-125: 125%; /* 125% x root font size */<br /> }<br /> <br /> /* _________________________________________________________________________________________________________________________*/<br /> <br /> /* Text Styles using Font Variables */<br /> <br /> /* Font Sizes */<br /> body { font-size: var(--font-size-100); }<br /> p { font-size: var(--font-size-100); }<br /> dl dt dd { font-size: var(--font-size-100); }<br /> dd { margin-bottom: 1em; } /* added 11 Oct 2022 to space between a dd and the next dt */<br /> /* ul ol li { font-size: var(--font-size-100); } */<br /> <br /> /* Headings are sized by percentage over the base font and also resize based on viewport width */<br /> h1 {font-size: var(--font-size-125);} <br /> h2 {font-size: var(--font-size-120);} /* h2 was previously not defined */<br /> h3 {font-size: var(--font-size-115);}<br /> h4 {font-size: var(--font-size-110);}<br /> h5 {font-size: var(--font-size-105);}<br /> /* h6 {font-size: var(--font-size-100);} modified 4 Jan 2025 */<br /> h6 {font-size: var(--font-size-090);}<br /> <br /> h1, h3, h4, h5, h6 {<br /> font-family: Arial, Helvetica, sans-serif;<br /> color: var(--clr-DeepPurple-base-30); <br /> font-weight: 600;<br /> }<br /> <br /> /* _________________________________________________________________________________________________________________________*/<br /> <br /> /* Text layout using padding - use vw for responsive */<br /> /* 10px = 0.625rem; 20px = 1.25rem; 30px = 1.875rem; 40px = 2.5rem; */<br /> /* h1, h2, h3 align with left of page. h4 is rarely used */<br /> /* h1, h2, h3 align with left of page. h4 is rarely used */<br /> h5 { padding-left: 0.5vw; } <br /> h6 { padding-left: 0.5vw; } <br /> p { padding-left: 1vw; padding-right:1vw; } <br /> <br /> /* Margin above, added 14 Dec 2025 to avoid need for <br /> before a major heading (h3) */<br /> h3 { margin-top: 0.2vh; } /* started with .5vw */<br /> <br /> /* padding below added 15 Dec 2025 */<br /> li { padding-bottom: 0.2vh; }<br /> <br /> <br /> <br /> /* ordered list ol and altered padding for a nested list */<br /> ol { display:block; position:relative; left:0.9vw; overflow-wrap: normal; word-wrap: normal; max-width:90%; padding-right:0.9vw; <br /> & ol { display:block; position:relative; left:-0.9vw; overflow-wrap: normal; word-wrap: normal; max-width:90%; list-style-type:lower-roman; }<br /> } <br /> <br /> /* Definition List */<br /> dl { padding-left: 2.5vw; padding-right:2.5vw; } <br /> dt { padding:right:2.5vw; padding-right:2.5vw; text-align:justify; }<br /> dd { padding:right:2.5vw; padding-right:2.5vw; text-align:justify; }<br /> <br /> <br /> /* _________________________________________________________________________________________________________________________*/<br /> <br /> /* 11 July 2025 Rows and Columns */<br /> <br /> /* 26 July 2020 New row/column layout */<br /> /* July 2025 Copied from www.mh370wiki.net ( with minor adjustments ) */<br /> .Row { display: flex; flex-flow: row nowrap; justify-content: flex-start; justify-content: space-between; width: 100%; } <br /> .row { display: flex; flex-flow: row nowrap; justify-content: flex-start; justify-content: space-between; width: 100%; } <br /> .column-left { display: flex; flex-flow: column; flex-grow: 1; flex-shrink: 1; padding-right: 1em; }<br /> .column-center {display: flex; flex-flow: column; flex-grow: 1; flex-shrink: 1; margin-left: 1em; margin-right: 1em; }<br /> .column-right {display: flex; flex-flow: column; flex-grow: 1; flex-shrink: 1; padding-left: 1em; }<br /> <br /> /* flex-basis determines column width */ <br /> .col-width-75 { flex-basis: 75%; flex-shrink: 15;} /* usually main column 75% and Comments or Notes 25% */<br /> .col-width-70 { flex-basis: 65%; flex-shrink: 13;} /* added 28 Oct 2020 to use with col-width-30 even though that is actually 33% */<br /> .col-width-60 { flex-basis: 60%; flex-shrink: 12;} /* two columns in ratio 3:2 */<br /> .col-width-50 { flex-basis: 50%; flex-shrink: 10;} /* two equal columns */<br /> .col-width-40 { flex-basis: 40%; flex-shrink: 8;} <br /> /*.col-width-30 { flex-basis: 33%; flex-shrink: 7;} */<br /> /* .col-width-30 { flex: 1 1 0;} /* 16 Nov 2020 If columns are equal then flex should be 1 1 0 */<br /> .col-width-30 { flex-basis: 0; }<br /> .col-width-25 { flex-basis: 25%; flex-shrink: 5;} /* usually right column */<br /> <br /> <br /> /* _________________________________________________________________________________________________________________________*/<br /> /* Tables - adapted from MH370 site 10 Dec 2025 */<br /> /* flex-font-base removed */<br /> <br /> <br /> th { font-weight:bold; }<br /> <br /> th, td { padding-left: 0.6em; padding-right: 0.6em; } /* added 29 Oct 2020. will apply to all types of table */ <br /> th, td { vertical-align: top; } /* added 31 Oct 2020. will apply to all types of table */<br /> /* Custom Tables */<br /> /* w=width Use class in conjunction with tbl or tblB */<br /> .w100 { width: 100%; } /* Table width 100% with no margins */<br /> .w90 { width: 90%; margin-left: auto; margin-right: auto; } /* Table width 90% centred */<br /> .w80 { width: 80%; margin-left: auto; margin-right: auto; } /* Table width 80% centred */<br /> .w75 { width: 75%; margin-left: auto; margin-right: auto; } /* Table width 75% centred */<br /> .w70 { width: 70%; margin-left: auto; margin-right: auto; } /* Table width 70% centred */<br /> .w60 { width: 60%; margin-left: auto; margin-right: auto; } /* Table width 60% centred */<br /> .w50 { width: 50%; margin-left: auto; margin-right: auto; } /* Table width 50% centred */<br /> .w40 { width: 40%; margin-left: auto; margin-right: auto; } /* Table width 40% centred */<br /> .w30 { width: 30%; margin-left: auto; margin-right: auto; } /* Table width 30%centred */<br /> .w25 { width: 25%; margin-left: auto; margin-right: auto; } /* Table width 25% centred */<br /> .w20 { width: 20%; margin-left: auto; margin-right: auto; } /* Table width 20% centred */<br /> .wauto { margin-left: auto; margin-right: auto; } <br /> <br /> /* Table centred */<br /> /* tbl = table. B=bordered. tblB is a bordered table with white background */<br /> /* tblBcenter = table with border and columns centered */<br /> <br /> .tbl { background-color: var(--clr-white); color: var(--clr-black); /* Background is white for a table with no borders. */<br /> vertical-align: top; }<br /> .tbl th td { background-color: var(--clr-white); color: var(--clr-black);<br /> text-align: left; font-weight: bold; vertical-align: top; }<br /> .tbl td { background-color: var(--clr-white); color: var(--clr-black);<br /> text-align: left; vertical-align: top; }<br /> <br /> .tbl tr:nth-child(even) { background-color: var(--clr-white); } /* overwrite the zebra striping default */<br /> .tbl tr:nth-child(odd) { background-color: var(--clr-white); } /* overwrite the zebra striping default */<br /> <br /> .tblB { background-color: var(--clr-white); color: var(--clr-black); <br /> border-collapse: collapse; <br /> border: 1px solid var(--clr-grey-base-50); }<br /> <br /> .tblB th { background-color: var(--clr-white); color: var(--clr-black);<br /> border-collapse: collapse; border: 1px solid; border-color: var(--clr-grey-base-50);<br /> text-align: left; font-weight: bold; }<br /> <br /> .tblB td { background-color: var(--clr-white); color: var(--clr-black);<br /> border-collapse: collapse; border: 1px solid var(--clr-grey-base-50);<br /> text-align: left; }<br /> <br /> .tblB tr:nth-child(even) { background-color: var(--clr-white); } /* overwrite the zebra striping default */<br /> .tblB tr:nth-child(odd) { background-color: var(--clr-white); } /* overwrite the zebra striping default */<br /> <br /> <br /> .tblBcenter { background-color: var(--clr-white); color: var(--clr-black); <br /> border-collapse: collapse; border: 1px solid; border-color: var(--clr-grey-base-50); }<br /> <br /> .tblBcenter th { background-color: var(--clr-white); color: var(--clr-black);<br /> border-collapse: collapse; border: 1px solid; border-color: var(--clr-grey-base-50);<br /> text-align: center; font-weight: bold; }<br /> <br /> .tblBcenter td { background-color: var(--clr-white); color: var(--clr-black);<br /> border-collapse: collapse; border: 1px solid; border-color: var(--clr-grey-base-50);<br /> text-align: center; }<br /> <br /> .tblBcenter tr:nth-child(even) { background-color: var(--clr-white); } /* overwrite the zebra striping default */<br /> .tblBcenter tr:nth-child(odd) { background-color: var(--clr-white); } /* overwrite the zebra striping default */<br /> <br /> <br /> <br /> /* Overflow for Custom Tables - added 30 Dec 2020 */<br /> .table { overflow-x: auto; } /* this works */<br /> /* .tbl .tblB .tblBcenter { overflow-x: auto; } /* should not show vertical scrollbar and horizontal only when needed */<br /> .tblB { overflow-x: auto; }</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Template:PageHeader&diff=2459 Template:PageHeader 2025-12-24T10:50:33Z

<p>GrantM: </p> <hr /> <div><includeonly> <br /> {{#seo:<br /> |title_mode=replace<br /> |title={{PAGENAME}}<br /> |keywords=MediaWiki, {{PAGENAME}}, hosted, hosting, instructional, guide<br /> |description=A Guide to Using MediaWiki in a Hosted Environment<br /> |site_name=mw.mh370.wiki<br /> |locale=en_EN<br /> |type=website<br /> |modified_time={{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}<br /> }}<br /> </includeonly><br /> <div class="header"><br /> <p style="font-size:150%; text-align:center;">A Guide to Using MediaWiki in a Hosted Environment</p><br /> <p style="font-size:120%; text-align:center;">An instructional website by the developer of <html><a href="https://www.mh370wiki.net" target="_blank"><b>mh370wiki.net</b></a></html> - a MediaWiki site about Malaysia Airlines Flight MH370.</p><br /> </div><br /> __NOTOC__</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Template:PageHeader&diff=2458 Template:PageHeader 2025-12-24T10:42:21Z

<p>GrantM: </p> <hr /> <div><includeonly> <br /> {{#seo:<br /> |title_mode=append<br /> |title={{PAGENAME}}<br /> |keywords=MediaWiki, {{PAGENAME}}, hosted, hosting, instructional, guide<br /> |description=A Guide to Using MediaWiki in a Hosted Environment<br /> |site_name=mw.mh370.wiki<br /> |locale=en_EN<br /> |type=website<br /> |modified_time={{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}<br /> }}<br /> </includeonly><br /> <div class="header"><br /> <p style="font-size:150%; text-align:center;">A Guide to Using MediaWiki in a Hosted Environment</p><br /> <p style="font-size:120%; text-align:center;">An instructional website by the developer of <html><a href="https://www.mh370wiki.net" target="_blank"><b>mh370wiki.net</b></a></html> - a MediaWiki site about Malaysia Airlines Flight MH370.</p><br /> </div><br /> __NOTOC__</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Template:PageHeader&diff=2457 Template:PageHeader 2025-12-24T10:39:53Z

<p>GrantM: </p> <hr /> <div><includeonly> <br /> {{#seo:<br /> |title_mode=append<br /> |title={{PAGENAME}}<br /> |keywords=MediaWiki, hosted, hosting, instructional, guide, {{{PAGENAME}}}<br /> |description=A Guide to Using MediaWiki in a Hosted Environment<br /> |site_name=mw.mh370.wiki<br /> |locale=en_EN<br /> |type=website<br /> |modified_time={{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}<br /> }}<br /> </includeonly><br /> <div class="header"><br /> <p style="font-size:150%; text-align:center;">A Guide to Using MediaWiki in a Hosted Environment</p><br /> <p style="font-size:120%; text-align:center;">An instructional website by the developer of <html><a href="https://www.mh370wiki.net" target="_blank"><b>mh370wiki.net</b></a></html> - a MediaWiki site about Malaysia Airlines Flight MH370.</p><br /> </div><br /> __NOTOC__</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Template:PageHeader&diff=2456 Template:PageHeader 2025-12-24T10:36:33Z

<p>GrantM: </p> <hr /> <div><includeonly> <br /> {{#seo:<br /> |title_mode=append<br /> |title={{{PAGENAME}}}<br /> |keywords=MediaWiki, hosted, hosting, instructional, guide, {{{PAGENAME}}}<br /> |description=A Guide to Using MediaWiki in a Hosted Environment<br /> |site_name=mw.mh370.wiki<br /> |locale=en_EN<br /> |type=website<br /> |modified_time={{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}<br /> }}<br /> </includeonly><br /> <div class="header"><br /> <p style="font-size:150%; text-align:center;">A Guide to Using MediaWiki in a Hosted Environment</p><br /> <p style="font-size:120%; text-align:center;">An instructional website by the developer of <html><a href="https://www.mh370wiki.net" target="_blank"><b>mh370wiki.net</b></a></html> - a MediaWiki site about Malaysia Airlines Flight MH370.</p><br /> </div><br /> __NOTOC__</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Template:PageHeader&diff=2455 Template:PageHeader 2025-12-24T10:31:19Z

<p>GrantM: </p> <hr /> <div><includeonly> <br /> {{#seo:<br /> |title_mode=append<br /> |title={{{PAGENAME}}}<br /> |keywords=MediaWiki, hosted, instructional, {{{PAGENAME}}}<br /> |description=A Guide to Using MediaWiki in a Hosted Environment<br /> |site_name=mw.mh370.wiki<br /> |locale=en_EN<br /> |type=website<br /> |modified_time={{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}<br /> }}<br /> </includeonly><br /> <div class="header"><br /> <p style="font-size:150%; text-align:center;">A Guide to Using MediaWiki in a Hosted Environment</p><br /> <p style="font-size:120%; text-align:center;">An instructional website by the developer of <html><a href="https://www.mh370wiki.net" target="_blank"><b>mh370wiki.net</b></a></html> - a MediaWiki site about Malaysia Airlines Flight MH370.</p><br /> </div><br /> __NOTOC__</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Template:PageHeader&diff=2454 Template:PageHeader 2025-12-24T10:15:57Z

<p>GrantM: </p> <hr /> <div><div class="header"><br /> <p style="font-size:150%; text-align:center;">A Guide to Using MediaWiki in a Hosted Environment</p><br /> <p style="font-size:120%; text-align:center;">An instructional website by the developer of <html><a href="https://www.mh370wiki.net" target="_blank"><b>mh370wiki.net</b></a></html> - a MediaWiki site about Malaysia Airlines Flight MH370.</p><br /> </div><br /> __NOTOC__<br /> <br /> <br /> <includeonly> <br /> <br /> <br /> <br /> {{#seo:<br /> |title_mode=append<br /> |title=Example SEO Wiki<br /> |keywords=WikiSEO, SEO, MediaWiki<br /> |description=An example description for this wiki<br /> |image=Wiki_Logo.png<br /> |image_alt=Wiki Logo<br /> |site_name=Example SEO Wiki<br /> |locale=en_EN<br /> |type=website<br /> |modified_time={{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}<br /> |published_time=2020-11-01<br /> }}<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> </includeonly></div>

GrantM https://mw.mh370.wiki/w/index.php?title=Namespaces&diff=2453 Namespaces 2025-12-24T09:35:38Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <div class="quote"><br /> <p>Pages on a MediaWiki wiki are grouped into collections called “namespaces” which differentiate between the purpose of the pages at a high level. Pages in certain namespaces can also have special properties or behave differently when they interact with other pages.</p><br /> <br /> <p>Namespaces are indicated in page titles by prefixing the page name with <namespace>:, so the prefix Help: in this page's title (Help:Namespaces) indicates that this page is in the Help namespace. Each namespace is identified by a number and a name, which can be translated and can also have some aliases.</p><br /> <br /> <p>A page whose name is not prefixed by a namespace lies in the mainspace. Note, however, that colons and prefixes can also appear in page titles without indicating a namespace: the page Foo:Namespaces is a page located in the mainspace because the namespace “Foo” does not exist. Similarly the page Help:Foo:Namespaces is in the “Help” namespace. </p><br /> <p style="text-align:center"><b>Source</b>: MediaWiki <html><a href="https://www.mediawiki.org/wiki/Help:Namespaces" target="_blank">Help:Namespaces </a></html></p><br /> </div> <br /> <br /><br /> <br /> <p>The concept of Namespaces is probably unique to MediaWiki. It is certainly a powerful and useful feature. Security can be assigned to each Namespace so that it can be public or restricted; content can be segregated into 'collections' by topic, and access controlled.</p><br /> <br /> <h3>Namespaces are Numbered</h3><br /> MediaWiki ships with 18 built-in namespaces:<br /> <ul><br /> <li>16 "real" namespaces, corresponding to actual pages, numbered 0 to 15, and grouped in subject/talk pairs<ref name="Man_Namespace" /></li><br /> <li>2 "virtual" namespaces (one for dynamically generated special pages, and one serving as an alias for direct file links), numbered -1 and -2, respectively. Since these namespaces don't correspond to pages stored in the database, one cannot create or delete pages in these namespaces, and there are no corresponding discussion namespaces.<ref name="Man_Namespace" /></li><br /> <li>Namespaces numbered 100-199 are reserved for site-specific namespaces, although there are some extensions that don't follow this convention. Extension writers use higher numbers, up to 32767.<ref name="Man_Custom_Namespace" /></li><br /> <li>Numbers from 3000 to 4999 are reserved for system administrators to define their custom namespaces.<ref name="Man_Custom_Namespace" /></li><br /> </ul><br /> <br /> <br /> <p>Namespaces are identified by a Number and allocated a name or an alias: names can be changed but the Number must remain constant.</p><br /> <p>Content namespaces are allocated an even number; associated Talk or discussion pages are allocated an odd number.</p><br /> <p>Custom Namespaces are defined in LocalSettings.php.</p><br /> <p>A list of namespaces is shown when opening Tools --> Special Pages --> All Pages.</p><br /> <p>Content can be moved between namespaces.</p><br /> <br /> <h3>Namespaces and the {{MH370Site}} website</h3><br /> <p>The table below lists the Namespaces used for content which is publicly accessible.</p><br /> <br /> <table class="tblB w90"><br /> <tr><br /> <th>Section</th><br /> <th>Description</th><br /> <th>Namespace Prefix</th><br /> <tr><br /> <tr><br /> <td>Main Content</td><br /> <td>Contains all general articles<br />Includes the Timeline.</td><br /> <td><i>No prefix</i></td><br /> </tr><br /> <tr><br /> <td>News</td><br /> <td>News and Media Statements from official sources, related to MH370</td><br /> <td>MH370News:</td><br /> </tr><br /> <tr><br /> <td>Safety Investigation Report (2018)</td><br /> <td>Includes extracts from the <i>Safety Investigation Report</i> which are then used as references or quoted in other articles.</td><br /> <td>SIR 2018:</td><br /> </tr><br /> <tr><br /> <td>Factual Information (2015)</td><br /> <td>Contains extracts from the <i>Factual Information</i> documents which were released in 2015.<br />These extracts were used as references or quoted in other articles but have mostly been superseded by the <i>Safety Investigation Report</i> (2018)</td><br /> <td>FI 2015:</td><br /> </tr><br /> <br /> <tr><br /> <td>Communications</td><br /> <td>This section contains transcripts of voice communications, text of ACARS messages, metadata from satellite communications and information related to communications with flight MH370.</td><br /> <td>Communications:</td><br /> </tr><br /> <br /> <tr><br /> <td>Passengers</td><br /> <td>This section contains information about each passenger from Passenger Manifests and Seating Plans plus other details published in media articles.</td><br /> <td>Passenger:</td><br /> </tr><br /> <br /> </table><br /> <br /> <h3>Hidden Namespaces and Transclusion</h3><br /> <p>In addition to the default namespaces in the MediaWiki installation, the {{MH370Site}} website there are several 'hidden' namespaces; content namespaces which require a user account and log-in to access.</p><br /> <p>However, a significant proportion of the 'hidden' content is actually visible to anonymous users because it is transcluded into pages with visible namespaces.</p><br /> <p>For example:-</p><br /> <ul><br /> <li>Reusable content, such as a Table from an official report, may be stored in a 'hidden' content namespace but transcluded into other pages as required. This ensures that a 'master' copy is formatted correctly and will always be the same when re-used.</li><br /> <li>The visible content in the MH370News: namespace is mostly transcluded from a content namespace which holds more than the visible content. For example, a media statement obtained from an original page source code will likely include custom css, or links which are outdated or not functional. The original is stored unchanged, and an edited version stripped of custom formatting is transcluded into the publicly accessible page.</p><br /> <li>The information displayed for each Passenger, or Crew Member on-board MH370 is collated from many sources. The displayed information is a transcluded subset of all that has been collected and stored in a 'hidden' content namespace.</li><br /> <li>Tooltips are transcluded into Glossary pages, and appear in context on all visible pages, but the tooltips (using the Extension Lingo) are in pages organised by topic in their own 'hidden' namespace. Instead of just one page for a glossary the {{MH370Site}} website has over 50 pages in the tooltips section.</p><br /> <li>References are in the Main namespace, or NS_Main, but the references are indexed or cross-linked by Reference IDs. Each ReferenceID is a page in a 'hidden' content namespace. The content is transcluded as required.</li><br /> </ul><br /> <p>To use a floating iceberg as an example, the visible content of the {{MH370Site}} website is like the tip of the iceberg; a significant proportion of the website is not visible but supports the accessible pages through transclusion.</p><br /> <br /><br /> <br /> <h3>Hidden 'Workspaces'</h3><br /> <p>Based on experience with the {{MH370Site}} website, this website also has a hidden namespace for draft content. This is like a workspace where articles can be started but remain unpublished, where ideas can be kept before they are developed into an article format, and where formatting or features can be tested before being applied.</p><br /> <p>However, instead of moving a completed article from the draft area I found it better to copy the content into the final page. This avoids a redirect.</p><br /> <br /><br /> <br /> {{DisplayCategoryTree<br /> |Topic=creating Namespaces<br /> |CatName=Namespaces<br /> |CatTree=<categorytree mode="pages">Namespaces</categorytree><br /> }}<br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Help:Namespaces </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Help:Namespaces" target="_blank">https://www.mediawiki.org/wiki/Help:Namespaces</a></html></dd><br /> <br /> <dt>Manual:Namespace </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Namespace" target="_blank">https://www.mediawiki.org/wiki/Manual:Namespace</a></html></dd><br /> <br /> <dt>Manual:Using custom namespaces</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Using_custom_namespaces" target="_blank">https://www.mediawiki.org/wiki/Manual:Using_custom_namespaces</a></html></dd><br /> <br /> <dt>Manual:Namespace constants</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Namespace_constants" target="_blank">https://www.mediawiki.org/wiki/Manual:Namespace_constants</a></html></dd><br /> </dl><br /> <br /> <h3>Notes</h3><br /> <references><br /> <br /> <br /> <ref name="Man_Namespace">See <i>Manual:Namespace</i></ref><br /> <ref name="Man_Custom_Namespace">See <i>Manual:Using custom namespaces </i></ref><br /> </references><br /> <br /> <br /> [[Category:Configure]]<br /> [[Category:Namespaces]]<br /> [[Category:Transclusion]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Namespaces&diff=2452 Namespaces 2025-12-24T09:34:54Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <div class="quote"><br /> <p>Pages on a MediaWiki wiki are grouped into collections called “namespaces” which differentiate between the purpose of the pages at a high level. Pages in certain namespaces can also have special properties or behave differently when they interact with other pages.</p><br /> <br /> <p>Namespaces are indicated in page titles by prefixing the page name with <namespace>:, so the prefix Help: in this page's title (Help:Namespaces) indicates that this page is in the Help namespace. Each namespace is identified by a number and a name, which can be translated and can also have some aliases.</p><br /> <br /> <p>A page whose name is not prefixed by a namespace lies in the mainspace. Note, however, that colons and prefixes can also appear in page titles without indicating a namespace: the page Foo:Namespaces is a page located in the mainspace because the namespace “Foo” does not exist. Similarly the page Help:Foo:Namespaces is in the “Help” namespace. </p><br /> <p style="text-align:center"><b>Source</b>: MediaWiki <html><a href="https://www.mediawiki.org/wiki/Help:Namespaces" target="_blank">Help:Namespaces </a></html></p><br /> </div> <br /> <br /><br /> <br /> <p>The concept of Namespaces is probably unique to MediaWiki. It is certainly a powerful and useful feature. Security can be assigned to each Namespace so that it can be public or restricted; content can be segregated into 'collections' by topic, and access controlled.</p><br /> <br /> <h3>Namespaces are Numbered</h3><br /> MediaWiki ships with 18 built-in namespaces:<br /> <ul><br /> <li>16 "real" namespaces, corresponding to actual pages, numbered 0 to 15, and grouped in subject/talk pairs<ref name="Man_Namespace" /></li><br /> <li>2 "virtual" namespaces (one for dynamically generated special pages, and one serving as an alias for direct file links), numbered -1 and -2, respectively. Since these namespaces don't correspond to pages stored in the database, one cannot create or delete pages in these namespaces, and there are no corresponding discussion namespaces.<ref name="Man_Namespace" /></li><br /> <li>Namespaces numbered 100-199 are reserved for site-specific namespaces, although there are some extensions that don't follow this convention. Extension writers use higher numbers, up to 32767.<ref name="Man_Custom_Namespace" /></li><br /> <li>Numbers from 3000 to 4999 are reserved for system administrators to define their custom namespaces.<ref name="Man_Custom_Namespace" /></li><br /> </ul><br /> <br /> <br /> <p>Namespaces are identified by a Number and allocated a name or an alias: names can be changed but the Number must remain constant.</p><br /> <p>Content namespaces are allocated an even number; associated Talk or discussion pages are allocated an odd number.</p><br /> <p>Custom Namespaces are defined in LocalSettings.php.</p><br /> <p>A list of namespaces is shown when opening Tools --> Special Pages --> All Pages.</p><br /> <p>Content can be moved between namespaces.</p><br /> <br /> <h3>Namespaces and the {{MH370Site}} website</h3><br /> <p>The table below lists the Namespaces used for content which is publicly accessible.</p><br /> <br /> <table class="tblB w90"><br /> <tr><br /> <th>Section</th><br /> <th>Description</th><br /> <th>Namespace Prefix</th><br /> <tr><br /> <tr><br /> <td>Main Content</td><br /> <td>Contains all general articles<br />Includes the Timeline.</td><br /> <td><i>No prefix</i></td><br /> </tr><br /> <tr><br /> <td>News</td><br /> <td>News and Media Statements from official sources, related to MH370</td><br /> <td>MH370News:</td><br /> </tr><br /> <tr><br /> <td>Safety Investigation Report (2018)</td><br /> <td>Includes extracts from the <i>Safety Investigation Report</i> which are then used as references or quoted in other articles.</td><br /> <td>SIR 2018:</td><br /> </tr><br /> <tr><br /> <td>Factual Information (2015)</td><br /> <td>Contains extracts from the <i>Factual Information</i> documents which were released in 2015.<br />These extracts were used as references or quoted in other articles but have mostly been superseded by the <i>Safety Investigation Report</i> (2018)</td><br /> <td>FI 2015:</td><br /> </tr><br /> <br /> <tr><br /> <td>Communications</td><br /> <td>This section contains transcripts of voice communications, text of ACARS messages, metadata from satellite communications and information related to communications with flight MH370.</td><br /> <td>Communications:</td><br /> </tr><br /> <br /> <tr><br /> <td>Passengers</td><br /> <td>This section contains information about each passenger from Passenger Manifests and Seating Plans plus other details published in media articles.</td><br /> <td>Passenger:</td><br /> </tr><br /> <br /> </table><br /> <br /> <h3>Hidden Namespaces and Transclusion</h3><br /> <p>In addition to the default namespaces in the MediaWiki installation, the {{MH370Site}} website there are several 'hidden' namespaces; content namespaces which require a user account and log-in to access.</p><br /> <p>However, a significant proportion of the 'hidden' content is actually visible to anonymous users because it is transcluded into pages with visible namespaces.</p><br /> <p>For example:-</p><br /> <ul><br /> <li>Reusable content, such as a Table from an official report, may be stored in a 'hidden' content namespace but transcluded into other pages as required. This ensures that a 'master' copy is formatted correctly and will always be the same when re-used.</li><br /> <li>The visible content in the MH370News: namespace is mostly transcluded from a content namespace which holds more than the visible content. For example, a media statement obtained from an original page source code will likely include custom css, or links which are outdated or not functional. The original is stored unchanged, and an edited version stripped of custom formatting is transcluded into the publicly accessible page.</p><br /> <li>The information displayed for each Passenger, or Crew Member on-board MH370 is collated from many sources. The displayed information is a transcluded subset of all that has been collected and stored in a 'hidden' content namespace.</li><br /> <li>Tooltips are transcluded into Glossary pages, and appear in context on all visible pages, but the tooltips (using the Extension Lingo) are in pages organised by topic in their own 'hidden' namespace. Instead of just one page for a glossary the {{MH370Site}} website has over 50 pages in the tooltips section.</p><br /> <li>References are in the Main namespace, or NS_Main, but the references are indexed or cross-linked by Reference IDs. Each ReferenceID is a page in a 'hidden' content namespace. The content is transcluded as required.</li><br /> </ul><br /> <p>To use a floating iceberg as an example, the visible content of the {{MH370Site}} website is like the tip of the iceberg; a significant proportion of the website is not visible but supports the accessible pages through transclusion.</p><br /> <br /><br /> <br /> <h3>Hidden 'Workspaces'</h3><br /> <p>Based on experience with the {{MH370Site}} website, this website also has a hidden namespace for draft content. This is like a workspace where articles can be started but remain unpublished, where ideas can be kept before they are developed into an article format, and where formatting or features can be tested before being applied.</p><br /> <p>However, instead of moving a completed article from the draft area I found it better to copy the content into the final page. This avoids a redirect.</p><br /> <br /><br /> <br /> {{DisplayCategoryTree<br /> |Topic=creating Namespaces<br /> |CatName=Namespaces<br /> |CatTree=<categorytree mode="pages">Namespaces</categorytree><br /> }}<br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Help:Namespaces </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Help:Namespaces" target="_blank">https://www.mediawiki.org/wiki/Help:Namespaces</a></html></dd><br /> <br /> <dt>Manual:Namespace </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Namespace" target="_blank">https://www.mediawiki.org/wiki/Manual:Namespace</a></html></dd><br /> <br /> <dt>Manual:Using custom namespaces</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Using_custom_namespaces" target="_blank">https://www.mediawiki.org/wiki/Manual:Using_custom_namespaces</a></html></dd><br /> <br /> <dt>Manual:Namespace constants</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Namespace_constants" target="_blank">https://www.mediawiki.org/wiki/Manual:Namespace_constants</a></html></dd><br /> </dl><br /> <br /> <h3>Notes</h3><br /> <references><br /> <br /> <br /> <ref name="Man_Namespace">See <i>Manual:Namespace</i></a></html></ref><br /> <ref name="Man_Custom_Namespace">See <i>Manual:Using custom namespaces </i></a></html></ref><br /> </references><br /> <br /> <br /> [[Category:Configure]]<br /> [[Category:Namespaces]]<br /> [[Category:Transclusion]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Transclusion_and_Subpages&diff=2451 Transclusion and Subpages 2025-12-24T09:33:04Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Subpages and Namespaces</h3><br /> <p>Although the concept of transcluding content from a subpage into a parent page sounds useful, by default MediaWiki does not allow subpages in the Main Namespace.</p><br /> <p>To enable subpages in both the Main and Template namespaces the following lines must be added to LocalSettings.php.</p><br /> <pre><br /> # Enable subpages in the main namespace<br /> $wgNamespacesWithSubpages[NS_MAIN] = true;<br /> <br /> # Enable subpages in the template namespace<br /> $wgNamespacesWithSubpages[NS_TEMPLATE] = true;<br /> </pre><br /> <br /> <p>In the {{MH370Site}} website I have enabled the use of subpages in most of the custom namespaces and describe transclusion between namespaces in this article [[Namespaces]].</p><br /> <p>I also use subpages in the Template namespace and describe the purpose in this article [[Templates]].</p><br /> <p>Below is the description of transclusion used with subpages on the {{MH370Site}} website.</p><br /> <br /> <br /> <br /> <h3>Transclusion and Subpages example from {{MH370Site}}</h3><br /> <p>The <i>Safety Investigation Report</i> for Malaysia Airlines Flight MH370 released in 2018 is a substantial document and I have included some sections in the {{MH370Site}} for reference purposes.</p><br /> <p>I basically 'deconstructed' this report into small sections. As an example, the Findings from the official Investigation is on this page: <html><a href="https://www.mh370.net/SIR_2018:3_Findings_and_Conclusion/3.1_Findings" target="_blank">SIR 2018:3 Findings and Conclusion/3.1 Findings</a></html>.</p><br /> <p>Each numbered section, however, is on a sub-page.</p><br /> <p>The <i>Findings</i> page actually looks like this:-</p><br /> <pre><br /> <noinclude>{{SIR2018/Header}}</noinclude><br /> <br /> <h4 style="margin-left:30px;">3.1 Findings</h4><br /> {{SIR 2018:3 Findings and Conclusion/3.1 Findings/3.1.1}}<br /> <br /> {{SIR 2018:3 Findings and Conclusion/3.1 Findings/3.1.2}}<br /> <br /> {{SIR 2018:3 Findings and Conclusion/3.1 Findings/3.1.3}}<br /> <br /> {{SIR 2018:3 Findings and Conclusion/3.1 Findings/3.1.4}}<br /> <br /> {{SIR 2018:3 Findings and Conclusion/3.1 Findings/3.1.5}}<br /> <br /> {{SIR 2018:3 Findings and Conclusion/3.1 Findings/3.1.6}}<br /> <br /> {{SIR 2018:3 Findings and Conclusion/3.1 Findings/3.1.7}}<br /> <br /> {{SIR 2018:3 Findings and Conclusion/3.1 Findings/3.1.8}}<br /> <br /> <noinclude>{{SIR2018/Footer}}</noinclude><br /> </pre><br /> <p>Each subpage has both a header and a footer but these are not included when the page is transcluded.</p><br /> <br /> <p>Also, each transcluded section contains a link to itself, so on the page <i>3.1 Findings</i>, each section number is actually a link. <i>3.1.1</i> links to the sub-page <i>SIR 2018:3 Findings and Conclusion/3.1 Findings/3.1.1</i>, for example.</p><br /> <p>I find that useful because if a section does not display correctly I can open that section easily instead of manually typing the full subpage name in the Search box.</p><br /> <p>In the subpage, the heading including the link looks like this:-</p><br /> <pre><br /> <p><b>[[SIR_2018:3_Findings_and_Conclusion/3.1_Findings/3.1.1|3.1.1]] Diversion from Filed Flight Plan Route</b></p><br /> </pre><br /> <br /><br /> <br /> <br /> [[Category:Transclusion]]<br /> [[Category:Subpages]]<br /> [[Category:$wgNamespacesWithSubpages]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Templates&diff=2450 Templates 2025-12-24T09:32:22Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <p>Templates are stored in the Template namespace, or NS_Template:</p><br /> <p>Templates are intended to be transcluded. When using a template it is not necessary to prefix the template name with the template namespace.</p><br /> <br /><br /> <br /> <h3>Templates and the {{MH370Site}} website</h3><br /> <p>Templates have been developed for many purposes, separated here into simple and complex examples:-</p><br /> <br /> <h5>Simple Templates</h5><br /> <p>Templates with no variables. The content is transcluded just as it is stored. Some examples are:-</p><br /> <ul><br /> <li>Dates are displayed by templates stored as a Day Number.<br /><br /> For example, Day 001 in the story of flight MH370 is Saturday, 8 March 2014. Throughout the website day numbers have been used and the corresponding dates have been transcluded from the Template nmamespace.</li><br /> <li>Page headers and footers. Standardised text is stored as templates and re-use ensures consistency.</li><br /> <li>Menus and Buttons. Each button, and each button state, is stored as a template. Buttons are transcluded into Menus. Menus are transcluded into pages.</li><br /> <li>Abbreviations. Within the website there are many references to the final Report. Instead of writing the report name each time, a template is used instead. Two version of the report name are frequently used:-<br /><br /> <ol><br /> <li>A short form, transcluded as <html><code>{{SIR2018/Ref}}</code></html> which returns <i>Safety Investigation Report MH370/01/2018</i>, and</li><br /> <li>A long form, transcluded as <html><code>{{SIR2018/FullRef}}</code></html> which returns Malaysian ICAO Annex 13 Safety Investigation Team for MH370, 02 July 2018, <i>Safety Investigation Report MH370/01/2018</i></li><br /> </ol><br /> <p>To reference a specific section, the instruction written with the template says:</p><br /> <pre><br /> <p>To use this reference use the following syntax:-</p><br /> <br /> <p><u>Source</u>:&nbsp;{{SIR2018/Ref}} [[Section N.n|Section N.n]] </p><br /> </pre><br /> </li><br /> </ul><br /> <p>See also: [[Simple Templates]].</p><br /> <br /><br /> <br /> <h5>Complex Templates</h5><br /> <p>These templates include variable parameters. Each parameter is enclosed by triple brackets {{{ and separated by the pipe symbol |.</p><br /> <p>The format is explained in the MediaWiki article <html><a href="https://www.mediawiki.org/wiki/Help:Templates" target="_blank">Help:Templates</a></html></p><br /> <p>For each of these templates there are two parts:-</p><br /> <ol><br /> <li>The actual template, which is the code required to format and present the information on a page, and</li><br /> <li>An instruction, which explains how the template is used and includes the code to be placed on a page to get the template to work.</li><br /> </ol><br /> <p>Without the saved instructions, the template would become useless because I would forget why it is written the way it is, and how to actually implement it.</p><br /> <p>In addition, there may be variants of the template for different contexts.</p><br /> <p>For example, each page in the Passenger namespace provides known information about each person on-board the ill-fated flight MH370. For each passenger we have several variants of a passenger manifest or seating plan. Some passengers had public or social media profiles which were tapped by mainstream media to create the human interest stories related to the flight. Some of the media reports included photograps, often extracted from social media pages.</p><br /> <p>So<br /><br /> <ul><br /> <li>every passenger has basic information collated from official passenger manifests</li><br /> <li>some passengers have additional information or profile provided by mainstream media</li><br /> <li>some mainstream media profiles include a photo.</li><br /> <li>For some passengers, additional notes have been created. For example those travelling on stolen passports.</li><br /> </ul><br /> </p><br /> <br /> <h3>Subpages in the Template Namespace</h3><br /> <p>The default setting is that subpages are not allowed in the Template namespace. However, I find it useful to create variants of a template as subpages of an instruction page in the Template namespace.</p><br /> <p>For example, passenger templates are subpages, named like this:-</p><br /> <ul><br /> <li>Passenger/Summary - this is the basic template for those with minimal data</li><br /> <li>Passenger/Media - for passengers with basic plus media profile</li><br /> <li>Passenger/Image - for passengers with basic plus media profile including an image</li><br /> </ul><br /> <p>And three more variants:-</p><br /> <ul><br /> <li>Passenger/Summary/Notes - for passengers with minimal data but additional clarification necessary with notes added</li><br /> <li>Passenger/Media/Notes - for passengers with basic plus media profile and additional clarification necessary with notes added</li><br /> <li>Passenger/Image/Notes - for passengers with basic plus media profile including an image and additional clarification necessary with notes added</li><br /> </ul><br /> <p>This might seem complicated but remember, there were 227 passengers on-board. The goal is to present relevant information in a consistent format.</p><br /> <p>An extract from the Template for Passenger/Media/Notes is shown below. The menu and page background is not included.</p><br /> <pre><br /> <html> <details open> <summary></html>{{PAGENAME}}<html></summary> </html><br /> <div style="margin-left:2.5em;">{{{Summary| }}}</div><br /> <html> </details> </html><br /> <br /> <html> <details> <summary>Media Sources</summary> </html><br /> <div style="margin-left:2.5em;">{{{Media| }}}</div><br /> <html> </details> </html><br /> <br /> <html> <details> <summary>Passenger Manifest Data</summary> </html><br /> <div style="margin-left:2.5em;">{{{Manifest| }}}</div><br /> <html> </details> </html><br /> <br /> <html> <details> <summary>Notes:-</summary> </html><br /> <div style="margin-left:2.5em;">{{{Notes| }}}</div><br /> <html> </details> </html><br /> </pre><br /> <p>Instructions for using this template looks like this:-</p><br /> <pre><br /> {{Template:Passenger/Media/Notes<br /> |Summary={{Pass_Data:{{PAGENAME}}/Summary}}<br /> |Media={{Pass_Data:{{PAGENAME}}/Media}}<br /> |Manifest={{Pass_Data:{{PAGENAME}}/Manifest}}<br /> |Notes={{Pass_Data:{{PAGENAME}}/Notes}}<br /> }}<br /> </pre><br /> <p>And that's all there is on every page where the available information about a passenger is based on the passenger manifests, plus one or more extracts from the media, plus an explanatory note.</p><br /> <p>All of the information presented is automatically transcluded from associated pages in the hidden namespace, written here as Pass_Data, where each page has the same name so that PAGENAME links to the correct page, and sub-pages hold the data to be transcluded. But there may be additional content on each sub-page which is not transcluded.</p><br /> <br /><br /> <p>See also: [[Complex Templates]].</p><br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Help:Templates </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Help:Templates" target="_blank">https://www.mediawiki.org/wiki/Help:Templates</a></html></dd><br /> <br /> <dt>Transclusion </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Transclusion" target="_blank">https://www.mediawiki.org/wiki/Transclusion</a></html></dd><br /> </dl><br /> <br /><br /> <br /> {{DisplayCategoryTree<br /> |Topic=MediaWiki Templates<br /> |CatName=Templates<br /> |CatTree=<categorytree mode="pages">Templates</categorytree><br /> }}<br /> <br /> [[Category:Use]]<br /> [[Category:Templates]]<br /> [[Category:Transclusion]]<br /> [[Category:Subpages]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Terminal&diff=2449 Terminal 2025-12-24T08:23:28Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>cPanel Terminal </h3><br /> <p>Many tasks related to the installation or upgrade of MediaWiki involve access to a 'command-line'. </p><br /> <p>In MediaWiki Manuals, when command-line access is required there are usually references to Secure Shell, SSH, a utility called puTTY and other obscure things.</p><br /> <p>The good news is that for account holders for a hosted website there is a much simpler method.</p><br /> <p>In cPanel -->Advanced there is an option called Terminal.</p><br /> <p>The Terminal page has the message 'This interface provides command line access to your account on the server.'</p><br /> <p>The interface is unfriendly, just like Command Prompt on a Windows desktop.</p><br /> <p>A big difference, however, is that the commands are different. Windows commands are a legacy from a DOS prompt; Terminal commands are consistent with Linux and Unix.</p><br /> <br /> <h3>Default Prompt</h3><br /> <p>Each account holder has an abbreviated account name. This forms part of the prompt. I your name was James Smith you may have an account name jamith, for example.</p><br /> <p>When opening Terminal, the prompt would be like this:-</p><br /> <pre><br /> [jamith@cpl84 ~]$<br /> </pre><br /> <p>$ is the home directory. Type ls and press Enter to get a directory listing.</p><br /> <p>Type cd followed by a directory name, to change directory</p><br /> <p>For other commands, see resources linked below.</p><br /> <br /> <br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=cPanel Terminal<br /> |CatName=Terminal<br /> |CatTree=<categorytree mode="pages">Terminal </categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Terminal for cPanel </dt><br /> <dd><html><a href="https://docs.cpanel.net/cpanel/advanced/terminal-in-cpanel/" target="_blank">https://docs.cpanel.net/cpanel/advanced/terminal-in-cpanel/ </a></html><br />This documentation simply explains what the Terminal is; it does not explain how to use it.</dd><br /> <br /> <dt>Top 60 Linux commands: What they are and how to use them effectively </dt><br /> <dd><html><a href="https://www.hostinger.com/tutorials/linux-commands" target="_blank">https://www.hostinger.com/tutorials/linux-commands</a></html><br />Useful documentation by Hostinger, a popular hosting service provider.</dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category:Terminal]]<br /> [[Category:Configure]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Terminal&diff=2448 Terminal 2025-12-24T08:20:13Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>cPanel Terminal </h3><br /> <p>Many tasks related to the installation or upgrade of MediaWiki involve access to a 'command-line'. </p><br /> <p>In MediaWiki Manuals, when command-line access is required there are usually references to Secure Shell, SSH, a utility called puTTY and other obscure things.</p><br /> <p>The good news is that for account holders for a hosted website there is a much simpler method.</p><br /> <p>In cPanel -->Advanced there is an option called Terminal.</p><br /> <p>The Terminal page has the message 'This interface provides command line access to your account on the server.'</p><br /> <p>The interface is unfriendly, just like Command Prompt on a Windows desktop.</p><br /> <p>A big difference, however, is that the commands are different. Windows commands are a legacy from a DOS prompt; Terminal commands are consistent with Linux and Unix.</p><br /> <br /> <h3>Default Prompt</h3><br /> <p>Each account holder has an abbreviated account name. This forms part of the prompt. I your name was James Smith you may have an account name jamith, for example.</p><br /> <p>When opening Terminal, the prompt would be like this:-</p><br /> <pre><br /> [jamith@cpl84 ~]$<br /> </pre><br /> <p>$ is the home directory. Type ls and press Enter to get a directory listing.</p><br /> <p>Type cd followed by a directory name, to change directory</p><br /> <br /> <br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=<br /> |CatName=<br /> |CatTree=<categorytree mode="pages"> </categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Terminal for cPanel </dt><br /> <dd><html><a href="https://docs.cpanel.net/cpanel/advanced/terminal-in-cpanel/" target="_blank">https://docs.cpanel.net/cpanel/advanced/terminal-in-cpanel/ </a></html><br />This documentation simply explains what the Terminal is; it does not explain how to use it.</dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category: ]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Terminal&diff=2447 Terminal 2025-12-24T08:17:22Z

<p>GrantM: Created page with "{{PageHeader}} <h3>cPanel Terminal </h3> <p>Many tasks related to the installation or upgrade of MediaWiki involve access to a 'command-line'. </p> <p>In MediaWiki Manuals, when command-line access is required there are usually references to Secure Shell, SSH, a utility called puTTY and other obscure things.</p> <p>The good news is that for account holders for a hosted website there is a much simpler method.</p> <p>In cPanel -->Advanced there is an option called Termina..."</p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>cPanel Terminal </h3><br /> <p>Many tasks related to the installation or upgrade of MediaWiki involve access to a 'command-line'. </p><br /> <p>In MediaWiki Manuals, when command-line access is required there are usually references to Secure Shell, SSH, a utility called puTTY and other obscure things.</p><br /> <p>The good news is that for account holders for a hosted website there is a much simpler method.</p><br /> <p>In cPanel -->Advanced there is an option called Terminal.</p><br /> <p>The Terminal page has the message 'This interface provides command line access to your account on the server.'</p><br /> <p>The interface is unfriendly, just like Command Prompt on a Windows desktop.</p><br /> <p>A big difference, however, is that the commands are different. Windows commands are a legacy from a DOS prompt; Terminal commands are consistent with Linux and Unix.</p><br /> <br /> <h3>Default Prompt</h3><br /> <p>Each account holder has an abbreviated account name. This forms part of the prompt. I your name was James Smith you may have an account name jamith, for example.</p><br /> <p>When opening Terminal, the prompt would be like this:-</p><br /> <pre><br /> [jamith@cpl84 ~]$<br /> </pre><br /> <p>$ is the home directory. Type ls and press Enter to get a directory listing.</p><br /> <p><br /> <br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=<br /> |CatName=<br /> |CatTree=<categorytree mode="pages"> </categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category: ]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=HTTP_Code_404&diff=2446 HTTP Code 404 2025-12-24T08:03:05Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Required but not found URLs (HTTP code 404) </h3><br /> <p>Statistics for a hosted website are available using cPanel --> Metrics --> Awstats.</p><br /> <p>Select the Domain, and View. For the selected Month, scroll down to a section headed HTTP Status Codes.</p><br /> <p>On the current page for this website only code 404 has a link. Apparently there were over 19000 recent 'hits' for which the web server returned HTTP Code 404.</p><br /> <p>The link on 404 opens the list of page requests which were 'not found'.</p><br /> <p>According to Awstats a total of 2350 URLs were requested, most of them around 50 times. Stats for the {{MH370Site}} website are worse - see below.</p><br /> <br /> <h3>Invalid Requests which are WordPress URLs</h3><br /> <p>Many of the requested URLs look like WordPress files, for example:-</p><br /> <ul><br /> <li>/Wp-content/admin.php</li><br /> <li>/Wp-includes/customize/chosen.php</li><br /> <li>/Wp-content/themes/about.php</li><br /> <li>/Wp-includes/index.php</li><br /> <li>/Wp-includes/html-api/index.php</li><br /> <li>/Wp-content/languages/index.php</li><br /> <li>/Wp-content/admin-header.php</li><br /> <li> and the list goes on...</li><br /> </ul><br /> <p>I find this annoying, and the web server does not know that these pages are invalid, so my MediaWiki installation has to cope with the request, search the database and inform the web server that the page cannot be found. So I decided (experimentally) to put a stop to it.</p><br /> <p>The pattern for these WordPress style URLs is reduced to three main directories:-</p><br /> <ul><br /> <li>wp-admin</li><br /> <li>wp-content</li><br /> <li>wp-includes</li><br /> </ul><br /> <p>A variant for each directory is a capital W. For each of these directories the files requested can be replaced by a *. </p><br /> <p>I added the following lines to a .htaccess file:-</p><br /> <pre><br /> RewriteEngine On<br /> # Serve an error without loading a custom page<br /> RewriteRule ^wp-admin(/.*)?$ - [R=404,L]<br /> RewriteRule ^Wp-admin(/.*)?$ - [R=404,L]<br /> RewriteRule ^wp-content(/.*)?$ - [R=404,L]<br /> RewriteRule ^Wp-content(/.*)?$ - [R=404,L]<br /> RewriteRule ^wp-includes(/.*)?$ - [R=404,L]<br /> RewriteRule ^Wp-includes(/.*)?$ - [R=404,L]<br /> </pre><br /> <br /> <p>Next month when I look at the site metrics I should see a substantial drop in the number of 404 errors and less of these invalid URLs in the list.</p><br /> <br /> <h3>Valid Requests for a page not found</h3><br /> <p>Another use for these statistics is to identify pages which are requested and which should be there, or did exist and maybe were moved.</p><br /> <p>The {{MH370Site}} website has undergone several significant structural changes over the development period and I deliberately did not fill the site with Redirects. I believed that if a new version was internally correct and had few if any 'wanted pages' then people browsing the site would rarely be looking for pages that were not there.</p><br /> <p>That assumption has been reasonably correct but a review of the Error 404 page requests showed about 20 pages which were frequently requested and do not currently exist at that URL (they were moved). The solution was to re-create the page and add a redirect to the current resource.</p><br /> <p>The syntax is simple:-</p><br /> <pre><br /> #REDIRECT [[pagename]]<br /> </pre><br /> <p>Comments can be placed on the page without affecting the redirection. This can be useful to document why the redirect was added and when.</p><br /> <br /> <h3>Valid Requests and Searches, not found</h3><br /> <p>Another use for the statistics is to see which Search Keyphrases and Keywords have been requested.</p><br /> <p>If these requests are valid, consistent with the website topic or content, and a matching resource does not exist, it shows what people want.</p><br /> <p>The solution is to create a resource that meets the need.</p><br /> <br /> <br /> <h3>Error 404 and the {{MH370Site}} Website</h3><br /> <p>In November 2025 the {{MH370Site}} website apparently attracted 409,929 unique visitors, a total of 511,160 hits, and absorbed a bandwidth of 4.23 GB.</p><br /> <p>Unbelievable! The number of people viewing the site can be estimated from the average duration, the number of views on specific pages, and for interest, the country of origin. Most of the bandwidth was probably used by robots, bots or crawlers. Some of the new AI crawlers made the list in November. Actions were taken!</p> <br /> <p>48 different robots crawled the site, probably accounting for most of the hits.</p><br /> <p>292,340 hits resulted in an HTTP Status Code 404 (Not Found).</p><br /> <p>Error 404 for about 20 of the frequently requested pages or URLs can be fixed using redirects - future statistics will show how effective that was.</p><br /> <p>The next large group of requests are pages /Special:WhatLinksHere which are normally restricted to logged-in users. The odd thing about those requests is that the option is in the Tools Menu and for anonymous users that is not visible at all.</p><br /> <p>Reviewing trends in search terms and page requests is part of site maintenance.</p><br /> <br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=HTTP Error Codes<br /> |CatName=HTTP Error Codes<br /> |CatTree=<categorytree mode="pages">HTTP Error Codes</categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Help:Redirects </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Help:Redirects" target="_blank">https://www.mediawiki.org/wiki/Help:Redirects</a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category:Secure]]<br /> [[Category:File htaccess]]<br /> [[Category:HTTP Error Codes]]<br /> [[Category:Maintain]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Category:HTTP_Error_Codes&diff=2445 Category:HTTP Error Codes 2025-12-24T07:56:31Z

<p>GrantM: Created page with "{{CategoryPage |ParentCategory=Maintain |CategoryDescription=HTTP Error Codes are returned to a user by the web server }}"</p> <hr /> <div>{{CategoryPage<br /> |ParentCategory=Maintain<br /> |CategoryDescription=HTTP Error Codes are returned to a user by the web server<br /> }}</div>

GrantM https://mw.mh370.wiki/w/index.php?title=HTTP_Code_404&diff=2444 HTTP Code 404 2025-12-24T07:55:12Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Required but not found URLs (HTTP code 404) </h3><br /> <p>Statistics for a hosted website are available using cPanel --> Metrics --> Awstats.</p><br /> <p>Select the Domain, and View. For the selected Month, scroll down to a section headed HTTP Status Codes.</p><br /> <p>On the current page for this website only code 404 has a link. Apparently there were over 19000 recent 'hits' for which the web server returned HTTP Code 404.</p><br /> <p>The link on 404 opens the list of page requests which were 'not found'.</p><br /> <p>According to Awstats a total of 2350 URLs were requested, most of them around 50 times. Stats for the {{MH370Site}} website are worse - see below.</p><br /> <br /> <h3>Invalid Requests which are WordPress URLs</h3><br /> <p>Many of the requested URLs look like WordPress files, for example:-</p><br /> <ul><br /> <li>/Wp-content/admin.php</li><br /> <li>/Wp-includes/customize/chosen.php</li><br /> <li>/Wp-content/themes/about.php</li><br /> <li>/Wp-includes/index.php</li><br /> <li>/Wp-includes/html-api/index.php</li><br /> <li>/Wp-content/languages/index.php</li><br /> <li>/Wp-content/admin-header.php</li><br /> <li> and the list goes on...</li><br /> </ul><br /> <p>I find this annoying, and the web server does not know that these pages are invalid, so my MediaWiki installation has to cope with the request, search the database and inform the web server that the page cannot be found. So I decided (experimentally) to put a stop to it.</p><br /> <p>The pattern for these WordPress style URLs is reduced to three main directories:-</p><br /> <ul><br /> <li>wp-admin</li><br /> <li>wp-content</li><br /> <li>wp-includes</li><br /> </ul><br /> <p>A variant for each directory is a capital W. For each of these directories the files requested can be replaced by a *. </p><br /> <p>I added the following lines to a .htaccess file:-</p><br /> <pre><br /> RewriteEngine On<br /> # Serve an error without loading a custom page<br /> RewriteRule ^wp-admin(/.*)?$ - [R=404,L]<br /> RewriteRule ^Wp-admin(/.*)?$ - [R=404,L]<br /> RewriteRule ^wp-content(/.*)?$ - [R=404,L]<br /> RewriteRule ^Wp-content(/.*)?$ - [R=404,L]<br /> RewriteRule ^wp-includes(/.*)?$ - [R=404,L]<br /> RewriteRule ^Wp-includes(/.*)?$ - [R=404,L]<br /> </pre><br /> <br /> <p>Next month when I look at the site metrics I should see a substantial drop in the number of 404 errors and less of these invalid URLs in the list.</p><br /> <br /> <h3>Valid Requests for a page not found</h3><br /> <p>Another use for these statistics is to identify pages which are requested and which should be there, or did exist and maybe were moved.</p><br /> <p>The {{MH370Site}} website has undergone several significant structural changes over the development period and I deliberately did not fill the site with Redirects. I believed that if a new version was internally correct and had few if any 'wanted pages' then people browsing the site would rarely be looking for pages that were not there.</p><br /> <p>That assumption has been reasonably correct but a review of the Error 404 page requests showed about 20 pages which were frequently requested and do not currently exist at that URL (they were moved). The solution was to re-create the page and add a redirect to the current resource.</p><br /> <p>The syntax is simple:-</p><br /> <pre><br /> #REDIRECT [[pagename]]<br /> </pre><br /> <p>Comments can be placed on the page without affecting the redirection. This can be useful to document why the redirect was added and when.</p><br /> <br /> <h3>Valid Requests and Searches, not found</h3><br /> <p>Another use for the statistics is to see which Search Keyphrases and Keywords have been requested.</p><br /> <p>If these requests are valid, consistent with the website topic or content, and a matching resource does not exist, it shows what people want.</p><br /> <p>The solution is to create a resource that meets the need.</p><br /> <br /> <br /> <h3>Error 404 and the {{MH370Site}} Website</h3><br /> <p>In November 2025 the {{MH370Site}} website apparently attracted 409,929 unique visitors, a total of 511,160 hits, and absorbed a bandwidth of 4.23 GB.</p><br /> <p>48 different robots crawled the site, probably accounting for most of the hits.</p><br /> <p>292,340 hits resulted in an HTTP Status Code 404 (Not Found).</p><br /> <p>Error 404 for about 20 of the frequently requested pages or URLs can be fixed using redirects - future statistics will show how effective that was.</p><br /> <p>The next large group of requests are pages /Special:WhatLinksHere which are normally restricted to logged-in users. The odd thing about those requests is that the option is in the Tools Menu and for anonymous users that is not visible at all.</p><br /> <p>Reviewing trends in search terms and page requests is part of site maintenance.</p><br /> <br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=HTTP Error Codes<br /> |CatName=HTTP Error Codes<br /> |CatTree=<categorytree mode="pages">HTTP Error Codes</categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Help:Redirects </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Help:Redirects" target="_blank">https://www.mediawiki.org/wiki/Help:Redirects</a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category:Secure]]<br /> [[Category:File htaccess]]<br /> [[Category:HTTP Error Codes]]<br /> [[Category:Maintain]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=HTTP_Code_404&diff=2443 HTTP Code 404 2025-12-24T07:39:30Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Required but not found URLs (HTTP code 404) </h3><br /> <p>Statistics for a hosted website are available using cPanel --> Metrics --> Awstats.</p><br /> <p>Select the Domain, and View. For the selected Month, scroll down to a section headed HTTP Status Codes.</p><br /> <p>On the current page for this website only code 404 has a link. Apparently there were over 19000 recent 'hits' for which the web server returned HTTP Code 404.</p><br /> <p>The link on 404 opens the list of page requests which were 'not found'.</p><br /> <p>According to Awstats a total of 2350 URLs were requested, most of them around 50 times.</p><br /> <br /> <h3>Invalid Requests which are WordPress URLs</h3><br /> <p>Many of the requested URLs look like WordPress files, for example:-</p><br /> <ul><br /> <li>/Wp-content/admin.php</li><br /> <li>/Wp-includes/customize/chosen.php</li><br /> <li>/Wp-content/themes/about.php</li><br /> <li>/Wp-includes/index.php</li><br /> <li>/Wp-includes/html-api/index.php</li><br /> <li>/Wp-content/languages/index.php</li><br /> <li>/Wp-content/admin-header.php</li><br /> <li> and the list goes on...</li><br /> </ul><br /> <p>I find this annoying, and the web server does not know that these pages are invalid, so my MediaWiki installation has to cope with the request, search the database and inform the web server that the page cannot be found. So I decided (experimentally) to put a stop to it.</p><br /> <p>The pattern for these WordPress style URLs is reduced to three main directories:-</p><br /> <ul><br /> <li>wp-admin</li><br /> <li>wp-content</li><br /> <li>wp-includes</li><br /> </ul><br /> <p>A variant for each directory is a capital W. For each of these directories the files requested can be replaced by a *. </p><br /> <p>I added the following lines to a .htaccess file:-</p><br /> <pre><br /> RewriteEngine On<br /> # Serve an error without loading a custom page<br /> RewriteRule ^wp-admin(/.*)?$ - [R=404,L]<br /> RewriteRule ^Wp-admin(/.*)?$ - [R=404,L]<br /> RewriteRule ^wp-content(/.*)?$ - [R=404,L]<br /> RewriteRule ^Wp-content(/.*)?$ - [R=404,L]<br /> RewriteRule ^wp-includes(/.*)?$ - [R=404,L]<br /> RewriteRule ^Wp-includes(/.*)?$ - [R=404,L]<br /> </pre><br /> <br /> <p>Next month when I look at the site metrics I should see a substantial drop in the number of 404 errors and less of these invalid URLs in the list.</p><br /> <br /> <h3>Valid Requests for a page not found</h3><br /> <p>Another use for these statistics is to identify pages which are requested and which should be there, or did exist and maybe were moved.</p><br /> <p>The {{MH370Site}} website has undergone several significant structural changes over the development period and I deliberately did not fill the site with Redirects. I believed that if a new version was internally correct and had few if any 'wanted pages' then people browsing the site would rarely be looking for pages that were not there.</p><br /> <p>That assumption has been reasonably correct but a review of the Error 404 page requests showed about 20 pages which were frequently requested and do not currently exist at that URL (they were moved). The solution was to re-create the page and add a redirect to the current resource.</p><br /> <p>The syntax is simple:-</p><br /> <pre><br /> #REDIRECT [[pagename]]<br /> </pre><br /> <p>Comments can be placed on the page without affecting the redirection. This can be useful to document why the redirect was added and when.</p><br /> <br /> <h3>Valid Requests and Searches, not found</h3><br /> <p>Another use for the statistics is to see which Search Keyphrases and Keywords have been requested.</p><br /> <p>If these requests are valid, consistent with the website topic or content, and a matching resource does not exist, it shows what people want.</p><br /> <p>The solution is to create a resource that meets the need.</p><br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=HTTP Error Codes<br /> |CatName=HTTP Error Codes<br /> |CatTree=<categorytree mode="pages">HTTP Error Codes</categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Help:Redirects </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Help:Redirects" target="_blank">https://www.mediawiki.org/wiki/Help:Redirects</a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category:Secure]]<br /> [[Category:File htaccess]]<br /> [[Category:HTTP Error Codes]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=HTTP_Code_404&diff=2442 HTTP Code 404 2025-12-24T07:32:27Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Required but not found URLs (HTTP code 404) </h3><br /> <p>Statistics for a hosted website are available using cPanel --> Metrics --> Awstats.</p><br /> <p>Select the Domain, and View. For the selected Month, scroll down to a section headed HTTP Status Codes.</p><br /> <p>On the current page for this website only code 404 has a link. Apparently there were over 19000 recent 'hits' for which the web server returned HTTP Code 404.</p><br /> <p>The link on 404 opens the list of page requests which were 'not found'.</p><br /> <p>According to Awstats a total of 2350 URLs were requested, most of them around 50 times.</p><br /> <br /> <h3>Invalid Requests which are WordPress URLs</h3><br /> <p>Many of the requested URLs look like WordPress files, for example:-</p><br /> <ul><br /> <li>/Wp-content/admin.php</li><br /> <li>/Wp-includes/customize/chosen.php</li><br /> <li>/Wp-content/themes/about.php</li><br /> <li>/Wp-includes/index.php</li><br /> <li>/Wp-includes/html-api/index.php</li><br /> <li>/Wp-content/languages/index.php</li><br /> <li>/Wp-content/admin-header.php</li><br /> <li> and the list goes on...</li><br /> </ul><br /> <p>I find this annoying, and the web server does not know that these pages are invalid, so my MediaWiki installation has to cope with the request, search the database and inform the web server that the page cannot be found. So I decided (experimentally) to put a stop to it.</p><br /> <p>The pattern for these WordPress style URLs is reduced to three main directories:-</p><br /> <ul><br /> <li>wp-admin</li><br /> <li>wp-content</li><br /> <li>wp-includes</li><br /> </ul><br /> <p>A variant for each directory is a capital W. For each of these directories the files requested can be replaced by a *. </p><br /> <p>I added the following lines to a .htaccess file:-</p><br /> <pre><br /> RewriteEngine On<br /> # Serve an error without loading a custom page<br /> RewriteRule ^wp-admin(/.*)?$ - [R=404,L]<br /> RewriteRule ^Wp-admin(/.*)?$ - [R=404,L]<br /> RewriteRule ^wp-content(/.*)?$ - [R=404,L]<br /> RewriteRule ^Wp-content(/.*)?$ - [R=404,L]<br /> RewriteRule ^wp-includes(/.*)?$ - [R=404,L]<br /> RewriteRule ^Wp-includes(/.*)?$ - [R=404,L]<br /> </pre><br /> <br /> <p>Next month when I look at the site metrics I should see a substantial drop in the number of 404 errors and less of these invalid URLs in the list.</p><br /> <br /> <h3>Valid Requests for a page not found</h3><br /> <p>Another use for these statistics is to identify pages which are requested and which should be there, or did exist and maybe were moved.</p><br /> <p>The {{MH370Site}} website has undergone several significant structural changes over the development period and I deliberately did not fill the site with Redirects. I believed that if a new version was internally correct and had few if any 'wanted pages' then people browsing the site would rarely be looking for pages that were not there.</p><br /> <p>That assumption has been reasonably correct but a review of the Error 404 page requests showed about 20 pages which were frequently requested and do not currently exist at that URL. The solution was to re-create the page and add a redirect to the current resource.</p><br /> <p>The syntax is simple:-</p><br /> <pre><br /> #REDIRECT [[pagename]]<br /> </pre><br /> <p>Comments can be placed on the page without affecting the redirection. This can be useful to document why the redirect was added and when.</p><br /> <br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=<br /> |CatName=<br /> |CatTree=<categorytree mode="pages"> </categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Help:Redirects </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Help:Redirects" target="_blank">https://www.mediawiki.org/wiki/Help:Redirects</a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category:Secure]]<br /> [[Category:File htaccess]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=HTTP_Code_404&diff=2441 HTTP Code 404 2025-12-24T07:05:35Z

<p>GrantM: Created page with "{{PageHeader}} <h3> </h3> <p> </p> {{DisplayCategoryTree |Topic= |CatName= |CatTree=<categorytree mode="pages"> </categorytree> }} <h3>Links</h3> <dl> <dt> </dt> <dd><html><a href=" " target="_blank"> </a></html></dd> <dt> </dt> <dd><html><a href=" " target="_blank"> </a></html></dd> <dt> </dt> <dd><html><a href=" " target="_blank"> </a></html></dd> <dt> </dt> <dd><html><a href=" " target="_blank"> </a></html></dd>..."</p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3> </h3><br /> <p> </p><br /> <br /> <br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=<br /> |CatName=<br /> |CatTree=<categorytree mode="pages"> </categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category:Security]]<br /> [[Category:Htaccess File]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Securing_MediaWiki&diff=2440 Securing MediaWiki 2025-12-24T07:04:44Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Securing a MediaWiki-based Website</h3><br /> <br /> <p>Please refer to the official MediaWiki documentation linked below - I'm not a security expert!</p><br /> <br /><br /> <br /> <p>MediaWiki is an application written in php which runs on Linux/Unix servers, stores data in databases like MySql and MariaDB, and content is presented to users by web servers, typically Apache or Ngiinx.</p><br /> <p>This used to be referred to by an acronym LAMP - Linux, Apache, MySQL, and PHP.</p><br /> <p>It can also be used to visualize a stack where each of the above is a layer and data is transferred from the layer below and transferred to a layer above. This concept fits with the layers in the TCP/IP model, and theoretically also the OSI Model.</p><br /> <p>These models, and the layer concept, are also useful from the perspective of Security.</p><br /> <p>For hosted websites, physical security is obviously a responsibility of the hosting provider, and the advantage of using a hosting service is that we do not need to maintain and secure the operating system, or the web server application. So, to a great extent, two layers in the LAMP stack are secured by the hosting provider - Linux and Apache, or the operating system and web server.</p><br /> <p>However:-</p><br /> <ul><br /> <li>The web server will allow anonymous users to view the contents of MediaWiki directories, unless prevented.</li><br /> <li>Anonymous users can create new user accounts, unless prevented.</li><br /> <li>Anonymous users, or those with self-created accounts, can add, alter or delete website content, unless prevented.</li><br /> <li>Anonymous users, or those with self-created accounts, can view website content which should be restricted, unless prevented.</li><br /> <li>A MediaWiki-based website could be used by malevolent actors to send spam and as a vehicle for other dangerous actions, unless prevented.</li><br /> </ul><br /> <p>Responsibility for preventing these actions is our responsibility.</p><br /> <br /><br /> <br /> <h3>A Spam Example</h3><br /> <p>One evening (a long time ago) I installed MediaWiki through a hosting service but didn't finish configuring it because it was late but didn't think that would matter.</p><br /> <p>The next day I received a phone call from the service provider to say that they had to shut my sites down because there was too much traffic.</p><br /> <p>I had made a simple mistake: the following lines should have been in LocalSettings.php:-</p><br /> <pre><br /> $wgGroupPermissions["*"]["createaccount"] = false;<br /> $wgGroupPermissions["*"]["edit"] = false;<br /> </pre><br /> <p>Bots obviously scan the Internet looking for vulnerabilities. My incomplete installation was found and probed. The absence of the above settings meant that anonymous users could create accounts. Lots of accounts were created, perhaps by a script. Those accounts were then used to send email. The emails were spam. The traffic volume grew to a level where it was noticed by the hosting service systems administrators. All within 12 hours!</p><br /> <p>Recent versions of MediaWiki may include the above settings in LocalSettings.php by default. But now it is the first thing I check when creating a new installation or implementing an upgrade.</p><br /> <br /><br /> <br /> <h3>Security Tools</h3><br /> <p>Some of the tools available to us which can be used to secure a MediaWiki-based website include:-</p><br /> <ul><br /> <li>The .htaccess file in the root directory. This provides instructions to the web server. There is another .htaccess file in the /w/images directory to prevent direct access.</li><br /> <li>Configuration in LocalSettings.php, such as defining user rights, access levels for user groups, and namespace permissions.</li><br /> <li>The extension Lockdown which provides more security than available using MediaWiki settings.</li><br /> <li>Securing the database settings and passwords.</li><br /> <li>Using strong passwords for access to the hosting service account, and the MediaWiki installation.</li><br /> </ul><br /> <br /><br /> <br /> <h3>Security and the {{MH370Site}} website</h3><br /> <p>To my knowledge security on this website has not been compromised, but people try.</p><br /> <p>The most common attempts are visible by reviewing logs and the statistics pages provided within cPanel.</p><br /> <p>It is well known that administrative access to Wordpress sites is the URL <i>domain name</i>/wp-admin. A common search, which results in a 404 message, is the potential login page at <i>the MH370 site</i>/wp-admin. If successful this probe would inevitably lead to attempts to bypass the administrator password. These probes, and attempts to probe the site logins directly, are undoubtedly automated and malevolent, but not successful. See article [[HTTP Code 404]]</p><br /> <br /><br /> <br /> <h3>Backup</h3><br /> <p>If the site security was breached, what is the worst that could happen? Beyond the spam example above, it would lead to a loss of trust in the integrity of the site content or database. I couldn't check every page. MediaWiki does allow for some changes to be rolled back. But my preferred option would be to delete the potentially corrupted database and connect to a previous version. For that, one would need a suitable backup. And therefore it makes sense to create regular database backups, and test them, so there is always a fall-back option.</p><br /> <br /><br /> <br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=securing MediaWiki<br /> |CatName=Secure<br /> |CatTree=<categorytree mode="pages">Secure</categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Security </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Security" target="_blank">https://www.mediawiki.org/wiki/Security</a></html><br />This page on the MediaWiki website is like a portal leading to other resources, many of which are listed below.</dd><br /> <br /> <dt>Manual:Security </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Security" target="_blank">https://www.mediawiki.org/wiki/Manual:Security</a></html></dd><br /> <br /> <dt>Manual:User rights </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:User_rights" target="_blank">https://www.mediawiki.org/wiki/Manual:User_rights</a></html></dd><br /> <br /> <dt>Manual:Preventing access</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Preventing_access" target="_blank">https://www.mediawiki.org/wiki/Manual:Preventing_access</a></html></dd><br /> <br /> <dt>Security for developers </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Security_for_developers" target="_blank">https://www.mediawiki.org/wiki/Security_for_developers</a></html></dd><br /> <br /> <dt>Security for developers/Architecture </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Security_for_developers/Architecture" target="_blank">https://www.mediawiki.org/wiki/Security_for_developers/Architecture</a></html></dd><br /> <br /> <dt>Security for developers/Tutorial </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Security_for_developers/Tutorial" target="_blank">https://www.mediawiki.org/wiki/Security_for_developers/Tutorial</a></html></dd><br /> <br /> <dt>Security checklist for developers</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Security_checklist_for_developers" target="_blank">https://www.mediawiki.org/wiki/Security_checklist_for_developers</a></html></dd><br /> <br /> <dt>Security/Training resources </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Security/Training_resources" target="_blank">https://www.mediawiki.org/wiki/Security/Training_resources</a></html></dd><br /> <br /> </dl><br /> <br /> <br /> <br /> <br /> [[Category:Secure]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Securing_MediaWiki&diff=2439 Securing MediaWiki 2025-12-24T07:01:03Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Securing a MediaWiki-based Website</h3><br /> <br /> <p>Please refer to the official MediaWiki documentation linked below - I'm not a security expert!</p><br /> <br /><br /> <br /> <p>MediaWiki is an application written in php which runs on Linux/Unix servers, stores data in databases like MySql and MariaDB, and content is presented to users by web servers, typically Apache or Ngiinx.</p><br /> <p>This used to be referred to by an acronym LAMP - Linux, Apache, MySQL, and PHP.</p><br /> <p>It can also be used to visualize a stack where each of the above is a layer and data is transferred from the layer below and transferred to a layer above. This concept fits with the layers in the TCP/IP model, and theoretically also the OSI Model.</p><br /> <p>These models, and the layer concept, are also useful from the perspective of Security.</p><br /> <p>For hosted websites, physical security is obviously a responsibility of the hosting provider, and the advantage of using a hosting service is that we do not need to maintain and secure the operating system, or the web server application. So, to a great extent, two layers in the LAMP stack are secured by the hosting provider - Linux and Apache, or the operating system and web server.</p><br /> <p>However:-</p><br /> <ul><br /> <li>The web server will allow anonymous users to view the contents of MediaWiki directories, unless prevented.</li><br /> <li>Anonymous users can create new user accounts, unless prevented.</li><br /> <li>Anonymous users, or those with self-created accounts, can add, alter or delete website content, unless prevented.</li><br /> <li>Anonymous users, or those with self-created accounts, can view website content which should be restricted, unless prevented.</li><br /> <li>A MediaWiki-based website could be used by malevolent actors to send spam and as a vehicle for other dangerous actions, unless prevented.</li><br /> </ul><br /> <p>Responsibility for preventing these actions is our responsibility.</p><br /> <br /><br /> <br /> <h3>A Spam Example</h3><br /> <p>One evening (a long time ago) I installed MediaWiki through a hosting service but didn't finish configuring it because it was late but didn't think that would matter.</p><br /> <p>The next day I received a phone call from the service provider to say that they had to shut my sites down because there was too much traffic.</p><br /> <p>I had made a simple mistake: the following lines should have been in LocalSettings.php:-</p><br /> <pre><br /> $wgGroupPermissions["*"]["createaccount"] = false;<br /> $wgGroupPermissions["*"]["edit"] = false;<br /> </pre><br /> <p>Bots obviously scan the Internet looking for vulnerabilities. My incomplete installation was found and probed. The absence of the above settings meant that anonymous users could create accounts. Lots of accounts were created, perhaps by a script. Those accounts were then used to send email. The emails were spam. The traffic volume grew to a level where it was noticed by the hosting service systems administrators. All within 12 hours!</p><br /> <p>Recent versions of MediaWiki may include the above settings in LocalSettings.php by default. But now it is the first thing I check when creating a new installation or implementing an upgrade.</p><br /> <br /><br /> <br /> <h3>Security Tools</h3><br /> <p>Some of the tools available to us which can be used to secure a MediaWiki-based website include:-</p><br /> <ul><br /> <li>The .htaccess file in the root directory. This provides instructions to the web server. There is another .htaccess file in the /w/images directory to prevent direct access.</li><br /> <li>Configuration in LocalSettings.php, such as defining user rights, access levels for user groups, and namespace permissions.</li><br /> <li>The extension Lockdown which provides more security than available using MediaWiki settings.</li><br /> <li>Securing the database settings and passwords.</li><br /> <li>Using strong passwords for access to the hosting service account, and the MediaWiki installation.</li><br /> </ul><br /> <br /><br /> <br /> <h3>Security and the {{MH370Site}} website</h3><br /> <p>To my knowledge security on this website has not been breached, but people try.</p><br /> <p>The most common attempts are visible by reviewing logs and the statistics pages provided within cPanel.</p><br /> <p>It is well known that administrative access to Wordpress sites is the URL <i>domain name</i>/wp-admin. A common search, which results in a 404 message, is the potential login page at <i>the MH370 site</i>/wp-admin. If successful this probe would inevitably lead to attempts to bypass the administrator password. These probes, and attempts to probe the site logins directly, are undoubtedly automated and malevolent, but not successful.</p><br /> <br /><br /> <br /> <h3>Backup</h3><br /> <p>If the site security was breached, what is the worst that could happen? Beyond the spam example above, it would lead to a loss of trust in the integrity of the site content or database. I couldn't check every page. MediaWiki does allow for some changes to be rolled back. But my preferred option would be to delete the potentially corrupted database and connect to a previous version. For that, one would need a suitable backup. And therefore it makes sense to create regular database backups, and test them, so there is always a fall-back option.</p><br /> <br /><br /> <br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=securing MediaWiki<br /> |CatName=Secure<br /> |CatTree=<categorytree mode="pages">Secure</categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Security </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Security" target="_blank">https://www.mediawiki.org/wiki/Security</a></html><br />This page on the MediaWiki website is like a portal leading to other resources, many of which are listed below.</dd><br /> <br /> <dt>Manual:Security </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Security" target="_blank">https://www.mediawiki.org/wiki/Manual:Security</a></html></dd><br /> <br /> <dt>Manual:User rights </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:User_rights" target="_blank">https://www.mediawiki.org/wiki/Manual:User_rights</a></html></dd><br /> <br /> <dt>Manual:Preventing access</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Preventing_access" target="_blank">https://www.mediawiki.org/wiki/Manual:Preventing_access</a></html></dd><br /> <br /> <dt>Security for developers </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Security_for_developers" target="_blank">https://www.mediawiki.org/wiki/Security_for_developers</a></html></dd><br /> <br /> <dt>Security for developers/Architecture </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Security_for_developers/Architecture" target="_blank">https://www.mediawiki.org/wiki/Security_for_developers/Architecture</a></html></dd><br /> <br /> <dt>Security for developers/Tutorial </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Security_for_developers/Tutorial" target="_blank">https://www.mediawiki.org/wiki/Security_for_developers/Tutorial</a></html></dd><br /> <br /> <dt>Security checklist for developers</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Security_checklist_for_developers" target="_blank">https://www.mediawiki.org/wiki/Security_checklist_for_developers</a></html></dd><br /> <br /> <dt>Security/Training resources </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Security/Training_resources" target="_blank">https://www.mediawiki.org/wiki/Security/Training_resources</a></html></dd><br /> <br /> </dl><br /> <br /> <br /> <br /> <br /> [[Category:Secure]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=CrawlerProtection&diff=2438 CrawlerProtection 2025-12-24T06:54:42Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <br /> <h3>Extension: CrawlerProtection </h3><br /> <div class="quote"><br /> <p>The CrawlerProtection extension blocks anonymous users from performing actions and accessing special pages which are most frequently abused by AI crawler bots. </p><br /> </div> <br /> <p>This Extension was released in 2025. Once installed, the extension requires no configuration.</p><br /> <p>Before installing a new extension on a live website such as {{MH370Site}} I prefer to test it with the same version of MediaWiki.</p><br /> <p>In this instance, I have installed it on this website, as a trial, and if there are no issues will install it on the {{MH370Site}} later.</p><br /> <br /><br /> <p>When the extension was downloaded the file was named CrawlerProtection-main.tar.gz</p><br /> <p>Consequently, the expanded version was in a folder named CrawlerProtection-main.</p><br /> <p>This was renamed simply CrawlerProtection prior to upload to the hosting site via FTP.</p><br /> <p>As I may reuse this upload I copied an instance of the CrawlerProtection folder to the /extensions directory for this website.</p><br /> <p>I added the following to LocalSettings.php, as per the instructions:-</p><br /> <pre><br /> ## Added (date entered)<br /> wfLoadExtension( 'CrawlerProtection' );<br /> </pre><br /> <p>Using MediaWiki Tools --> Special pages --> Data and tools --> Version, I can see that the extension is installed.</p><br /> <p>Unlike other installed extensions there is no hyperlink to the extension's page on the MediaWiki website.</p><br /> <p>There was no noticeable affect on the operation of this website.</p><br /> <br /> <h3>Extension Performance</h3><br /> <p>How do you know what the CrawlerProtection extension is doing, how effective it is and what it has blocked?</p><br /> <p>When I know the answer I will publish it here...</p><br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=MediaWiki Extensions<br /> |CatName=Extensions<br /> |CatTree=<categorytree mode="pages">Extensions</categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Extension:CrawlerProtection </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Extension:CrawlerProtection" target="_blank">https://www.mediawiki.org/wiki/Extension:CrawlerProtection</a></html></dd><br /> <br /> <dt>Manual:Handling web crawlers </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Handling_web_crawlers" target="_blank">https://www.mediawiki.org/wiki/Manual:Handling_web_crawlers</a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category:Extensions]]<br /> [[Category:Robots]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=CrawlerProtection&diff=2437 CrawlerProtection 2025-12-24T06:53:57Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <br /> <h3>Extension: CrawlerProtection </h3><br /> <div class="quote"><br /> <p>The CrawlerProtection extension blocks anonymous users from performing actions and accessing special pages which are most frequently abused by AI crawler bots. </p><br /> </div> <br /> <p>This Extension was released in 2025. Once installed, the extension requires no configuration.</p><br /> <p>Before installing a new extension on a live website such as {{MH370Site}} I prefer to test it with the same version of MediaWiki.</p><br /> <p>In this instance, I have installed it on this website, as a trial, and if there are no issues will install it on the {{MH370Site}} later.</p><br /> <br /><br /> <p>When the extension was downloaded the file was named CrawlerProtection-main.tar.gz</p><br /> <p>Consequently, the expanded version was in a folder named CrawlerProtection-main.</p><br /> <p>This was renamed simply CrawlerProtection prior to upload to the hosting site via FTP.</p><br /> <p>As I may reuse this upload I copied an instance of the CrawlerProtection folder to the /extensions directory for this website.</p><br /> <p>I added the following to LocalSettings.php, as per the instructions:-</p><br /> <pre><br /> ## Added (date entered)<br /> wfLoadExtension( 'CrawlerProtection' );<br /> </pre><br /> <p>Using MediaWiki Tools --> Special pages --> Data and tools --> Version, I can see that the extension is installed.</p><br /> <p>Unlike other installed extensions there is no hyperlink to the extension's page on the MediaWiki website.</p><br /> <p>There was no noticeable affect on the operation of this website.</p><br /> <br /> <h3>Extension Performance</h3><br /> <p>How do you know what the CrawlerProtection extension is doing, how effective it is and what it has blocked?</p><br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=MediaWiki Extensions<br /> |CatName=Extensions<br /> |CatTree=<categorytree mode="pages">Extensions</categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Extension:CrawlerProtection </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Extension:CrawlerProtection" target="_blank">https://www.mediawiki.org/wiki/Extension:CrawlerProtection</a></html></dd><br /> <br /> <dt>Manual:Handling web crawlers </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Handling_web_crawlers" target="_blank">https://www.mediawiki.org/wiki/Manual:Handling_web_crawlers</a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category:Extensions]]<br /> [[Category:Robots]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Category:Robots&diff=2436 Category:Robots 2025-12-24T06:52:04Z

<p>GrantM: Created page with "{{CategoryPage |ParentCategory=Configure |CategoryDescription=Pages relating to robots, bots, crawlers etc. }}"</p> <hr /> <div>{{CategoryPage<br /> |ParentCategory=Configure<br /> |CategoryDescription=Pages relating to robots, bots, crawlers etc.<br /> }}</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Robots.txt&diff=2435 Robots.txt 2025-12-24T06:51:05Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Directives to Robots</h3><br /> <p>The most common method for website administrators to control web crawlers is by creating a robots.txt file. This is placed in the website root directory, usually with a sitemap.</p><br /> <p>The robots.txt file tells search engine robots where to find a Site Map, and instructions which allow or disallow robot's access to parts of the website. For example, some Namespaces may be accessible and search is allowed; others are disallowed.</p><br /> <p>Google provides some insight into how their web crawler will interpret a robots.txt file, and also provides a tool to assist in the creation and testing of a robots.txt file.</p><br /> <p>However, MediaWiki presents some interesting problems because of the Namespaces and Talk namespaces, Special Pages and maybe other areas which should be specifically denied.</p> <br /> <br /> <h3>Robots and MediaWiki</h3><br /> <p>MediaWiki has several methods to control robots:-</p><br /> <ol><br /> <li>A robots.txt file can be placed in the root directory. This can also link to a sitemap.</li><br /> <li>Robot policies can be defined using variables in LocalSettings.php - see <i>Manual:Robot policy</i></li><br /> <li>Magic Words can be added to specific pages to control indexing.</li><br /> </ol><br /> <br /> <h3>Robots.txt File is Visible</h3><br /> <p>Because the robots.txt file is known to be placed in a root directory anyone can browse to a website <i>websiteURL/robots.txt</i> and the text will be displayed in a browser window.</p><br /> <p>For a normal webnsite if you list files or directories which you don't want bots or robots to scan then you are also listing files or directories which exist but now have listed for anyone who is reading this file.</p><br /> <p>For a MediaWiki-based website the 'files or directories' are virtual - they are pages or articles and namespaces.</p><br /> <p>To prevent crawlers from accessing specific namespaces it is probably better to rely on the variables which can be configured in LocalSettings.php, and avoid publishing the namespace names in a robots.txt file.</p><br /> <br /> <br /> <br /> <h3>Manual:Robot policy</h3><br /> <p>Although this Manual has limited information, it does list the variables which can be configured to tell web crawlers and other tools what to exclude. The use of the directive 'allow' in robots.txt is not really supported - robots.txt works by exclusion. Basically, anything not denied is allowed.</p><br /> <p>The configuration settings listed in the <i>Manual:Robot policy</i> are:-</p> <br /> <ul><br /> <li><html><a href="https://www.mediawiki.org/wiki/Manual:$wgDefaultRobotPolicy" target="_blank">$wgDefaultRobotPolicy</a></html> - Default robot exclusion policy for the wiki</li><br /> <li><html><a href="https://www.mediawiki.org/wiki/Manual:$wgArticleRobotPolicies" target="_blank">$wgArticleRobotPolicies</a></html> - Allow customization of robot policies on a per-article basis</li><br /> <li><html><a href="https://www.mediawiki.org/wiki/Manual:$wgExemptFromUserRobotsControl" target="_blank">$wgExemptFromUserRobotsControl</a></html> - An array of namespace keys in which the __INDEX__/__NOINDEX__ magic words will not function</li><br /> <li><html><a href="https://www.mediawiki.org/wiki/Manual:$wgNamespaceRobotPolicies" target="_blank">$wgNamespaceRobotPolicies</a></html> - Allow customization of robot policies on a per-namespace basis</li><br /> </ul><br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Manual:Robot policy </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Robot_policy" target="_blank">https://www.mediawiki.org/wiki/Manual:Robot_policy</a></html></dd><br /> <br /> <dt>Manual:robots.txt</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Robots.txt" target="_blank">https://www.mediawiki.org/wiki/Manual:Robots.txt</a></html></dd><br /> <br /> <dt>Manual:Noindex</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Noindex" target="_blank">https://www.mediawiki.org/wiki/Manual:Noindex</a></html></dd><br /> <br /> <dt>Introduction to robots.txt (Google Search Central) </dt><br /> <dd><html><a href="https://developers.google.com/search/docs/crawling-indexing/robots/intro" target="_blank">https://developers.google.com/search/docs/crawling-indexing/robots/intro</a></html></dd><br /> <br /> <dt>How to write and submit a robots.txt file (Google Search Central) </dt><br /> <dd><html><a href="https://developers.google.com/search/docs/crawling-indexing/robots/create-robots-txt" target="_blank">https://developers.google.com/search/docs/crawling-indexing/robots/create-robots-txt</a></html></dd><br /> <br /> <dt>The Ultimate 2025 List of Web Crawlers and Good Bots: Identification, Examples, and Best Practices </dt><br /> <dd><html><a href="https://www.humansecurity.com/learn/blog/crawlers-list-known-bots-guide/" target="_blank">https://www.humansecurity.com/learn/blog/crawlers-list-known-bots-guide/ </a></html></dd><br /> <br /> <dt>Manual:Handling web crawlers</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Handling_web_crawlers" target="_blank">https://www.mediawiki.org/wiki/Manual:Handling_web_crawlers</a></html><br /> This is a relatively new resource on the MediaWiki website and also mentions a new Extension:[[CrawlerProtection]].</dd><br /> <br /> </dl><br /> <br /> [[Category:$wgDefaultRobotPolicy]]<br /> [[Category:$wgArticleRobotPolicies]]<br /> [[Category:$wgExemptFromUserRobotsControl]]<br /> [[Category:$wgNamespaceRobotPolicies]]<br /> [[Category:LocalSettings.php]]<br /> [[Category:Robots]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=CrawlerProtection&diff=2434 CrawlerProtection 2025-12-24T06:44:15Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <br /> <h3>Extension: CrawlerProtection </h3><br /> <div class="quote"><br /> <p>The CrawlerProtection extension blocks anonymous users from performing actions and accessing special pages which are most frequently abused by AI crawler bots. </p><br /> </div> <br /> <p>This Extension was released in 2025. Once installed, the extension requires no configuration.</p><br /> <p>Before installing a new extension on a live website such as {{MH370Site}} I prefer to test it with the same version of MediaWiki.</p><br /> <p>In this instance, I have installed it on this website, as a trial, and if there are no issues will install it on the {{MH370Site}} later.</p><br /> <br /><br /> <p>When the extension was downloaded the file was named CrawlerProtection-main.tar.gz</p><br /> <p>Consequently, the expanded version was in a folder named CrawlerProtection-main.</p><br /> <p>This was renamed simply CrawlerProtection prior to upload to the hosting site via FTP.</p><br /> <p>As I may reuse this upload I copied an instance of the CrawlerProtection folder to the /extensions directory for this website.</p><br /> <p>I added the following to LocalSettings.php, as per the instructions:-</p><br /> <pre><br /> ## Added (date entered)<br /> wfLoadExtension( 'CrawlerProtection' );<br /> </pre><br /> <br /> {{DisplayCategoryTree<br /> |Topic=<br /> |CatName=<br /> |CatTree=<categorytree mode="pages"> </categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Extension:CrawlerProtection </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Extension:CrawlerProtection" target="_blank">https://www.mediawiki.org/wiki/Extension:CrawlerProtection</a></html></dd><br /> <br /> <dt>Manual:Handling web crawlers </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Handling_web_crawlers" target="_blank">https://www.mediawiki.org/wiki/Manual:Handling_web_crawlers</a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category: ]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=CrawlerProtection&diff=2433 CrawlerProtection 2025-12-24T06:37:27Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <br /> <h3>Extension: CrawlerProtection </h3><br /> <div class="quote"><br /> <p>The CrawlerProtection extension blocks anonymous users from performing actions and accessing special pages which are most frequently abused by AI crawler bots. </p><br /> </div> <br /> <p>This Extension was released in 2025. Once installed, the extension requires no configuration.</p><br /> <p>Before installing a new extension on a live website such as {{MH370Site}} I prefer to test it with the same version of MediaWiki.</p><br /> <p>In this instance, I have installed it on this website, as a trial, and if there are no issues will install it on the {{MH370Site}} later.</p><br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=<br /> |CatName=<br /> |CatTree=<categorytree mode="pages"> </categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Extension:CrawlerProtection </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Extension:CrawlerProtection" target="_blank">https://www.mediawiki.org/wiki/Extension:CrawlerProtection</a></html></dd><br /> <br /> <dt>Manual:Handling web crawlers </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Handling_web_crawlers" target="_blank">https://www.mediawiki.org/wiki/Manual:Handling_web_crawlers</a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category: ]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=CrawlerProtection&diff=2432 CrawlerProtection 2025-12-24T06:29:45Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <br /> <h3>Extension: CrawlerProtection </h3><br /> <div class="quote"><br /> <p>The CrawlerProtection extension blocks anonymous users from performing actions and accessing special pages which are most frequently abused by AI crawler bots. </p><br /> </div> <br /> <br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=<br /> |CatName=<br /> |CatTree=<categorytree mode="pages"> </categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category: ]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=CrawlerProtection&diff=2431 CrawlerProtection 2025-12-24T06:29:26Z

<p>GrantM: Created page with "{{PageHeader}} <h3>Extension: CrawlerProtection </h3> <div class="quote;"> <p>he CrawlerProtection extension blocks anonymous users from performing actions and accessing special pages which are most frequently abused by AI crawler bots. </p> </div>  {{DisplayCategoryTree |Topic= |CatName= |CatTree=<categorytree mode="pages"> </categorytree> }} <h3>Links</h3> <dl> <dt> </dt> <dd><html><a href=" " target="_blank"> </a></html></dd>..."</p> <hr /> <div>{{PageHeader}}<br /> <br /> <br /> <h3>Extension: CrawlerProtection </h3><br /> <div class="quote;"><br /> <p>he CrawlerProtection extension blocks anonymous users from performing actions and accessing special pages which are most frequently abused by AI crawler bots. </p><br /> </div> <br /> <br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=<br /> |CatName=<br /> |CatTree=<categorytree mode="pages"> </categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category: ]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Category:$wgShowExceptionDetails&diff=2430 Category:$wgShowExceptionDetails 2025-12-24T04:13:38Z

<p>GrantM: Created page with "{{CategoryPage |ParentCategory=Variables |CategoryDescription=A variable used for troubleshooting }}"</p> <hr /> <div>{{CategoryPage<br /> |ParentCategory=Variables<br /> |CategoryDescription=A variable used for troubleshooting<br /> }}</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Runtime_Exception_Errors&diff=2429 Runtime Exception Errors 2025-12-24T04:12:55Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Runtime Exception Errors </h3><br /> <p>Here is an example of a typical runtime exception error message:-</p><br /> <html><br /> <img src="/w/MyImages/Trouble/RuntimeExceptionError.jpg"<br /> height: auto; <br /> onContextMenu="return false;"><br /> </html><br /> <br /> <p>To get more detail, add the following line to the end of the LocalSettings.php file:-</p><br /> <pre><br /> $wgShowExceptionDetails = true;<br /> </pre><br /> <br /> <br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=<br /> |CatName=Troubleshooting<br /> |CatTree=<categorytree mode="pages"> </categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Manual:Common errors and symptoms</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Common_errors_and_symptoms" target="_blank">https://www.mediawiki.org/wiki/Manual:Common_errors_and_symptoms</a></html></dd><br /> <br /> <dt>Manual:$wgShowExceptionDetails </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:$wgShowExceptionDetails" target="_blank">https://www.mediawiki.org/wiki/Manual:$wgShowExceptionDetails</a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category:$wgShowExceptionDetails]]<br /> [[Category:Troubleshooting]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Runtime_Exception_Errors&diff=2428 Runtime Exception Errors 2025-12-24T04:09:25Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Runtime Exception Errors </h3><br /> <p>Here is an example of a typical runtime exception error message:-</p><br /> <html><br /> <img src="/w/MyImages/Trouble/RuntimeExceptionError.jpg"<br /> height: auto; <br /> onContextMenu="return false;"><br /> </html><br /> <br /> <br /> <br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=<br /> |CatName=Troubleshooting<br /> |CatTree=<categorytree mode="pages"> </categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Manual:Common errors and symptoms</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Common_errors_and_symptoms" target="_blank">https://www.mediawiki.org/wiki/Manual:Common_errors_and_symptoms</a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category: ]]<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> See image for Runtime Exception Error<br /> <br /> <p>Add <html><code>$wgShowExceptionDetails = true;M/code></html> at the bottom of LocalSettings.php</p><br /> <p>This gives a more detail about error message.</p></div>

GrantM https://mw.mh370.wiki/w/index.php?title=Runtime_Exception_Errors&diff=2427 Runtime Exception Errors 2025-12-24T04:06:20Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Runtime Exception Errors </h3><br /> <p>here is an example of a typical runtime exception error message:-</p><br /> <html><br /> <img src="/w/MyImages/Trouble/RuntimeExceptionError.jpg"<br /> height: auto; <br /> onContextMenu="return false;"><br /> </html><br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=<br /> |CatName=Troubleshooting<br /> |CatTree=<categorytree mode="pages"> </categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category: ]]<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> See image for Runtime Exception Error<br /> <br /> <p>Add <html><code>$wgShowExceptionDetails = true;M/code></html> at the bottom of LocalSettings.php</p><br /> <p>This gives a more detail about error message.</p></div>

GrantM https://mw.mh370.wiki/w/index.php?title=Help:Manual/Images&diff=2426 Help:Manual/Images 2025-12-24T04:05:24Z

<p>GrantM: Created page with "<h3>Images are stored in a sub-folder MyImages</h3> <p>Older images were uploaded to the default images folder and its a mess.</p> <p>This code works:-</p> <pre> <h3>Website Analytics or Statistics</h3> <p>cPanel has a section headed <b>Metrics</b>. </p> <html> <img src="/w/MyImages/cPanel/Metrics.jpg" height: auto; onContextMenu="return false;"> </html> </pre>"</p> <hr /> <div><h3>Images are stored in a sub-folder MyImages</h3><br /> <p>Older images were uploaded to the default images folder and its a mess.</p><br /> <p>This code works:-</p><br /> <pre><br /> <h3>Website Analytics or Statistics</h3><br /> <p>cPanel has a section headed <b>Metrics</b>. </p><br /> <html><br /> <img src="/w/MyImages/cPanel/Metrics.jpg"<br /> height: auto; <br /> onContextMenu="return false;"><br /> </html><br /> </pre></div>

GrantM https://mw.mh370.wiki/w/index.php?title=Runtime_Exception_Errors&diff=2425 Runtime Exception Errors 2025-12-24T03:58:53Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Runtime Exception Errors </h3><br /> <p>here is an example of a typical runtime exception error message:-</p><br /> [[File:../MyImages/Trouble/RuntimeExceptionError.jpg]]<br /> <br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=<br /> |CatName=Troubleshooting<br /> |CatTree=<categorytree mode="pages"> </categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category: ]]<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> See image for Runtime Exception Error<br /> <br /> <p>Add <html><code>$wgShowExceptionDetails = true;M/code></html> at the bottom of LocalSettings.php</p><br /> <p>This gives a more detail about error message.</p></div>

GrantM https://mw.mh370.wiki/w/index.php?title=Runtime_Exception_Errors&diff=2424 Runtime Exception Errors 2025-12-24T03:58:38Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Runtime Exception Errors </h3><br /> <p>here is an example of a typical runtime exception error message:-</p><br /> [[File:/MyImages/Trouble/RuntimeExceptionError.jpg]]<br /> <br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=<br /> |CatName=Troubleshooting<br /> |CatTree=<categorytree mode="pages"> </categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category: ]]<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> See image for Runtime Exception Error<br /> <br /> <p>Add <html><code>$wgShowExceptionDetails = true;M/code></html> at the bottom of LocalSettings.php</p><br /> <p>This gives a more detail about error message.</p></div>

GrantM https://mw.mh370.wiki/w/index.php?title=Runtime_Exception_Errors&diff=2423 Runtime Exception Errors 2025-12-24T03:51:49Z

<p>GrantM: GrantM moved page RuntimeException to Runtime Exception Errors without leaving a redirect</p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Runtime Exception Errors </h3><br /> <p> </p><br /> <br /> <br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=<br /> |CatName=<br /> |CatTree=<categorytree mode="pages"> </categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category: ]]<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> See image for Runtime Exception Error<br /> <br /> <p>Add <html><code>$wgShowExceptionDetails = true;M/code></html> at the bottom of LocalSettings.php</p><br /> <p>This gives a more detail about error message.</p></div>

GrantM https://mw.mh370.wiki/w/index.php?title=Runtime_Exception_Errors&diff=2422 Runtime Exception Errors 2025-12-24T03:51:34Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Runtime Exception Errors </h3><br /> <p> </p><br /> <br /> <br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=<br /> |CatName=<br /> |CatTree=<categorytree mode="pages"> </categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> <br /> <dt> </dt><br /> <dd><html><a href=" " target="_blank"> </a></html></dd><br /> </dl><br /> <br /> <br /> <br /> [[Category: ]]<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> See image for Runtime Exception Error<br /> <br /> <p>Add <html><code>$wgShowExceptionDetails = true;M/code></html> at the bottom of LocalSettings.php</p><br /> <p>This gives a more detail about error message.</p></div>

GrantM https://mw.mh370.wiki/w/index.php?title=Subdomains_and_cPanel&diff=2421 Subdomains and cPanel 2025-12-24T03:50:02Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Domains, Subdomains and cPanel </h3><br /> <p>The domain name registered for a website forms part of the URL used by a web browser. The domain portion of a URL is used to query DNS servers so that the browser can direct a query for a webpage to a specific IP Address. </p><br /> <p>However, apart from an insufficient number of IP Version 4 addresses, the hosting service providers share each IP address among several user accounts. At the very least if you have an account with several websites they will all share the same IP address.</p><br /> <br /> <h3>The Main Domain</h3><br /> <p>When you establish an account with a hosting service provider you usually register a domain name for the first website, or supply a domain name which may have been registered separately.</p><br /> <p>This becomes your Main Domain.</p><br /> <p>For purposes of this explanation, assume that the main domain is <i>MyWebsite.wiki</i>. The URL would therefore be <html><code>https://www.mywebsite.wiki</code></html></p><br /> <p>Websites are usually located in a subdirectory of your /home account, at /home/public_html. So the main domain may point to /home/public_html/MyWebsite. </p><br /> <p>As recommended, your MediaWiki installation will be in a subdirectory /w, or /home/public_html/MyWebsite/w</p><br /> <p>A BIG problem results if the hosting provider did not allocate subdirectory in /public_html because a normal cPanel user does not have sufficient privileges to create a new folder for their main domain.</p><br /> <p>This BIG problem becomes apparent when want to add separate websites after you register and add additional domains or if you create subdomains to use for separate websites. A solution is a complex system of .htaccess files, not covered in this article.</p><br /> <br /> <h3>Addon Domains</h3><br /> <p>If you have additional registered domains they are added via cPanel --> Domains --> Domains which opens a list of domains.</p><br /> <p>A Subdomain can be added as described in the article [[Create a Subdomain]].</p><br /> <p>For this example we will begin with a subdomain for mywebsite.wiki which we will call ships, so the domain will be listed as <i>ships.mywebsite.wiki</i>.</p><br /> <p>The associated website could be located at /public_html/Ships and MediaWiki would be installed in /public_html/Ships/w</p><br /> <p>But the website <i>ships.mywebsite.wiki</i> shares the same IP address as <i>www.mywebsite.wiki</i> and <i>mywebsite.wiki</i>.</p><br /> <p>A set of DNS records exists for the main domain <i>mywebsite.wiki</i> and DNS records are created for <i>ships.mywebsite.wiki</i> and added to the records for the domain <i>mywebsite.wiki</i>.</p><br /> <br /><br /> <p>The same process occurs if you add additional domains. For example if you register <i>shipsandplanes.wiki</i> and create a website for <i>Ships and Planes</i> it will share the same IP address as the main domain and any other subdomains of the main domain.</p><br /> <p>DNS records for the new domain <i>shipsandplanes.wiki</i> will be created AND additional records will be added to the <i>mywebsite.wiki</i> DNS record.</p><br /> <p>cPanel will treat the new domain as though it is a subdomain of your main domain and creates records for <i>shipsandplanes.wiki.mywebsite.wiki</i>.</p><br /> <br /><br /> <p>The DNS records are visible via cPanel -->Domains --> Zone Editor.</p><br /> <p>The 'subdomains' are actually visible via cPanel -->Domains but not shown by default. Click on the toothed wheel symbol on the menu bar - this setting toggles 'Show Associated Subdomains' and 'Hide Associated Subdomains'.</p><br /> <p>The subdomains that this applies to are these 'extra' subdomains.</p><br /> <br /> <h3>Related Issues</h3><br /> <p>All of the domain.maindomain zone records are valid. That means you can legitimately put this URL in a browser <html><code>https://shipsandplanes.wiki.mywebsite.wiki</code></html> and it will load your website shipsandplanes.wiki</p><br /> <p>Some browsers are configured to display a search term as well as, or instead of, the page address. So although a webpage request has been correctly resolved to the actual domain name, the browser may display the longer url which includes the main domain.</p><br /> <p>Can this be avoided or prevented? Unfortunately, no.</p><br /> <p>Actually, the situation becomes more complex if the number of registered domains is increased, and worse if there are redirects which make it difficult to unravel what is happening.</p><br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=Subdomains and cPanel<br /> |CatName=Domains<br /> |CatTree=<categorytree mode="pages">Domains </categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Create a New Domain </dt><br /> <dd><html><a href="https://docs.cpanel.net/cpanel/domains/domains/create-a-new-domain/" target="_blank">https://docs.cpanel.net/cpanel/domains/domains/create-a-new-domain/ </a></html><br />cPanel calls these <i>Addon Domains</i></dd><br /> <br /> <dt>How Your Server Handles Domains and Virtual Hosts </dt><br /> <dd><html><a href="https://docs.cpanel.net/knowledge-base/cpanel-product/how-your-server-handles-domains-and-virtual-hosts/" target="_blank">https://docs.cpanel.net/knowledge-base/cpanel-product/how-your-server-handles-domains-and-virtual-hosts/</a></html><br />cPanel documentation which covers the content of this article, explained their way</dd><br /> <br /> <dt>Basic WebHost Manager Setup </dt><br /> <dd><html><a href="https://docs.cpanel.net/whm/server-configuration/basic-webhost-manager-setup/" target="_blank">https://docs.cpanel.net/whm/server-configuration/basic-webhost-manager-setup/</a></html><br />This page describes what is set up for a new account holder, by the Service Provider 'behind the scenes'.</dd><br /> </dl><br /> <br /> <br /> <br /> [[Category:Domains]]<br /> [[Category:cPanel]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Category:Database&diff=2420 Category:Database 2025-12-24T03:48:52Z

<p>GrantM: Created page with "{{CategoryPage |ParentCategory=MediaWiki |CategoryDescription=Each mediaWiki-based website uses a database. }}"</p> <hr /> <div>{{CategoryPage<br /> |ParentCategory=MediaWiki<br /> |CategoryDescription=Each mediaWiki-based website uses a database.<br /> }}</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Choosing_a_Colour_Scheme&diff=2419 Choosing a Colour Scheme 2025-12-24T03:44:38Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Customising the Interface of a MediaWiki-based Website</h3><br /> <p>The appearance of a MediaWiki-based website is controlled by CSS Classes used by MediaWiki and by the installed Skin.</p><br /> <p>Altering the appearance, or customising the Interface, involves editing MediaWiki:Common.css and the skin CSS which is also in the MediaWiki: namespace.</p><br /> <p>Processes involved in customising the interface are covered in separate articles:-</p><br /> {{Customise Interface List}}<br /> <br /><br /> <br /> <p>There are two easy ways to choose a colour scheme.</p><br /> <br /> <h3>1 Sample Colours in an Image</h3><br /> <p>The {{MH370Site}} website theme is based on the colours in a Boeing 777 Flight Deck. Specifically from a photograph from the cockpit of the actual aircraft which went missing. This image is available from <html><a href="https://commons.wikimedia.org/wiki/Main_Page" target="_blank">Wikimedia Commons</a></html> and is shown below:-</p><br /> [[File:Boeing 777-2H6-ER, Malaysia Airlines AN0561319.jpg|800px|Cockpit of the Boeing 777]]<br /> <p>There are shades of brown, grey, blue/purple and creme in this image. Text is also visible in white, green, orange and blue.</p><br /> <p>These colours are represented in the theme created for the {{MH370Site}} website. The 'black screen' is used only on the Main Page and on passenger pages where it creates a sombre background. Other pages are brighter but still framed by a shaped border to replicate the cockpit display screens. The site Tagline <i>MH370 DECODED</i> is styled to be similar to the <i>BOEING 777</i> label on the instrument panel. </p><br /> [[File:MH370SiteV4.jpg|800px]]<br /> <br /><br /> <br /><br /> <br /> <h3>2 Use Shades of Complementary Colours</h3><br /> <p>The colour scheme for this website started with a choice of SteelBlue. This is one of 140 color names supported by current browsers and is shown on the page <html><a href="https://www.w3schools.com/tags/ref_colornames.asp" target="_blank">HTML Color Names</a></html> published by w3Schools.</p><br /> [[File:SteelBlue.jpg|SteelBlue from w3Schools]]<br /> <p>The hex code is #4682B4. Using this hex code in the w3Schools <html><a href="https://www.w3schools.com/colors/colors_picker.asp" target="_blank">HTML Color Picker</a></html> shows where the color is placed on a spectrum of light to dark:- </p><br /> [[File:SteelBlue49.jpg|alt=Steel Blue on spectrum at 49%|Steel Blue on spectrum at 49%]]<br /> <p>I prefer to work with whole percentages, so the base color for this website will be #4785B8, but I will still call it SteelBlue.</p><br /> <p>Using the hex code #4785B8 in the w3Schools' Color Picker now provides a range of suitable colours:-</p><br /> [[File:SteelBlueColorRange.jpg|alt=Color Range based on Steel Blue|Color Range based on Steel Blue]]<br /> <p>These shades of blue (monochrome complimentary) will be used for the MediaWiki page header, background, and border around the content.<p><br /> <p>I want a different color range for use in the Sidebar. My goal is to use something quite different to clearly distinguish between MediaWiki CSS classes and the Vector and CollapsibleVector CSS classes.</p><br /> <p>A first option was to consider a colour which is complementary to SteelBlue. I used several on-line color wheels to find a color complimentary to my SteelBlue <span style="background-color:#4785B8">#4785B8</span><br /> and they each suggested a brown with the hex code <span style="background-color:#B87A47;">#B87A47</span> which doesn't appeal. However, I noticed on the w3Schools <html><a href="https://www.w3schools.com/tags/ref_colornames.asp" target="_blank">HTML Color Names</a></html> adjacent to the SteelBlue is a Tan color with hex code <span style="background-color:#D2B48C;">#D2B48C</span> so I propose using that for the Sidebar.</p><br /> <p>On the W3Schools <html><a href="https://www.w3schools.com/colors/colors_picker.asp" target="_blank">Color Picker</a></html> #D2B48C is at 69%, but the color at 50% will become my base color.</p><br /> [[File:Tan69percent.jpg|alt=Tan colors|Tan colors]]<br /> <p>The full range from the W3Schools <html><a href="https://www.w3schools.com/colors/colors_picker.asp" target="_blank">Color Picker</a></html> is shown below, with the base Tan color #B88747 at 50%.</p><br /> [[File:TanColorRange.jpg|alt=Tan Color Range from w3Schools Color Picker|Tan Color Range from w3Schools Color Picker]]<br /> <br /> <h3>Color Names</h3><br /> <p>CSS variables can be used for colors. See article [[Colors as Variables]].</p><br /> <p>Two sets of variables will be created to identify shades of our two colors, SteelBlue and Tan, but limited to the useful shades only.</p><br /> <p>The following will be added to MediaWiki:Common.css.</p><br /> <pre><br /> /* Steel Blue */<br /> :root { --SteelBlue-80: #B6CEE2;<br /> --SteelBlue-70: #91B6D4;<br /> --SteelBlue-60: #6C9DC6;<br /> --SteelBlue-50: #4785B8;<br /> --SteelBlue-40: #396A93;<br /> }<br /> <br /> /* Tan */<br /> :root { --Tan-90: #F1E7DA;<br /> --Tan-80: #E2CFB6;<br /> --Tan-70: #D4B791;<br /> --Tan-60: #C69F6C;<br /> --Tan-50: #B88747;<br /> --Tan-40: #936C39;<br /> }<br /> </pre><br /> <br /> <h3>Related Articles</h3><br /> <ol><br /> <li>[[Choosing a Colour Scheme]] (described here)</li><br /> <li>[[Identify Interface Classes|Identifying the various CSS Classes]] used by both MediaWiki and the active Skin</li><br /> <li>[[Apply a Custom Colour Scheme|Applying a Custom Colour Scheme]] to appropriate Classes in MediaWiki:common.css and the skin CSS, for example MediaWiki:Vector.css, as used here.</li><br /> </ol><br /> <br /> <br /> <h3>Links</h3><br /> <h5>Resources from w3Schools</h5><br /> {{Snippets:Resources from w3Schools}}<br /> <br /> [[Category:Interface]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Skins&diff=2418 Skins 2025-12-24T03:44:23Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>MediaWiki Skins </h3><br /> <p>Skins define the look and feel of the user interface for the MediaWiki-based website. </p><br /> <p>MediaWiki is currently supplied with four skins: MinervaNeue, MonoBook, Timeless, and two versions of Vector (Vector and Vector 2022).</p><br /> <p>The default installation loads all of these skins but one is selected as the default by the variable [[:Category:$wgDefaultSkin|$wgDefaultSkin]].</p><br /> <p>If allowed, users (with accounts) can select a skin, according to their preference, from the loaded available skins.</p><br /> <br /><br /> <br /> <h3>Skins and the {{MH370Site}} website</h3><br /> <p>The {{MH370Site}} website currently uses the Vector skin with the CollapsibleVector extension which enables drop-down menus in the Sidebar.</p><br /> <p>The website has previously used the Foreground skin and the Pivot skin, both of which are based on the Zurb Foundation CSS Framework. The advantage is that functional CSS is included.</p><br /> <p>However, the Vector skin is bundled with MediaWiki so is less of a risk when it is time to upgrade. And the CollapsibleVector extension is very usable. And I learned how to create my own CSS so no longer need the Foundation code.</p><br /> <p>Vector is a plain skin, visualise Wikipedia for example, but it has been significantly customised for the {{MH370Site}} website. This process is described in these articles:-</p><br /> {{Customise Interface List}}<br /> <br /><br /> <br /> <br /> <br /> <br /> {{DisplayCategoryTree<br /> |Topic=MediaWiki Skins<br /> |CatName=Skins<br /> |CatTree=<categorytree mode="pages">Skins </categorytree><br /> }}<br /> <br /> <br /> <h3>Links</h3><br /> <dl><br /> <dt>Help:Skins</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Help:Skins" target="_blank">https://www.mediawiki.org/wiki/Help:Skins</a></html></dd><br /> <br /> <dt>Manual:Skins </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Skins" target="_blank">https://www.mediawiki.org/wiki/Manual:Skins</a></html></dd><br /> <br /> <dt>Manual:$wgDefaultSkin</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:$wgDefaultSkin" target="_blank">https://www.mediawiki.org/wiki/Manual:$wgDefaultSkin</a></html></dd><br /> <br /> <dt>Bundled extensions and skins </dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Bundled_extensions_and_skins#Skins" target="_blank">https://www.mediawiki.org/wiki/Bundled_extensions_and_skins#Skins</a></html></dd><br /> <br /> <dt>Category:All skins </dt><br /> <dd>A MediaWiki category page listing skins currently registered at MediaWiki.<br /><br /> <html><a href="https://www.mediawiki.org/wiki/Category:All_skins" target="_blank">https://www.mediawiki.org/wiki/Category:All_skins</a></html></dd><br /> </dl><br /> <br /> <br /> [[Category:Customise]]<br /> [[Category:Skins]]<br /> [[Category:$wgDefaultSkin]]<br /> [[Category:Interface]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=MediaWiki_Default_Styles&diff=2417 MediaWiki Default Styles 2025-12-24T03:44:01Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <p>The concept of Cascading Style Sheets is that a hierarchy permits inheritance but to override the style inherited by an element requires understanding the cascade.</p><br /> <p>MediaWiki has various styles pre-defined which are loaded as default styles.</p><br /> <p>Just as the configuration settings in Localsettings.php override MediaWiki default configurations, styles (CSS) created in MediaWiki:Common.css override MediaWiki default styles.</p><br /> <p>Similarly, a customised appearance for the interface can be developed by styles (CSS) in MediaWiki:Vector.css which override the Vector skin default styles.</p><br /> <p>If Vector is not the default skin, the custom CSS will be in MediaWiki:<i>Skin Name</i>.css</p><br /> <br /> <h3>Finding MediaWiki Default Styles</h3><br /> <p>One location with many style sheets in .less format is the directory /w/resources/src/mediawiki.skinning </p><br /> <p>Some of the interesting files are:-</p><br /> <div style="margin-left:2em;"><br /> <h5>/w/resources/src/mediawiki.skinning</h5><br /> <p><ul><br /> <li>content.body.less - defines mw-body-content</li><br /> <li>content.tables.less - defines a usable class .wikitable </li><br /> <li>content.elements.less - defines styles for elements including headings, links, paragraphs, lists</li><br /> <li>i18n-all-lists-margins.less - default margins for list types ul, ol and dd</li><br /> <li>interface-site-notice.less - position and alignment of #sitenotice </li><br /> <li>interface-subtitle.less </li><br /> <li>interface.category.less </li><br /> </ul></p><br /> <br /> <h5>/w/resources/src/mediawiki.less </h5><br /> <p><ul><br /> <li>mediawiki.skin.defaults - defines a lot of default colors</li><br /> </ul></p><br /> <br /> <h5>/w/resources/src/mediawiki.page.gallery</h5><br /> <p><ul><br /> <li>gallery.less - defines styles used for image galleries. See <html><a href="https://www.mediawiki.org/wiki/Help:Images" target="_blank">Help:Images</a></html> </li><br /> </ul></p><br /> <br /><br /> <br /> <br /> <p>See Also: [[Vector Skin Styles]]</p><br /> <br /> [[Category:CSS]]<br /> [[Category:Interface]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Apply_a_Custom_Colour_Scheme&diff=2416 Apply a Custom Colour Scheme 2025-12-24T03:43:39Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Customising the Interface of a MediaWiki-based Website</h3><br /> <p>The appearance of a MediaWiki-based website is controlled by CSS Classes used by MediaWiki and by the installed Skin.</p><br /> <p>Altering the appearance, or customising the Interface, involves editing MediaWiki:Common.css and the skin CSS which is also in the MediaWiki: namespace.</p><br /> <p>Processes involved in customising the interface are covered in separate articles:-</p><br /> {{Customise Interface List}}<br /> <br /><br /> <br /> <h3>How to Apply a Custom Colour Scheme</h3><br /> <p>The steps covered so far include:- </p><br /> <ol><br /> <li>[[Identify Interface Classes|Identify the CSS Classes]] for screen elements; standard MediaWiki Classes and skin Classes</li><br /> <li>[[Choosing a Colour Scheme|Design a colour scheme]]; choose the colour palette, [[Colors as Variables|create colour variables]]</li><br /> </ol><br /> <p>Custom CSS is applied to MediaWiki:Common.css and to the skin CSS, for example MediaWiki:Vector.css used here.</p><br /> <br /> <br /> <p>The table below shows the colours used on this website. This can be verified by matching a colour to part of the interface.</p><br /> <br /> {{Snippets:Colour Theme table}}<br /> <br /> <h3>Colours in Common.css</h3><br /> <p>The following CSS has been added to Common.css for this website:-</p><br /> <pre><br /> /* Items sorted with lightest color shade first, approximating a Z order */<br /> <br /> #mw-head { background-color: var(--SteelBlue-80); } /* full width at top of screen, behind logo */<br /> <br /> /* mw-body-content is in front of mw-body */<br /> .mw-body-content { background-color: var(--PageBackground); border-radius: 1em; padding-top:2em; padding-bottom:2em; padding-left:2.5em; padding-right:2.5em; } <br /> <br /> .mw-body { background-color: var(--SteelBlue-70); } /* is background for everything below header and right of left panel and down to footer */<br /> <br /> .mw-footer { background-color: var(--SteelBlue-60); } /* does not extend to bottom of the screen */<br /> <br /> #mw-panel.vector-legacy-sidebar.collapsible-nav { background-color: var(--SteelBlue-50); } /* background for menu but extends to top of screen and behind logo and in front of header */<br /> <br /> body { background-color: var(--SteelBlue-40); } /* everything below mw-head, full width of screen, to bottom of screen */<br /> <br /> .catlinks { background-color: var(--LightSteelBlue); } /* border on category row */<br /> .mw-normal-catlinks { background-color: var(--LightSteelBlue-90); padding-left:20px; } <br /> </pre><br /> <br /> <h3>Colours in Vector.css</h3><br /> <p>The following CSS has been added to Vector.css for this website:-</p><br /> <pre><br /> /* Items arranged with lightest color shades first, also approximating a Z order */<br /> <br /> #mw-panel.collapsible-nav .vector-menu-content { background-color: var(--Tan-80); } /* background color on drop down sub menu */<br /> <br /> .vector-menu-heading-label { background-color: var(--Tan-70); } /* this is the background for the text only, not full width */<br /> <br /> /* menu headings - define for expanded and collapsed - container for the label text, full width of sidebar */<br /> #mw-panel.collapsible-nav .portal.collapsed .vector-menu-heading { background-color: var(--Tan-60); } <br /> #mw-panel.collapsible-nav .portal.expanded .vector-menu-heading { background-color: var(--Tan-60); }<br /> <br /> .vector-menu-portal { background-color: var(--Tan-50); } /* background for the menu */<br /> <br /> #p-tb { background-color: var(--Tan-40); } /* Tools Menu */<br /> </pre><br /> <br /> <h3>Related Articles</h3><br /> {{DisplayCategoryTree<br /> |Topic=Customising the Interface<br /> |CatName=Customise the Interface<br /> |CatTree=<categorytree mode="pages">Customise the Interface </categorytree><br /> }}<br /> <br /> <br /> [[Category:Interface]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Identify_Interface_Classes&diff=2415 Identify Interface Classes 2025-12-24T03:43:27Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <h3>Customising the Interface of a MediaWiki-based Website</h3><br /> <p>The appearance of a MediaWiki-based website is controlled by CSS Classes used by MediaWiki and by the installed Skin.</p><br /> <p>Altering the appearance, or customising the Interface, involves editing MediaWiki:Common.css and the skin CSS which is also in the MediaWiki: namespace.</p><br /> <p>Processes involved in customising the interface are covered in separate articles:-</p><br /> {{Customise Interface List}}<br /> <br /><br /> <br /> <br /> <h3>Identify CSS Classes</h3><br /> <p>To customise the appearance of a MediaWiki-based website it will be necessary to identify the CSS classes defined by MediaWiki and the current Skin. This website uses the Vector skin and also the Extension:CollapsibleVector which enables drop-down menus in the Sidebar.</p><br /> <p>Firefox Developer Edition is used here to display the page source for the Main page on this website, with many of the sections expanded to reveal the CSS classes.</p><br /> [[File:WebDeveloperClasses1.jpg|alt=Interface classes in Firefox Web Developer Tools|Interface classes in Firefox Web Developer Tools]]<br /> <p>The next image expands the navigation parts at the page header.</p><br /> [[File:WebDeveloperClasses2.jpg|alt=Interface classes in Web Developer Tools|Interface classes in Web Developer Tools]]<br /> <p>The next image expands the panel containing the Sidebar and the first menu item(s).</p><br /> [[File:WebDeveloperClasses3.jpg|alt=Interface classes in Web Developer Tools|Interface classes in Web Developer Tools]]<br /> <p>This final image captures the Tools menu and the Footer.</p><br /> [[File:WebDeveloperClasses4.jpg|alt=Interface classes in Web Developer Tools|Interface classes in Web Developer Tools]]<br /> <br /><br /> <br /> <h3>Two Sources of CSS Classes</h3><br /> <p>MediaWiki developers follow naming conventions which enable us to identify the source of each CSS class:-</p><br /> <ol><br /> <li>MediaWiki code prefixes each class with <i>mw-</i>, for example mw-panel or mw-list-item</li><br /> <li>Styles used by the skin, in this case Vector, are prefixed <i>vector-</i>, for example vector-menu-content-list</li><br /> <li>Styles used by the Extension:CollapsibleVector are less obvious. This extension enables a drop-down menu which must have two states - expanded or collapsed. Wherever those terms are used in conjunction with other Vector classes it can be assumed that CollapsibleVector is the source.</li><br /> </ol><br /> <p>Notice that a menu (below a heading) is an unordered list and although the container is vector-menu-content-list the actual list items use the MediaWiki class mw-list-item.</p><br /> <br /> <h3>A List of Classes</h3><br /> <p>The following list is likely not complete, and although each MediaWiki-based website will have all or most of these same classes there will be differences depending on the MediaWiki version, the Skin and the skin version, and any Extensions which affect the interface</p><br /> <br /> <pre><br /> .mw-body<br /> .mw-head<br /> .mw-portlet<br /> .mw-first-heading<br /> .mw-body-content<br /> .mw-page-title-main<br /> .mw-panel<br /> .mw-navigation<br /> .mw-list-item<br /> .mw-normal-catlinks<br /> .mw-footer<br /> <br /> .vector-body<br /> .vector-menu-heading <br /> .vector-menu-heading-label<br /> .vector-menu-content<br /> .vector-menu-content-list<br /> .vector-search-box<br /> .vector-search-box-form<br /> </pre><br /> <br /> <h3>Where are Default Classes Defined?</h3><br /> <p>The article [[Searching for Default Settings]] describes a method to find where CSS Classes used by MediaWiki and the installed Skin are defined.</p><br /> <br /><br /> <br /> <h3>Customising a Style</h3><br /> <p>Each of the MediaWiki classes prefixed mw- could be customised with CSS in MediaWiki:Common.css. The changes would apply to all skins.</p><br /> <p>Each of the classes related to Vector and the Extension:CollapsibleVector could be customised with CSS in MediaWiki:Vector.css</p><br /> <p>If Vector is the only Skin available to all users, for convenience all custom styles applied to the interface could be added to MediaWiki:Vector.css. That is what I did for the {{MH370Site}} website, because I already have a lot of CSS in MediaWiki:Common.css.</p></p><br /> <br /> <br /> <br /> [[Category:Interface]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Interface_Administrator_Role&diff=2414 Interface Administrator Role 2025-12-24T03:43:08Z

<p>GrantM: </p> <hr /> <div>{{PageHeader}}<br /> <br /> <div class="quote"><br /> <p>Interface administrators can edit CSS/JS pages that they do not own (that is, any page ending with .css or .js that is either in the MediaWiki: namespace or is another user's user subpage). In particular, they have the ability to edit sitewide CSS/JS pages (pages such as MediaWiki:Common.js or MediaWiki:Vector.css, or the gadget pages listed on Special:Gadgets). These pages are executed by the browser of wiki editors and readers as code, which can be used to change how content is styled, change the behavior of pages, or even create highly complex tools. In addition, they can also edit all other pages in the MediaWiki namespace.</p><br /> <p>The interface-admin group was introduced into MediaWiki in version MediaWiki 1.32.</p><br /> <br /> <p style="text-align:center"><b>Source</b>: Project:Interface administrators <html><a href="https://www.mediawiki.org/wiki/Project:Interface_administrators" Target="_blank">https://www.mediawiki.org/wiki/Project:Interface_administrators</a></html><br /><b>See Also</b>: <html><a href="https://www.mediawiki.org/wiki/Special:ListGroupRights#interface-admin" target="_blank"> Rights attached to Interface Administrators</a></html> </p><br /> </div> <br /> <br /> <br /> <h3>Resources for MediaWiki Interface Administrators</h3><br /> <dl><br /> <dt>Manual:CSS</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:CSS" target="_blank">https://www.mediawiki.org/wiki/Manual:CSS</a></html></dd><br /> <br /> <dt>Manual:Interface</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Interface" target="_blank">https://www.mediawiki.org/wiki/Manual:Interface</a></html></dd><br /> <br /> <dt>Manual:Interface/Stylesheets</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Interface/Stylesheets" target="_blank">https://www.mediawiki.org/wiki/Manual:Interface/Stylesheets</a></html></dd><br /> <br /> <dt>Manual:Interface/JavaScript</dt><br /> <dd><html><a href="https://www.mediawiki.org/wiki/Manual:Interface/JavaScript" target="_blank">https://www.mediawiki.org/wiki/Manual:Interface/JavaScript</a></html></dd><br /> </dl><br /> <br /><br /> <br /> {{DisplayCategoryTree<br /> |Topic=role of MediaWiki Interface Administrator<br /> |CatName=Interface Administrator<br /> |CatTree=<categorytree mode="pages">Interface Administrator</categorytree><br /> }}<br /> <br /> <br /> [[Category:Interface Administrator]]<br /> [[Category:Interface]]</div>

GrantM https://mw.mh370.wiki/w/index.php?title=Category:Interface&diff=2413 Category:Interface 2025-12-24T03:41:57Z

<p>GrantM: Created page with "{{CategoryPage |ParentCategory=Customise |CategoryDescription=The visual interface to a MediaWiki-based website. Each 'skin' provides a basic 'theme' which can be further customised. }}"</p> <hr /> <div>{{CategoryPage<br /> |ParentCategory=Customise<br /> |CategoryDescription=The visual interface to a MediaWiki-based website. Each 'skin' provides a basic 'theme' which can be further customised.<br /> }}</div>

GrantM