MediaWiki-1.39 - User contributions [en]

Rs2

2026-01-23T18:37:38Z

Admin:

[[Image:https://docs.eckford.ca/a-74jpg|right|thumb|250px|This is the caption]]

An online source of RADARSAT-2 operations data and documentation since launch.

<h2>Navigation Methods</h2>
{{Enhanced|From a desktop machine:}}
<ul>
<li>[https://sh1rs2wikidu01.mda.ca/Main_Page <strong>R2 Wiki</strong>] </li>
<li>[https://transferdepot.sh1rs2wikidu01.mda.ca <strong>TransferDepot </strong>] </li>
<li>[https://sh1rs2wikidu01.mda.ca/Special:ApprovedManuals <strong>Operational Manual Procedures</strong>]</li></ul>

{{Safe|From the Control Room and legacy machines:}}
<ul>
<li>[http://142.73.160.81/index.php/Main_Page?useskin=monobook <strong>R2 Wiki</strong> ] </li>
<li>[http://142.73.160.62/ <strong>TransferDepot</strong>] </li>
<li>[http://142.73.160.81/Special:ApprovedManuals?useskin=monobook <strong>Operational Manual Procedures</strong>] </strong> </li></ul>

== System Configuration ==

'''MDA R2-Wiki New stuff/should read:'''<BR>
[[Cortex|Cortex Explained:]] Mission Control & High level description<BR>
-----
[[MissionPriorities| Mission Priorities:]] Top Mission Priorities from SAF, Bugs and projects <BR>
[[Current Spacecraft Configuration| Current Spacecraft Configuration:]] Overview of current Spacecraft configuration, subsystem status and performance <BR>
[[System_Configuration|Ground System Configuration:]] Ground Segment SW<BR>

Template:Info

2026-01-23T18:11:20Z

Admin:

<div style="border-left: 4px solid #3498db; background: #eaf2f8; padding: 0.8em; margin: 1 em 0;">
<strong>Info:</strong> {{{1}}}
</div>
<noinclude>
[[Category:Templates]]
</noinclude>

MediaWiki:Sidebar

2026-01-23T18:10:19Z

Admin:

* navigation
** mainpage|mainpage-description
** Rs2|rs2
** recentchanges-url|recentchanges
** randompage-url|randompage
** helppage|help-mediawiki
** MediaWiki_Tips|MW for the Sh1re
** MediaWiki:Sidebar|MediaWiki Sidebar
** Special:AllPages/Template:|Templates
** purge-main|Purge Main Page
* SEARCH
* TOOLBOX
* LANGUAGES

<h3> Now you can</h3>
<p>This one was different</p>
<pre>** MediaWiki:Sidebar|MediaWiki Sidebar</p>
<p>
Link to other MediaWiki: pages (like MediaWiki:Common.css, MediaWiki:Mainpage-description), just remember to include the full namespace like MediaWiki:Mainpage-description </p>

MediaWiki:Sidebar

2026-01-23T18:09:48Z

Admin:

* navigation
** mainpage|mainpage-description
** MediaWiki:Rs2|rs2
** recentchanges-url|recentchanges
** randompage-url|randompage
** helppage|help-mediawiki
** MediaWiki_Tips|MW for the Sh1re
** MediaWiki:Sidebar|MediaWiki Sidebar
** Special:AllPages/Template:|Templates
** purge-main|Purge Main Page
* SEARCH
* TOOLBOX
* LANGUAGES

<h3> Now you can</h3>
<p>This one was different</p>
<pre>** MediaWiki:Sidebar|MediaWiki Sidebar</p>
<p>
Link to other MediaWiki: pages (like MediaWiki:Common.css, MediaWiki:Mainpage-description), just remember to include the full namespace like MediaWiki:Mainpage-description </p>

Template:Notice

2026-01-22T20:35:47Z

Admin:

<div class="mw-note" style="margin: 1em 0; padding: 5px 10px; border-left: 5px solid #36c; background-color: #f8f9fa; border-radius: 2px;">
<strong>Upcoming Event:</strong> {{{event_name|Annual Community Meetup}}} <br />
<small>Scheduled for: {{{date|TBA}}} at {{{location|Main Hall}}}</small>
<p style="margin-top: 5px; font-size: 0.9em;">{{{description|Join us for our yearly gathering to discuss upcoming wiki projects and milestones!}}}</p>
</div>
<noinclude>
[[Category:Templates]]
</noinclude>

Main Page

2026-01-22T20:25:46Z

Admin:

<strong>MediaWiki has been installed.</strong>
{{Notice
| event_name = Wiki launch
| date = January 12th
| location = Lisa's Desk
| description = Don't forget to cast your vote for the next wiki admin!
}}
== Import CustomQueryPage ==
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?

== Let's Get Started ==

* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]

=== Installing CustomQueryPage ===
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code>
* Extract it into your extensions folder:
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code>
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code>
* Run <code>php maintenance/update.php --quick</code>.
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.

= Quick Start: ROUTINE Management =

=== 1. Seed the ROUTINE in the DB ===
Before Lisa touches the UI, make sure the database has ROUTINE data.

* Use the import script or manual SQL method.
* Required tables:
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).
** <code>mw_tag_pages</code> — one row per approved page.
* If needed, run: <code>php maintenance/update.php --quick</code>

{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}

=== 2. Use the Special Page to Switch or Clone ===

* Go to: <code>Special:CustomQuerySettings</code>
* Two options:
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.
** '''Clone ROUTINE → New ROUTINE''':
*** From: <code>ROUTINE_4.110</code>
*** To: <code>ROUTINE_4.111</code>
*** Submit → this copies rows and updates the active tag.

=== 3. Verify the Result ===

* Visit: <code>Special:ApprovedManuals</code>
* Confirm the listing shows <code>ROUTINE_4.111</code>
* Lisa can now publish or review the approved manuals.
* No DB access required.

= Optional: JSON/API Importer =

If you're ready to skip the SQL import:

* Define a JSON payload that includes:
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.
* Build a:
** REST endpoint, or
** Action API module, or
** Maintenance script that reads JSON

Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.

{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}

Main Page

2026-01-22T20:25:36Z

Admin:

<strong>MediaWiki has been installed.</strong>
{{Notice
| event_name = Wiki launch
| date = January 12th
| location = Lisa's Desk
| description = Don't forget to cast your vote for the next wiki admin!
}}

== Import CustomQueryPage ==
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?

== Let's Get Started ==

* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]

=== Installing CustomQueryPage ===
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code>
* Extract it into your extensions folder:
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code>
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code>
* Run <code>php maintenance/update.php --quick</code>.
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.

= Quick Start: ROUTINE Management =

=== 1. Seed the ROUTINE in the DB ===
Before Lisa touches the UI, make sure the database has ROUTINE data.

* Use the import script or manual SQL method.
* Required tables:
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).
** <code>mw_tag_pages</code> — one row per approved page.
* If needed, run: <code>php maintenance/update.php --quick</code>

{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}

=== 2. Use the Special Page to Switch or Clone ===

* Go to: <code>Special:CustomQuerySettings</code>
* Two options:
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.
** '''Clone ROUTINE → New ROUTINE''':
*** From: <code>ROUTINE_4.110</code>
*** To: <code>ROUTINE_4.111</code>
*** Submit → this copies rows and updates the active tag.

=== 3. Verify the Result ===

* Visit: <code>Special:ApprovedManuals</code>
* Confirm the listing shows <code>ROUTINE_4.111</code>
* Lisa can now publish or review the approved manuals.
* No DB access required.

= Optional: JSON/API Importer =

If you're ready to skip the SQL import:

* Define a JSON payload that includes:
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.
* Build a:
** REST endpoint, or
** Action API module, or
** Maintenance script that reads JSON

Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.

{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}

Template:Notice

2026-01-22T20:13:51Z

Admin:

<div class="mw-note" style="margin: 1em 0; padding: 10px 15px; border-left: 5px solid #36c; background-color: #f8f9fa; border-radius: 2px;">
<strong>Upcoming Event:</strong> {{{event_name|Annual Community Meetup}}} <br />
<small>Scheduled for: {{{date|TBA}}} at {{{location|Main Hall}}}</small>
<p style="margin-top: 5px; font-size: 0.9em;">{{{description|Join us for our yearly gathering to discuss upcoming wiki projects and milestones!}}}</p>
</div>

<noinclude>
[[Category:Templates]]
</noinclude>

Template:Note

2026-01-22T19:55:47Z

Admin:

<div class="mw-note" style="border-left: 5px solid #36c; background-color: #eef; padding: 0.8em; margin: 1em 0;">
<strong>Note:</strong> {{{1}}}
</div>

<noinclude>
[[Category:Templates]]
</noinclude>

Template:Documentation

2026-01-22T19:55:07Z

Admin:

<div style="padding: 10px; background: #f0f0f0; border: 1px solid #aaa; margin-bottom: 1em;">
'''This is a documentation subpage.''' It contains usage information, categories, and other content that is not part of the original template page.
</div>

<p> include the docs with /docs </p>

<noinclude>
[[Category:Templates]]
</noinclude>

Template:Documentation

2026-01-22T19:54:19Z

Admin:

Template:Documentation

2026-01-22T19:53:53Z

Admin:

<div style="float: right;">
[ {{fullurl:{{PAGENAME}}|action=edit}} Edit Doc ] | [ {{fullurl:{{BASEPAGENAME}}|action=edit}} Edit Code ]
</div>

<br />

<br />

<div style="padding: 10px; background: #f0f0f0; border: 1px solid #aaa; margin-bottom: 1em;">
'''This is a documentation subpage.''' It contains usage information, categories, and other content that is not part of the original template page.
</div>

<noinclude>
[[Category:Templates]]
</noinclude>

Template:Documentation

2026-01-22T19:52:05Z

Admin:

Template:Tip

2026-01-22T19:35:43Z

Admin:

<div class="mw-tpl-tip" style="margin: 1em 0; border: 1px solid #a2a9b1; background-color: #f8f9fa; padding: 10px; border-left: 10px solid #36c; display: flex; align-items: center;">
<div style="margin-right: 15px; font-size: 24px;">💡</div>
<div style="flex-grow: 1;">
'''Tip:''' {{{1|Your tip text goes here.}}}
</div>
</div>

<noinclude>{{documentation}}</noinclude>

<noinclude>
[[Category:Templates]]
</noinclude>

Template:Warning

2026-01-22T19:31:45Z

Admin:

<div style="border-left: 4px solid #c00; background: #fee; padding: 10px; border-left: 10px solid #36c; display: flex; align-items: center;">
<div style="margin-right: 15px; font-size: 24px;">⚠️</div>
<div style="flex-grow: 1;">
<strong>Warning:</strong> {{{1}}}
</div>

<noinclude>
[[Category:Templates]]
</noinclude>

Template:Tip

2026-01-22T19:29:01Z

Admin:

Template:Info

2026-01-22T19:28:25Z

Admin:

<div style="border-left: 4px solid #3498db; background: #eaf2f8; padding: 0.8em; margin: 1 em 0;">
<strong>Info:</strong> {{{1}}}
</div>

<noinclude>
[[Category:Templates]]
</noinclude>

Template:Warning

2026-01-22T19:26:55Z

Admin:

<div style="border-left: 4px solid #c00; background: #fee; padding: 0.8em; margin: 1em 0;">
<strong>Warning:</strong> {{{1}}}
</div>

<noinclude>
[[Category:Templates]]
</noinclude>

Template:Warning

2026-01-22T19:26:29Z

Admin:

<div style="border-left: 4px solid #c00; background: #fee; padding: 0.8em; margin: 1em 0;">
<strong>Warning:</strong> {{{1}}}
</div>

<noinclude>
[[Category:Templates]]
</noinclude>

Template:Tip

2026-01-22T19:24:04Z

Admin:

Template:Notice

2026-01-22T19:22:46Z

Admin:

<div class="mw-note" style="border-left: 5px solid #36c; background-color: #eef; padding: 0.8em; margin: 1em 0;">
<strong>Notice:</strong> {{{1}}}
</div>
<noinclude>
<h3>Usage:</h3>
To display the text as above just add the call from your page in this format.

<pre>
{{Notice|This is helpful context.}}
</pre>
</noinclude>

<noinclude>
[[Category:Templates]]
</noinclude>

Template:Documentation

2026-01-22T19:22:16Z

Admin:

The simplest use of templates is as follows: Create a page called <tvar name=1><code>Template:Welcome</code></tvar> with the content below:
</translate>

<translate> Hello! Welcome to the wiki.</translate>

<translate>

You have created your first template! Now, insert the code below in a new page:
</translate>

<noinclude>
[[Category:Templates]]
</noinclude>

Template:Hatnote

2026-01-22T19:22:02Z

Admin:

<div role="note" class="hatnote" style="font-style: italic; margin-bottom: 0.5em; padding-left: 1.6em;">
{{{1}}}
</div>

<noinclude>
[[Category:Templates]]
</noinclude>

Template:Hatnote

2026-01-22T19:17:38Z

Admin:

<div role="note" class="hatnote" style="font-style: italic; margin-bottom: 0.5em; padding-left: 1.6em;">
{{{1}}}
</div>

[[:Category:Templates]]

Template:Info

2026-01-22T18:51:35Z

Admin:

<div style="border-left: 4px solid #3498db; background: #eaf2f8; padding: 0.8em; margin: 1 em 0;">
<strong>Info:</strong> {{{1}}}
</div>

[[:Category:Templates]]

Purge Main Page

2026-01-22T01:51:33Z

Admin:

MediaWiki:Purge-main-url

2026-01-22T01:51:00Z

Admin: Created page with "{{fullurl:Main Page|action=purge}}"

Purge Main Page

2026-01-22T01:48:04Z

Admin:

/index.php?title=Main_Page&action=purge

Purge Main Page

2026-01-22T01:46:14Z

Admin: Created page with "Purge Main Page"

Purge Main Page

MediaWiki:Purge-main

2026-01-22T01:45:12Z

Admin: Created page with "Purge Main Page"

Purge Main Page

MediaWiki:Sidebar

2026-01-22T01:44:41Z

Admin:

Main Page

2026-01-22T00:58:06Z

Admin: /* Import CustomQueryPage */

<strong>MediaWiki has been installed.</strong>

== Import CustomQueryPage ==
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?

== Let's Get Started ==

* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]

=== Installing CustomQueryPage ===
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code>
* Extract it into your extensions folder:
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code>
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code>
* Run <code>php maintenance/update.php --quick</code>.
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.

= Quick Start: ROUTINE Management =

=== 1. Seed the ROUTINE in the DB ===
Before Lisa touches the UI, make sure the database has ROUTINE data.

* Use the import script or manual SQL method.
* Required tables:
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).
** <code>mw_tag_pages</code> — one row per approved page.
* If needed, run: <code>php maintenance/update.php --quick</code>

{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}

=== 2. Use the Special Page to Switch or Clone ===

* Go to: <code>Special:CustomQuerySettings</code>
* Two options:
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.
** '''Clone ROUTINE → New ROUTINE''':
*** From: <code>ROUTINE_4.110</code>
*** To: <code>ROUTINE_4.111</code>
*** Submit → this copies rows and updates the active tag.

=== 3. Verify the Result ===

* Visit: <code>Special:ApprovedManuals</code>
* Confirm the listing shows <code>ROUTINE_4.111</code>
* Lisa can now publish or review the approved manuals.
* No DB access required.

= Optional: JSON/API Importer =

If you're ready to skip the SQL import:

* Define a JSON payload that includes:
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.
* Build a:
** REST endpoint, or
** Action API module, or
** Maintenance script that reads JSON

Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.

{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}

Main Page

2026-01-22T00:57:29Z

Admin: This install is originally intended for the ROUTINE Manuals publication workflow.

<strong>MediaWiki has been installed.</strong>

== Import CustomQueryPage ==
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?

* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]

=== Installing CustomQueryPage ===
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code>
* Extract it into your extensions folder:
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code>
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code>
* Run <code>php maintenance/update.php --quick</code>.
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.

= Quick Start: ROUTINE Management =

=== 1. Seed the ROUTINE in the DB ===
Before Lisa touches the UI, make sure the database has ROUTINE data.

* Use the import script or manual SQL method.
* Required tables:
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).
** <code>mw_tag_pages</code> — one row per approved page.
* If needed, run: <code>php maintenance/update.php --quick</code>

