Jump to content

Known Site Issues & Fixes: Difference between revisions

From The Sovereign Games (MoA Lab)
← Older editNewer edit →

Sovereign (talk | contribs)

3 user groups
3,632 edits
VisualWikitext
No edit summary
Tag: Manual revert
No edit summary
Line 1: Line 1:
== SMW Silently Ignores #set on Template: Namespace Pages ==


'''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).
{{Development Notice
|status = Active Maintenance
}}


'''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.
{{GameModule
| type = Meta & Framework
| category = [[:Category:Meta & Framework|Meta & Framework]]
| Functional Layer = Maintenance
| Application Layer = Framework Infrastructure
| Version = 0.1
| Maturity = Development
| Last Updated = 2026-07-14
| 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.
}}


'''Fix:''' Set `$smwgNamespacesWithSemanticLinks[NS_TEMPLATE] = true;` in LocalSettings.php, then purge affected pages.
= Known Site Issues & Fixes =


'''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.
'''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 ==
* '''Technical/infrastructure bugs''' — template logic errors, namespace-specific failures, extension configuration issues (e.g. SMW settings), broken parser functions, Lua module errors.
* Issues that are '''specific to this wiki's setup''', not general MediaWiki knowledge easily found elsewhere.
* Issues worth recording '''even when unresolved''' — a documented failed fix attempt saves the next person from retrying the same dead end.
== What This Page Is NOT For ==
* '''Content calibration findings''' — those belong in a page's own Calibration Report (Talk page or `/Calibration Log`), not here.
* '''Governance/taxonomy decisions''' — those belong in [[Decision Records: Governance Memory]], not here.
* '''Open conceptual questions''' — those belong as a [[Breadcrumb Philosophy|breadcrumb]] on the relevant page itself, not here, unless the question is specifically about a technical mechanism.
* '''General MediaWiki documentation''' — if the answer is "read the MediaWiki manual," it doesn't need an entry here. This page is for things '''specific to how this wiki is configured''', not general platform knowledge.
'''Rule of thumb:''' if fixing it required understanding something specific about *this* wiki's configuration or *this* project's templates — not just MediaWiki in general — it belongs here.
== How to Use This Page ==
* '''Reports and discussion about entries on this page happen on this page's Talk page''' — not inline here. This page stays a clean, scannable log; the reasoning, back-and-forth, and any dispute about a fix lives on Talk.
* When you find or fix an issue, add an entry below using the format in '''How to Add an Entry'''.
* When you '''attempt''' a fix that '''doesn't work''', record that too — a documented failed attempt is genuinely valuable; it prevents the next person from repeating it.
* Mark status honestly: '''Open''' (unresolved), '''Mitigated''' (workaround exists, root cause not fixed), or '''Resolved''' (actually fixed).
== How to Add an Entry ==
<pre><nowiki>
== [Short, specific title of the issue] ==
'''Status:''' Open / Mitigated / Resolved
'''Symptom:''' What actually goes wrong, concretely — what you'd observe if you hit this.
'''Root cause:''' What's actually causing it, if known. State "not yet identified" if unknown rather than guessing.
'''Fix (or attempted fix):''' What was tried, and whether it worked. If it didn't work, say so plainly — that's still valuable information.
'''Current mitigation:''' If no real fix exists yet, what's the practical workaround in the meantime.
'''Found by:''' Who found it, and when.
'''Next steps:''' What still needs investigating, if anything.
</nowiki></pre>
== Log ==
<!-- Add new entries below this line, most recent first -->
== See Also ==
* [[Breadcrumb Philosophy]]
* [[Decision Records: Governance Memory]]
* [[Page Structure Calibration Checklist]]
== Calibration Dependencies ==
* [[Breadcrumb Philosophy]]
'''See the Game. Refuse the Game. Build Better.'''
[[Category:Meta & Framework]]
[[Category:Site Maintenance]]
[[Category:Site Maintenance]]
<div style="display:none;">
{{Resource
| Title = Known Site Issues & Fixes
| URL = https://www.thesovereigngames.com/wiki/Known_Site_Issues_%26_Fixes
| Description = A single-page log of known technical bugs, quirks, and configuration issues found on this wiki — symptoms, root causes, fixes, and current status.
| Category = Meta & Framework
}}
</div>
{{Admin Page Status
| categorization = Done
| calibration_review = Self-Assessment
| instrument_grade = Development
| validation = Low
| calibration_rationale = First creation of this page. Structured as a single scannable log per project owner's explicit choice (simpler than Decision Records' index/report split, since site issues are typically shorter). Scope deliberately narrowed to technical/infrastructure issues only, with explicit exclusions for content, governance, and conceptual questions to prevent scope creep into territory already covered by other mechanisms.
| review_confidence = Moderate
| review_date = 2026-07-14
| reviewed_by = Sovereign
| priority = Core
| review_threshold = 60
| has_backlinks = Not checked
| outbound_links_valid = Not checked
| in_outline = No
| in_category_outline = No
| templates_complete = Done
| formatting_standard = Meets standard
| symmetry_check = Not applicable
| self_report_flagged = No
| terminology_consistent = Yes
| standing_check = Self-assessed only
| drift_report_status = None open
| depends_on = Breadcrumb Philosophy
}}

