Main Page

 MediaWiki has been installed.

 Consult the User’s Guide for information on
 using the wiki software.

 == Getting started ==
 * Configuration settings list
 * 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 ==
 * CustomQueryPage for mw1359

 === Installing CustomQueryPage ===
 # Download the bundle: wget https://mw.eckford.ca/downloads/CustomQueryPage-mw1359.tar.gz
 # Extract 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.

 = Where We Stand =
 * CustomQueryPage now includes the 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. 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 mw_logging.log_user*, so we
 seeded mw_customquerypage_settings manually to keep the UI working.

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

 == Next steps on mw.eckfordc (MW 1.39) ==
 # Copy extensions-mw1359/CustomQueryPage onto the host.
 # Ensure mw_tags/mw_tag_pages include at least one ROUTINE (for example, import
 ROUTINE_4.110).
 # Visit Special:CustomQuerySettings, 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 mw_customquerypage_settings.
 * On sh1re/sh0re, update.php still balks at dropping mw_logging.log_user*; 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 ROUTINE_4.111;
 README documents the “Quick clone workflow.”
 * Nothing extra is required in LocalSettings.php; 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 php maintenance/update.php --quick if mw_customquerypage_settings
 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, ROUTINE_4.111) and click
 Save tag if the rows already exist.
 * Clone form: source ROUTINE_4.110, target ROUTINE_4.111, 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 ROUTINE_4.111.
 * 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:

#::

if ( function_exists( 'opcache_reset' ) ) {
      opcache_reset();
  }

 # Run the clone from the server:

#::

php extensions/CustomQueryPage/maintenance/testClone.php \
      --wiki=eckfordc_mw19424 \
      --source=ROUTINE_4.110 \
      --target=ROUTINE_4.111 \
      --user=Admin
  

 # Check Special:ApprovedManuals; if the script prints an error, copy the message verbatim so we can patch
 it.