{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}

=== 2. Use the Special Page to Switch or Clone ===

* Go to: <code>Special:CustomQuerySettings</code>
* Two options:
** '''Set Active Tag''' — type <code>ROUTINE_4.111</code>, then Save.
** '''Clone ROUTINE → New ROUTINE''':
*** From: <code>ROUTINE_4.110</code>
*** To: <code>ROUTINE_4.111</code>
*** Submit → this copies rows and updates the active tag.

=== 3. Verify the Result ===

* Visit: <code>Special:ApprovedManuals</code>
* Confirm the listing shows <code>ROUTINE_4.111</code>
* Lisa can now publish or review the approved manuals.
* No DB access required.

= Optional: JSON/API Importer =

If you're ready to skip the SQL import:

* Define a JSON payload that includes:
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.
* Build a:
** REST endpoint, or
** Action API module, or
** Maintenance script that reads JSON

Once defined, MediaWiki can import directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.

{{Warning|Avoid touching the database manually if you want to adopt the JSON route. The importer will safely handle all insertions.}}

MediaWiki Tips

2026-01-22T00:52:40Z

Admin: /* See also */

= MediaWiki Tips =

This page collects useful formatting techniques, admin tricks, and style conventions used across the Sh1re Commons and related wikis (e.g. Eckfordc). Contributions welcome.