Revision as of 05:16, 16 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.




Sovereign-Games-OG-Image.jpg

Meta

Known Site Issues & Fixes

Type Meta & Framework
Functional Layer
Application Layer Framework Infrastructure
Category Meta & Framework
Version 0.1
Maturity Development
Last Calibration 2026-07-14
Status Permanent Beta
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.

Core Principles

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

Navigation

Related


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

  • Technical/infrastructure bugs — template logic errors, namespace-specific failures, extension configuration issues (e.g. SMW settings), broken parser functions, Lua module errors.
  • Issues that are specific to this wiki's setup, not general MediaWiki knowledge easily found elsewhere.
  • Issues worth recording even when unresolved — a documented failed fix attempt saves the next person from retrying the same dead end.

What This Page Is NOT For

  • Content calibration findings — those belong in a page's own Calibration Report (Talk page or `/Calibration Log`), not here.
  • Governance/taxonomy decisions — those belong in Decision Records: Governance Memory, not here.
  • Open conceptual questions — those belong as a breadcrumb on the relevant page itself, not here, unless the question is specifically about a technical mechanism.
  • General MediaWiki documentation — if the answer is "read the MediaWiki manual," it doesn't need an entry here. This page is for things specific to how this wiki is configured, not general platform knowledge.

Rule of thumb: if fixing it required understanding something specific about *this* wiki's configuration or *this* project's templates — not just MediaWiki in general — it belongs here.

How to Use This Page

  • Reports and discussion about entries on this page happen on this page's Talk page — not inline here. This page stays a clean, scannable log; the reasoning, back-and-forth, and any dispute about a fix lives on Talk.
  • When you find or fix an issue, add an entry below using the format in How to Add an Entry.
  • When you attempt a fix that doesn't work, record that too — a documented failed attempt is genuinely valuable; it prevents the next person from repeating it.
  • Mark status honestly: Open (unresolved), Mitigated (workaround exists, root cause not fixed), or Resolved (actually fixed).

How to Add an Entry

== [Short, specific title of the issue] ==

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

'''Symptom:''' What actually goes wrong, concretely — what you'd observe if you hit this.

'''Root cause:''' What's actually causing it, if known. State "not yet identified" if unknown rather than guessing.

'''Fix (or attempted fix):''' What was tried, and whether it worked. If it didn't work, say so plainly — that's still valuable information.

'''Current mitigation:''' If no real fix exists yet, what's the practical workaround in the meantime.

'''Found by:''' Who found it, and when.

'''Next steps:''' What still needs investigating, if anything.

Log

See Also

Calibration Dependencies

See the Game. Refuse the Game. Build Better.



Page Reference

Title Known Site Issues & Fixes
URL https://www.thesovereigngames.com/wiki/Known_Site_Issues_%26_Fixes
Description A single-page log of known technical bugs, quirks, and configuration issues found on this wiki — symptoms, root causes, fixes, and current status.
Category Meta & Framework



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