The Visual Troubleshoot flowchart maps user symptoms to entries in the Web Dictionary and Error Guide. When a new section name is introduced to either JSON file (not just new entries in an existing section), the flowchart’s SYMPTOMS array needs a manual update. If skipped, that entire new section becomes unreachable through the flowchart despite being fully live and correctly formatted everywhere else.
⚡ Quick Fix (TL;DR)
The Culprit: The CSS & Layout Issues section was added to the Error Guide with 18 complete entries. The section mapping in the flowchart was never updated, leaving it invisible to the Troubleshoot buttons.
The Fix: The flowchart's SYMPTOMS array was updated to include the new section; the affected symptom's description was broadened to match. Treat this as a template: any future new section name added to either JSON file should trigger a deliberate check for completeness in the flowchart mapping, rather than waiting for a visitor report to uncover the gap.
Rather not untangle this yourself? Our Done-For-You team handles exactly this kind of thing, start to finish.
See DFY options → Was this helpful? Thanks for the feedback!
Tagged in :