== Naming, Linking, and Underscores ==

MediaWiki converts spaces to underscores (`MediaWiki_Tips` → `MediaWiki Tips`).

You can also use internal links like this:

<pre>
[[MediaWiki Tips]]
</pre>

If the page doesn’t exist, it shows up as a red link — clicking it lets you create the page directly.

== Template Styling ==

=== {{Note}} ===

{{Note|Use this template to show helpful callouts like this one.}}

Create or edit the template here: [[Template:Note]]

Paste this code:

<pre>
<div style="border-left: 4px solid #36c; background: #eef; padding: 0.8em; margin: 1em 0;">
<strong>Note:</strong> {{{1}}}
</div>
</pre>

=== {{Warning}} ===

{{Warning|Use this template to flag risky actions, like editing core DB tables.}}

Create/edit [[Template:Warning]] with this:

<pre>
<div style="border-left: 4px solid #c00; background: #fee; padding: 0.8em; margin: 1em 0;">
<strong>Warning:</strong> {{{1}}}
</div>
</pre>

== Zero-JS Enhancements ==

This wiki stack is hardened for legacy environments — no JavaScript required. Where others use JS libraries, we prefer:

* **Pure HTML/CSS** navigation boxes and style blocks
* **Table of contents** via headings (e.g. `== Section ==`)
* **No collapsibles or toggles** (unless emulated with `<details>` in supported browsers)
* Minimal inline CSS for color blocks, tooltips, and alerts

== Recommended Conventions ==

* Use `<code>` for inline paths and scripts: <code>php maintenance/update.php</code>
* Use `<pre>` or `<syntaxhighlight lang="bash">` for CLI blocks
* All admin helper pages should be tagged like this:

<pre>
[[Category:Documentation]]
</pre>

== See also ==

* [[Special:CustomQuerySettings]] — ROUTINE tag management
* [[Special:ApprovedManuals]] — View approved manuals by tag
* [[Template:Note]] / [[Template:Warning]] — for styling callouts

[[Category:Documentation]]

MediaWiki:Sidebar

2026-01-22T00:52:01Z

Admin:

MediaWiki:Sidebar

2026-01-22T00:50:33Z

Admin:

MediaWiki:Sidebar

2026-01-22T00:49:48Z

MediaWiki Tips

2026-01-22T00:46:40Z

Admin: /* See also */

= MediaWiki Tips =

This page collects useful formatting techniques, admin tricks, and style conventions used across the Sh1re Commons and related wikis (e.g. Eckfordc). Contributions welcome.

== Naming, Linking, and Underscores ==

MediaWiki converts spaces to underscores (`MediaWiki_Tips` → `MediaWiki Tips`).

You can also use internal links like this:

<pre>
[[MediaWiki Tips]]
</pre>

If the page doesn’t exist, it shows up as a red link — clicking it lets you create the page directly.

== Template Styling ==

=== {{Note}} ===

{{Note|Use this template to show helpful callouts like this one.}}

Create or edit the template here: [[Template:Note]]

Paste this code:

<pre>
<div style="border-left: 4px solid #36c; background: #eef; padding: 0.8em; margin: 1em 0;">
<strong>Note:</strong> {{{1}}}
</div>
</pre>

=== {{Warning}} ===

{{Warning|Use this template to flag risky actions, like editing core DB tables.}}

Create/edit [[Template:Warning]] with this:

<pre>
<div style="border-left: 4px solid #c00; background: #fee; padding: 0.8em; margin: 1em 0;">
<strong>Warning:</strong> {{{1}}}
</div>
</pre>

== Zero-JS Enhancements ==

This wiki stack is hardened for legacy environments — no JavaScript required. Where others use JS libraries, we prefer:

* **Pure HTML/CSS** navigation boxes and style blocks
* **Table of contents** via headings (e.g. `== Section ==`)
* **No collapsibles or toggles** (unless emulated with `<details>` in supported browsers)
* Minimal inline CSS for color blocks, tooltips, and alerts

== Recommended Conventions ==

* Use `<code>` for inline paths and scripts: <code>php maintenance/update.php</code>
* Use `<pre>` or `<syntaxhighlight lang="bash">` for CLI blocks
* All admin helper pages should be tagged like this:

<pre>
[[Category:Documentation]]
</pre>

== See also ==

* [[Special:CustomQuerySettings]] — ROUTINE tag management
* [[Special:ApprovedManuals]] — View approved manuals by tag
* [[Special:ApprovedManuals]] -
* [[Template:Note]] / [[Template:Warning]] — for styling callouts

[[Category:Documentation]]

MediaWiki Tips

2026-01-22T00:45:01Z

Admin: Created page with " = MediaWiki Tips = This page collects useful formatting techniques, admin tricks, and style conventions used across the Sh1re Commons and related wikis (e.g. Eckfordc). Contributions welcome. == Naming, Linking, and Underscores == MediaWiki converts spaces to underscores (`MediaWiki_Tips` → `MediaWiki Tips`). You can also use internal links like this: <pre> MediaWiki Tips </pre> If the page doesn’t exist, it shows up as a red link — clicking it lets you..."

Template:Warning

2026-01-22T00:15:09Z

Admin: Created page with "<div style="border-left: 4px solid #c00; background: #fee; padding: 0.8em; margin: 1em 0;"> <strong>Warning:</strong> {{{1}}} </div>"

<div style="border-left: 4px solid #c00; background: #fee; padding: 0.8em; margin: 1em 0;">
<strong>Warning:</strong> {{{1}}}
</div>

Main Page

2026-01-22T00:12:50Z

Admin: add templates

Template:Note

2026-01-21T23:58:40Z

Admin: Created page with "<div class="mw-note" style="border-left: 5px solid #36c; background-color: #eef; padding: 0.8em; margin: 1em 0;"> <strong>Note:</strong> {{{1}}} </div> <noinclude> This is the <code>{{Note}}</code> template. Use it to highlight general tips or context. Usage: <pre> {{Note|This is helpful context.}} </pre> </noinclude>"

<div class="mw-note" style="border-left: 5px solid #36c; background-color: #eef; padding: 0.8em; margin: 1em 0;">
<strong>Note:</strong> {{{1}}}
</div>
<noinclude>
This is the <code>{{Note}}</code> template. Use it to highlight general tips or context.

Usage:
<pre>
{{Note|This is helpful context.}}
</pre>
</noinclude>

Main Page

2026-01-21T23:56:48Z

Admin: Formatting courtesy of ChatGPT 4o

<strong>MediaWiki has been installed.</strong>

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

== Import CustomQueryPage ==
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]

=== Installing CustomQueryPage ===
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code>
* Extract it into your extensions folder:
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code>
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code>
* Run <code>php maintenance/update.php --quick</code>.
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.

= Where We Stand =

