Main Page - Revision history

172.97.51.228: /* 1. Seed the ROUTINE in the DB */

2026-03-17T12:49:28Z

1. Seed the ROUTINE in the DB

← Older revision		Revision as of 08:49, 17 March 2026
Line 191:		Line 191:

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

	* Use the import script or manual SQL method.		* Use the import script or manual SQL method.

Tux at 13:59, 16 March 2026

2026-03-16T13:59:41Z

← Older revision		Revision as of 09:59, 16 March 2026
Line 127:		Line 127:

	---		---
			= DEBUG STEPS =

	~~Hi Lisa, If this doesn~~		== In a nutshell ==

			* What ROUTINE is showing on Approved manuals?

			* What ROUTINE tag displays on the ROUTINE tags page?

			* What exact message appeared after clicking the button?

			== Tech Fixes ==

			Please let me know if this is fixed or if you need another step. Based on what's happening, I can probably help :)

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

Tux at 13:51, 16 March 2026

2026-03-16T13:51:15Z

← Older revision		Revision as of 09:51, 16 March 2026
Line 13:		Line 13:
	# Open '''ROUTINE tags'''.		# Open '''ROUTINE tags'''.

	=== To roll back to an existing ROUTINE ===		=== To activate or roll back to an existing ROUTINE ===

	Use the '''top ROUTINE field'''.		Use the '''top ROUTINE field'''.

	Enter the exact existing ROUTINE value you want to ~~return to~~, for example:		Enter the exact existing ROUTINE value you want to use, for example:

	<code>ROUTINE_4.110</code>		<code>ROUTINE_4.110</code>

	Then ~~save or~~ activate ~~it.~~		Then click '''Activate tag'''.

			This can be used to:

			* activate the current working ROUTINE
			* return to a previous ROUTINE
			* confirm that an existing ROUTINE bundle still works

	'''Do not''' use '''Clone ROUTINE release''' for rollback.		'''Do not''' use '''Clone ROUTINE release''' for rollback.
Line 27:		Line 33:
	=== To create the next ROUTINE ===		=== To create the next ROUTINE ===

	~~Use~~ '''Clone ROUTINE release'''.		First make sure the current ROUTINE is correct in the '''top ROUTINE field'''.
			If needed, enter the current ROUTINE there and click '''Activate tag''' first.

			Then use '''Clone ROUTINE release'''.

	Enter:		Enter:

	* '''Source ROUTINE''': the current release, for example <code>ROUTINE_4.110</code>		* '''Source ROUTINE''': the current active release, for example <code>ROUTINE_4.110</code>
	* '''New ROUTINE''': the new release, for example <code>ROUTINE_4.111</code>		* '''New ROUTINE''': the new release, for example <code>ROUTINE_4.111</code>

	Then submit the form.		Then submit the form.

			This should:

			* create the new ROUTINE tag
			* copy the current bundle into the new ROUTINE
			* activate the new ROUTINE automatically

	== What to check immediately after ==		== What to check immediately after ==

	After ~~saving~~ or cloning:		After activating or cloning:

	# Stay on the page and note the message shown at the top.		# Stay on the page and note the message shown at the top.
Line 47:		Line 62:
	== Important ==		== Important ==

			* '''Activate tag''' uses an existing ROUTINE.
			* '''Clone ROUTINE release''' creates a new ROUTINE from an existing one.
	* '''Rollback''' means activating an existing ROUTINE in the top field.		* '''Rollback''' means activating an existing ROUTINE in the top field.
	* '''Clone''' means creating a new ROUTINE in the lower form.
	* Enter the ROUTINE exactly as written, for example <code>ROUTINE_4.110</code>.		* Enter the ROUTINE exactly as written, for example <code>ROUTINE_4.110</code>.
	* Changing approved document revisions does '''not''' by itself create a new ROUTINE label.		* Changing approved document revisions does '''not''' by itself create a new ROUTINE label.
Line 109:		Line 125:

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

			---

			Hi Lisa, If this doesn

Tux at 13:44, 16 March 2026

2026-03-16T13:44:37Z

← Older revision		Revision as of 09:44, 16 March 2026
Line 1:		Line 1:
	~~```mediawiki~~
	{{Info\|Updated March 16, 2026.}}		{{Info\|Updated March 16, 2026.}}

Line 109:		Line 109:

	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.		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.
	~~```~~

Tux: Add debug steps to Operational Procedures

2026-03-16T13:44:13Z

