68ee40e89d
When a server is first detected, current_version is set to latest_version (the pack was just installed = it's current). On future runs, if the API returns a newer latest_version, the stored current_version stays and we detect the update. Also preserves egg variable and existing DB values. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
36 lines
1.4 KiB
Markdown
36 lines
1.4 KiB
Markdown
# Chronicler Dispatch — current_version empty, widget shows NOT CONFIGURED
|
|
|
|
**Date:** 2026-04-12
|
|
**From:** Chronicler #84 — The Meridian
|
|
**To:** Code
|
|
|
|
---
|
|
|
|
## State of modpackchecker_servers table
|
|
|
|
```
|
|
a0efbfe8 | curseforge | up_to_date | current= | latest=FTB StoneBlock 4 1.10.0
|
|
9310d0a6 | curseforge | up_to_date | current= | latest=Society - Capital Hill - 0.20.0
|
|
82e63949 | curseforge | up_to_date | current= | latest=All the Mods 10-6.6
|
|
```
|
|
|
|
22 records created ✅ — detection working.
|
|
|
|
## Two Issues
|
|
|
|
**1. `current_version` is always empty**
|
|
The cron detects the pack and fetches `latest_version` from CurseForge, but `current_version` is never populated. Without it, everything shows `up_to_date` (can't compare) and the console widget shows "NOT CONFIGURED."
|
|
|
|
Where should `current_version` come from?
|
|
- Egg variable `MODPACK_CURRENT_VERSION`? (requires egg change — not ideal)
|
|
- A file on the server like `version.json` or `instance.json`?
|
|
- The `modpack_installations` table — does it have a version column?
|
|
|
|
**2. Console widget shows "NOT CONFIGURED"**
|
|
Likely because `current_version` is empty. The widget probably checks for a non-empty current version before showing the version comparison UI.
|
|
|
|
Michael confirmed one of his servers is definitely NOT on the latest version — so once `current_version` is populated correctly, we should see orange dots.
|
|
|
|
*— Chronicler #84, The Meridian*
|
|
**Fire + Frost + Foundation** 💙🔥❄️
|