* '''CustomQueryPage''' now ships with a simplified clone path:
** ''Special:CustomQuerySettings'' copies the ''mw_tag_pages'' rows from ''ROUTINE_4.110'' to ''ROUTINE_4.111'',
** clones the ''mw_tags'' row,
** and immediately points the listing at the new tag.
** Success banner fixed; README documents the exact steps (see the new ''"Quick clone workflow"'').
* On sh1re/sh0re we never finished the MediaWiki core patch that deletes ''mw_logging.log_user*''.
** We seeded ''mw_customquerypage_settings'' manually instead so Lisa could keep using the UI.

== Why mw_tags felt “bypassed” during export ==

* On dev we inserted the active tag row directly into ''mw_customquerypage_settings''; the clone form still expects
the regular ''mw_tags'' / ''mw_tag_pages'' tables.
** If those tables contain the ''4.110'' data (they should after your MySQL import), the UI will re-use them.
** If the environment you tested lacked ''mw_tags'', we need to confirm the table exists and is populated before cloning.
* There’s nothing special to reference in ''LocalSettings.php''; MediaWiki core creates ''mw_tags'' / ''mw_tag_pages''
automatically.
** Our extension simply reads/writes them via the load balancer.

== Next steps if you want to exercise it on mw.eckford.ca ==

# Copy ''extensions-mw1359/CustomQueryPage'' to the MW 1.39 box.
# Ensure ''mw_tags'' / ''mw_tag_pages'' have at least one ROUTINE (e.g., import ''ROUTINE_4.110'').
# Visit ''Special:CustomQuerySettings'', confirm the clone form works end-to-end:
#* new ''mw_tags'' row
#* ApprovedManuals listing updated
# Once Lisa confirms the UI covers her release work (set tag + clone), we can document the progressive-release workflow on her admin page.

If that 1.39 run reveals that ''mw_tags'' truly doesn’t exist in that environment, we’ll know we must create it
(or point the extension at your custom release table).

Otherwise, the existing code already ties directly into ''mw_tags'', so maintaining progressive releases is just a matter of Lisa cloning each ROUTINE and then toggling the Approved Manuals view as you outlined.

= Recap (Last Week → Now) =

* Finished the MW 1.35.9 ''CustomQueryPage'' build with the simplified clone workflow so Lisa can re-tag approved releases inside MediaWiki.
** ''Special:CustomQuerySettings'' now handles both:
*** ''Set active tag''
*** ''Clone ROUTINE_x.xxx → ROUTINE_y.yyy''
* Deployed the same bits to ''eckfordc'' (MW 1.39) and ''sh1re/sh0re''.
** The tables you saw (''mw_tags'' / ''mw_tag_pages'' plus ''mw_customquerypage_settings'') match what the extension uses.
* ''update.php'' keeps screaming about dropping legacy logging indexes.
** On dev we skipped the patch and seeded the settings table manually.
** Production installs just need to run update once so ''mw_customquerypage_settings'' exists.

== Where we landed ==

* DB access for humans stays off the table:
** whoever preps the ROUTINE export runs the existing script/import
** Lisa only touches the Special pages
* The ROUTINE clone form is working end-to-end:
** confirmed by the success banner
** ApprovedManuals shows ''ROUTINE_4.111''
** the README now documents the exact steps
* No special mention of ''mw_tags'' in ''LocalSettings.php'' is required.
** It’s core schema, and the extension already hits it directly.

== Next step: JSON/API practice ==

