https://mw.eckford.ca:443/api.php?action=feedcontributions&feedformat=atom&user=TuxMediaWiki-1.39 - User contributions [en]2026-07-17T12:59:53ZUser contributionsMediaWiki 1.39.17https://mw.eckford.ca:443/index.php?title=Rs2&diff=199Rs22026-04-10T01:31:46Z<p>Tux: </p>
<hr />
<div><br />
[[File:pallette.jpg|thumb|right|150px|colour pallette]]<br />
<br />
<pre><br />
<br />
Did you know: <br />
<br />
That Ye Olde Box(es) are machines that should be treated tenderly<br />
That Sh1re is hearth of security<br />
<br />
</pre><br />
<br />
<br />
An online source of RADARSAT-2 operations data and documentation since launch.<br />
<br />
<h2>Navigation Methods</h2><br />
{{Enhanced|From a desktop machine:}}<br />
<ul><br />
<li>[https://sh1rs2wikidu01.mda.ca/Main_Page <strong>R2 Wiki</strong>] </li><br />
<li>[https://transferdepot.sh1rs2wikidu01.mda.ca <strong>TransferDepot </strong>] </li><br />
<li>[https://sh1rs2wikidu01.mda.ca/Special:ApprovedManuals <strong>Operational Manual Procedures</strong>]</li></ul><br />
<br />
{{Safe|From the Control Room and legacy machines:}}<br />
<ul><br />
<li>[http://142.73.160.81/index.php/Main_Page?useskin=monobook <strong>R2 Wiki</strong> ] </li><br />
<li>[http://142.73.160.62/ <strong>TransferDepot</strong>] </li><br />
<li>[http://142.73.160.81/Special:ApprovedManuals?useskin=monobook <strong>Operational Manual Procedures</strong>] </strong> </li></ul><br />
<br />
== System Configuration ==<br />
<br />
'''MDA R2-Wiki New stuff/should read:'''<BR><br />
[[Cortex|Cortex Explained:]] Mission Control & High level description<BR><br />
-----<br />
[[MissionPriorities| Mission Priorities:]] Top Mission Priorities from SAF, Bugs and projects <BR><br />
[[Current Spacecraft Configuration| Current Spacecraft Configuration:]] Overview of current Spacecraft configuration, subsystem status and performance <BR><br />
[[System_Configuration|Ground System Configuration:]] Ground Segment SW<BR></div>Tuxhttps://mw.eckford.ca:443/index.php?title=MediaWiki:Sidebar&diff=197MediaWiki:Sidebar2026-03-16T14:11:44Z<p>Tux: </p>
<hr />
<div><br />
* navigation<br />
** mainpage|mainpage-description<br />
** Rs2|rs2 prod<br />
** Definitions|Definitions<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help-mediawiki<br />
** MediaWiki_Tips|MW for the Sh1re<br />
** Special:ListFiles|Uploaded Files<br />
** Special:Upload|Upload Files<br />
** MediaWiki:Sidebar|MediaWiki Sidebar<br />
** Special:AllPages/Template:|Templates<br />
** purge-main|page purges<br />
<br />
deployment<br />
* Special:Upload|Upload Package<br />
* Special:ListFiles|Deployment Files<br />
<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES<br />
<br />
<h3> Now you can</h3> <br />
<p>This one was different</p><br />
<pre>** MediaWiki:Sidebar|MediaWiki Sidebar</p><br />
<p><br />
Link to other MediaWiki: pages (like MediaWiki:Common.css, MediaWiki:Mainpage-description), just remember to include the full namespace like MediaWiki:Mainpage-description </p></div>Tuxhttps://mw.eckford.ca:443/index.php?title=MediaWiki:Sidebar&diff=196MediaWiki:Sidebar2026-03-16T14:10:41Z<p>Tux: </p>
<hr />
<div><br />
* navigation<br />
** mainpage|mainpage-description<br />
** Rs2|rs2<br />
** Definitions|Definitions<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help-mediawiki<br />
** MediaWiki_Tips|MW for the Sh1re<br />
** Special:ListFiles|Uploaded Files<br />
** Special:Upload|Upload Files<br />
** MediaWiki:Sidebar|MediaWiki Sidebar<br />
** Special:AllPages/Template:|Templates<br />
** purge-main|page purges<br />
<br />
deployment<br />
* Special:Upload|Upload Package<br />
* Special:ListFiles|Deployment Files<br />
<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES<br />
<br />
<h3> Now you can</h3> <br />
<p>This one was different</p><br />
<pre>** MediaWiki:Sidebar|MediaWiki Sidebar</p><br />
<p><br />
Link to other MediaWiki: pages (like MediaWiki:Common.css, MediaWiki:Mainpage-description), just remember to include the full namespace like MediaWiki:Mainpage-description </p></div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=195Main Page2026-03-16T13:59:41Z<p>Tux: </p>
<hr />
<div><br />
{{Info|Updated March 16, 2026.}}<br />
<br />
= ROUTINE troubleshooting notes =<br />
<br />
These notes are for checking or changing the active ROUTINE in the Manual Procedures workflow.<br />
<br />
== Normal workflow ==<br />
<br />
# Log in.<br />
# Open '''Approved manuals'''.<br />
# Note the ROUTINE shown at the top of the page.<br />
# Open '''ROUTINE tags'''.<br />
<br />
=== To activate or roll back to an existing ROUTINE ===<br />
<br />
Use the '''top ROUTINE field'''.<br />
<br />
Enter the exact existing ROUTINE value you want to use, for example:<br />
<br />
<code>ROUTINE_4.110</code><br />
<br />
Then click '''Activate tag'''.<br />
<br />
This can be used to:<br />
<br />
* activate the current working ROUTINE<br />
* return to a previous ROUTINE<br />
* confirm that an existing ROUTINE bundle still works<br />
<br />
'''Do not''' use '''Clone ROUTINE release''' for rollback.<br />
<br />
=== To create the next ROUTINE ===<br />
<br />
First make sure the current ROUTINE is correct in the '''top ROUTINE field'''. <br />
If needed, enter the current ROUTINE there and click '''Activate tag''' first.<br />
<br />
Then use '''Clone ROUTINE release'''.<br />
<br />
Enter:<br />
<br />
* '''Source ROUTINE''': the current active release, for example <code>ROUTINE_4.110</code><br />
* '''New ROUTINE''': the new release, for example <code>ROUTINE_4.111</code><br />
<br />
Then submit the form.<br />
<br />
This should:<br />
<br />
* create the new ROUTINE tag<br />
* copy the current bundle into the new ROUTINE<br />
* activate the new ROUTINE automatically<br />
<br />
== What to check immediately after ==<br />
<br />
After activating or cloning:<br />
<br />
# Stay on the page and note the message shown at the top.<br />
# Open '''Approved manuals''' again.<br />
# Confirm whether the ROUTINE heading changed.<br />
# Confirm whether the manual list changed as expected.<br />
<br />
== Important ==<br />
<br />
* '''Activate tag''' uses an existing ROUTINE.<br />
* '''Clone ROUTINE release''' creates a new ROUTINE from an existing one.<br />
* '''Rollback''' means activating an existing ROUTINE in the top field.<br />
* Enter the ROUTINE exactly as written, for example <code>ROUTINE_4.110</code>.<br />
* Changing approved document revisions does '''not''' by itself create a new ROUTINE label.<br />
* A new ROUTINE appears only after it is cloned or otherwise created in the ROUTINE tables.<br />
<br />
= Emergency fallback test in LocalSettings.php =<br />
<br />
Use this only if the normal ROUTINE activation path is not working and you need to test whether the wiki is falling back to configuration.<br />
<br />
== Method 1: Change the fallback ROUTINE in <code>LocalSettings.php</code> ==<br />
<br />
Edit this line in <code>LocalSettings.php</code>:<br />
<br />
<syntaxhighlight lang="php"><br />
$wgCustomQueryPageDefaultTag = 'ROUTINE_4.111';<br />
</syntaxhighlight><br />
<br />
Then:<br />
<br />
# Save the file.<br />
# Reload [[Special:RoutineTags]].<br />
# Reload [[Special:ApprovedManuals]].<br />
<br />
If nothing changes:<br />
<br />
# Do a hard refresh in the browser.<br />
# If it is still unchanged, ask the sysadmin to restart PHP or the container.<br />
# Reload both special pages again.<br />
<br />
Expected result:<br />
<br />
* If the page starts showing <code>ROUTINE_4.111</code>, the extension is reading the fallback value from configuration.<br />
* If it still shows <code>ROUTINE_4.110</code>, this change did not affect the current read path.<br />
<br />
== Method 2: Quick page check ==<br />
<br />
After Method 1, check both pages, not just one:<br />
<br />
* [[Special:RoutineTags]]<br />
* [[Special:ApprovedManuals]]<br />
<br />
Things to confirm:<br />
<br />
* Does [[Special:RoutineTags]] show <code>ROUTINE_4.111</code> as the visible current or default tag?<br />
* Does the heading on [[Special:ApprovedManuals]] change to the new ROUTINE?<br />
* Does the document list appear to match the intended release?<br />
<br />
== Method 3: See documentation ==<br />
<br />
Use the ROUTINE workflow and recovery notes for deeper troubleshooting.<br />
<br />
Known points:<br />
<br />
* ROUTINE labels are stored in <code>mw_tags</code>.<br />
* ROUTINE membership is stored in <code>mw_tag_pages</code>.<br />
* The current approved set is stored in <code>mw_approved_revs</code>.<br />
* The active selected ROUTINE is stored in <code>mw_customquerypage_settings</code>.<br />
* Activating a ROUTINE rebuilds <code>mw_approved_revs</code>.<br />
* Rollback is done by reactivating the previous ROUTINE.<br />
<br />
If the manual <code>LocalSettings.php</code> edit and page refresh do not restore expected behaviour, continue with the documented extension workflow and technical recovery notes.<br />
<br />
---<br />
= DEBUG STEPS = <br />
<br />
== In a nutshell == <br />
<br />
* What ROUTINE is showing on Approved manuals?<br />
<br />
* What ROUTINE tag displays on the ROUTINE tags page?<br />
<br />
* What exact message appeared after clicking the button?<br />
<br />
== Tech Fixes ==<br />
<br />
Please let me know if this is fixed or if you need another step. Based on what's happening, I can probably help :)<br />
<br />
-----------------------------------------------------------<br />
<br />
{{Info| Released Vesion 1.0 is available as Latest Version released Feb 26, 2026}}<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
'''Data model summary:''' <code>page_latest</code> tracks the most recent edit, <code>mw_approved_revs</code> identifies the revision currently approved for display, and each ROUTINE snapshot in <code>mw_tag_pages</code> records which revision belongs to that release.<br />
<br />
---------------------------------------------------------<br />
<br />
The following information can be used as an installation guide. Only download files tagged latest<br />
<br />
'''''<br />
<br />
= OBSOLETE Pre-release =<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
See procedure for rollback to reset to a previous version. Set tag ONLY. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
<br />
<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Note: Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> does not exist yet, or if you are intentionally applying the CustomQueryPage schema changes in a controlled maintenance window.}}<br />
<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=194Main Page2026-03-16T13:51:15Z<p>Tux: </p>
<hr />
<div><br />
{{Info|Updated March 16, 2026.}}<br />
<br />
= ROUTINE troubleshooting notes =<br />
<br />
These notes are for checking or changing the active ROUTINE in the Manual Procedures workflow.<br />
<br />
== Normal workflow ==<br />
<br />
# Log in.<br />
# Open '''Approved manuals'''.<br />
# Note the ROUTINE shown at the top of the page.<br />
# Open '''ROUTINE tags'''.<br />
<br />
=== To activate or roll back to an existing ROUTINE ===<br />
<br />
Use the '''top ROUTINE field'''.<br />
<br />
Enter the exact existing ROUTINE value you want to use, for example:<br />
<br />
<code>ROUTINE_4.110</code><br />
<br />
Then click '''Activate tag'''.<br />
<br />
This can be used to:<br />
<br />
* activate the current working ROUTINE<br />
* return to a previous ROUTINE<br />
* confirm that an existing ROUTINE bundle still works<br />
<br />
'''Do not''' use '''Clone ROUTINE release''' for rollback.<br />
<br />
=== To create the next ROUTINE ===<br />
<br />
First make sure the current ROUTINE is correct in the '''top ROUTINE field'''. <br />
If needed, enter the current ROUTINE there and click '''Activate tag''' first.<br />
<br />
Then use '''Clone ROUTINE release'''.<br />
<br />
Enter:<br />
<br />
* '''Source ROUTINE''': the current active release, for example <code>ROUTINE_4.110</code><br />
* '''New ROUTINE''': the new release, for example <code>ROUTINE_4.111</code><br />
<br />
Then submit the form.<br />
<br />
This should:<br />
<br />
* create the new ROUTINE tag<br />
* copy the current bundle into the new ROUTINE<br />
* activate the new ROUTINE automatically<br />
<br />
== What to check immediately after ==<br />
<br />
After activating or cloning:<br />
<br />
# Stay on the page and note the message shown at the top.<br />
# Open '''Approved manuals''' again.<br />
# Confirm whether the ROUTINE heading changed.<br />
# Confirm whether the manual list changed as expected.<br />
<br />
== Important ==<br />
<br />
* '''Activate tag''' uses an existing ROUTINE.<br />
* '''Clone ROUTINE release''' creates a new ROUTINE from an existing one.<br />
* '''Rollback''' means activating an existing ROUTINE in the top field.<br />
* Enter the ROUTINE exactly as written, for example <code>ROUTINE_4.110</code>.<br />
* Changing approved document revisions does '''not''' by itself create a new ROUTINE label.<br />
* A new ROUTINE appears only after it is cloned or otherwise created in the ROUTINE tables.<br />
<br />
= Emergency fallback test in LocalSettings.php =<br />
<br />
Use this only if the normal ROUTINE activation path is not working and you need to test whether the wiki is falling back to configuration.<br />
<br />
== Method 1: Change the fallback ROUTINE in <code>LocalSettings.php</code> ==<br />
<br />
Edit this line in <code>LocalSettings.php</code>:<br />
<br />
<syntaxhighlight lang="php"><br />
$wgCustomQueryPageDefaultTag = 'ROUTINE_4.111';<br />
</syntaxhighlight><br />
<br />
Then:<br />
<br />
# Save the file.<br />
# Reload [[Special:RoutineTags]].<br />
# Reload [[Special:ApprovedManuals]].<br />
<br />
If nothing changes:<br />
<br />
# Do a hard refresh in the browser.<br />
# If it is still unchanged, ask the sysadmin to restart PHP or the container.<br />
# Reload both special pages again.<br />
<br />
Expected result:<br />
<br />
* If the page starts showing <code>ROUTINE_4.111</code>, the extension is reading the fallback value from configuration.<br />
* If it still shows <code>ROUTINE_4.110</code>, this change did not affect the current read path.<br />
<br />
== Method 2: Quick page check ==<br />
<br />
After Method 1, check both pages, not just one:<br />
<br />
* [[Special:RoutineTags]]<br />
* [[Special:ApprovedManuals]]<br />
<br />
Things to confirm:<br />
<br />
* Does [[Special:RoutineTags]] show <code>ROUTINE_4.111</code> as the visible current or default tag?<br />
* Does the heading on [[Special:ApprovedManuals]] change to the new ROUTINE?<br />
* Does the document list appear to match the intended release?<br />
<br />
== Method 3: See documentation ==<br />
<br />
Use the ROUTINE workflow and recovery notes for deeper troubleshooting.<br />
<br />
Known points:<br />
<br />
* ROUTINE labels are stored in <code>mw_tags</code>.<br />
* ROUTINE membership is stored in <code>mw_tag_pages</code>.<br />
* The current approved set is stored in <code>mw_approved_revs</code>.<br />
* The active selected ROUTINE is stored in <code>mw_customquerypage_settings</code>.<br />
* Activating a ROUTINE rebuilds <code>mw_approved_revs</code>.<br />
* Rollback is done by reactivating the previous ROUTINE.<br />
<br />
If the manual <code>LocalSettings.php</code> edit and page refresh do not restore expected behaviour, continue with the documented extension workflow and technical recovery notes.<br />
<br />
---<br />
<br />
Hi Lisa, If this doesn<br />
<br />
<br />
-----------------------------------------------------------<br />
<br />
{{Info| Released Vesion 1.0 is available as Latest Version released Feb 26, 2026}}<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
'''Data model summary:''' <code>page_latest</code> tracks the most recent edit, <code>mw_approved_revs</code> identifies the revision currently approved for display, and each ROUTINE snapshot in <code>mw_tag_pages</code> records which revision belongs to that release.<br />
<br />
---------------------------------------------------------<br />
<br />
The following information can be used as an installation guide. Only download files tagged latest<br />
<br />
'''''<br />
<br />
= OBSOLETE Pre-release =<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
See procedure for rollback to reset to a previous version. Set tag ONLY. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
<br />
<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Note: Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> does not exist yet, or if you are intentionally applying the CustomQueryPage schema changes in a controlled maintenance window.}}<br />
<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=193Main Page2026-03-16T13:44:37Z<p>Tux: </p>
<hr />
<div><br />
{{Info|Updated March 16, 2026.}}<br />
<br />
= ROUTINE troubleshooting notes =<br />
<br />
These notes are for checking or changing the active ROUTINE in the Manual Procedures workflow.<br />
<br />
== Normal workflow ==<br />
<br />
# Log in.<br />
# Open '''Approved manuals'''.<br />
# Note the ROUTINE shown at the top of the page.<br />
# Open '''ROUTINE tags'''.<br />
<br />
=== To roll back to an existing ROUTINE ===<br />
<br />
Use the '''top ROUTINE field'''.<br />
<br />
Enter the exact existing ROUTINE value you want to return to, for example:<br />
<br />
<code>ROUTINE_4.110</code><br />
<br />
Then save or activate it.<br />
<br />
'''Do not''' use '''Clone ROUTINE release''' for rollback.<br />
<br />
=== To create the next ROUTINE ===<br />
<br />
Use '''Clone ROUTINE release'''.<br />
<br />
Enter:<br />
<br />
* '''Source ROUTINE''': the current release, for example <code>ROUTINE_4.110</code><br />
* '''New ROUTINE''': the new release, for example <code>ROUTINE_4.111</code><br />
<br />
Then submit the form.<br />
<br />
== What to check immediately after ==<br />
<br />
After saving or cloning:<br />
<br />
# Stay on the page and note the message shown at the top.<br />
# Open '''Approved manuals''' again.<br />
# Confirm whether the ROUTINE heading changed.<br />
# Confirm whether the manual list changed as expected.<br />
<br />
== Important ==<br />
<br />
* '''Rollback''' means activating an existing ROUTINE in the top field.<br />
* '''Clone''' means creating a new ROUTINE in the lower form.<br />
* Enter the ROUTINE exactly as written, for example <code>ROUTINE_4.110</code>.<br />
* Changing approved document revisions does '''not''' by itself create a new ROUTINE label.<br />
* A new ROUTINE appears only after it is cloned or otherwise created in the ROUTINE tables.<br />
<br />
= Emergency fallback test in LocalSettings.php =<br />
<br />
Use this only if the normal ROUTINE activation path is not working and you need to test whether the wiki is falling back to configuration.<br />
<br />
== Method 1: Change the fallback ROUTINE in <code>LocalSettings.php</code> ==<br />
<br />
Edit this line in <code>LocalSettings.php</code>:<br />
<br />
<syntaxhighlight lang="php"><br />
$wgCustomQueryPageDefaultTag = 'ROUTINE_4.111';<br />
</syntaxhighlight><br />
<br />
Then:<br />
<br />
# Save the file.<br />
# Reload [[Special:RoutineTags]].<br />
# Reload [[Special:ApprovedManuals]].<br />
<br />
If nothing changes:<br />
<br />
# Do a hard refresh in the browser.<br />
# If it is still unchanged, ask the sysadmin to restart PHP or the container.<br />
# Reload both special pages again.<br />
<br />
Expected result:<br />
<br />
* If the page starts showing <code>ROUTINE_4.111</code>, the extension is reading the fallback value from configuration.<br />
* If it still shows <code>ROUTINE_4.110</code>, this change did not affect the current read path.<br />
<br />
== Method 2: Quick page check ==<br />
<br />
After Method 1, check both pages, not just one:<br />
<br />
* [[Special:RoutineTags]]<br />
* [[Special:ApprovedManuals]]<br />
<br />
Things to confirm:<br />
<br />
* Does [[Special:RoutineTags]] show <code>ROUTINE_4.111</code> as the visible current or default tag?<br />
* Does the heading on [[Special:ApprovedManuals]] change to the new ROUTINE?<br />
* Does the document list appear to match the intended release?<br />
<br />
== Method 3: See documentation ==<br />
<br />
Use the ROUTINE workflow and recovery notes for deeper troubleshooting.<br />
<br />
Known points:<br />
<br />
* ROUTINE labels are stored in <code>mw_tags</code>.<br />
* ROUTINE membership is stored in <code>mw_tag_pages</code>.<br />
* The current approved set is stored in <code>mw_approved_revs</code>.<br />
* The active selected ROUTINE is stored in <code>mw_customquerypage_settings</code>.<br />
* Activating a ROUTINE rebuilds <code>mw_approved_revs</code>.<br />
* Rollback is done by reactivating the previous ROUTINE.<br />
<br />
If the manual <code>LocalSettings.php</code> edit and page refresh do not restore expected behaviour, continue with the documented extension workflow and technical recovery notes.<br />
<br />
<br />
-----------------------------------------------------------<br />
<br />
{{Info| Released Vesion 1.0 is available as Latest Version released Feb 26, 2026}}<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
'''Data model summary:''' <code>page_latest</code> tracks the most recent edit, <code>mw_approved_revs</code> identifies the revision currently approved for display, and each ROUTINE snapshot in <code>mw_tag_pages</code> records which revision belongs to that release.<br />
<br />
---------------------------------------------------------<br />
<br />
The following information can be used as an installation guide. Only download files tagged latest<br />
<br />
'''''<br />
<br />
= OBSOLETE Pre-release =<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
See procedure for rollback to reset to a previous version. Set tag ONLY. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
<br />
<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Note: Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> does not exist yet, or if you are intentionally applying the CustomQueryPage schema changes in a controlled maintenance window.}}<br />
<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=192Main Page2026-03-16T13:44:13Z<p>Tux: Add debug steps to Operational Procedures</p>
<hr />
<div>```mediawiki<br />
{{Info|Updated March 16, 2026.}}<br />
<br />
= ROUTINE troubleshooting notes =<br />
<br />
These notes are for checking or changing the active ROUTINE in the Manual Procedures workflow.<br />
<br />
== Normal workflow ==<br />
<br />
# Log in.<br />
# Open '''Approved manuals'''.<br />
# Note the ROUTINE shown at the top of the page.<br />
# Open '''ROUTINE tags'''.<br />
<br />
=== To roll back to an existing ROUTINE ===<br />
<br />
Use the '''top ROUTINE field'''.<br />
<br />
Enter the exact existing ROUTINE value you want to return to, for example:<br />
<br />
<code>ROUTINE_4.110</code><br />
<br />
Then save or activate it.<br />
<br />
'''Do not''' use '''Clone ROUTINE release''' for rollback.<br />
<br />
=== To create the next ROUTINE ===<br />
<br />
Use '''Clone ROUTINE release'''.<br />
<br />
Enter:<br />
<br />
* '''Source ROUTINE''': the current release, for example <code>ROUTINE_4.110</code><br />
* '''New ROUTINE''': the new release, for example <code>ROUTINE_4.111</code><br />
<br />
Then submit the form.<br />
<br />
== What to check immediately after ==<br />
<br />
After saving or cloning:<br />
<br />
# Stay on the page and note the message shown at the top.<br />
# Open '''Approved manuals''' again.<br />
# Confirm whether the ROUTINE heading changed.<br />
# Confirm whether the manual list changed as expected.<br />
<br />
== Important ==<br />
<br />
* '''Rollback''' means activating an existing ROUTINE in the top field.<br />
* '''Clone''' means creating a new ROUTINE in the lower form.<br />
* Enter the ROUTINE exactly as written, for example <code>ROUTINE_4.110</code>.<br />
* Changing approved document revisions does '''not''' by itself create a new ROUTINE label.<br />
* A new ROUTINE appears only after it is cloned or otherwise created in the ROUTINE tables.<br />
<br />
= Emergency fallback test in LocalSettings.php =<br />
<br />
Use this only if the normal ROUTINE activation path is not working and you need to test whether the wiki is falling back to configuration.<br />
<br />
== Method 1: Change the fallback ROUTINE in <code>LocalSettings.php</code> ==<br />
<br />
Edit this line in <code>LocalSettings.php</code>:<br />
<br />
<syntaxhighlight lang="php"><br />
$wgCustomQueryPageDefaultTag = 'ROUTINE_4.111';<br />
</syntaxhighlight><br />
<br />
Then:<br />
<br />
# Save the file.<br />
# Reload [[Special:RoutineTags]].<br />
# Reload [[Special:ApprovedManuals]].<br />
<br />
If nothing changes:<br />
<br />
# Do a hard refresh in the browser.<br />
# If it is still unchanged, ask the sysadmin to restart PHP or the container.<br />
# Reload both special pages again.<br />
<br />
Expected result:<br />
<br />
* If the page starts showing <code>ROUTINE_4.111</code>, the extension is reading the fallback value from configuration.<br />
* If it still shows <code>ROUTINE_4.110</code>, this change did not affect the current read path.<br />
<br />
== Method 2: Quick page check ==<br />
<br />
After Method 1, check both pages, not just one:<br />
<br />
* [[Special:RoutineTags]]<br />
* [[Special:ApprovedManuals]]<br />
<br />
Things to confirm:<br />
<br />
* Does [[Special:RoutineTags]] show <code>ROUTINE_4.111</code> as the visible current or default tag?<br />
* Does the heading on [[Special:ApprovedManuals]] change to the new ROUTINE?<br />
* Does the document list appear to match the intended release?<br />
<br />
== Method 3: See documentation ==<br />
<br />
Use the ROUTINE workflow and recovery notes for deeper troubleshooting.<br />
<br />
Known points:<br />
<br />
* ROUTINE labels are stored in <code>mw_tags</code>.<br />
* ROUTINE membership is stored in <code>mw_tag_pages</code>.<br />
* The current approved set is stored in <code>mw_approved_revs</code>.<br />
* The active selected ROUTINE is stored in <code>mw_customquerypage_settings</code>.<br />
* Activating a ROUTINE rebuilds <code>mw_approved_revs</code>.<br />
* Rollback is done by reactivating the previous ROUTINE.<br />
<br />
If the manual <code>LocalSettings.php</code> edit and page refresh do not restore expected behaviour, continue with the documented extension workflow and technical recovery notes.<br />
```<br />
<br />
<br />
<br />
-----------------------------------------------------------<br />
<br />
{{Info| Released Vesion 1.0 is available as Latest Version released Feb 26, 2026}}<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
'''Data model summary:''' <code>page_latest</code> tracks the most recent edit, <code>mw_approved_revs</code> identifies the revision currently approved for display, and each ROUTINE snapshot in <code>mw_tag_pages</code> records which revision belongs to that release.<br />
<br />
---------------------------------------------------------<br />
<br />
The following information can be used as an installation guide. Only download files tagged latest<br />
<br />
'''''<br />
<br />
= OBSOLETE Pre-release =<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
See procedure for rollback to reset to a previous version. Set tag ONLY. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
<br />
<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Note: Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> does not exist yet, or if you are intentionally applying the CustomQueryPage schema changes in a controlled maintenance window.}}<br />
<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=191Main Page2026-03-14T00:50:18Z<p>Tux: /* ROUTINE issue patch to fallback settings */</p>
<hr />
<div><br />
<br />
{{Info| Updated March 12, 2026.}}<br />
<br />
= Reset ROUTINE manually =<br />
<br />
==ROUTINE issue patch to fallback settings==<br />
<br />
== Method 1: Change the fallback ROUTINE in <code>LocalSettings.php</code> ==<br />
<br />
Use this as a quick test or temporary recovery step. ssh tux 210.32.36.141 /home/tux/mw1359/LocalSettings.php<br />
<br />
Edit this line in <code>LocalSettings.php</code>:<br />
<br />
<code><br />
$wgCustomQueryPageDefaultTag = 'ROUTINE_4.111';<br />
</code><br />
<br />
Then:<br />
<br />
# Save the file.<br />
# Reload [[Special:RoutineTags]].<br />
# Reload [[Special:ApprovedManuals]].<br />
<br />
If nothing changes:<br />
<br />
# Do a hard refresh in the browser.<br />
# If it is still unchanged, ask the sysadmin to restart PHP or the container.<br />
# Reload both special pages again.<br />
<br />
Expected result:<br />
<br />
* If the page starts showing <code>ROUTINE_4.111</code>, the extension is reading the fallback value from configuration.<br />
* If it still shows <code>ROUTINE_4.110</code>, this change did not affect the current read path.<br />
<br />
== Method 2: Quick page check ==<br />
<br />
After Method 1, check both pages, not just one:<br />
<br />
* [[Special:RoutineTags]]<br />
* [[Special:ApprovedManuals]]<br />
<br />
Things to confirm:<br />
<br />
* Does [[Special:RoutineTags]] show <code>ROUTINE_4.111</code> as the visible current or default tag?<br />
* Does the heading on [[Special:ApprovedManuals]] change to the new ROUTINE?<br />
* Does the document list appear to match the intended release?<br />
<br />
This is the easiest check available when direct SQL access is not available.<br />
<br />
== Method 3: See documentation ==<br />
<br />
''Link TBD''<br />
<br />
Use the ROUTINE workflow and recovery notes for deeper troubleshooting.<br />
<br />
Known points:<br />
<br />
* ROUTINE labels are stored in <code>mw_tags</code>.<br />
* ROUTINE membership is stored in <code>mw_tag_pages</code>.<br />
* The current approved set is stored in <code>mw_approved_revs</code>.<br />
* The active selected ROUTINE is stored in <code>mw_customquerypage_settings</code>.<br />
* Activating a ROUTINE rebuilds <code>mw_approved_revs</code>.<br />
* Rollback is done by reactivating the previous ROUTINE.<br />
<br />
If the manual <code>LocalSettings.php</code> edit and page refresh do not restore expected behaviour, continue with the documented extension workflow and technical recovery notes.<br />
<br />
-----------------------------------------------------------<br />
<br />
{{Info| Released Vesion 1.0 is available as Latest Version released Feb 26, 2026}}<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
'''Data model summary:''' <code>page_latest</code> tracks the most recent edit, <code>mw_approved_revs</code> identifies the revision currently approved for display, and each ROUTINE snapshot in <code>mw_tag_pages</code> records which revision belongs to that release.<br />
<br />
---------------------------------------------------------<br />
<br />
The following information can be used as an installation guide. Only download files tagged latest<br />
<br />
'''''<br />
<br />
= OBSOLETE Pre-release =<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
<br />
<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Note: Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> does not exist yet, or if you are intentionally applying the CustomQueryPage schema changes in a controlled maintenance window.}}<br />
<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=190Main Page2026-03-14T00:48:26Z<p>Tux: /* Method 1: Change the fallback ROUTINE in LocalSettings.php */</p>
<hr />
<div><br />
<br />
{{Info| Updated March 12, 2026.}}<br />
<br />
= Reset ROUTINE manually =<br />
<br />
== ROUTINE issue patch to fallback settings == <br />
<br />
== Method 1: Change the fallback ROUTINE in <code>LocalSettings.php</code> ==<br />
<br />
Use this as a quick test or temporary recovery step. ssh tux 210.32.36.141 /home/tux/mw1359/LocalSettings.php<br />
<br />
Edit this line in <code>LocalSettings.php</code>:<br />
<br />
<code><br />
$wgCustomQueryPageDefaultTag = 'ROUTINE_4.111';<br />
</code><br />
<br />
Then:<br />
<br />
# Save the file.<br />
# Reload [[Special:RoutineTags]].<br />
# Reload [[Special:ApprovedManuals]].<br />
<br />
If nothing changes:<br />
<br />
# Do a hard refresh in the browser.<br />
# If it is still unchanged, ask the sysadmin to restart PHP or the container.<br />
# Reload both special pages again.<br />
<br />
Expected result:<br />
<br />
* If the page starts showing <code>ROUTINE_4.111</code>, the extension is reading the fallback value from configuration.<br />
* If it still shows <code>ROUTINE_4.110</code>, this change did not affect the current read path.<br />
<br />
== Method 2: Quick page check ==<br />
<br />
After Method 1, check both pages, not just one:<br />
<br />
* [[Special:RoutineTags]]<br />
* [[Special:ApprovedManuals]]<br />
<br />
Things to confirm:<br />
<br />
* Does [[Special:RoutineTags]] show <code>ROUTINE_4.111</code> as the visible current or default tag?<br />
* Does the heading on [[Special:ApprovedManuals]] change to the new ROUTINE?<br />
* Does the document list appear to match the intended release?<br />
<br />
This is the easiest check available when direct SQL access is not available.<br />
<br />
== Method 3: See documentation ==<br />
<br />
''Link TBD''<br />
<br />
Use the ROUTINE workflow and recovery notes for deeper troubleshooting.<br />
<br />
Known points:<br />
<br />
* ROUTINE labels are stored in <code>mw_tags</code>.<br />
* ROUTINE membership is stored in <code>mw_tag_pages</code>.<br />
* The current approved set is stored in <code>mw_approved_revs</code>.<br />
* The active selected ROUTINE is stored in <code>mw_customquerypage_settings</code>.<br />
* Activating a ROUTINE rebuilds <code>mw_approved_revs</code>.<br />
* Rollback is done by reactivating the previous ROUTINE.<br />
<br />
If the manual <code>LocalSettings.php</code> edit and page refresh do not restore expected behaviour, continue with the documented extension workflow and technical recovery notes.<br />
<br />
-----------------------------------------------------------<br />
<br />
{{Info| Released Vesion 1.0 is available as Latest Version released Feb 26, 2026}}<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
'''Data model summary:''' <code>page_latest</code> tracks the most recent edit, <code>mw_approved_revs</code> identifies the revision currently approved for display, and each ROUTINE snapshot in <code>mw_tag_pages</code> records which revision belongs to that release.<br />
<br />
---------------------------------------------------------<br />
<br />
The following information can be used as an installation guide. Only download files tagged latest<br />
<br />
'''''<br />
<br />
= OBSOLETE Pre-release =<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
<br />
<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Note: Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> does not exist yet, or if you are intentionally applying the CustomQueryPage schema changes in a controlled maintenance window.}}<br />
<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=189Main Page2026-03-14T00:39:45Z<p>Tux: /* 1. Seed the ROUTINE in the DB */</p>
<hr />
<div><br />
<br />
{{Info| Updated March 12, 2026.}}<br />
<br />
= Reset ROUTINE manually =<br />
<br />
== ROUTINE issue patch to fallback settings == <br />
<br />
== Method 1: Change the fallback ROUTINE in <code>LocalSettings.php</code> ==<br />
<br />
Use this as a quick test or temporary recovery step.<br />
<br />
Edit this line in <code>LocalSettings.php</code>:<br />
<br />
<syntaxhighlight lang="php"><br />
$wgCustomQueryPageDefaultTag = 'ROUTINE_4.111';<br />
</syntaxhighlight><br />
<br />
Then:<br />
<br />
# Save the file.<br />
# Reload [[Special:RoutineTags]].<br />
# Reload [[Special:ApprovedManuals]].<br />
<br />
If nothing changes:<br />
<br />
# Do a hard refresh in the browser.<br />
# If it is still unchanged, ask the sysadmin to restart PHP or the container.<br />
# Reload both special pages again.<br />
<br />
Expected result:<br />
<br />
* If the page starts showing <code>ROUTINE_4.111</code>, the extension is reading the fallback value from configuration.<br />
* If it still shows <code>ROUTINE_4.110</code>, this change did not affect the current read path.<br />
<br />
== Method 2: Quick page check ==<br />
<br />
After Method 1, check both pages, not just one:<br />
<br />
* [[Special:RoutineTags]]<br />
* [[Special:ApprovedManuals]]<br />
<br />
Things to confirm:<br />
<br />
* Does [[Special:RoutineTags]] show <code>ROUTINE_4.111</code> as the visible current or default tag?<br />
* Does the heading on [[Special:ApprovedManuals]] change to the new ROUTINE?<br />
* Does the document list appear to match the intended release?<br />
<br />
This is the easiest check available when direct SQL access is not available.<br />
<br />
== Method 3: See documentation ==<br />
<br />
''Link TBD''<br />
<br />
Use the ROUTINE workflow and recovery notes for deeper troubleshooting.<br />
<br />
Known points:<br />
<br />
* ROUTINE labels are stored in <code>mw_tags</code>.<br />
* ROUTINE membership is stored in <code>mw_tag_pages</code>.<br />
* The current approved set is stored in <code>mw_approved_revs</code>.<br />
* The active selected ROUTINE is stored in <code>mw_customquerypage_settings</code>.<br />
* Activating a ROUTINE rebuilds <code>mw_approved_revs</code>.<br />
* Rollback is done by reactivating the previous ROUTINE.<br />
<br />
If the manual <code>LocalSettings.php</code> edit and page refresh do not restore expected behaviour, continue with the documented extension workflow and technical recovery notes.<br />
<br />
-----------------------------------------------------------<br />
<br />
{{Info| Released Vesion 1.0 is available as Latest Version released Feb 26, 2026}}<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
'''Data model summary:''' <code>page_latest</code> tracks the most recent edit, <code>mw_approved_revs</code> identifies the revision currently approved for display, and each ROUTINE snapshot in <code>mw_tag_pages</code> records which revision belongs to that release.<br />
<br />
---------------------------------------------------------<br />
<br />
The following information can be used as an installation guide. Only download files tagged latest<br />
<br />
'''''<br />
<br />
= OBSOLETE Pre-release =<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
<br />
<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Note: Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> does not exist yet, or if you are intentionally applying the CustomQueryPage schema changes in a controlled maintenance window.}}<br />
<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=188Main Page2026-03-14T00:35:28Z<p>Tux: /* OBSOLETE Pre-release */</p>
<hr />
<div><br />
<br />
{{Info| Updated March 12, 2026.}}<br />
<br />
= Reset ROUTINE manually =<br />
<br />
== ROUTINE issue patch to fallback settings == <br />
<br />
== Method 1: Change the fallback ROUTINE in <code>LocalSettings.php</code> ==<br />
<br />
Use this as a quick test or temporary recovery step.<br />
<br />
Edit this line in <code>LocalSettings.php</code>:<br />
<br />
<syntaxhighlight lang="php"><br />
$wgCustomQueryPageDefaultTag = 'ROUTINE_4.111';<br />
</syntaxhighlight><br />
<br />
Then:<br />
<br />
# Save the file.<br />
# Reload [[Special:RoutineTags]].<br />
# Reload [[Special:ApprovedManuals]].<br />
<br />
If nothing changes:<br />
<br />
# Do a hard refresh in the browser.<br />
# If it is still unchanged, ask the sysadmin to restart PHP or the container.<br />
# Reload both special pages again.<br />
<br />
Expected result:<br />
<br />
* If the page starts showing <code>ROUTINE_4.111</code>, the extension is reading the fallback value from configuration.<br />
* If it still shows <code>ROUTINE_4.110</code>, this change did not affect the current read path.<br />
<br />
== Method 2: Quick page check ==<br />
<br />
After Method 1, check both pages, not just one:<br />
<br />
* [[Special:RoutineTags]]<br />
* [[Special:ApprovedManuals]]<br />
<br />
Things to confirm:<br />
<br />
* Does [[Special:RoutineTags]] show <code>ROUTINE_4.111</code> as the visible current or default tag?<br />
* Does the heading on [[Special:ApprovedManuals]] change to the new ROUTINE?<br />
* Does the document list appear to match the intended release?<br />
<br />
This is the easiest check available when direct SQL access is not available.<br />
<br />
== Method 3: See documentation ==<br />
<br />
''Link TBD''<br />
<br />
Use the ROUTINE workflow and recovery notes for deeper troubleshooting.<br />
<br />
Known points:<br />
<br />
* ROUTINE labels are stored in <code>mw_tags</code>.<br />
* ROUTINE membership is stored in <code>mw_tag_pages</code>.<br />
* The current approved set is stored in <code>mw_approved_revs</code>.<br />
* The active selected ROUTINE is stored in <code>mw_customquerypage_settings</code>.<br />
* Activating a ROUTINE rebuilds <code>mw_approved_revs</code>.<br />
* Rollback is done by reactivating the previous ROUTINE.<br />
<br />
If the manual <code>LocalSettings.php</code> edit and page refresh do not restore expected behaviour, continue with the documented extension workflow and technical recovery notes.<br />
<br />
-----------------------------------------------------------<br />
<br />
{{Info| Released Vesion 1.0 is available as Latest Version released Feb 26, 2026}}<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
'''Data model summary:''' <code>page_latest</code> tracks the most recent edit, <code>mw_approved_revs</code> identifies the revision currently approved for display, and each ROUTINE snapshot in <code>mw_tag_pages</code> records which revision belongs to that release.<br />
<br />
---------------------------------------------------------<br />
<br />
The following information can be used as an installation guide. Only download files tagged latest<br />
<br />
'''''<br />
<br />
= OBSOLETE Pre-release =<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
<br />
<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=187Main Page2026-03-14T00:34:39Z<p>Tux: </p>
<hr />
<div><br />
<br />
{{Info| Updated March 12, 2026.}}<br />
<br />
= Reset ROUTINE manually =<br />
<br />
== ROUTINE issue patch to fallback settings == <br />
<br />
== Method 1: Change the fallback ROUTINE in <code>LocalSettings.php</code> ==<br />
<br />
Use this as a quick test or temporary recovery step.<br />
<br />
Edit this line in <code>LocalSettings.php</code>:<br />
<br />
<syntaxhighlight lang="php"><br />
$wgCustomQueryPageDefaultTag = 'ROUTINE_4.111';<br />
</syntaxhighlight><br />
<br />
Then:<br />
<br />
# Save the file.<br />
# Reload [[Special:RoutineTags]].<br />
# Reload [[Special:ApprovedManuals]].<br />
<br />
If nothing changes:<br />
<br />
# Do a hard refresh in the browser.<br />
# If it is still unchanged, ask the sysadmin to restart PHP or the container.<br />
# Reload both special pages again.<br />
<br />
Expected result:<br />
<br />
* If the page starts showing <code>ROUTINE_4.111</code>, the extension is reading the fallback value from configuration.<br />
* If it still shows <code>ROUTINE_4.110</code>, this change did not affect the current read path.<br />
<br />
== Method 2: Quick page check ==<br />
<br />
After Method 1, check both pages, not just one:<br />
<br />
* [[Special:RoutineTags]]<br />
* [[Special:ApprovedManuals]]<br />
<br />
Things to confirm:<br />
<br />
* Does [[Special:RoutineTags]] show <code>ROUTINE_4.111</code> as the visible current or default tag?<br />
* Does the heading on [[Special:ApprovedManuals]] change to the new ROUTINE?<br />
* Does the document list appear to match the intended release?<br />
<br />
This is the easiest check available when direct SQL access is not available.<br />
<br />
== Method 3: See documentation ==<br />
<br />
''Link TBD''<br />
<br />
Use the ROUTINE workflow and recovery notes for deeper troubleshooting.<br />
<br />
Known points:<br />
<br />
* ROUTINE labels are stored in <code>mw_tags</code>.<br />
* ROUTINE membership is stored in <code>mw_tag_pages</code>.<br />
* The current approved set is stored in <code>mw_approved_revs</code>.<br />
* The active selected ROUTINE is stored in <code>mw_customquerypage_settings</code>.<br />
* Activating a ROUTINE rebuilds <code>mw_approved_revs</code>.<br />
* Rollback is done by reactivating the previous ROUTINE.<br />
<br />
If the manual <code>LocalSettings.php</code> edit and page refresh do not restore expected behaviour, continue with the documented extension workflow and technical recovery notes.<br />
<br />
-----------------------------------------------------------<br />
<br />
{{Info| Released Vesion 1.0 is available as Latest Version released Feb 26, 2026}}<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
'''Data model summary:''' <code>page_latest</code> tracks the most recent edit, <code>mw_approved_revs</code> identifies the revision currently approved for display, and each ROUTINE snapshot in <code>mw_tag_pages</code> records which revision belongs to that release.<br />
<br />
---------------------------------------------------------<br />
<br />
The following information can be used as an installation guide. Only download files tagged latest<br />
<br />
'''''<br />
<br />
===== OBSOLETE Pre-release =====<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
<br />
<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=186Main Page2026-03-14T00:32:56Z<p>Tux: Test fallback routine to set ROUTINE</p>
<hr />
<div>{{Info|ROUTINE issue patch to fallback settings. Updated March 12, 2026.}}<br />
<br />
= Reset ROUTINE manually =<br />
<br />
== Method 1: Change the fallback ROUTINE in <code>LocalSettings.php</code> ==<br />
<br />
Use this as a quick test or temporary recovery step.<br />
<br />
Edit this line in <code>LocalSettings.php</code>:<br />
<br />
<syntaxhighlight lang="php"><br />
$wgCustomQueryPageDefaultTag = 'ROUTINE_4.111';<br />
</syntaxhighlight><br />
<br />
Then:<br />
<br />
# Save the file.<br />
# Reload [[Special:RoutineTags]].<br />
# Reload [[Special:ApprovedManuals]].<br />
<br />
If nothing changes:<br />
<br />
# Do a hard refresh in the browser.<br />
# If it is still unchanged, ask the sysadmin to restart PHP or the container.<br />
# Reload both special pages again.<br />
<br />
Expected result:<br />
<br />
* If the page starts showing <code>ROUTINE_4.111</code>, the extension is reading the fallback value from configuration.<br />
* If it still shows <code>ROUTINE_4.110</code>, this change did not affect the current read path.<br />
<br />
== Method 2: Quick page check ==<br />
<br />
After Method 1, check both pages, not just one:<br />
<br />
* [[Special:RoutineTags]]<br />
* [[Special:ApprovedManuals]]<br />
<br />
Things to confirm:<br />
<br />
* Does [[Special:RoutineTags]] show <code>ROUTINE_4.111</code> as the visible current or default tag?<br />
* Does the heading on [[Special:ApprovedManuals]] change to the new ROUTINE?<br />
* Does the document list appear to match the intended release?<br />
<br />
This is the easiest check available when direct SQL access is not available.<br />
<br />
== Method 3: See documentation ==<br />
<br />
''Link TBD''<br />
<br />
Use the ROUTINE workflow and recovery notes for deeper troubleshooting.<br />
<br />
Known points:<br />
<br />
* ROUTINE labels are stored in <code>mw_tags</code>.<br />
* ROUTINE membership is stored in <code>mw_tag_pages</code>.<br />
* The current approved set is stored in <code>mw_approved_revs</code>.<br />
* The active selected ROUTINE is stored in <code>mw_customquerypage_settings</code>.<br />
* Activating a ROUTINE rebuilds <code>mw_approved_revs</code>.<br />
* Rollback is done by reactivating the previous ROUTINE.<br />
<br />
If the manual <code>LocalSettings.php</code> edit and page refresh do not restore expected behaviour, continue with the documented extension workflow and technical recovery notes.<br />
<br />
-----------------------------------------------------------<br />
<br />
{{Info| Released Vesion 1.0 is available as Latest Version released Feb 26, 2026}}<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
'''Data model summary:''' <code>page_latest</code> tracks the most recent edit, <code>mw_approved_revs</code> identifies the revision currently approved for display, and each ROUTINE snapshot in <code>mw_tag_pages</code> records which revision belongs to that release.<br />
<br />
---------------------------------------------------------<br />
<br />
The following information can be used as an installation guide. Only download files tagged latest<br />
<br />
'''''<br />
<br />
===== OBSOLETE Pre-release =====<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
<br />
<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=185Main Page2026-03-14T00:30:42Z<p>Tux: </p>
<hr />
<div>{{Info| ROUTINE issue patch to fallback settings Updated March 12, 2026}}<br />
<br />
## Reset ROUTINE manually<br />
<br />
### Method 1 — Change the default ROUTINE in `LocalSettings.php`<br />
<br />
Use this when you want a quick operational test or temporary recovery.<br />
<br />
Edit this line in `LocalSettings.php`:<br />
<br />
```php<br />
$wgCustomQueryPageDefaultTag = 'ROUTINE_4.111';<br />
```<br />
<br />
Then:<br />
<br />
1. save the file<br />
2. reload `Special:RoutineTags`<br />
3. reload `Special:ApprovedManuals`<br />
<br />
If nothing changes:<br />
<br />
1. do a hard refresh<br />
2. if still unchanged, have the sysadmin restart PHP / the container<br />
3. reload both pages again<br />
<br />
Expected result:<br />
<br />
* if the page starts showing `ROUTINE_4.111`, this path is affecting what the extension reads<br />
* if it still shows `ROUTINE_4.110`, this method did not change the active read path<br />
<br />
---<br />
<br />
### Method 2 — Quick sanity check<br />
<br />
After Method 1, verify both pages, not just one.<br />
<br />
Check:<br />
<br />
* `Special:RoutineTags`<br />
* `Special:ApprovedManuals`<br />
<br />
What to look for:<br />
<br />
* does `Special:RoutineTags` show `ROUTINE_4.111` as the visible current/default tag?<br />
* does `Special:ApprovedManuals` heading change to the new ROUTINE?<br />
* does the document list appear to match the intended release?<br />
<br />
This is the easiest non-SQL confirmation available when direct DB access is not available onsite.<br />
<br />
---<br />
<br />
### Method 3 — See documentation Link TBD<br />
<br />
Use the documented release workflow and recovery notes.<br />
<br />
Key points already established:<br />
<br />
* ROUTINE labels live in `mw_tags`<br />
* ROUTINE membership lives in `mw_tag_pages`<br />
* the current approved set is `mw_approved_revs`<br />
* the active selected ROUTINE is stored in `mw_customquerypage_settings`<br />
* activating a ROUTINE rebuilds `mw_approved_revs`<br />
* rollback is done by reactivating the previous ROUTINE<br />
<br />
If manual file edit and page refresh do not restore expected behavior, use the documented extension workflow and technical notes for deeper recovery.<br />
<br />
<br />
<br />
<br />
-----------------------------------------------------------<br />
<br />
{{Info| Released Vesion 1.0 is available as Latest Version released Feb 26, 2026}}<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
'''Data model summary:''' <code>page_latest</code> tracks the most recent edit, <code>mw_approved_revs</code> identifies the revision currently approved for display, and each ROUTINE snapshot in <code>mw_tag_pages</code> records which revision belongs to that release.<br />
<br />
---------------------------------------------------------<br />
<br />
The following information can be used as an installation guide. Only download files tagged latest<br />
<br />
'''''<br />
<br />
===== OBSOLETE Pre-release =====<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
<br />
<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=184Main Page2026-03-07T02:39:31Z<p>Tux: </p>
<hr />
<div><br />
-----------------------------------------------------------<br />
<br />
{{Info| Released Vesion 1.0 is available as Latest Version released Feb 26, 2026}}<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
'''Data model summary:''' <code>page_latest</code> tracks the most recent edit, <code>mw_approved_revs</code> identifies the revision currently approved for display, and each ROUTINE snapshot in <code>mw_tag_pages</code> records which revision belongs to that release.<br />
<br />
---------------------------------------------------------<br />
<br />
The following information can be used as an installation guide. Only download files tagged latest<br />
<br />
'''''<br />
<br />
===== OBSOLETE Pre-release =====<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
<br />
<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=183Main Page2026-03-07T02:38:32Z<p>Tux: </p>
<hr />
<div><br />
-----------------------------------------------------------<br />
<br />
{{Info| Released Vesion 1.0 is available as Latest Version released Feb 26, 2026}}<br />
[[Special:ListFiles|Uploaded Files]]<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
'''Data model summary:''' <code>page_latest</code> tracks the most recent edit, <code>mw_approved_revs</code> identifies the revision currently approved for display, and each ROUTINE snapshot in <code>mw_tag_pages</code> records which revision belongs to that release.<br />
<br />
---------------------------------------------------------<br />
<br />
The following information can be used as an installation guide. Only download files tagged latest<br />
<br />
'''''<br />
<br />
===== OBSOLETE Pre-release =====<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
<br />
<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=182Main Page2026-03-07T02:36:38Z<p>Tux: </p>
<hr />
<div><br />
-----------------------------------------------------------<br />
<br />
{{Info| Released Vesion 1.0 is available as Latest Version released Feb 26, 2026}}<br />
[[Special:ListFiles|Uploaded Files]]<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
'''Data model summary:''' <code>page_latest</code> tracks the most recent edit, <code>mw_approved_revs</code> identifies the revision currently approved for display, and each ROUTINE snapshot in <code>mw_tag_pages</code> records which revision belongs to that release.<br />
<br />
---------------------------------------------------------<br />
<br />
'''''ToDo: Document the location of the uploaded file Version 1.0'''''<br />
<br />
'''''<br />
<br />
===== OBSOLETE Pre-release =====<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
<br />
<br />
[[:File:CustomQueryPage-latest.tgz|CustomQueryPage – latest deployment bundle]]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=181Main Page2026-03-07T02:26:02Z<p>Tux: </p>
<hr />
<div><br />
-----------------------------------------------------------<br />
<br />
{{Info| Released Vesion 1.0 is available as Latest Version released Feb 26, 2026}}<br />
[[Special:ListFiles|Uploaded Files]]<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
'''Data model summary:''' <code>page_latest</code> tracks the most recent edit, <code>mw_approved_revs</code> identifies the revision currently approved for display, and each ROUTINE snapshot in <code>mw_tag_pages</code> records which revision belongs to that release.<br />
<br />
---------------------------------------------------------<br />
<br />
'''''ToDo: Document the location of the uploaded file Version 1.0'''''<br />
<br />
'''''<br />
<br />
===== OBSOLETE Pre-release =====<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=180Main Page2026-03-07T02:24:07Z<p>Tux: /* OBSOLETE */</p>
<hr />
<div><br />
-----------------------------------------------------------<br />
<br />
{{Tip|Latest Version released Feb 26, 2026}}<br />
[[Special:ListFiles|Uploaded Files]]<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
'''Data model summary:''' <code>page_latest</code> tracks the most recent edit, <code>mw_approved_revs</code> identifies the revision currently approved for display, and each ROUTINE snapshot in <code>mw_tag_pages</code> records which revision belongs to that release.<br />
<br />
---------------------------------------------------------<br />
<br />
'''''ToDo: Document the location of the uploaded file Version 1.0'''''<br />
<br />
'''''<br />
<br />
===== OBSOLETE Pre-release =====<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=179Main Page2026-03-07T02:23:28Z<p>Tux: </p>
<hr />
<div><br />
-----------------------------------------------------------<br />
<br />
{{Tip|Latest Version released Feb 26, 2026}}<br />
[[Special:ListFiles|Uploaded Files]]<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
'''Data model summary:''' <code>page_latest</code> tracks the most recent edit, <code>mw_approved_revs</code> identifies the revision currently approved for display, and each ROUTINE snapshot in <code>mw_tag_pages</code> records which revision belongs to that release.<br />
<br />
---------------------------------------------------------<br />
<br />
'''''ToDo: Document the location of the uploaded file Version 1.0'''''<br />
<br />
'''''<br />
<br />
===== OBSOLETE =====<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=MediaWiki:Sidebar&diff=178MediaWiki:Sidebar2026-03-07T01:48:50Z<p>Tux: </p>
<hr />
<div><br />
* navigation<br />
** Definitions|Definitions<br />
** mainpage|mainpage-description<br />
** Rs2|rs2<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help-mediawiki<br />
** MediaWiki_Tips|MW for the Sh1re<br />
** Special:ListFiles|Uploaded Files<br />
** Special:Upload|Upload Files<br />
** MediaWiki:Sidebar|MediaWiki Sidebar<br />
** Special:AllPages/Template:|Templates<br />
** purge-main|page purges<br />
<br />
deployment<br />
* Special:Upload|Upload Package<br />
* Special:ListFiles|Deployment Files<br />
<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES<br />
<br />
<h3> Now you can</h3> <br />
<p>This one was different</p><br />
<pre>** MediaWiki:Sidebar|MediaWiki Sidebar</p><br />
<p><br />
Link to other MediaWiki: pages (like MediaWiki:Common.css, MediaWiki:Mainpage-description), just remember to include the full namespace like MediaWiki:Mainpage-description </p></div>Tuxhttps://mw.eckford.ca:443/index.php?title=MediaWiki:Sidebar&diff=177MediaWiki:Sidebar2026-03-07T01:42:43Z<p>Tux: </p>
<hr />
<div><br />
* navigation<br />
** Definitions|Definitions<br />
** mainpage|mainpage-description<br />
** Rs2|rs2<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help-mediawiki<br />
** MediaWiki_Tips|MW for the Sh1re<br />
** Special:ListFiles|Uploaded Files<br />
** MediaWiki:Sidebar|MediaWiki Sidebar<br />
** Special:AllPages/Template:|Templates<br />
** purge-main|page purges<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES<br />
<br />
<h3> Now you can</h3> <br />
<p>This one was different</p><br />
<pre>** MediaWiki:Sidebar|MediaWiki Sidebar</p><br />
<p><br />
Link to other MediaWiki: pages (like MediaWiki:Common.css, MediaWiki:Mainpage-description), just remember to include the full namespace like MediaWiki:Mainpage-description </p></div>Tuxhttps://mw.eckford.ca:443/index.php?title=MediaWiki:Sidebar&diff=176MediaWiki:Sidebar2026-03-07T01:39:25Z<p>Tux: </p>
<hr />
<div><br />
* navigation<br />
** Definitions|Definitions<br />
** mainpage|mainpage-description<br />
** Rs2|rs2<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help-mediawiki<br />
** MediaWiki_Tips|MW for the Sh1re<br />
** listfiles|Uploaded Files<br />
** MediaWiki:Sidebar|MediaWiki Sidebar<br />
** Special:AllPages/Template:|Templates<br />
** purge-main|page purges<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES<br />
<br />
<h3> Now you can</h3> <br />
<p>This one was different</p><br />
<pre>** MediaWiki:Sidebar|MediaWiki Sidebar</p><br />
<p><br />
Link to other MediaWiki: pages (like MediaWiki:Common.css, MediaWiki:Mainpage-description), just remember to include the full namespace like MediaWiki:Mainpage-description </p></div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=175Main Page2026-03-07T01:34:06Z<p>Tux: </p>
<hr />
<div><br />
-----------------------------------------------------------<br />
<br />
{{Tip|Latest Version released Feb 26, 2026}}<br />
[[Special:ListFiles|Uploaded Files]]<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
---------------------------------------------------------<br />
<br />
'''''ToDo: Document the location of the uploaded file Version 1.0'''''<br />
<br />
''''' This version is missing one critical feature. It is now obsolete. This is pre-release. '''''<br />
<br />
---------------------------------------------------------<br />
<br />
''''' The revision ID does not appear to be updated on the documents that have been updated for this ROUTINE release. <br />
All the docs are tagged with the new release, but we have to do a refresh first so the docs that have been updated --- and approved display the '''''updated rel_id'''''.<br />
Be sure to only take revid from the Source of Truth itself: mw_revision<br />
'''''<br />
<br />
<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=174Main Page2026-03-07T01:33:38Z<p>Tux: </p>
<hr />
<div><br />
-----------------------------------------------------------<br />
<br />
<br />
{{Tip|Latest Version released Feb 26, 2026}}<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
[[Special:ListFiles|Uploaded Files]]<br />
<br />
---------------------------------------------------------<br />
<br />
'''''ToDo: Document the location of the uploaded file Version 1.0'''''<br />
<br />
''''' This version is missing one critical feature. It is now obsolete. This is pre-release. '''''<br />
<br />
---------------------------------------------------------<br />
<br />
''''' The revision ID does not appear to be updated on the documents that have been updated for this ROUTINE release. <br />
All the docs are tagged with the new release, but we have to do a refresh first so the docs that have been updated --- and approved display the '''''updated rel_id'''''.<br />
Be sure to only take revid from the Source of Truth itself: mw_revision<br />
'''''<br />
<br />
<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=ROUTINE-Data-Model&diff=173ROUTINE-Data-Model2026-03-07T01:27:41Z<p>Tux: </p>
<hr />
<div><br />
== TL;DR – ROUTINE Release Model ==<br />
<br />
ROUTINE releases are defined entirely by two tables:<br />
<br />
<pre><br />
mw_tags<br />
mw_tag_pages<br />
</pre><br />
<br />
* <code>mw_tags.tag_id</code> stores the ROUTINE label (for example <code>ROUTINE_4.110</code>)<br />
* <code>mw_tag_pages</code> maps each ROUTINE to the exact page revision that belongs to that release<br />
<br />
<pre><br />
tag_id → release label<br />
tag_page → page_id<br />
tag_rev → approved revision for that release<br />
</pre><br />
<br />
Everything else is derived.<br />
<br />
=== Source of truth ===<br />
<br />
<pre><br />
mw_tags<br />
mw_tag_pages<br />
</pre><br />
<br />
=== Supporting wiki data ===<br />
<br />
<pre><br />
mw_page<br />
mw_revision<br />
</pre><br />
<br />
=== Derived runtime table ===<br />
<br />
<pre><br />
mw_approved_revs<br />
</pre><br />
<br />
<code>mw_approved_revs</code> is not migration data and can always be regenerated from the ROUTINE snapshot.<br />
<br />
----<br />
<br />
== ROUTINE Data Relationships (Overview) ==<br />
<br />
{| class="wikitable"<br />
! Table<br />
! Role<br />
! Key Fields<br />
! Notes<br />
|-<br />
| '''mw_tags'''<br />
| Defines each ROUTINE release label<br />
| <code>tag_id</code><br><br />
<code>publish</code><br><br />
<code>locked</code><br><br />
<code>deleted</code><br><br />
<code>comment</code><br />
| Example: <code>ROUTINE_4.110</code><br />
|-<br />
| '''mw_tag_pages'''<br />
| Release snapshot mapping pages to revisions<br />
| <code>tag_id</code><br><br />
<code>tag_page</code><br><br />
<code>tag_rev</code><br />
| Defines exactly which revision belongs to a ROUTINE release<br />
|-<br />
| '''mw_revision'''<br />
| Stores revision history<br />
| <code>rev_id</code><br><br />
<code>rev_page</code><br><br />
<code>rev_timestamp</code><br />
| Each revision belongs to a page<br />
|-<br />
| '''mw_page'''<br />
| Page identity and metadata<br />
| <code>page_id</code><br><br />
<code>page_namespace</code><br><br />
<code>page_title</code><br><br />
<code>page_latest</code><br />
| Used for display and navigation<br />
|-<br />
| '''mw_approved_revs'''<br />
| Runtime projection used by ApprovedRevs<br />
| <code>page_id</code><br><br />
<code>rev_id</code><br><br />
<code>approver_id</code><br><br />
<code>approval_date</code><br />
| Derived table rebuilt during ROUTINE activation<br />
|}<br />
<br />
----<br />
<br />
== Data Flow ==<br />
<br />
<pre><br />
mw_tags<br />
↓<br />
mw_tag_pages<br />
↓<br />
mw_revision<br />
↓<br />
mw_page<br />
<br />
Activation rebuilds:<br />
<br />
mw_tag_pages → mw_revision → mw_approved_revs<br />
</pre><br />
<br />
----<br />
<br />
== Important Principle ==<br />
<br />
'''The authoritative ROUTINE snapshot lives in:'''<br />
<br />
<pre><br />
mw_tags + mw_tag_pages<br />
</pre><br />
<br />
Everything else can be regenerated.<br />
<br />
----<br />
<br />
== Administrator Rule ==<br />
<br />
'''Do not edit <code>mw_approved_revs</code> manually.'''<br />
<br />
If something looks wrong in ApprovedRevs:<br />
<br />
# Activate the correct ROUTINE tag.<br />
# Allow the system to rebuild <code>mw_approved_revs</code> from the ROUTINE snapshot.<br />
<br />
This guarantees consistency between the release label and approved revisions.<br />
<br />
<br />
== Operational Behavior ==<br />
<br />
'''Activate ROUTINE'''<br />
<br />
<pre><br />
ROUTINE tag selected<br />
↓<br />
mw_tag_pages snapshot identified<br />
↓<br />
mw_approved_revs rebuilt<br />
</pre><br />
<br />
'''Rollback'''<br />
<br />
<pre><br />
Activate older ROUTINE tag<br />
</pre><br />
<br />
Approved revisions immediately revert to that snapshot.<br />
<br />
----<br />
<br />
== Key Insight (Breakthrough) ==<br />
<br />
The ROUTINE system does '''not''' store approval history in <code>mw_approved_revs</code>.<br />
<br />
Instead it stores the release snapshot in:<br />
<br />
<pre><br />
mw_tag_pages<br />
</pre><br />
<br />
That snapshot defines exactly which revision of each page belongs to a release.<br />
<br />
<code>mw_approved_revs</code> is only a runtime projection used by the ApprovedRevs extension.<br />
<br />
----<br />
<br />
== Safe Test Dataset ==<br />
<br />
To build an offsite development stub you only need:<br />
<br />
<pre><br />
mw_tags<br />
mw_tag_pages<br />
mw_page<br />
mw_revision<br />
</pre><br />
<br />
<code>mw_approved_revs</code> can be empty and regenerated during activation.<br />
<br />
----<br />
<br />
== One Sentence Summary ==<br />
<br />
'''ROUTINE releases are simply named snapshots of page revisions stored in <code>mw_tag_pages</code>.'''<br />
<br />
Everything else can be rebuilt.<br />
<br />
----<br />
<br />
== ROUTINE Data Model and Test Stub Notes ==<br />
<br />
These notes describe the data structures used by the ROUTINE workflow in MediaWiki and how to construct a reusable development stub dataset for offsite work.<br />
<br />
The goal is to preserve the important relationships between ROUTINE labels, pages, and revisions without requiring production data.<br />
<br />
----<br />
<br />
== 1. Authoritative ROUTINE Data ==<br />
<br />
The authoritative release mapping lives in two tables.<br />
<br />
=== mw_tags ===<br />
<br />
Defines each ROUTINE label.<br />
<br />
{| class="wikitable"<br />
! Field<br />
! Purpose<br />
|-<br />
| tag_id<br />
| ROUTINE identifier (for example ROUTINE_4.110)<br />
|-<br />
| publish<br />
| Indicates whether the tag is considered published<br />
|-<br />
| locked<br />
| Prevents edits to the tag<br />
|-<br />
| deleted<br />
| Soft delete flag<br />
|-<br />
| comment<br />
| Optional deployment comment<br />
|}<br />
<br />
Important note:<br />
<br />
In this system the ROUTINE identifier is stored in '''tag_id''', not <code>tag_name</code>.<br />
<br />
All extension logic joins on:<br />
<br />
<pre><br />
mw_tags.tag_id<br />
</pre><br />
<br />
Example values:<br />
<br />
<pre><br />
ROUTINE_4.110<br />
ROUTINE_4.111<br />
ROUTINE_4.112<br />
</pre><br />
<br />
----<br />
<br />
=== mw_tag_pages ===<br />
<br />
Defines which revision of each page belongs to a ROUTINE release.<br />
<br />
{| class="wikitable"<br />
! Field<br />
! Purpose<br />
|-<br />
| tag_id<br />
| ROUTINE label<br />
|-<br />
| tag_page<br />
| Page ID<br />
|-<br />
| tag_rev<br />
| Approved revision ID<br />
|}<br />
<br />
This table represents the '''release snapshot'''.<br />
<br />
Example:<br />
<br />
{| class="wikitable"<br />
! tag_id<br />
! tag_page<br />
! tag_rev<br />
|-<br />
| ROUTINE_4.110<br />
| 101<br />
| 5001<br />
|-<br />
| ROUTINE_4.110<br />
| 102<br />
| 5002<br />
|-<br />
| ROUTINE_4.111<br />
| 101<br />
| 5001<br />
|-<br />
| ROUTINE_4.111<br />
| 102<br />
| 5009<br />
|}<br />
<br />
This means:<br />
<br />
* page 101 did not change between releases<br />
* page 102 received a new revision in 4.111<br />
<br />
----<br />
<br />
== 2. Supporting MediaWiki Core Data ==<br />
<br />
The ROUTINE workflow relies on normal MediaWiki tables.<br />
<br />
=== mw_page ===<br />
<br />
Identifies pages.<br />
<br />
{| class="wikitable"<br />
! Field<br />
! Purpose<br />
|-<br />
| page_id<br />
| Primary page identifier<br />
|-<br />
| page_namespace<br />
| Namespace<br />
|-<br />
| page_title<br />
| Page title<br />
|-<br />
| page_latest<br />
| Current revision ID<br />
|}<br />
<br />
Relationship:<br />
<br />
<pre><br />
mw_revision.rev_page = mw_page.page_id<br />
</pre><br />
<br />
----<br />
<br />
=== mw_revision ===<br />
<br />
Stores revision history.<br />
<br />
{| class="wikitable"<br />
! Field<br />
! Purpose<br />
|-<br />
| rev_id<br />
| Revision ID<br />
|-<br />
| rev_page<br />
| Page ID<br />
|-<br />
| rev_timestamp<br />
| Revision timestamp<br />
|}<br />
<br />
Relationship used by ROUTINE logic:<br />
<br />
<pre><br />
mw_tag_pages.tag_rev = mw_revision.rev_id<br />
</pre><br />
<br />
----<br />
<br />
== 3. Derived Runtime Table ==<br />
<br />
=== mw_approved_revs ===<br />
<br />
This table is '''not''' part of the migrated ROUTINE data.<br />
<br />
It is a runtime projection used by the ApprovedRevs extension.<br />
<br />
{| class="wikitable"<br />
! Field<br />
! Purpose<br />
|-<br />
| page_id<br />
| Page identifier<br />
|-<br />
| rev_id<br />
| Approved revision<br />
|-<br />
| approver_id<br />
| User who approved<br />
|-<br />
| approval_date<br />
| Approval timestamp<br />
|}<br />
<br />
Important constraint:<br />
<br />
<pre><br />
page_id UNIQUE<br />
</pre><br />
<br />
Only one approved revision per page can exist at a time.<br />
<br />
----<br />
<br />
== Important Operational Insight ==<br />
<br />
<code>mw_approved_revs</code> was not included in the ROUTINE migration.<br />
<br />
On the sh0re environment the table still existed only because the environment was not dropped during migration.<br />
<br />
Therefore:<br />
<br />
'''mw_approved_revs should be considered derived state.'''<br />
<br />
It can always be rebuilt from:<br />
<br />
<pre><br />
mw_tags<br />
mw_tag_pages<br />
mw_revision<br />
</pre><br />
<br />
----<br />
<br />
== Final Operational Principle ==<br />
<br />
The '''source of truth''' for ROUTINE releases is:<br />
<br />
<pre><br />
mw_tags + mw_tag_pages<br />
</pre><br />
<br />
Everything else can be regenerated.<br />
<br />
This makes rollback, cloning, and importer workflows safe and predictable.<br />
```<br />
<br />
---<br />
<br />
This version will render cleanly in MediaWiki because it uses:<br />
<br />
* `== headings ==`<br />
* `{| class="wikitable" |}` tables<br />
* `<pre>` blocks instead of ``` fences<br />
* `<code>` inline formatting<br />
<br />
---</div>Tuxhttps://mw.eckford.ca:443/index.php?title=ROUTINE-Data-Model&diff=172ROUTINE-Data-Model2026-03-07T01:21:56Z<p>Tux: Release notes with Version 1 created</p>
<hr />
<div>Good idea. A TL;DR at the top saves future-you (and Simon) from rereading the whole document.<br />
<br />
Here’s a clean one you can drop **at the very top of the notes**.<br />
<br />
---<br />
<br />
# TL;DR – ROUTINE Release Model<br />
<br />
ROUTINE releases are defined entirely by **two tables**:<br />
<br />
```<br />
mw_tags<br />
mw_tag_pages<br />
```<br />
<br />
* `mw_tags.tag_id` stores the ROUTINE label (e.g. `ROUTINE_4.110`)<br />
* `mw_tag_pages` maps each ROUTINE to the **exact page revision** that belongs to that release<br />
<br />
```<br />
tag_id → release label<br />
tag_page → page_id<br />
tag_rev → approved revision for that release<br />
```<br />
<br />
Everything else is derived.<br />
<br />
### Source of truth<br />
<br />
```<br />
mw_tags<br />
mw_tag_pages<br />
```<br />
<br />
### Supporting wiki data<br />
<br />
```<br />
mw_page<br />
mw_revision<br />
```<br />
<br />
### Derived runtime table<br />
<br />
```<br />
mw_approved_revs<br />
```<br />
<br />
`mw_approved_revs` is **not migration data** and can always be regenerated from the ROUTINE snapshot.<br />
<br />
---<br />
<br />
# Operational Behavior<br />
<br />
**Activate ROUTINE**<br />
<br />
```<br />
ROUTINE tag selected<br />
↓<br />
mw_tag_pages snapshot identified<br />
↓<br />
mw_approved_revs rebuilt<br />
```<br />
<br />
**Rollback**<br />
<br />
```<br />
Activate older ROUTINE tag<br />
```<br />
<br />
Approved revisions immediately revert to that snapshot.<br />
<br />
---<br />
<br />
# Key Insight (Breakthrough)<br />
<br />
The ROUTINE system does **not store approval history in mw_approved_revs**.<br />
<br />
Instead it stores the **release snapshot** in:<br />
<br />
```<br />
mw_tag_pages<br />
```<br />
<br />
That snapshot defines exactly which revision of each page belongs to a release.<br />
<br />
`mw_approved_revs` is only a **runtime projection** used by the ApprovedRevs extension.<br />
<br />
---<br />
<br />
# Safe Test Dataset<br />
<br />
To build an offsite development stub you only need:<br />
<br />
```<br />
mw_tags<br />
mw_tag_pages<br />
mw_page<br />
mw_revision<br />
```<br />
<br />
`mw_approved_revs` can be empty and regenerated during activation.<br />
<br />
---<br />
<br />
# One Sentence Summary<br />
<br />
**ROUTINE releases are simply named snapshots of page revisions stored in `mw_tag_pages`.**<br />
<br />
Everything else can be rebuilt.<br />
<br />
---<br />
<br />
If you'd like, I can also give you a **very small ASCII diagram of the data relationships** that fits on one screen. It's surprisingly helpful when someone new inherits the system (Simon in particular).<br />
<br />
<br />
---<br />
<br />
# ROUTINE Data Model and Test Stub Notes<br />
<br />
These notes describe the data structures used by the ROUTINE workflow in MediaWiki and how to construct a reusable development stub dataset for offsite work.<br />
<br />
The goal is to preserve the important relationships between ROUTINE labels, pages, and revisions without requiring production data.<br />
<br />
---<br />
<br />
# 1. Authoritative ROUTINE Data<br />
<br />
The authoritative release mapping lives in two tables.<br />
<br />
## `mw_tags`<br />
<br />
Defines each ROUTINE label.<br />
<br />
Example fields:<br />
<br />
| Field | Purpose |<br />
| --------- | ------------------------------------------------- |<br />
| `tag_id` | ROUTINE identifier (e.g. `ROUTINE_4.110`) |<br />
| `publish` | Indicates whether the tag is considered published |<br />
| `locked` | Prevents edits to the tag |<br />
| `deleted` | Soft delete flag |<br />
| `comment` | Optional deployment comment |<br />
<br />
Important note:<br />
<br />
In this system the ROUTINE identifier is stored in **`tag_id`**, not `tag_name`.<br />
<br />
All extension logic joins on:<br />
<br />
```<br />
mw_tags.tag_id<br />
```<br />
<br />
Example values:<br />
<br />
```<br />
ROUTINE_4.110<br />
ROUTINE_4.111<br />
ROUTINE_4.112<br />
```<br />
<br />
---<br />
<br />
## `mw_tag_pages`<br />
<br />
Defines which revision of each page belongs to a ROUTINE release.<br />
<br />
Fields:<br />
<br />
| Field | Purpose |<br />
| ---------- | -------------------- |<br />
| `tag_id` | ROUTINE label |<br />
| `tag_page` | Page ID |<br />
| `tag_rev` | Approved revision ID |<br />
<br />
This table represents the **release snapshot**.<br />
<br />
Example:<br />
<br />
| tag_id | tag_page | tag_rev |<br />
| ------------- | -------- | ------- |<br />
| ROUTINE_4.110 | 101 | 5001 |<br />
| ROUTINE_4.110 | 102 | 5002 |<br />
| ROUTINE_4.111 | 101 | 5001 |<br />
| ROUTINE_4.111 | 102 | 5009 |<br />
<br />
This means:<br />
<br />
* page 101 did not change between releases<br />
* page 102 received a new revision in 4.111<br />
<br />
---<br />
<br />
# 2. Supporting MediaWiki Core Data<br />
<br />
The ROUTINE workflow relies on normal MediaWiki tables.<br />
<br />
## `mw_page`<br />
<br />
Identifies pages.<br />
<br />
Important fields:<br />
<br />
| Field | Purpose |<br />
| ---------------- | ----------------------- |<br />
| `page_id` | Primary page identifier |<br />
| `page_namespace` | Namespace |<br />
| `page_title` | Page title |<br />
| `page_latest` | Current revision ID |<br />
<br />
Relationship:<br />
<br />
```<br />
mw_revision.rev_page = mw_page.page_id<br />
```<br />
<br />
---<br />
<br />
## `mw_revision`<br />
<br />
Stores revision history.<br />
<br />
Important fields:<br />
<br />
| Field | Purpose |<br />
| --------------- | ------------------ |<br />
| `rev_id` | Revision ID |<br />
| `rev_page` | Page ID |<br />
| `rev_timestamp` | Revision timestamp |<br />
<br />
Relationship used by ROUTINE logic:<br />
<br />
```<br />
mw_tag_pages.tag_rev = mw_revision.rev_id<br />
```<br />
<br />
---<br />
<br />
# 3. Derived Runtime Table<br />
<br />
## `mw_approved_revs`<br />
<br />
This table is **not part of the migrated ROUTINE data**.<br />
<br />
It is a runtime projection used by the **ApprovedRevs extension**.<br />
<br />
Schema:<br />
<br />
| Field | Purpose |<br />
| --------------- | ------------------ |<br />
| `page_id` | Page identifier |<br />
| `rev_id` | Approved revision |<br />
| `approver_id` | User who approved |<br />
| `approval_date` | Approval timestamp |<br />
<br />
Important constraint:<br />
<br />
```<br />
page_id UNIQUE<br />
```<br />
<br />
Only one approved revision per page can exist at a time.<br />
<br />
---<br />
<br />
# Important Operational Insight<br />
<br />
`mw_approved_revs` was **not included in the ROUTINE migration**.<br />
<br />
On the sh0re environment the table still existed only because the environment was not dropped during migration.<br />
<br />
Therefore:<br />
<br />
**`mw_approved_revs` should be considered derived state.**<br />
<br />
It can always be rebuilt from:<br />
<br />
```<br />
mw_tags<br />
mw_tag_pages<br />
mw_revision<br />
```<br />
<br />
---<br />
<br />
# 4. Activation Workflow<br />
<br />
When a ROUTINE tag is activated:<br />
<br />
1. The selected ROUTINE label is verified in `mw_tags`.<br />
2. All pages belonging to that tag are identified via `mw_tag_pages`.<br />
3. `mw_approved_revs` is refreshed to match the snapshot.<br />
<br />
Conceptually:<br />
<br />
```<br />
mw_tag_pages → mw_revision → mw_approved_revs<br />
```<br />
<br />
Rollback is therefore simple:<br />
<br />
```<br />
activate ROUTINE_4.110<br />
```<br />
<br />
and the approved revisions revert to that snapshot.<br />
<br />
---<br />
<br />
# 5. Reusable Test Dataset<br />
<br />
A reusable development stub should include:<br />
<br />
### Required tables<br />
<br />
```<br />
mw_tags<br />
mw_tag_pages<br />
mw_page<br />
mw_revision<br />
```<br />
<br />
### Optional<br />
<br />
```<br />
mw_approved_revs (empty)<br />
```<br />
<br />
---<br />
<br />
# Recommended Stub Structure<br />
<br />
A useful small dataset contains:<br />
<br />
| Item | Suggested Count |<br />
| ------------ | --------------- |<br />
| ROUTINE tags | 3 |<br />
| pages | 5–8 |<br />
| revisions | 6–10 |<br />
| tag mappings | 8–15 |<br />
<br />
---<br />
<br />
# Example Release Story<br />
<br />
### ROUTINE_4.110<br />
<br />
Pages:<br />
<br />
```<br />
Startup_Procedure<br />
Shutdown_Procedure<br />
Network_Check<br />
Incident_Escalation<br />
```<br />
<br />
### ROUTINE_4.111<br />
<br />
Pages:<br />
<br />
```<br />
Startup_Procedure (unchanged)<br />
Shutdown_Procedure (new revision)<br />
Backup_Verification (new page)<br />
Incident_Escalation (unchanged)<br />
```<br />
<br />
This creates realistic test scenarios:<br />
<br />
| Scenario | Purpose |<br />
| -------------- | ---------------------- |<br />
| unchanged page | verify revision reuse |<br />
| updated page | verify revision update |<br />
| removed page | verify exclusion |<br />
| new page | verify clone/import |<br />
<br />
---<br />
<br />
# 6. Minimal Fields That Must Be Accurate<br />
<br />
The following identifiers must remain correct in any stub dataset:<br />
<br />
```<br />
mw_tags.tag_id<br />
mw_tag_pages.tag_id<br />
mw_tag_pages.tag_page<br />
mw_tag_pages.tag_rev<br />
mw_page.page_id<br />
mw_page.page_title<br />
mw_revision.rev_id<br />
mw_revision.rev_page<br />
mw_revision.rev_timestamp<br />
```<br />
<br />
Everything else may be dummy data if necessary.<br />
<br />
---<br />
<br />
# 7. Future Importer Design<br />
<br />
If a JSON/API importer is later introduced, its logical structure should mirror the release mapping.<br />
<br />
Example conceptual payload:<br />
<br />
```json<br />
{<br />
"tag_id": "ROUTINE_4.112",<br />
"pages": [<br />
{<br />
"page_id": 101,<br />
"rev_id": 5001<br />
},<br />
{<br />
"page_id": 102,<br />
"rev_id": 5009<br />
}<br />
]<br />
}<br />
```<br />
<br />
This maps directly to `mw_tag_pages`.<br />
<br />
---<br />
<br />
# Final Operational Principle<br />
<br />
The **source of truth** for ROUTINE releases is:<br />
<br />
```<br />
mw_tags + mw_tag_pages<br />
```<br />
<br />
Everything else can be regenerated.<br />
<br />
This makes rollback, cloning, and importer workflows safe and predictable.<br />
<br />
---</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=171Main Page2026-03-07T00:47:21Z<p>Tux: </p>
<hr />
<div><br />
-----------------------------------------------------------<br />
<br />
<br />
{{Tip|Latest Version released Feb 26, 2026}}<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
* Download Latest: <code>Special:CustomQuerySettings</code><br />
<br />
---------------------------------------------------------<br />
<br />
'''''ToDo: Document the location of the uploaded file Version 1.0'''''<br />
<br />
''''' This version is missing one critical feature. It is now obsolete. This is pre-release. '''''<br />
<br />
---------------------------------------------------------<br />
<br />
''''' The revision ID does not appear to be updated on the documents that have been updated for this ROUTINE release. <br />
All the docs are tagged with the new release, but we have to do a refresh first so the docs that have been updated --- and approved display the '''''updated rel_id'''''.<br />
Be sure to only take revid from the Source of Truth itself: mw_revision<br />
'''''<br />
<br />
<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=170Main Page2026-03-07T00:46:23Z<p>Tux: </p>
<hr />
<div><br />
-----------------------------------------------------------<br />
<br />
<br />
{{Version 1.0|Latest Version released Feb 26, 2026}}<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
* Download Latest: <code>Special:CustomQuerySettings</code><br />
<br />
<br />
<br />
---------------------------------------------------------<br />
<br />
'''''ToDo: Document the location of the uploaded file Version 1.0'''''<br />
<br />
''''' This version is missing one critical feature. It is now obsolete. This is pre-release. '''''<br />
<br />
---------------------------------------------------------<br />
<br />
''''' The revision ID does not appear to be updated on the documents that have been updated for this ROUTINE release. <br />
All the docs are tagged with the new release, but we have to do a refresh first so the docs that have been updated --- and approved display the '''''updated rel_id'''''.<br />
Be sure to only take revid from the Source of Truth itself: mw_revision<br />
'''''<br />
<br />
<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=169Main Page2026-03-07T00:43:30Z<p>Tux: </p>
<hr />
<div><br />
-----------------------------------------------------------<br />
<br />
Latest Version released Feb 26, 2026<br />
<br />
<br />
<br />
Version 1.0<br />
<br />
<br />
<br />
File:CustomQueryPage-latest.tgz<br />
<br />
* Download Latest: <code>Special:CustomQuerySettings</code><br />
<br />
<br />
<br />
---------------------------------------------------------<br />
<br />
'''''ToDo: Document the location of the uploaded file Version 1.0'''''<br />
<br />
''''' This version is missing one critical feature. It is now obsolete. This is pre-release. '''''<br />
<br />
---------------------------------------------------------<br />
<br />
''''' The revision ID does not appear to be updated on the documents that have been updated for this ROUTINE release. <br />
All the docs are tagged with the new release, but we have to do a refresh first so the docs that have been updated --- and approved display the '''''updated rel_id'''''.<br />
Be sure to only take revid from the Source of Truth itself: mw_revision<br />
'''''<br />
<br />
<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=168Main Page2026-03-07T00:18:43Z<p>Tux: </p>
<hr />
<div><br />
---------------------------------------------------------<br />
<br />
'''''ToDo: Document the location of the uploaded file Version 1.0'''''<br />
<br />
''''' This version is missing one critical feature. It is now obsolete. This is pre-release. '''''<br />
<br />
---------------------------------------------------------<br />
<br />
''''' The revision ID does not appear to be updated on the documents that have been updated for this ROUTINE release. <br />
All the docs are tagged with the new release, but we have to do a refresh first so the docs that have been updated --- and approved display the '''''updated rel_id'''''.<br />
Be sure to only take revid from the Source of Truth itself: mw_revision<br />
'''''<br />
<br />
<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=167Main Page2026-03-07T00:17:55Z<p>Tux: </p>
<hr />
<div>'''''ToDo: Document the location of the uploaded file Version 1.0'''''<br />
<br />
''''' This version is missing one critical feature. It is now obsolete. This is pre-release. '''''<br />
<br />
<br />
''''' The revision ID does not appear to be updated on the documents that have been updated for this ROUTINE release. <br />
All the docs are tagged with the new release, but we have to do a refresh first so the docs that have been updated --- and approved display the '''''updated rel_id'''''.<br />
Be sure to only take revid from the Source of Truth itself: mw_revision<br />
'''''<br />
<br />
<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=File:CustomQueryPage-latest.tgz&diff=165File:CustomQueryPage-latest.tgz2026-03-06T22:07:19Z<p>Tux: Released version 1.0</p>
<hr />
<div>== Summary ==<br />
Released version 1.0</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=164Main Page2026-02-14T00:26:03Z<p>Tux: </p>
<hr />
<div><br />
''''' This version is missing one critical feature. The revision ID does not appear to be updated on the documents that have been updated for this ROUTINE release. <br />
All the docs are tagged with the new release, but we have to do a refresh first so the docs that have been updated --- and approved display the '''''updated rel_id'''''.<br />
Be sure to only take revid from the Source of Truth itself: mw_revision<br />
'''''<br />
<br />
<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=MediaWiki:Sidebar&diff=163MediaWiki:Sidebar2026-02-14T00:22:10Z<p>Tux: </p>
<hr />
<div><br />
* navigation<br />
** Definitions|Definitions<br />
** mainpage|mainpage-description<br />
** Rs2|rs2<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help-mediawiki<br />
** MediaWiki_Tips|MW for the Sh1re<br />
** MediaWiki:Sidebar|MediaWiki Sidebar<br />
** Special:AllPages/Template:|Templates<br />
** purge-main|page purges<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES<br />
<br />
<h3> Now you can</h3> <br />
<p>This one was different</p><br />
<pre>** MediaWiki:Sidebar|MediaWiki Sidebar</p><br />
<p><br />
Link to other MediaWiki: pages (like MediaWiki:Common.css, MediaWiki:Mainpage-description), just remember to include the full namespace like MediaWiki:Mainpage-description </p></div>Tuxhttps://mw.eckford.ca:443/index.php?title=Definitions&diff=162Definitions2026-02-14T00:17:33Z<p>Tux: Created page with " ; AI Agents : An AI agent is a system that autonomously performs tasks by perceiving its environment, making decisions, and taking actions to achieve specific goals. These systems can operate with limited human supervision and are designed to handle complex workflows using available tools"</p>
<hr />
<div><br />
<br />
; AI Agents<br />
<br />
: An AI agent is a system that autonomously performs tasks by perceiving its environment, making decisions, and taking actions to achieve specific goals. These systems can operate with limited human supervision and are designed to handle complex workflows using available tools</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=161Main Page2026-01-30T19:11:57Z<p>Tux: </p>
<hr />
<div><br />
''''' This version is missing one critical feature. The revision ID does not appear to be updated on the documents that have been updated for this ROUTINE release. <br />
All the docs are tagged with the new release, but we have to do a refresh first so the docs that have been updated --- and approved display the '''''updated rel_id'''''.<br />
'''''<br />
<br />
<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=160Main Page2026-01-30T19:11:31Z<p>Tux: </p>
<hr />
<div><br />
''''' This version is missing one critical feature. The revision ID does not appear to be updated on the documents that have been updated for this ROUTINE release. <br />
All the docs are tagged with the new release, but we have to do a refresh first so the docs that have been updated --- and approved display the updated rel_id.<br />
'''''<br />
<br />
<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Main_Page&diff=159Main Page2026-01-30T19:10:56Z<p>Tux: </p>
<hr />
<div><br />
````` This version is missing one critical feature. The revision ID does not appear to be updated on the documents that have been updated for this ROUTINE release. <br />
All the docs are tagged with the new release, but we have to do a refresh first so the docs that have been updated --- and approved display the updated rel_id.`````<br />
<br />
<br />
<strong>MediaWiki has been installed.</strong><br />
{{Notice<br />
| event_name = Wiki launch<br />
| date = February 12th<br />
| location = Lisa's Desk <br />
| description = Count down to the retirement of the efs3 server!<br />
}} <br />
{{{Hatnote|content is content}}}<br />
<br />
== Import CustomQueryPage ==<br />
This install is originally intended for the ROUTINE Manuals publication workflow. That's all it does now, but hey, it's a good place to keep notes too. Did you know for MediaWiki you create a page by writing the name in the address bar? How tricky is that?<br />
<br />
== NOTE ==<br />
Nice to have: the Special:CustomQuerySettings page has a [Clone ROUTINE] button it should also have a [Reset] button in case I want to do it again. <br />
<br />
== Let's Get Started ==<br />
<br />
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]<br />
<br />
=== Installing CustomQueryPage ===<br />
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code><br />
* Extract it into your extensions folder:<br />
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code><br />
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code><br />
* Run <code>php maintenance/update.php --quick</code>.<br />
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.<br />
<br />
= Quick Start: ROUTINE Management =<br />
<br />
=== 1. Seed the ROUTINE in the DB ===<br />
Before Lisa touches the UI, make sure the database has ROUTINE data.<br />
<br />
* Use the import script or manual SQL method.<br />
* Required tables:<br />
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).<br />
** <code>mw_tag_pages</code> — one row per approved page.<br />
* If needed, run: <code>php maintenance/update.php --quick</code><br />
{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}<br />
=== 2. Use the Special Page to Switch or Clone ===<br />
<br />
Please note that the Revision is part of this query and display. Any documents that have been approved since the last release should have a new revision and this new revision should be included in the ROUTINE_tag <br />
<br />
* Go to: <code>Special:CustomQuerySettings</code><br />
* Two options:<br />
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.<br />
** '''Clone ROUTINE → New ROUTINE''':<br />
*** From: <code>ROUTINE_4.110</code><br />
*** To: <code>ROUTINE_4.111</code><br />
*** Submit → this copies rows and updates the active tag.<br />
<br />
=== 3. Verify the Result ===<br />
<br />
* Visit: <code>Special:ApprovedManuals</code><br />
* Confirm the listing shows <code>ROUTINE_4.111</code><br />
* Lisa can now publish or review the approved manuals.<br />
* No DB access required.<br />
<br />
= Optional: JSON/API Importer =<br />
<br />
If you're ready to skip the SQL import:<br />
<br />
* Define a JSON payload that includes:<br />
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.<br />
* Build a:<br />
** REST endpoint, or<br />
** Action API module, or<br />
** Maintenance script that reads JSON<br />
<br />
Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.<br />
<br />
{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}</div>Tuxhttps://mw.eckford.ca:443/index.php?title=Rs2&diff=154Rs22026-01-23T21:07:59Z<p>Tux: </p>
<hr />
<div><br />
[[File:pallette.jpg|thumb|right|150px|colour pallette]]<br />
<br />
<br />
An online source of RADARSAT-2 operations data and documentation since launch.<br />
<br />
<h2>Navigation Methods</h2><br />
{{Enhanced|From a desktop machine:}}<br />
<ul><br />
<li>[https://sh1rs2wikidu01.mda.ca/Main_Page <strong>R2 Wiki</strong>] </li><br />
<li>[https://transferdepot.sh1rs2wikidu01.mda.ca <strong>TransferDepot </strong>] </li><br />
<li>[https://sh1rs2wikidu01.mda.ca/Special:ApprovedManuals <strong>Operational Manual Procedures</strong>]</li></ul><br />
<br />
{{Safe|From the Control Room and legacy machines:}}<br />
<ul><br />
<li>[http://142.73.160.81/index.php/Main_Page?useskin=monobook <strong>R2 Wiki</strong> ] </li><br />
<li>[http://142.73.160.62/ <strong>TransferDepot</strong>] </li><br />
<li>[http://142.73.160.81/Special:ApprovedManuals?useskin=monobook <strong>Operational Manual Procedures</strong>] </strong> </li></ul><br />
<br />
== System Configuration ==<br />
<br />
'''MDA R2-Wiki New stuff/should read:'''<BR><br />
[[Cortex|Cortex Explained:]] Mission Control & High level description<BR><br />
-----<br />
[[MissionPriorities| Mission Priorities:]] Top Mission Priorities from SAF, Bugs and projects <BR><br />
[[Current Spacecraft Configuration| Current Spacecraft Configuration:]] Overview of current Spacecraft configuration, subsystem status and performance <BR><br />
[[System_Configuration|Ground System Configuration:]] Ground Segment SW<BR></div>Tuxhttps://mw.eckford.ca:443/index.php?title=Rs2&diff=153Rs22026-01-23T21:07:38Z<p>Tux: </p>
<hr />
<div><br />
[[File:pallette.jpg|thumb|right|250px|colour pallette]]<br />
<br />
<br />
An online source of RADARSAT-2 operations data and documentation since launch.<br />
<br />
<h2>Navigation Methods</h2><br />
{{Enhanced|From a desktop machine:}}<br />
<ul><br />
<li>[https://sh1rs2wikidu01.mda.ca/Main_Page <strong>R2 Wiki</strong>] </li><br />
<li>[https://transferdepot.sh1rs2wikidu01.mda.ca <strong>TransferDepot </strong>] </li><br />
<li>[https://sh1rs2wikidu01.mda.ca/Special:ApprovedManuals <strong>Operational Manual Procedures</strong>]</li></ul><br />
<br />
{{Safe|From the Control Room and legacy machines:}}<br />
<ul><br />
<li>[http://142.73.160.81/index.php/Main_Page?useskin=monobook <strong>R2 Wiki</strong> ] </li><br />
<li>[http://142.73.160.62/ <strong>TransferDepot</strong>] </li><br />
<li>[http://142.73.160.81/Special:ApprovedManuals?useskin=monobook <strong>Operational Manual Procedures</strong>] </strong> </li></ul><br />
<br />
== System Configuration ==<br />
<br />
'''MDA R2-Wiki New stuff/should read:'''<BR><br />
[[Cortex|Cortex Explained:]] Mission Control & High level description<BR><br />
-----<br />
[[MissionPriorities| Mission Priorities:]] Top Mission Priorities from SAF, Bugs and projects <BR><br />
[[Current Spacecraft Configuration| Current Spacecraft Configuration:]] Overview of current Spacecraft configuration, subsystem status and performance <BR><br />
[[System_Configuration|Ground System Configuration:]] Ground Segment SW<BR></div>Tuxhttps://mw.eckford.ca:443/index.php?title=Rs2&diff=152Rs22026-01-23T20:41:32Z<p>Tux: </p>
<hr />
<div><br />
[[File:pallette.jpg|thumb|right|150px|colour pallette]]<br />
<br />
<br />
An online source of RADARSAT-2 operations data and documentation since launch.<br />
<br />
<h2>Navigation Methods</h2><br />
{{Enhanced|From a desktop machine:}}<br />
<ul><br />
<li>[https://sh1rs2wikidu01.mda.ca/Main_Page <strong>R2 Wiki</strong>] </li><br />
<li>[https://transferdepot.sh1rs2wikidu01.mda.ca <strong>TransferDepot </strong>] </li><br />
<li>[https://sh1rs2wikidu01.mda.ca/Special:ApprovedManuals <strong>Operational Manual Procedures</strong>]</li></ul><br />
<br />
{{Safe|From the Control Room and legacy machines:}}<br />
<ul><br />
<li>[http://142.73.160.81/index.php/Main_Page?useskin=monobook <strong>R2 Wiki</strong> ] </li><br />
<li>[http://142.73.160.62/ <strong>TransferDepot</strong>] </li><br />
<li>[http://142.73.160.81/Special:ApprovedManuals?useskin=monobook <strong>Operational Manual Procedures</strong>] </strong> </li></ul><br />
<br />
== System Configuration ==<br />
<br />
'''MDA R2-Wiki New stuff/should read:'''<BR><br />
[[Cortex|Cortex Explained:]] Mission Control & High level description<BR><br />
-----<br />
[[MissionPriorities| Mission Priorities:]] Top Mission Priorities from SAF, Bugs and projects <BR><br />
[[Current Spacecraft Configuration| Current Spacecraft Configuration:]] Overview of current Spacecraft configuration, subsystem status and performance <BR><br />
[[System_Configuration|Ground System Configuration:]] Ground Segment SW<BR></div>Tuxhttps://mw.eckford.ca:443/index.php?title=Rs2&diff=151Rs22026-01-23T20:41:08Z<p>Tux: </p>
<hr />
<div><br />
[[File:pallette.jpg|thumb|left|150px|This is a caption]]<br />
<br />
<br />
An online source of RADARSAT-2 operations data and documentation since launch.<br />
<br />
<h2>Navigation Methods</h2><br />
{{Enhanced|From a desktop machine:}}<br />
<ul><br />
<li>[https://sh1rs2wikidu01.mda.ca/Main_Page <strong>R2 Wiki</strong>] </li><br />
<li>[https://transferdepot.sh1rs2wikidu01.mda.ca <strong>TransferDepot </strong>] </li><br />
<li>[https://sh1rs2wikidu01.mda.ca/Special:ApprovedManuals <strong>Operational Manual Procedures</strong>]</li></ul><br />
<br />
{{Safe|From the Control Room and legacy machines:}}<br />
<ul><br />
<li>[http://142.73.160.81/index.php/Main_Page?useskin=monobook <strong>R2 Wiki</strong> ] </li><br />
<li>[http://142.73.160.62/ <strong>TransferDepot</strong>] </li><br />
<li>[http://142.73.160.81/Special:ApprovedManuals?useskin=monobook <strong>Operational Manual Procedures</strong>] </strong> </li></ul><br />
<br />
== System Configuration ==<br />
<br />
'''MDA R2-Wiki New stuff/should read:'''<BR><br />
[[Cortex|Cortex Explained:]] Mission Control & High level description<BR><br />
-----<br />
[[MissionPriorities| Mission Priorities:]] Top Mission Priorities from SAF, Bugs and projects <BR><br />
[[Current Spacecraft Configuration| Current Spacecraft Configuration:]] Overview of current Spacecraft configuration, subsystem status and performance <BR><br />
[[System_Configuration|Ground System Configuration:]] Ground Segment SW<BR></div>Tuxhttps://mw.eckford.ca:443/index.php?title=Rs2&diff=150Rs22026-01-23T20:38:37Z<p>Tux: </p>
<hr />
<div><br />
[[Image: pallette.jpg |right]]<br />
<br />
An online source of RADARSAT-2 operations data and documentation since launch.<br />
<br />
<h2>Navigation Methods</h2><br />
{{Enhanced|From a desktop machine:}}<br />
<ul><br />
<li>[https://sh1rs2wikidu01.mda.ca/Main_Page <strong>R2 Wiki</strong>] </li><br />
<li>[https://transferdepot.sh1rs2wikidu01.mda.ca <strong>TransferDepot </strong>] </li><br />
<li>[https://sh1rs2wikidu01.mda.ca/Special:ApprovedManuals <strong>Operational Manual Procedures</strong>]</li></ul><br />
<br />
{{Safe|From the Control Room and legacy machines:}}<br />
<ul><br />
<li>[http://142.73.160.81/index.php/Main_Page?useskin=monobook <strong>R2 Wiki</strong> ] </li><br />
<li>[http://142.73.160.62/ <strong>TransferDepot</strong>] </li><br />
<li>[http://142.73.160.81/Special:ApprovedManuals?useskin=monobook <strong>Operational Manual Procedures</strong>] </strong> </li></ul><br />
<br />
== System Configuration ==<br />
<br />
'''MDA R2-Wiki New stuff/should read:'''<BR><br />
[[Cortex|Cortex Explained:]] Mission Control & High level description<BR><br />
-----<br />
[[MissionPriorities| Mission Priorities:]] Top Mission Priorities from SAF, Bugs and projects <BR><br />
[[Current Spacecraft Configuration| Current Spacecraft Configuration:]] Overview of current Spacecraft configuration, subsystem status and performance <BR><br />
[[System_Configuration|Ground System Configuration:]] Ground Segment SW<BR></div>Tuxhttps://mw.eckford.ca:443/index.php?title=Rs2&diff=149Rs22026-01-23T20:37:09Z<p>Tux: </p>
<hr />
<div><br />
<br />
<br />
An online source of RADARSAT-2 operations data and documentation since launch.<br />
<br />
<h2>Navigation Methods</h2><br />
{{Enhanced|From a desktop machine:}}<br />
<ul><br />
<li>[https://sh1rs2wikidu01.mda.ca/Main_Page <strong>R2 Wiki</strong>] </li><br />
<li>[https://transferdepot.sh1rs2wikidu01.mda.ca <strong>TransferDepot </strong>] </li><br />
<li>[https://sh1rs2wikidu01.mda.ca/Special:ApprovedManuals <strong>Operational Manual Procedures</strong>]</li></ul><br />
<br />
{{Safe|From the Control Room and legacy machines:}}<br />
<ul><br />
<li>[http://142.73.160.81/index.php/Main_Page?useskin=monobook <strong>R2 Wiki</strong> ] </li><br />
<li>[http://142.73.160.62/ <strong>TransferDepot</strong>] </li><br />
<li>[http://142.73.160.81/Special:ApprovedManuals?useskin=monobook <strong>Operational Manual Procedures</strong>] </strong> </li></ul><br />
<br />
== System Configuration ==<br />
<br />
'''MDA R2-Wiki New stuff/should read:'''<BR><br />
[[Cortex|Cortex Explained:]] Mission Control & High level description<BR><br />
-----<br />
[[MissionPriorities| Mission Priorities:]] Top Mission Priorities from SAF, Bugs and projects <BR><br />
[[Current Spacecraft Configuration| Current Spacecraft Configuration:]] Overview of current Spacecraft configuration, subsystem status and performance <BR><br />
[[System_Configuration|Ground System Configuration:]] Ground Segment SW<BR></div>Tuxhttps://mw.eckford.ca:443/index.php?title=Rs2&diff=148Rs22026-01-23T20:32:56Z<p>Tux: </p>
<hr />
<div><br />
[[Image: pallette.jpg |right]]<br />
<br />
An online source of RADARSAT-2 operations data and documentation since launch.<br />
<br />
<h2>Navigation Methods</h2><br />
{{Enhanced|From a desktop machine:}}<br />
<ul><br />
<li>[https://sh1rs2wikidu01.mda.ca/Main_Page <strong>R2 Wiki</strong>] </li><br />
<li>[https://transferdepot.sh1rs2wikidu01.mda.ca <strong>TransferDepot </strong>] </li><br />
<li>[https://sh1rs2wikidu01.mda.ca/Special:ApprovedManuals <strong>Operational Manual Procedures</strong>]</li></ul><br />
<br />
{{Safe|From the Control Room and legacy machines:}}<br />
<ul><br />
<li>[http://142.73.160.81/index.php/Main_Page?useskin=monobook <strong>R2 Wiki</strong> ] </li><br />
<li>[http://142.73.160.62/ <strong>TransferDepot</strong>] </li><br />
<li>[http://142.73.160.81/Special:ApprovedManuals?useskin=monobook <strong>Operational Manual Procedures</strong>] </strong> </li></ul><br />
<br />
== System Configuration ==<br />
<br />
'''MDA R2-Wiki New stuff/should read:'''<BR><br />
[[Cortex|Cortex Explained:]] Mission Control & High level description<BR><br />
-----<br />
[[MissionPriorities| Mission Priorities:]] Top Mission Priorities from SAF, Bugs and projects <BR><br />
[[Current Spacecraft Configuration| Current Spacecraft Configuration:]] Overview of current Spacecraft configuration, subsystem status and performance <BR><br />
[[System_Configuration|Ground System Configuration:]] Ground Segment SW<BR></div>Tuxhttps://mw.eckford.ca:443/index.php?title=Rs2&diff=147Rs22026-01-23T20:32:43Z<p>Tux: </p>
<hr />
<div><br />
<br />
<br />
An online source of RADARSAT-2 operations data and documentation since launch.<br />
<br />
<h2>Navigation Methods</h2><br />
{{Enhanced|From a desktop machine:}}<br />
<ul><br />
<li>[https://sh1rs2wikidu01.mda.ca/Main_Page <strong>R2 Wiki</strong>] </li><br />
<li>[https://transferdepot.sh1rs2wikidu01.mda.ca <strong>TransferDepot </strong>] </li><br />
<li>[https://sh1rs2wikidu01.mda.ca/Special:ApprovedManuals <strong>Operational Manual Procedures</strong>]</li></ul><br />
<br />
{{Safe|From the Control Room and legacy machines:}}<br />
<ul><br />
<li>[http://142.73.160.81/index.php/Main_Page?useskin=monobook <strong>R2 Wiki</strong> ] </li><br />
<li>[http://142.73.160.62/ <strong>TransferDepot</strong>] </li><br />
<li>[http://142.73.160.81/Special:ApprovedManuals?useskin=monobook <strong>Operational Manual Procedures</strong>] </strong> </li></ul><br />
<br />
== System Configuration ==<br />
<br />
'''MDA R2-Wiki New stuff/should read:'''<BR><br />
[[Cortex|Cortex Explained:]] Mission Control & High level description<BR><br />
-----<br />
[[MissionPriorities| Mission Priorities:]] Top Mission Priorities from SAF, Bugs and projects <BR><br />
[[Current Spacecraft Configuration| Current Spacecraft Configuration:]] Overview of current Spacecraft configuration, subsystem status and performance <BR><br />
[[System_Configuration|Ground System Configuration:]] Ground Segment SW<BR></div>Tuxhttps://mw.eckford.ca:443/index.php?title=File:Pallette.jpg&diff=146File:Pallette.jpg2026-01-23T20:31:47Z<p>Tux: Tux uploaded a new version of File:Pallette.jpg</p>
<hr />
<div></div>Tuxhttps://mw.eckford.ca:443/index.php?title=Rs2&diff=145Rs22026-01-23T20:31:20Z<p>Tux: </p>
<hr />
<div><br />
[[Image: spallette.jpg |right]]<br />
<br />
An online source of RADARSAT-2 operations data and documentation since launch.<br />
<br />
<h2>Navigation Methods</h2><br />
{{Enhanced|From a desktop machine:}}<br />
<ul><br />
<li>[https://sh1rs2wikidu01.mda.ca/Main_Page <strong>R2 Wiki</strong>] </li><br />
<li>[https://transferdepot.sh1rs2wikidu01.mda.ca <strong>TransferDepot </strong>] </li><br />
<li>[https://sh1rs2wikidu01.mda.ca/Special:ApprovedManuals <strong>Operational Manual Procedures</strong>]</li></ul><br />
<br />
{{Safe|From the Control Room and legacy machines:}}<br />
<ul><br />
<li>[http://142.73.160.81/index.php/Main_Page?useskin=monobook <strong>R2 Wiki</strong> ] </li><br />
<li>[http://142.73.160.62/ <strong>TransferDepot</strong>] </li><br />
<li>[http://142.73.160.81/Special:ApprovedManuals?useskin=monobook <strong>Operational Manual Procedures</strong>] </strong> </li></ul><br />
<br />
== System Configuration ==<br />
<br />
'''MDA R2-Wiki New stuff/should read:'''<BR><br />
[[Cortex|Cortex Explained:]] Mission Control & High level description<BR><br />
-----<br />
[[MissionPriorities| Mission Priorities:]] Top Mission Priorities from SAF, Bugs and projects <BR><br />
[[Current Spacecraft Configuration| Current Spacecraft Configuration:]] Overview of current Spacecraft configuration, subsystem status and performance <BR><br />
[[System_Configuration|Ground System Configuration:]] Ground Segment SW<BR></div>Tuxhttps://mw.eckford.ca:443/index.php?title=File:Pallette.jpg&diff=144File:Pallette.jpg2026-01-23T20:27:11Z<p>Tux: </p>
<hr />
<div></div>Tux