Main Page

Info: ROUTINE issue patch to fallback settings Updated March 12, 2026

1. 1. Reset ROUTINE manually

1. 1. 1. Method 1 — Change the default ROUTINE in `LocalSettings.php`

Use this when you want a quick operational test or temporary recovery.

Edit this line in `LocalSettings.php`:

```php $wgCustomQueryPageDefaultTag = 'ROUTINE_4.111'; ```

Then:

1. save the file 2. reload `Special:RoutineTags` 3. reload `Special:ApprovedManuals`

If nothing changes:

1. do a hard refresh 2. if still unchanged, have the sysadmin restart PHP / the container 3. reload both pages again

Expected result:

• if the page starts showing `ROUTINE_4.111`, this path is affecting what the extension reads
• if it still shows `ROUTINE_4.110`, this method did not change the active read path

---

1. 1. 1. Method 2 — Quick sanity check

After Method 1, verify both pages, not just one.

Check:

• `Special:RoutineTags`
• `Special:ApprovedManuals`

What to look for:

• does `Special:RoutineTags` show `ROUTINE_4.111` as the visible current/default tag?
• does `Special:ApprovedManuals` heading change to the new ROUTINE?
• does the document list appear to match the intended release?

This is the easiest non-SQL confirmation available when direct DB access is not available onsite.

---

1. 1. 1. Method 3 — See documentation Link TBD

Use the documented release workflow and recovery notes.

Key points already established:

• ROUTINE labels live in `mw_tags`
• ROUTINE membership lives in `mw_tag_pages`
• the current approved set is `mw_approved_revs`
• the active selected ROUTINE is stored in `mw_customquerypage_settings`
• activating a ROUTINE rebuilds `mw_approved_revs`
• rollback is done by reactivating the previous ROUTINE

If manual file edit and page refresh do not restore expected behavior, use the documented extension workflow and technical notes for deeper recovery.

---

Info: Released Vesion 1.0 is available as Latest Version released Feb 26, 2026

CustomQueryPage – latest deployment bundle

File:CustomQueryPage-latest.tgz

Data model summary: page_latest tracks the most recent edit, mw_approved_revs identifies the revision currently approved for display, and each ROUTINE snapshot in mw_tag_pages records which revision belongs to that release.

---

The following information can be used as an installation guide. Only download files tagged latest

OBSOLETE Pre-release

MediaWiki has been installed.

   Upcoming Event: Wiki launch 

   Scheduled for: February 12th at Lisa's Desk

Count down to the retirement of the efs3 server!

content is content

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?

NOTE

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.

Let's Get Started

• CustomQueryPage for mw1359

CustomQueryPage – latest deployment bundle

Installing CustomQueryPage

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

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:
  • mw_tags — one row per ROUTINE (e.g., ROUTINE_4.111).
  • mw_tag_pages — one row per approved page.
• If needed, run: php maintenance/update.php --quick

Note: Only run update.php if mw_customquerypage_settings doesn't exist yet.

2. Use the Special Page to Switch or Clone

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

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

3. Verify the Result

• Visit: Special:ApprovedManuals
• Confirm the listing shows ROUTINE_4.111
• 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:
  • page_id, rev_id, deploy_comment, wikitext, etc.
• Build a:
  • REST endpoint, or
  • Action API module, or
  • Maintenance script that reads JSON

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

⚠️

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