* Since new ROUTINEs are usually just re-tagging existing pages (rarely brand-new content), the current clone form covers the common path.
* If you want to practice building a JSON/API importer for the rare cases when a ROUTINE bundle comes from outside:
** define the payload first
** describe the data coming out of your export process:
*** page_id
*** rev_id
*** deploy_comment
*** wikitext
*** etc.
** decide whether you want:
*** a REST endpoint
*** an Action API module
*** a CLI maintenance script that reads JSON
** once we agree on the schema, I can wire the MediaWiki-side code so Lisa (or a bot) can feed in the new release without touching MySQL
```

Next we can also convert the “ROUTINE_x.xxx → ROUTINE_y.yyy” bits into `<code>` style and wrap the “update.php” warning into a warning box format (using templates like `{{Note}}` / `{{Warning}}` if our wiki has them).

= Quick Start: ROUTINE Management =

=== 1. Seed the ROUTINE in the DB ===
Before Lisa touches the UI, make sure the database has ROUTINE data.

* Use the import script or manual SQL method.
* Required tables:
** <code>mw_tags</code> — one row per ROUTINE (e.g., <code>ROUTINE_4.111</code>).
** <code>mw_tag_pages</code> — one row per approved page.
* If needed, run: <code>php maintenance/update.php --quick</code>

{{Note|Only run <code>update.php</code> if <code>mw_customquerypage_settings</code> doesn't exist yet.}}

=== 2. Use the Special Page to Switch or Clone ===

* Go to: <code>Special:CustomQuerySettings</code>
* Two options:
** **Set Active Tag** — type <code>ROUTINE_4.111</code>, then Save.
** **Clone ROUTINE → New ROUTINE**:
*** From: <code>ROUTINE_4.110</code>
*** To: <code>ROUTINE_4.111</code>
*** Submit → this copies rows and updates the active tag.

=== 3. Verify the Result ===

* Visit: <code>Special:ApprovedManuals</code>
* Confirm the listing shows <code>ROUTINE_4.111</code>
* Lisa can now publish or review the approved manuals.
* No DB access required.

= Optional: JSON/API Importer =

If you're ready to skip the SQL import:

* Define a JSON payload that includes:
** <code>page_id</code>, <code>rev_id</code>, <code>deploy_comment</code>, <code>wikitext</code>, etc.
* Build a:
** REST endpoint, or
** Action API module, or
** Maintenance script that reads JSON

Once defined, we’ll wire MediaWiki to import it directly into <code>mw_tags</code> / <code>mw_tag_pages</code>.
Lisa keeps working via Special pages — nothing changes for her.

{{Warning|Avoid touching the DB manually if you want to adopt the JSON route. The importer will handle safe insertion.}}

Main Page

2026-01-21T23:47:39Z

Admin: That’s the entire page, stitched together and formatted for the client. No guessing, no duplicates—just one cohesive document you can hand over today.

<strong>MediaWiki has been installed.</strong>

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User’s Guide] for information on
using the wiki software.

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing
list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for
your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your
wiki]

== Import CustomQueryPage ==
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]

=== Installing CustomQueryPage ===
# Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code>
# Extract into your extensions folder: <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/
extensions</code>
# Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code>
# Run <code>php maintenance/update.php --quick</code>
# Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g. <code>ROUTINE_4.110</code>), and
confirm <code>Special:ApprovedManuals</code>.

= Where We Stand =
* '''CustomQueryPage''' now includes the simplified clone path:
** ''Special:CustomQuerySettings'' copies the ''mw_tag_pages'' rows from <code>ROUTINE_4.110</code> to
<code>ROUTINE_4.111</code>, clones the ''mw_tags'' row, and immediately points the listing at the new tag. The
success banner is fixed and README documents the “Quick clone workflow.”
* On sh1re/sh0re we still need to finish the MediaWiki patch that drops <code>mw_logging.log_user*</code>, so we
seeded <code>mw_customquerypage_settings</code> manually to keep the UI working.

== Why mw_tags felt “bypassed” ==
* On dev we inserted the active tag row directly into <code>mw_customquerypage_settings</code>; the clone form
still expects the standard <code>mw_tags</code>/<code>mw_tag_pages</code> tables.
* If those tables contain the 4.110 data (they should after your import), the UI reuses them immediately.
* Nothing special is required in <code>LocalSettings.php</code>; our extension simply uses the core tables via
the MediaWiki load balancer.

== Next steps on mw.eckfordc (MW 1.39) ==
# Copy <code>extensions-mw1359/CustomQueryPage</code> onto the host.
# Ensure <code>mw_tags</code>/<code>mw_tag_pages</code> include at least one ROUTINE (for example, import
<code>ROUTINE_4.110</code>).
# Visit <code>Special:CustomQuerySettings</code>, run the clone form end to end, and confirm the changed
listing.
# Once Lisa confirms the UI workflow, document the promotion steps on her admin page.

= Recap (Last Week → Now) =
* Finished the MW 1.35.9 build with the simplified clone workflow (Set active tag + Clone ROUTINE_x.xxx →
ROUTINE_y.yyy).
* Deployed the same code to eckfordc (1.39) and sh1re/sh0re (1.35.9); all installs now have ''mw_tags'',
''mw_tag_pages'', and <code>mw_customquerypage_settings</code>.
* On sh1re/sh0re, <code>update.php</code> still balks at dropping <code>mw_logging.log_user*</code>; we seeded
the settings row manually until the patch runs cleanly.

== Where we landed ==
* No human DB access – the release script populates ``mw_tags``/``mw_tag_pages``, and Lisa works entirely
through the Special pages.
* ''Special:CustomQuerySettings'' + ''Special:ApprovedManuals'' both confirmed for <code>ROUTINE_4.111</code>;
README documents the “Quick clone workflow.”
* Nothing extra is required in <code>LocalSettings.php</code>; the extension uses the standard tables via
MediaWiki services.

== Next step: JSON/API practice ==
* Since most releases are re-tags, the clone form covers the common path.
* For the rare “new” ROUTINE payload, define a JSON schema (page_id, rev_id, deployment comment, wikitext, etc.)
and decide whether you want a REST endpoint, an Action API module, or a CLI importer so everything stays inside
MediaWiki.

= Routine Workflow (ship today) =

== 1. Seed the ROUTINE data ==
* Import the raw rows (''mw_tags'' + ''mw_tag_pages'') via the export/import script.
* After import, run <code>php maintenance/update.php --quick</code> if <code>mw_customquerypage_settings</code>
does not exist yet.

== 2. Use the Special page ==
* Log in as a sysop and open [[Special:CustomQuerySettings]].
* Top form (Set active tag): type the ROUTINE you want live (for example, <code>ROUTINE_4.111</code>) and click
'''Save tag''' if the rows already exist.
* Clone form: source <code>ROUTINE_4.110</code>, target <code>ROUTINE_4.111</code>, optional note. Submit once
to duplicate the tag entirely inside MediaWiki (no DB work).

== 3. Verify ==
* Visit [[Special:ApprovedManuals]]; it now lists the pages tagged with <code>ROUTINE_4.111</code>.
* Lisa reviews/publishes directly from there—no database access required.

(Once the data is in place, you either run the import script or use the clone form. When a JSON/API importer is
ready, it replaces step 1; steps 2 and 3 stay the same.)

== Maintenance helper (eckfordc, MW 1.39) ==
# Flush Opcache once so PHP rereads the helper:
#::<pre>if ( function_exists( 'opcache_reset' ) ) {
opcache_reset();
}</pre>
# Run the clone from the server:
#::<pre>php extensions/CustomQueryPage/maintenance/testClone.php \
--wiki=eckfordc_mw19424 \
--source=ROUTINE_4.110 \
--target=ROUTINE_4.111 \
--user=Admin
</pre>
# Check [[Special:ApprovedManuals]]; if the script prints an error, copy the message verbatim so we can patch
it.

Main Page

2026-01-21T23:45:27Z

Admin:

<strong>MediaWiki has been installed.</strong>

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

== Import CustomQueryPage ==
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]

=== Installing CustomQueryPage ===
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code>
* Extract it into your extensions folder:
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code>
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code>
* Run <code>php maintenance/update.php --quick</code>.
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.

= Where We Stand =

* '''CustomQueryPage''' now ships with a simplified clone path:
** ''Special:CustomQuerySettings'' copies the ''mw_tag_pages'' rows from ''ROUTINE_4.110'' to ''ROUTINE_4.111'',
** clones the ''mw_tags'' row,
** and immediately points the listing at the new tag.
** Success banner fixed; README documents the exact steps (see the new ''"Quick clone workflow"'').
* On sh1re/sh0re we never finished the MediaWiki core patch that deletes ''mw_logging.log_user*''.
** We seeded ''mw_customquerypage_settings'' manually instead so Lisa could keep using the UI.

== Why mw_tags felt “bypassed” during export ==

* On dev we inserted the active tag row directly into ''mw_customquerypage_settings''; the clone form still expects
the regular ''mw_tags'' / ''mw_tag_pages'' tables.
** If those tables contain the ''4.110'' data (they should after your MySQL import), the UI will re-use them.
** If the environment you tested lacked ''mw_tags'', we need to confirm the table exists and is populated before cloning.
* There’s nothing special to reference in ''LocalSettings.php''; MediaWiki core creates ''mw_tags'' / ''mw_tag_pages''
automatically.
** Our extension simply reads/writes them via the load balancer.

== Next steps if you want to exercise it on mw.eckford.ca ==

# Copy ''extensions-mw1359/CustomQueryPage'' to the MW 1.39 box.
# Ensure ''mw_tags'' / ''mw_tag_pages'' have at least one ROUTINE (e.g., import ''ROUTINE_4.110'').
# Visit ''Special:CustomQuerySettings'', confirm the clone form works end-to-end:
#* new ''mw_tags'' row
#* ApprovedManuals listing updated
# Once Lisa confirms the UI covers her release work (set tag + clone), we can document the progressive-release workflow on her admin page.

If that 1.39 run reveals that ''mw_tags'' truly doesn’t exist in that environment, we’ll know we must create it
(or point the extension at your custom release table).

Otherwise, the existing code already ties directly into ''mw_tags'', so maintaining progressive releases is just a matter of Lisa cloning each ROUTINE and then toggling the Approved Manuals view as you outlined.

Yep — here’s that whole block “mw-ified” into clean MediaWiki wikitext (copy/paste ready):

```wiki
= Recap (Last Week → Now) =

* Finished the MW 1.35.9 ''CustomQueryPage'' build with the simplified clone workflow so Lisa can re-tag approved releases inside MediaWiki.
** ''Special:CustomQuerySettings'' now handles both:
*** ''Set active tag''
*** ''Clone ROUTINE_x.xxx → ROUTINE_y.yyy''
* Deployed the same bits to ''eckfordc'' (MW 1.39) and ''sh1re/sh0re''.
** The tables you saw (''mw_tags'' / ''mw_tag_pages'' plus ''mw_customquerypage_settings'') match what the extension uses.
* ''update.php'' keeps screaming about dropping legacy logging indexes.
** On dev we skipped the patch and seeded the settings table manually.
** Production installs just need to run update once so ''mw_customquerypage_settings'' exists.

== Where we landed ==

* DB access for humans stays off the table:
** whoever preps the ROUTINE export runs the existing script/import
** Lisa only touches the Special pages
* The ROUTINE clone form is working end-to-end:
** confirmed by the success banner
** ApprovedManuals shows ''ROUTINE_4.111''
** the README now documents the exact steps
* No special mention of ''mw_tags'' in ''LocalSettings.php'' is required.
** It’s core schema, and the extension already hits it directly.

== Next step: JSON/API practice ==

