Jump to content

Known Site Issues & Fixes: Difference between revisions

From The Sovereign Games (MoA Lab)
← Older edit

Sovereign (talk | contribs)

3 user groups
3,697 edits
VisualWikitext
No edit summary
 
(17 intermediate revisions by the same user not shown)
Line 1: Line 1:
== SMW Silently Ignores #set on Template: Namespace Pages ==
{{Development Notice
{{Trans - Stand Alone - Insert in 'Main Page' - Not Talk Cal Log - Not Sub Dep Rep}}
|status = Active Maintenance
}}
= Known Site Issues & Fixes =


'''Symptom:''' Admin Page Status fields display correctly and store correctly in Cargo, but never appear in Special:Browse or SMW queries — specifically and only on pages in the Template: namespace (e.g. Template:Admin Page Status/doc, Template:GameModule/doc).
'''Purpose:''' Document how this project records and manages '''technical''' bugs, quirks, parser issues, template failures, extension configuration problems, and other infrastructure-specific issues.


'''Cause:''' SMW's `$smwgNamespacesWithSemanticLinks` configuration excludes the Template namespace by default. `#set` calls are silently no-ops there — no error, no warning, just nothing stored.
This page explains the process.


'''Fix:''' Set `$smwgNamespacesWithSemanticLinks[NS_TEMPLATE] = true;` in LocalSettings.php, then purge affected pages.
The '''Talk page is the official issue and report log.'''
{{GameModule
| type = Meta & Framework
<!-- HIDDEN GUIDE: pick from existing controlled vocabulary — check Category pages before inventing a new type. -->
| category = [[:Category:Meta & Framework|Meta & Framework]]
<!-- HIDDEN GUIDE: must match an existing Category page. -->
| Calibration Type = Maintenance
<!-- HIDDEN GUIDE: options — Governance, Diagnostic, Maintenance, Framework, Calibration. Parameter name Calibration Type; displays as Functional Layer. Do not rename the stored parameter. -->
| Application Layer = Framework Infrastructure
<!-- HIDDEN GUIDE: options — Multi-Layer, Framework Infrastructure, Individual, Institutional, Civilizational. New values only via deliberate vocabulary update on Page Structure Calibration Checklist and Template:GameModule/doc. -->
| Version = 0.2
| Maturity = Development
<!-- HIDDEN GUIDE: Experimental, Development, Confirmed, Field Validated, Reference Standard Candidate -->
| Last Updated = 2026-07-20
<!-- CRITICAL: static only. Must match review_date. FORBIDDEN: magic words. -->
| description = Single-page log of known technical bugs and configuration issues on this wiki. Entries live here; discussion and detailed reports on Talk — no separate Calibration Log subpage.
}}
== Purpose ==


'''How it was found:''' Bisection — confirmed the template itself worked (fresh test page, main namespace, succeeded), then narrowed by testing the identical block across pages in different namespaces until the pattern (Template: fails, everywhere else works) became visible. Content length, field names, and phrasing were all red herrings ruled out along the way.
This page defines how technical issues are handled for this wiki.


