Witching Hour — upgrade and regression checks
Keep your edits
Export/back up the installed Witching Hour style, record its exact key/version/default/active state, and save any companion settings. A fresh XML import can replace saved text, regions, colors or assets; do not reimport over an edited live theme just because an addon companion has a newer patch.
Check after a change
- Confirm the correct style key and default/active selection; a different theme should not become default silently.
- Check header/footer branding, hero/CTA text where the theme supplies them, menu links and light/dark contrast.
- Test mobile rails, chat/settings dialogs, rich text editor and native select labels on a real page. Refresh cached assets before diagnosing stale CSS.
- Check a topic/reply, resource page and staff screen as appropriate; a screenshot of the homepage alone does not prove all templates.
If an Edit button only refreshes and no settings open, record the core/theme versions and use an existing authorized companion settings screen where supplied. Repeated clicking or installing a random addon is not a fix for a missing core editor. Restore the backed-up style on regression; do not delete user posts or reinstall the forum.
Licensed remote updates require a compatible corrected core/service; the reviewed156x has known LMP contract blockers. Manual authorized import/update remains the documented route until that journey is proven.
