CyberMind-FR aefc6e5265 fix: Read status from data parameter in wizard step 1 (v0.6.0-r5) ... Fix Next button remaining disabled despite correct status: - Change renderStep1 to read from data parameter instead of wizardData - Read status.crowdsec and status.lapi_status from passed data - Ensures button state reflects actual API response Issue: Next button not clickable even with LAPI available Cause: renderStep1 reading from stale wizardData instead of fresh data Solution: Read from data parameter passed by render() Frontend Changes: - htdocs/luci-static/resources/view/crowdsec-dashboard/wizard.js - renderStep1: Read from data.status instead of this.wizardData - Extract crowdsecRunning and lapiAvailable from data parameter Version: 0.6.0-5 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>		2026-01-07 09:05:34 +01:00
..
alerts.js	fix(luci-app-crowdsec-dashboard): Fix API instantiation error	2026-01-06 15:56:33 +01:00
bouncers.js	feat: Firewall Bouncer Management UI in Bouncers Page	2026-01-06 20:25:15 +01:00
decisions.js	fix(luci-app-crowdsec-dashboard): Fix API instantiation error	2026-01-06 15:56:33 +01:00
metrics.js	fix: String concatenation with DOM elements in CrowdSec views	2026-01-06 19:24:55 +01:00
overview.js	feat(luci-app-crowdsec-dashboard): Add graceful error handling when service stopped	2026-01-06 16:07:01 +01:00
settings.js	fix: String concatenation with DOM elements in CrowdSec views	2026-01-06 19:24:55 +01:00
waf.js	fix: String concatenation with DOM elements in CrowdSec views	2026-01-06 19:24:55 +01:00
wizard.js	fix: Read status from data parameter in wizard step 1 (v0.6.0-r5)	2026-01-07 09:05:34 +01:00