Add debug steps to Operational Procedures

@@ Line 1: / Line 1: @@
-{{Info| Updated March 12, 2026.}}
+These notes are for checking or changing the active ROUTINE in the Manual Procedures workflow.
-= Reset ROUTINE manually =
+== Normal workflow ==
-==ROUTINE issue patch to fallback settings==
+# Log in.
 == Method 1: Change the fallback ROUTINE in <code>LocalSettings.php</code> ==
 Edit this line in <code>LocalSettings.php</code>:
-<code>
+<syntaxhighlight lang="php">
 $wgCustomQueryPageDefaultTag = 'ROUTINE_4.111';
-</code>
+</syntaxhighlight>
 Then:
@@ Line 46: / Line 94: @@
 * Does the heading on [[Special:ApprovedManuals]] change to the new ROUTINE?
 * Does the document list appear to match the intended release?
 == Method 3: See documentation ==
 Use the ROUTINE workflow and recovery notes for deeper troubleshooting.
@@ Line 65: / Line 109: @@
 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.
 -----------------------------------------------------------
@@ Line 95: / Line 142: @@
 == 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.
+See procedure for rollback to reset to a previous version. Set tag ONLY.
 == Let's Get Started ==

Tux: /* ROUTINE issue patch to fallback settings */

2026-03-14T00:50:18Z

ROUTINE issue patch to fallback settings

← Older revision		Revision as of 20:50, 13 March 2026
Line 5:		Line 5:
	= Reset ROUTINE manually =		= Reset ROUTINE manually =

	== ROUTINE issue patch to fallback settings ==		==ROUTINE issue patch to fallback settings==

	== Method 1: Change the fallback ROUTINE in <code>LocalSettings.php</code> ==		== Method 1: Change the fallback ROUTINE in <code>LocalSettings.php</code> ==

Tux: /* Method 1: Change the fallback ROUTINE in LocalSettings.php */

2026-03-14T00:48:26Z

Method 1: Change the fallback ROUTINE in LocalSettings.php

← Older revision		Revision as of 20:48, 13 March 2026
Line 9:		Line 9:
	== Method 1: Change the fallback ROUTINE in <code>LocalSettings.php</code> ==		== Method 1: Change the fallback ROUTINE in <code>LocalSettings.php</code> ==

	Use this as a quick test or temporary recovery step.		Use this as a quick test or temporary recovery step. ssh tux 210.32.36.141 /home/tux/mw1359/LocalSettings.php

	Edit this line in <code>LocalSettings.php</code>:		Edit this line in <code>LocalSettings.php</code>:

	<~~syntaxhighlight lang="php"~~>		<code>
	$wgCustomQueryPageDefaultTag = 'ROUTINE_4.111';		$wgCustomQueryPageDefaultTag = 'ROUTINE_4.111';
	</~~syntaxhighlight~~>		</code>

	Then:		Then:

Tux: /* 1. Seed the ROUTINE in the DB */

2026-03-14T00:39:45Z

1. Seed the ROUTINE in the DB

← Older revision		Revision as of 20:39, 13 March 2026
Line 123:		Line 123:
	** <code>mw_tag_pages</code> — one row per approved page.		** <code>mw_tag_pages</code> — one row per approved page.
	* If needed, run: <code>php maintenance/update.php --quick</code>		* 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.}}		{{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.}}

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

Tux: /* OBSOLETE Pre-release */

2026-03-14T00:35:28Z

OBSOLETE Pre-release

← Older revision		Revision as of 20:35, 13 March 2026
Line 81:		Line 81:
	'''''		'''''

	~~====~~= OBSOLETE Pre-release ~~====~~=		= OBSOLETE Pre-release =
	<strong>MediaWiki has been installed.</strong>		<strong>MediaWiki has been installed.</strong>
	{{Notice		{{Notice

Tux at 00:34, 14 March 2026

2026-03-14T00:34:39Z

← Older revision		Revision as of 20:34, 13 March 2026
Line 1:		Line 1:
	{{Info\|~~ROUTINE issue patch to fallback settings.~~ Updated March 12, 2026.}}

			{{Info\| Updated March 12, 2026.}}

	= Reset ROUTINE manually =		= Reset ROUTINE manually =

			== ROUTINE issue patch to fallback settings ==

	== Method 1: Change the fallback ROUTINE in <code>LocalSettings.php</code> ==		== Method 1: Change the fallback ROUTINE in <code>LocalSettings.php</code> ==