Known Site Issues & Fixes - Revision history

Sovereign: /* What belongs here */

2026-07-24T12:10:02Z

What belongs here

← Older revision		Revision as of 08:10, 24 July 2026
Line 61:		Line 61:

	This keeps the maintenance process simple while preserving complete technical history.		This keeps the maintenance process simple while preserving complete technical history.

			== Technical Issue Report Template ==

			Create one Talk section for each technical issue using the following format.

			<pre><nowiki>
			=== [Short descriptive title] ===

			'''Status:''' Open / Mitigated / Resolved

			'''Date opened:'''
			YYYY-MM-DD

			'''Last updated:'''
			YYYY-MM-DD

			'''Reported by:'''

			'''Affected pages/templates:'''

			'''Category:'''
			Template / Parser / Lua / SMW / Cargo / Namespace / Extension / CSS / JavaScript / Other

			'''Observed behavior:'''
			Describe exactly what happens.

			'''Expected behavior:'''
			Describe what should happen.

			'''Environment:'''
			Relevant namespace, template, extension, browser, or configuration if applicable.

			'''Root cause:'''
			Known cause or "Not yet determined."

			'''Investigation history:'''
			Document observations, testing, and reasoning.

			'''Attempts:'''
			Record every attempted fix.
			Include both successful and unsuccessful attempts.

			'''Current mitigation:'''
			Temporary workaround, if any.

			'''Resolution:'''
			Leave blank until resolved.

			'''Standing:'''
			Open / Mitigated / Resolved

			'''Related pages:'''

			'''Dependencies:'''

			'''Notes:'''
			</nowiki></pre>

			== Reporting Standards ==

			* One technical issue per Talk section.
			* Keep investigation with the issue.
			* Preserve unsuccessful attempts.
			* Never delete technical history.
			* Update the existing report rather than creating duplicate reports.
			* When resolved, update the report instead of removing it.
			* If a new issue is discovered during investigation, open a separate Talk section.

	== What belongs here ==		== What belongs here ==

Sovereign: Calibration Report | 2026-07-24 | v0.2-dev | Self-Assessment | Known Site Issues & Fixes Talk = reports/discussion; article = entry log only (no Calibration Log subpage). Entry template + dates/Talk link. Open Transparency issue entry completed shell. Breadcrumb-Open. Dates unchanged.

2026-07-24T12:08:27Z

Calibration Report | 2026-07-24 | v0.2-dev | Self-Assessment | Known Site Issues & Fixes Talk = reports/discussion; article = entry log only (no Calibration Log subpage). Entry template + dates/Talk link. Open Transparency issue entry completed shell. Breadcrumb-Open. Dates unchanged.

Show changes

Sovereign: Structural pre-cal only. Fixed param name, added inline option comments, added missing mandatory templates, corrected template order. Nonconformances logged first. Content calibration still pending.

2026-07-20T13:24:07Z

Structural pre-cal only. Fixed param name, added inline option comments, added missing mandatory templates, corrected template order. Nonconformances logged first. Content calibration still pending.

Show changes

Sovereign: /* See Also */

2026-07-18T17:04:58Z

Sovereign at 17:03, 18 July 2026

2026-07-18T17:03:53Z

← Older revision		Revision as of 13:03, 18 July 2026
Line 2:		Line 2:
	\|status = Active Maintenance		\|status = Active Maintenance
	}}		}}
			= Known Site Issues & Fixes =

			'''Purpose:''' This page tracks '''technical''' bugs, quirks, and configuration issues specific to this wiki's setup — things like namespace-scoped template failures, extension configuration gaps, or parser quirks that cost real time to diagnose. It exists so a fix (or a failed fix attempt) only has to be discovered once, not rediscovered from scratch the next time the same symptom shows up on a different page.

	{{GameModule		{{GameModule
Line 13:		Line 16:
	\| description = A single-page log of known technical bugs, quirks, and configuration issues found on this wiki — their symptoms, root causes (where known), fixes attempted, and current status.		\| description = A single-page log of known technical bugs, quirks, and configuration issues found on this wiki — their symptoms, root causes (where known), fixes attempted, and current status.
	}}		}}

	~~= Known Site Issues & Fixes =~~

	'''Purpose:''' This page tracks '''technical''' bugs, quirks, and configuration issues specific to this wiki's setup — things like namespace-scoped template failures, extension configuration gaps, or parser quirks that cost real time to diagnose. It exists so a fix (or a failed fix attempt) only has to be discovered once, not rediscovered from scratch the next time the same symptom shows up on a different page.

	== What This Page Is For ==		== What This Page Is For ==

Sovereign at 16:00, 18 July 2026

2026-07-18T16:00:12Z

← Older revision		Revision as of 12:00, 18 July 2026
Line 106:		Line 106:
	\| reviewed_by = Sovereign		\| reviewed_by = Sovereign
	\| priority = Core		\| priority = Core
	\| review_threshold = 1		\| review_threshold = 30
	\| has_backlinks = Not checked		\| has_backlinks = Not checked
	\| outbound_links_valid = Not checked		\| outbound_links_valid = Not checked

Sovereign at 15:55, 18 July 2026

2026-07-18T15:55:10Z