* Since new ROUTINEs are usually just re-tagging existing pages (rarely brand-new content), the current clone form covers the common path.
* If you want to practice building a JSON/API importer for the rare cases when a ROUTINE bundle comes from outside:
** define the payload first
** describe the data coming out of your export process:
*** page_id
*** rev_id
*** deploy_comment
*** wikitext
*** etc.
** decide whether you want:
*** a REST endpoint
*** an Action API module
*** a CLI maintenance script that reads JSON
** once we agree on the schema, I can wire the MediaWiki-side code so Lisa (or a bot) can feed in the new release without touching MySQL
```

Next we can also convert the “ROUTINE_x.xxx → ROUTINE_y.yyy” bits into `<code>` style and wrap the “update.php” warning into a warning box format (using templates like `{{Note}}` / `{{Warning}}` if our wiki has them).

<pre>

/*------------------------------------------------
| |
| GARBAGE BELOW |
| |
| not happy |
| |
|----------------------------------------------*/

</pre>

> Here’s the end-to-end process using what we already shipped, so you can rehearse it before touching the JSON/
API work:

1. Seed the ROUTINE in the DB (once per release)

- You still need the raw data (page/revision/tag rows) staged somewhere. Today that comes from the export/import
script—either the manual SQL process or whatever automation you have.
- Import creates/updates:
- mw_tags: one row per ROUTINE (tag_id = 'ROUTINE_4.111', comment/deploy note, etc.).
- mw_tag_pages: one row per approved page (tag_id, tag_page, tag_rev).
- After import, run php maintenance/update.php --quick if the customquerypage_settings table doesn’t exist yet
(once per wiki).

2. Use the Special page to switch or clone

- Log in as a sysop on the wiki.
- Go to Special:CustomQuerySettings.
- The top form shows the currently active ROUTINE (pulled from mw_customquerypage_settings). Type
ROUTINE_4.111 and Save if you just want to point the listing at an existing tag.
- The Clone form lets Lisa duplicate one ROUTINE to another inside MediaWiki itself (no new import).
Set “Source ROUTINE” to the tag you already have (e.g., ROUTINE_4.110) and “New ROUTINE” to the next one
(ROUTINE_4.111). Submit; the extension copies the mw_tags and mw_tag_pages rows and switches the active tag
automatically.

3. Verify

- Visit Special:ApprovedManuals. It now lists the pages tagged with ROUTINE_4.111.
- Lisa reviews or publishes from there; no DB access required.

So to “create” ROUTINE_4.111 today you either (a) run the existing import script to load a fresh ROUTINE, or (b)
use the clone form to copy an older tag to the new name. Once the data is in place, Special:ApprovedManuals /
Special:CustomQuerySettings handle everything else.

When you’re ready to build the JSON/API importer, we’ll replace step 1 (manual DB import) with a MediaWiki
maintenance/API module that reads your JSON bundle and inserts the mw_tags/mw_tag_pages rows. But the rest of
the process stays the same, and Lisa keeps working entirely through the Special pages.

Main Page

2026-01-21T23:44:37Z

Admin:

<strong>MediaWiki has been installed.</strong>

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

== Import CustomQueryPage ==
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]

=== Installing CustomQueryPage ===
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code>
* Extract it into your extensions folder:
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code>
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code>
* Run <code>php maintenance/update.php --quick</code>.
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.

= Where We Stand =

* '''CustomQueryPage''' now ships with a simplified clone path:
** ''Special:CustomQuerySettings'' copies the ''mw_tag_pages'' rows from ''ROUTINE_4.110'' to ''ROUTINE_4.111'',
** clones the ''mw_tags'' row,
** and immediately points the listing at the new tag.
** Success banner fixed; README documents the exact steps (see the new ''"Quick clone workflow"'').
* On sh1re/sh0re we never finished the MediaWiki core patch that deletes ''mw_logging.log_user*''.
** We seeded ''mw_customquerypage_settings'' manually instead so Lisa could keep using the UI.

== Why mw_tags felt “bypassed” during export ==

* On dev we inserted the active tag row directly into ''mw_customquerypage_settings''; the clone form still expects
the regular ''mw_tags'' / ''mw_tag_pages'' tables.
** If those tables contain the ''4.110'' data (they should after your MySQL import), the UI will re-use them.
** If the environment you tested lacked ''mw_tags'', we need to confirm the table exists and is populated before cloning.
* There’s nothing special to reference in ''LocalSettings.php''; MediaWiki core creates ''mw_tags'' / ''mw_tag_pages''
automatically.
** Our extension simply reads/writes them via the load balancer.

== Next steps if you want to exercise it on mw.eckford.ca ==

# Copy ''extensions-mw1359/CustomQueryPage'' to the MW 1.39 box.
# Ensure ''mw_tags'' / ''mw_tag_pages'' have at least one ROUTINE (e.g., import ''ROUTINE_4.110'').
# Visit ''Special:CustomQuerySettings'', confirm the clone form works end-to-end:
#* new ''mw_tags'' row
#* ApprovedManuals listing updated
# Once Lisa confirms the UI covers her release work (set tag + clone), we can document the progressive-release workflow on her admin page.

If that 1.39 run reveals that ''mw_tags'' truly doesn’t exist in that environment, we’ll know we must create it
(or point the extension at your custom release table).

Otherwise, the existing code already ties directly into ''mw_tags'', so maintaining progressive releases is just a matter of Lisa cloning each ROUTINE and then toggling the Approved Manuals view as you outlined.

Yep — here’s that whole block “mw-ified” into clean MediaWiki wikitext (copy/paste ready):

```wiki
= Recap (Last Week → Now) =

* Finished the MW 1.35.9 ''CustomQueryPage'' build with the simplified clone workflow so Lisa can re-tag approved releases inside MediaWiki.
** ''Special:CustomQuerySettings'' now handles both:
*** ''Set active tag''
*** ''Clone ROUTINE_x.xxx → ROUTINE_y.yyy''
* Deployed the same bits to ''eckfordc'' (MW 1.39) and ''sh1re/sh0re''.
** The tables you saw (''mw_tags'' / ''mw_tag_pages'' plus ''mw_customquerypage_settings'') match what the extension uses.
* ''update.php'' keeps screaming about dropping legacy logging indexes.
** On dev we skipped the patch and seeded the settings table manually.
** Production installs just need to run update once so ''mw_customquerypage_settings'' exists.

== Where we landed ==

* DB access for humans stays off the table:
** whoever preps the ROUTINE export runs the existing script/import
** Lisa only touches the Special pages
* The ROUTINE clone form is working end-to-end:
** confirmed by the success banner
** ApprovedManuals shows ''ROUTINE_4.111''
** the README now documents the exact steps
* No special mention of ''mw_tags'' in ''LocalSettings.php'' is required.
** It’s core schema, and the extension already hits it directly.

== Next step: JSON/API practice ==

