Main Page

MediaWiki has been installed.

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?

• CustomQueryPage for mw1359

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

• 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.