← Older revision		Revision as of 11:55, 18 July 2026
Line 106:		Line 106:
	\| reviewed_by = Sovereign		\| reviewed_by = Sovereign
	\| priority = Core		\| priority = Core
	\| review_threshold = 0		\| review_threshold = 1
	\| has_backlinks = Not checked		\| has_backlinks = Not checked
	\| outbound_links_valid = Not checked		\| outbound_links_valid = Not checked

Sovereign at 15:53, 18 July 2026

2026-07-18T15:53:59Z

← Older revision		Revision as of 11:53, 18 July 2026
Line 106:		Line 106:
	\| reviewed_by = Sovereign		\| reviewed_by = Sovereign
	\| priority = Core		\| priority = Core
	\| review_threshold = 60		\| review_threshold = 0
	\| has_backlinks = Not checked		\| has_backlinks = Not checked
	\| outbound_links_valid = Not checked		\| outbound_links_valid = Not checked

Sovereign: /* Standalone Transparency Fails on Template: Namespace Pages */

2026-07-18T15:24:10Z

Standalone Transparency Fails on Template: Namespace Pages

← Older revision		Revision as of 11:24, 18 July 2026
Line 70:		Line 70:
	'''Symptom:''' [[Template:Standalone Transparency]]'s Talk-page links do not resolve correctly when the template is used on a page in the `Template:` namespace.		'''Symptom:''' [[Template:Standalone Transparency]]'s Talk-page links do not resolve correctly when the template is used on a page in the `Template:` namespace.

	[[https://www.thesovereigngames.com/wiki/Talk:Known_Site_Issues_%26_Fixes#Standalone_Transparency_Fails_on_Template~~:_Namespace_Pages\|'''View & Discuss''']~~]		[https://www.thesovereigngames.com/wiki/Talk:Known_Site_Issues_%26_Fixes#Standalone_Transparency_Fails_on_Template%3A_Namespace_Pages Standalone Transparency Fix]

	== See Also ==		== See Also ==

Sovereign: /* Standalone Transparency Fails on Template: Namespace Pages */ Cleaned it up to stream line it and put link to full report

2026-07-18T15:20:08Z

Standalone Transparency Fails on Template: Namespace Pages: Cleaned it up to stream line it and put link to full report

← Older revision		Revision as of 11:20, 18 July 2026
Line 64:		Line 64:
	<!-- Add new entries below this line, most recent first -->		<!-- Add new entries below this line, most recent first -->

	== Standalone Transparency Fails on Template: Namespace Pages ==		=== Standalone Transparency Fails on Template: Namespace Pages ===

	'''Status:''' Open — unresolved		'''Status:''' Open — unresolved
Line 70:		Line 70:
	'''Symptom:''' [[Template:Standalone Transparency]]'s Talk-page links do not resolve correctly when the template is used on a page in the `Template:` namespace.		'''Symptom:''' [[Template:Standalone Transparency]]'s Talk-page links do not resolve correctly when the template is used on a page in the `Template:` namespace.

	'''Root cause:''' Not yet identified. May or may not be related to the earlier-resolved SMW namespace exclusion bug (`$smwgNamespacesWithSemanticLinks` not including `NS_TEMPLATE`) — that fix addressed semantic data storage, not link resolution, so the underlying mechanisms are likely different even though both manifest on the same namespace.		[[https://www.thesovereigngames.com/wiki/Talk:Known_Site_Issues_%26_Fixes#Standalone_Transparency_Fails_on_Template:_Namespace_Pages\|'''View & Discuss''']]

	'''Fix (or attempted fix):''' Replaced `{{PAGENAME}}` with `{{FULLPAGENAME}}` in both link targets, on the theory that the failure matched the known pattern where `PAGENAME` silently strips the namespace prefix. '''This did not resolve the issue.'''

	~~'''Current mitigation~~:~~''' `{{Standalone Transparency}}` is marked "do not use on `Template:` pages~~.~~" No workaround currently exists for templates needing a transparency footer in that namespace~~. ~~[[Template~~:~~Doc Page Transparency]] may be a safe alternative but has not been separately verified against this same failure mode.~~

	~~'''Found by~~:''' ~~Sovereign, 2026-07-14, during general template cleanup pass.~~

	'''~~Next steps:''' Not yet investigated further. Worth checking whether [[Template:Doc Page Transparency~~]] ~~has the identical bug before assuming it's a safe alternative.~~

	== See Also ==		== See Also ==

← Older revision		Revision as of 13:04, 18 July 2026
Line 78:		Line 78:
	'''See the Game. Refuse the Game. Build Better.'''		'''See the Game. Refuse the Game. Build Better.'''
	{{RelatedPages}}		{{RelatedPages}}
	{{~~Page~~ Transparency}}		{{Standalone Transparency}}
	{{Calibration Maintenance}}		{{Calibration Maintenance}}
	{{Calibration Dependent}}		{{Calibration Dependent}}
Line 86:		Line 86:
	[[Category:Site Maintenance]]		[[Category:Site Maintenance]]

	~~<div style="display:none;">~~
	{{Resource		{{Resource
	\| Title = Known Site Issues & Fixes		\| Title = Known Site Issues & Fixes
Line 93:		Line 92:
	\| Category = Meta & Framework		\| Category = Meta & Framework
	}}		}}
	~~</div>~~

	{{Admin Page Status		{{Admin Page Status