* Since new ROUTINEs are usually just re-tagging existing pages (rarely brand-new content), the current clone form covers the common path.
* If you want to practice building a JSON/API importer for the rare cases when a ROUTINE bundle comes from outside:
** define the payload first
** describe the data coming out of your export process:
*** page_id
*** rev_id
*** deploy_comment
*** wikitext
*** etc.
** decide whether you want:
*** a REST endpoint
*** an Action API module
*** a CLI maintenance script that reads JSON
** once we agree on the schema, I can wire the MediaWiki-side code so Lisa (or a bot) can feed in the new release without touching MySQL
```

Next we can also convert the “ROUTINE_x.xxx → ROUTINE_y.yyy” bits into `<code>` style and wrap the “update.php” warning into a warning box format (using templates like `{{Note}}` / `{{Warning}}` if our wiki has them).

/*------------------------------------------------
| |
| GARBAGE BELOW |
| |
| not happy |
| |
|----------------------------------------------*/
> Here’s the end-to-end process using what we already shipped, so you can rehearse it before touching the JSON/
API work:

1. Seed the ROUTINE in the DB (once per release)

- You still need the raw data (page/revision/tag rows) staged somewhere. Today that comes from the export/import
script—either the manual SQL process or whatever automation you have.
- Import creates/updates:
- mw_tags: one row per ROUTINE (tag_id = 'ROUTINE_4.111', comment/deploy note, etc.).
- mw_tag_pages: one row per approved page (tag_id, tag_page, tag_rev).
- After import, run php maintenance/update.php --quick if the customquerypage_settings table doesn’t exist yet
(once per wiki).

2. Use the Special page to switch or clone

- Log in as a sysop on the wiki.
- Go to Special:CustomQuerySettings.
- The top form shows the currently active ROUTINE (pulled from mw_customquerypage_settings). Type
ROUTINE_4.111 and Save if you just want to point the listing at an existing tag.
- The Clone form lets Lisa duplicate one ROUTINE to another inside MediaWiki itself (no new import).
Set “Source ROUTINE” to the tag you already have (e.g., ROUTINE_4.110) and “New ROUTINE” to the next one
(ROUTINE_4.111). Submit; the extension copies the mw_tags and mw_tag_pages rows and switches the active tag
automatically.

3. Verify

- Visit Special:ApprovedManuals. It now lists the pages tagged with ROUTINE_4.111.
- Lisa reviews or publishes from there; no DB access required.

So to “create” ROUTINE_4.111 today you either (a) run the existing import script to load a fresh ROUTINE, or (b)
use the clone form to copy an older tag to the new name. Once the data is in place, Special:ApprovedManuals /
Special:CustomQuerySettings handle everything else.

When you’re ready to build the JSON/API importer, we’ll replace step 1 (manual DB import) with a MediaWiki
maintenance/API module that reads your JSON bundle and inserts the mw_tags/mw_tag_pages rows. But the rest of
the process stays the same, and Lisa keeps working entirely through the Special pages.

Main Page

2026-01-21T23:08:32Z

Admin:

Main Page

2026-01-21T23:00:14Z

Admin: formatting frenzie!

<strong>MediaWiki has been installed.</strong>

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

== Import CustomQueryPage ==
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]

=== Installing CustomQueryPage ===
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code>
* Extract it into your extensions folder:
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code>
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code>
* Run <code>php maintenance/update.php --quick</code>.
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.

= Where We Stand =

* '''CustomQueryPage''' now ships with a simplified clone path:
** ''Special:CustomQuerySettings'' copies the ''mw_tag_pages'' rows from ''ROUTINE_4.110'' to ''ROUTINE_4.111'',
** clones the ''mw_tags'' row,
** and immediately points the listing at the new tag.
** Success banner fixed; README documents the exact steps (see the new ''"Quick clone workflow"'').
* On sh1re/sh0re we never finished the MediaWiki core patch that deletes ''mw_logging.log_user*''.
** We seeded ''mw_customquerypage_settings'' manually instead so Lisa could keep using the UI.

== Why mw_tags felt “bypassed” during export ==

* On dev we inserted the active tag row directly into ''mw_customquerypage_settings''; the clone form still expects
the regular ''mw_tags'' / ''mw_tag_pages'' tables.
** If those tables contain the ''4.110'' data (they should after your MySQL import), the UI will re-use them.
** If the environment you tested lacked ''mw_tags'', we need to confirm the table exists and is populated before cloning.
* There’s nothing special to reference in ''LocalSettings.php''; MediaWiki core creates ''mw_tags'' / ''mw_tag_pages''
automatically.
** Our extension simply reads/writes them via the load balancer.

== Next steps if you want to exercise it on mw.eckford.ca ==

# Copy ''extensions-mw1359/CustomQueryPage'' to the MW 1.39 box.
# Ensure ''mw_tags'' / ''mw_tag_pages'' have at least one ROUTINE (e.g., import ''ROUTINE_4.110'').
# Visit ''Special:CustomQuerySettings'', confirm the clone form works end-to-end:
#* new ''mw_tags'' row
#* ApprovedManuals listing updated
# Once Lisa confirms the UI covers her release work (set tag + clone), we can document the progressive-release workflow on her admin page.

If that 1.39 run reveals that ''mw_tags'' truly doesn’t exist in that environment, we’ll know we must create it
(or point the extension at your custom release table).

Otherwise, the existing code already ties directly into ''mw_tags'', so maintaining progressive releases is just a matter of Lisa cloning each ROUTINE and then toggling the Approved Manuals view as you outlined.

Yep — here’s that whole block “mw-ified” into clean MediaWiki wikitext (copy/paste ready):

```wiki
= Recap (Last Week → Now) =

* Finished the MW 1.35.9 ''CustomQueryPage'' build with the simplified clone workflow so Lisa can re-tag approved releases inside MediaWiki.
** ''Special:CustomQuerySettings'' now handles both:
*** ''Set active tag''
*** ''Clone ROUTINE_x.xxx → ROUTINE_y.yyy''
* Deployed the same bits to ''eckfordc'' (MW 1.39) and ''sh1re/sh0re''.
** The tables you saw (''mw_tags'' / ''mw_tag_pages'' plus ''mw_customquerypage_settings'') match what the extension uses.
* ''update.php'' keeps screaming about dropping legacy logging indexes.
** On dev we skipped the patch and seeded the settings table manually.
** Production installs just need to run update once so ''mw_customquerypage_settings'' exists.

== Where we landed ==

* DB access for humans stays off the table:
** whoever preps the ROUTINE export runs the existing script/import
** Lisa only touches the Special pages
* The ROUTINE clone form is working end-to-end:
** confirmed by the success banner
** ApprovedManuals shows ''ROUTINE_4.111''
** the README now documents the exact steps
* No special mention of ''mw_tags'' in ''LocalSettings.php'' is required.
** It’s core schema, and the extension already hits it directly.

== Next step: JSON/API practice ==

* Since new ROUTINEs are usually just re-tagging existing pages (rarely brand-new content), the current clone form covers the common path.
* If you want to practice building a JSON/API importer for the rare cases when a ROUTINE bundle comes from outside:
** define the payload first
** describe the data coming out of your export process:
*** page_id
*** rev_id
*** deploy_comment
*** wikitext
*** etc.
** decide whether you want:
*** a REST endpoint
*** an Action API module
*** a CLI maintenance script that reads JSON
** once we agree on the schema, I can wire the MediaWiki-side code so Lisa (or a bot) can feed in the new release without touching MySQL

== Routine Clone (eckfordc) ==
# (One time) Clear Opcache: temporarily add
<code>if ( function_exists( 'opcache_reset' ) ) { opcache_reset(); }</code>
to <code>LocalSettings.php</code>, load any page, then remove the snippet.
# Run the maintenance helper:
<pre>
php extensions/CustomQueryPage/maintenance/testClone.php \
--wiki=eckfordc_mw19424 \
--source=ROUTINE_4.110 \
--target=ROUTINE_4.111 \
--user=Admin
</pre>
This clones the tag and prints “Cloned X pages (Y revisions)” or the exact SQL error.
# Visit [[Special:ApprovedManuals]]; it should now show <code>ROUTINE_4.111</code>.
# If the clone fails, rerun step 2 and copy the error output so we can patch it.

-----------------

= Recap (Last Week → Now) =

* Finished the MW 1.35.9 '''CustomQueryPage''' build with the simplified clone workflow so Lisa can re-tag
approved releases inside MediaWiki.
** ''Special:CustomQuerySettings'' now handles both “Set active tag” and “Clone ROUTINE_x.xxx → ROUTINE_y.yyy”.
* Deployed the same bits to eckfordc (MW 1.39) and sh1re/sh0re.
** All installations have the expected tables (''mw_tags'', ''mw_tag_pages'', ''mw_customquerypage_settings'').
* ''update.php'' still balks at dropping ``mw_logging.log_user*`` on sh1re/sh0re, so we seeded the settings
table manually until the patch runs cleanly.

== Where we landed ==
* No human DB access: the release export populates ``mw_tags``/``mw_tag_pages``, and Lisa stays within the
Special pages.
* ''Special:CustomQuerySettings'' + ''Special:ApprovedManuals'' confirmed for <code>ROUTINE_4.111</code>; README
documents the “Quick clone workflow”.
* Nothing special needed in <code>LocalSettings.php</code>; the extension uses the standard tables via MediaWiki
services.

== Next step: JSON/API practice ==
* Since most releases are just re-tagging existing pages, the clone form covers the common path.
* For the rare “new” ROUTINE payload, we can define a JSON schema (page_id, rev_id, comment, wikitext, etc.) and
build either
** a REST endpoint,
** an Action API module, or
** a CLI maintenance script
that ingests the data without direct SQL access.

= Routine Clone (eckfordc) =

# One-time: flush Opcache so PHP reloads the helper script:
#::Add this to <code>LocalSettings.php</code>, load any page, then remove it:
#::<pre>if ( function_exists( 'opcache_reset' ) ) {
opcache_reset();
}</pre>
# Run the maintenance helper:
#::<pre>php extensions/CustomQueryPage/maintenance/testClone.php \
--wiki=eckfordc_mw19424 \
--source=ROUTINE_4.110 \
--target=ROUTINE_4.111 \
--user=Admin
</pre>
# Visit [[Special:ApprovedManuals]]; it should now show <code>ROUTINE_4.111</code>.
# If the clone fails, rerun step 2 and capture the error text so we can patch it.

Main Page

2026-01-21T22:44:49Z

Admin: Routine Clone (eckfordc)

Main Page

2026-01-21T22:30:08Z

Admin:

<strong>MediaWiki has been installed.</strong>

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

== Import CustomQueryPage ==
* [https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz CustomQueryPage for mw1359]