Technical issues include:
* Template failures
* Parser or Lua issues
* Semantic MediaWiki / Cargo configuration problems
* Namespace-specific behavior
* Extension limitations
* Infrastructure-specific quirks
* Other technical issues unique to this wiki
The goal is to ensure each issue is documented once, investigated once, and resolved without rediscovering the same problem repeatedly.
== Recording Model ==
Technical issue tracking follows a simple separation of responsibilities.
* '''This page''' documents the maintenance process.
* '''[[Talk:Known Site Issues & Fixes]]''' is the official issue register, investigation log, discussion thread, testing history, failed-attempt record, and resolution history.
No separate Calibration Log or report subpages should be created for technical issues.
Talk provides:
* chronological history
* threaded discussion
* reply capability
* investigation records
* implementation notes
* successful and failed attempts
* final resolution
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 ==
Technical issues specific to this wiki, including:
* Template behavior
* Parser behavior
* Namespace problems
* Extension configuration
* Infrastructure maintenance
* Technical implementation issues
== What does not belong here ==
* Content calibration findings
** Use the page Talk page or that page's Calibration Log.
* Governance decisions
** Use [[Decision Records: Governance Memory]].
* Conceptual incompleteness
** Use [[Breadcrumb Philosophy]].
* General MediaWiki documentation
** If the answer is simply "read the MediaWiki manual," it does not belong here.
== Reporting a Technical Issue ==
When a technical issue is discovered:
# Create a new section on [[Talk:Known Site Issues & Fixes]].
# Describe the observed behavior.
# Document investigation.
# Record both successful and failed attempts.
# Update the discussion as work progresses.
# Mark the issue resolved when complete.
The Talk page serves as the permanent maintenance record.
== Guiding Principles ==
* Record issues once.
* Keep investigation attached to the issue.
* Preserve failed attempts.
* Avoid duplicate reports.
* Keep process separate from discussion.
* Let Talk serve as the technical maintenance history.
== See also ==
* [[Nonconformance Reporting Procedure]]
* [[Page Structure Calibration Checklist]]
* [[Decision Records: Governance Memory]]
* [[Breadcrumb Philosophy]]
'''See the Game. Refuse the Game. Build Better.'''
== Open Calibration Items ==
* Monitor whether Talk-only issue tracking continues to scale effectively.
* Revisit only if technical issue volume makes additional indexing necessary.
''See the Page Transparency & Calibration section above for this page's Talk, Decision Records, and related maintenance links.''
{{RelatedPages}}
{{Standalone Transparency}}
{{Calibration Dependent}}
{{Calibration Dependencies Display}}
{{Calibration Maintenance}}
{{Framework Reference}}
{{Calibration Procedure Reference}}
{{Tracking Logs Reference}}
[[Category:Meta & Framework]]
[[Category:Site Maintenance]]
[[Category:Site Maintenance]]
{{Resource
| Title = Known Site Issues & Fixes
| URL = https://www.thesovereigngames.com/wiki/Known_Site_Issues_%26_Fixes
| Description = Single-page log of known technical bugs and configuration issues on this wiki. Discussion and reports on Talk — no separate Calibration Log subpage.
| Category = Meta & Framework
}}
{{Admin Page Status
<!-- Do Not Remove commented out Reference Options -->
<!-- === CORE STATUS === -->
<!-- options: Done, Needs review, Not started -->
| categorization = Done
<!-- options: Self-Assessment, Confirmed Rating -->
| calibration_review = Self-Assessment
<!-- options: Experimental, Development, Confirmed, Field Validated, Reference Standard Candidate -->
| instrument_grade = Development
<!-- options: Low, Moderate, High -->
| validation = Low
| calibration_rationale = Clarified Talk as report channel (no Calibration Log subpage). Tightened entry template (dates, Talk link, === under Log). Filled incomplete Standalone Transparency entry shell. Application Layer vocabulary aligned. Open issue remains — Breadcrumb-Open for incomplete entry fields / open bug. Cycle dates unchanged.
| review_confidence = Moderate
<!-- options: High, Moderate, Low -->
| review_date = 2026-07-20
| reviewed_by = Sovereign
<!-- options: Core, Supporting, Peripheral -->
| priority = Core
| review_threshold = 30
<!-- options: Yes, No, Not checked -->
| has_backlinks = Not checked
<!-- options: Yes, Has red links, No, Not checked -->
| outbound_links_valid = Not checked
<!-- options: Yes, No -->
| in_outline = No
<!-- options: Yes, No -->
| in_category_outline = No
<!-- options: Done, Needs review, Not started -->
| templates_complete = Done
<!-- options: Meets standard, Needs work, Not checked -->
| formatting_standard = Meets standard
<!-- options: Applied, Not applicable, Needs work -->
| symmetry_check = Not applicable
<!-- options: Yes, No, Not applicable -->
| self_report_flagged = No
<!-- options: Yes, Needs work, Not checked -->
| terminology_consistent = Yes
<!-- options: Confirmed by other party, Self-assessed only -->
| standing_check = Self-assessed only
<!-- options: Breadcrumb-Open, Nonconformance-Open, Nonconformance-Open-With-Dependencies, Resolved-Unverified, Disputed, None open — None open alone only -->
| drift_report_status = Breadcrumb-Open
| depends_on = Nonconformance Reporting Procedure; Page Structure Calibration Checklist
}}

Latest revision as of 08:10, 24 July 2026

Welcome to the MoA–TSG Lab. The wiki is the bench. The work is Metrology of the Abstract. Adopt the tools or leave them on the rack — either way, the need doesn't wait.

  • Lab Note: A redlink is not a failure. It identifies Calibration Debt—work waiting to be measured, mapped, and calibrated.

CYCLE Calibration position

Status — Active Maintenance

This page is a conceptual instrument under Permanent Beta. It declares a real calibration position, not a finished product waiting to ship. Checking continues; an edit is only required when evidence demands it. Stage: Seed to Fruit.

Feedback welcome — especially clarity, failure modes, and calibration gaps. Use discussion or Contribute.


Known Site Issues & Fixes

Purpose: Document how this project records and manages technical bugs, quirks, parser issues, template failures, extension configuration problems, and other infrastructure-specific issues.

This page explains the process.

The Talk page is the official issue and report log.



Sovereign-Games-OG-Image.jpg

Meta

Known Site Issues & Fixes

Type Meta & Framework
Functional Layer Maintenance
Application Layer Framework Infrastructure
Category Meta & Framework
Version 0.2
Maturity Development
Last Calibration 2026-07-20
Status Permanent Beta
Description Single-page log of known technical bugs and configuration issues on this wiki. Entries live here; discussion and detailed reports on Talk — no separate Calibration Log subpage.

Core Principles

  • Reality gets final vote
  • See the Game. Refuse the Game. Build Better.
  • Permanent Beta

Navigation

Related


Purpose

This page defines how technical issues are handled for this wiki.

Technical issues include:

  • Template failures
  • Parser or Lua issues
  • Semantic MediaWiki / Cargo configuration problems
  • Namespace-specific behavior
  • Extension limitations
  • Infrastructure-specific quirks
  • Other technical issues unique to this wiki

The goal is to ensure each issue is documented once, investigated once, and resolved without rediscovering the same problem repeatedly.

Recording Model

Technical issue tracking follows a simple separation of responsibilities.

  • This page documents the maintenance process.
  • Talk:Known Site Issues & Fixes is the official issue register, investigation log, discussion thread, testing history, failed-attempt record, and resolution history.

No separate Calibration Log or report subpages should be created for technical issues.

Talk provides:

  • chronological history
  • threaded discussion
  • reply capability
  • investigation records
  • implementation notes
  • successful and failed attempts
  • final resolution

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. 

=== [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:'''

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

Technical issues specific to this wiki, including:

  • Template behavior
  • Parser behavior
  • Namespace problems
  • Extension configuration
  • Infrastructure maintenance
  • Technical implementation issues

What does not belong here

  • Content calibration findings
    • Use the page Talk page or that page's Calibration Log.
  • General MediaWiki documentation
    • If the answer is simply "read the MediaWiki manual," it does not belong here.

Reporting a Technical Issue

When a technical issue is discovered:

  1. Create a new section on Talk:Known Site Issues & Fixes.
  2. Describe the observed behavior.
  3. Document investigation.
  4. Record both successful and failed attempts.
  5. Update the discussion as work progresses.
  6. Mark the issue resolved when complete.

The Talk page serves as the permanent maintenance record.

Guiding Principles

  • Record issues once.
  • Keep investigation attached to the issue.
  • Preserve failed attempts.
  • Avoid duplicate reports.
  • Keep process separate from discussion.
  • Let Talk serve as the technical maintenance history.

See also

See the Game. Refuse the Game. Build Better.

Open Calibration Items

  • Monitor whether Talk-only issue tracking continues to scale effectively.
  • Revisit only if technical issue volume makes additional indexing necessary.

See the Page Transparency & Calibration section above for this page's Talk, Decision Records, and related maintenance links.



Structural Connections


Page Transparency & Calibration

This page is under continuous calibration in line with the Permanent Beta principle.

Public Discussion Welcome

Questions, suggestions, feedback, disagreement, and proposed improvements are welcome on the Talk page.

Light rules:

  • Prefer evidence and concrete examples over slogans.
  • Apply Diagnostic Inversion Test when criticizing — the same standard to this page that you would apply elsewhere.
  • Distinguish observation from conclusion.
  • Calibration entries and Decision Records are maintenance records; public discussion belongs in ordinary Talk threads.
  • This framework remains in Permanent Beta. Better calibration is always in scope.



Calibration Dependent

Pages that list this page as a load-bearing dependency:

Page Priority Instrument Grade Last Updated Cycle Status Drift Status
Template/Doc Calibration Pattern Core Experimental 2026-07-14 Current Breadcrumb-Open
Milestone: The Cargo List-Field Fix — The Dependency Graph Becomes Possible Core Confirmed 2026-07-14 Current None open
Nonconformance Reporting Procedure Core Experimental 2026-07-20 Current Breadcrumb-Open
Feature Request Log Supporting Experimental 2026-07-14 Current None open
Calibration Failure Log Supporting Experimental 2026-07-24 Current Breadcrumb-Open
Template:Calibration Template Supporting Development 2026-07-20 Current Breadcrumb-Open

If this page is edited substantively, review the list above per the Ripple Review rule — see Calibration Dependencies: Standards and Process#Rule: Core-Priority Changes Trigger Mandatory Ripple Review.


Calibration Dependencies

Pages this page relies on as load-bearing dependencies: Nonconformance Reporting Procedure • Page Structure Calibration Checklist If incorrect, edit the `depends_on` field in Admin Page Status — do not edit this section directly, it is auto-generated.



Calibration References

This page is calibrated against the following core standards and reference materials:



Page Construction & Maintenance References

How we construct, maintain, and utilize each page as a self-admin control panel.

  • Distributed Instrumentation — the architectural principle behind why this page (and every page) carries its own live instrumentation, rather than relying on a separate central dashboard.
  • Page Structure Calibration Checklist — the Step 0 structural pass every page should pass before content calibration begins; this page's own structure should be checkable against it.
  • Template:New Page Seed — the seed template this page's basic structure was built from.
  • Calibration Log: When to Create One — the decision procedure this page's own Talk-only vs. dedicated-log status was decided against.
  • Framework Features Reference — maintains consistency and traceability across the framework's structural features while avoiding unnecessary maintenance overhead; consult before introducing a new structural pattern this page might otherwise duplicate.



Calibration Procedure

In development. See Calibration Procedure for current status. No formal step-by-step procedure exists yet beyond the practices demonstrated across individual pages developed during the initial creation of this project.



Tracking & Log Pages



Page Reference

Title Known Site Issues & Fixes
URL https://www.thesovereigngames.com/wiki/Known_Site_Issues_%26_Fixes
Description Single-page log of known technical bugs and configuration issues on this wiki. Discussion and reports on Talk — no separate Calibration Log subpage.
Category Meta & Framework



Retrieved from "https://www.thesovereigngames.com/index.php?title=Known_Site_Issues_%26_Fixes&oldid=3517"