=== Installing CustomQueryPage ===
* Download the bundle: <code>wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz</code>
* Extract it into your extensions folder:
** <code>tar -xzf CustomQueryPage-mw1359.tar.gz -C /srv/mediawiki/extensions</code>
* Edit <code>LocalSettings.php</code> and add <code>wfLoadExtension( 'CustomQueryPage' );</code>
* Run <code>php maintenance/update.php --quick</code>.
* Visit <code>Special:CustomQuerySettings</code>, set the ROUTINE tag (e.g., <code>ROUTINE_4.110</code>), and confirm <code>Special:ApprovedManuals</code>.

= Where We Stand =

* '''CustomQueryPage''' now ships with a simplified clone path:
** ''Special:CustomQuerySettings'' copies the ''mw_tag_pages'' rows from ''ROUTINE_4.110'' to ''ROUTINE_4.111'',
** clones the ''mw_tags'' row,
** and immediately points the listing at the new tag.
** Success banner fixed; README documents the exact steps (see the new ''"Quick clone workflow"'').
* On sh1re/sh0re we never finished the MediaWiki core patch that deletes ''mw_logging.log_user*''.
** We seeded ''mw_customquerypage_settings'' manually instead so Lisa could keep using the UI.

== Why mw_tags felt “bypassed” during export ==

* On dev we inserted the active tag row directly into ''mw_customquerypage_settings''; the clone form still expects
the regular ''mw_tags'' / ''mw_tag_pages'' tables.
** If those tables contain the ''4.110'' data (they should after your MySQL import), the UI will re-use them.
** If the environment you tested lacked ''mw_tags'', we need to confirm the table exists and is populated before cloning.
* There’s nothing special to reference in ''LocalSettings.php''; MediaWiki core creates ''mw_tags'' / ''mw_tag_pages''
automatically.
** Our extension simply reads/writes them via the load balancer.

== Next steps if you want to exercise it on mw.eckford.ca ==

# Copy ''extensions-mw1359/CustomQueryPage'' to the MW 1.39 box.
# Ensure ''mw_tags'' / ''mw_tag_pages'' have at least one ROUTINE (e.g., import ''ROUTINE_4.110'').
# Visit ''Special:CustomQuerySettings'', confirm the clone form works end-to-end:
#* new ''mw_tags'' row
#* ApprovedManuals listing updated
# Once Lisa confirms the UI covers her release work (set tag + clone), we can document the progressive-release workflow on her admin page.

If that 1.39 run reveals that ''mw_tags'' truly doesn’t exist in that environment, we’ll know we must create it
(or point the extension at your custom release table).

Otherwise, the existing code already ties directly into ''mw_tags'', so maintaining progressive releases is just a matter of Lisa cloning each ROUTINE and then toggling the Approved Manuals view as you outlined.

Yep — here’s that whole block “mw-ified” into clean MediaWiki wikitext (copy/paste ready):

```wiki
= Recap (Last Week → Now) =

* Finished the MW 1.35.9 ''CustomQueryPage'' build with the simplified clone workflow so Lisa can re-tag approved releases inside MediaWiki.
** ''Special:CustomQuerySettings'' now handles both:
*** ''Set active tag''
*** ''Clone ROUTINE_x.xxx → ROUTINE_y.yyy''
* Deployed the same bits to ''eckfordc'' (MW 1.39) and ''sh1re/sh0re''.
** The tables you saw (''mw_tags'' / ''mw_tag_pages'' plus ''mw_customquerypage_settings'') match what the extension uses.
* ''update.php'' keeps screaming about dropping legacy logging indexes.
** On dev we skipped the patch and seeded the settings table manually.
** Production installs just need to run update once so ''mw_customquerypage_settings'' exists.

== Where we landed ==

* DB access for humans stays off the table:
** whoever preps the ROUTINE export runs the existing script/import
** Lisa only touches the Special pages
* The ROUTINE clone form is working end-to-end:
** confirmed by the success banner
** ApprovedManuals shows ''ROUTINE_4.111''
** the README now documents the exact steps
* No special mention of ''mw_tags'' in ''LocalSettings.php'' is required.
** It’s core schema, and the extension already hits it directly.

== Next step: JSON/API practice ==

* Since new ROUTINEs are usually just re-tagging existing pages (rarely brand-new content), the current clone form covers the common path.
* If you want to practice building a JSON/API importer for the rare cases when a ROUTINE bundle comes from outside:
** define the payload first
** describe the data coming out of your export process:
*** page_id
*** rev_id
*** deploy_comment
*** wikitext
*** etc.
** decide whether you want:
*** a REST endpoint
*** an Action API module
*** a CLI maintenance script that reads JSON
** once we agree on the schema, I can wire the MediaWiki-side code so Lisa (or a bot) can feed in the new release without touching MySQL
```

Next we can also convert the “ROUTINE_x.xxx → ROUTINE_y.yyy” bits into `<code>` style and wrap the “update.php” warning into a warning box format (using templates like `{{Note}}` / `{{Warning}}` if our wiki has them).

> Here’s the end-to-end process using what we already shipped, so you can rehearse it before touching the JSON/
API work:

1. Seed the ROUTINE in the DB (once per release)

- You still need the raw data (page/revision/tag rows) staged somewhere. Today that comes from the export/import
script—either the manual SQL process or whatever automation you have.
- Import creates/updates:
- mw_tags: one row per ROUTINE (tag_id = 'ROUTINE_4.111', comment/deploy note, etc.).
- mw_tag_pages: one row per approved page (tag_id, tag_page, tag_rev).
- After import, run php maintenance/update.php --quick if the customquerypage_settings table doesn’t exist yet
(once per wiki).

2. Use the Special page to switch or clone

- Log in as a sysop on the wiki.
- Go to Special:CustomQuerySettings.
- The top form shows the currently active ROUTINE (pulled from mw_customquerypage_settings). Type
ROUTINE_4.111 and Save if you just want to point the listing at an existing tag.
- The Clone form lets Lisa duplicate one ROUTINE to another inside MediaWiki itself (no new import).
Set “Source ROUTINE” to the tag you already have (e.g., ROUTINE_4.110) and “New ROUTINE” to the next one
(ROUTINE_4.111). Submit; the extension copies the mw_tags and mw_tag_pages rows and switches the active tag
automatically.

3. Verify

- Visit Special:ApprovedManuals. It now lists the pages tagged with ROUTINE_4.111.
- Lisa reviews or publishes from there; no DB access required.

So to “create” ROUTINE_4.111 today you either (a) run the existing import script to load a fresh ROUTINE, or (b)
use the clone form to copy an older tag to the new name. Once the data is in place, Special:ApprovedManuals /
Special:CustomQuerySettings handle everything else.

When you’re ready to build the JSON/API importer, we’ll replace step 1 (manual DB import) with a MediaWiki
maintenance/API module that reads your JSON bundle and inserts the mw_tags/mw_tag_pages rows. But the rest of
the process stays the same, and Lisa keeps working entirely through the Special pages.

--------------------------------------------------

Sure — here’s that block converted into clean **MediaWiki wikitext** (with headings, bullets, and a syntax-highlighted code block):

```wiki
== Quick Snapshot ==

* The eckfordc server has the updated CustomQueryPage files (clone UI + schema detection).
* The maintenance script <code>testClone.php</code> is in place but still running the old cached code because PHP hasn’t picked up the new file yet.

== What To Do Now ==

# Flush Opcache once so PHP reads the new script:
#* Temporarily add this at the bottom of <code>LocalSettings.php</code>:
#* <syntaxhighlight lang="php">
if ( function_exists( 'opcache_reset' ) ) {
opcache_reset();
}
</syntaxhighlight>
#* Load any wiki page once (you’ll see the site normally).
#* Remove the snippet.
# Run the maintenance clone again:
#* <syntaxhighlight lang="bash">
php extensions/CustomQueryPage/maintenance/testClone.php \
--wiki=eckfordc_mw19424 \
--source=ROUTINE_4.110 \
--target=ROUTINE_4.111 \
--user=Admin
</syntaxhighlight>
#* Now that the script is reloaded, this will either produce a friendly “Cloned X pages” message or the actual SQL error we need to fix.
# If the clone succeeds, hit [[Special:ApprovedManuals]]; it should instantly show <code>ROUTINE_4.111</code>. If it errors, grab the output and I’ll help patch whatever’s left.
```