mirror of
https://github.com/fosrl/pangolin.git
synced 2026-07-16 06:08:33 -05:00
[GH-ISSUE #2528] UI toggle for "Enable Rules" and "Email Whitelist" does not reflect DB state on initial load #38976
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#38976
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Kapot on GitHub (Feb 24, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2528
Describe the Bug
When
applyRulesand/oremailWhitelistEnabledare set to1directly in the SQLite database, the corresponding toggles in the UI ("Enable Rules" on the Rules tab, "Email Whitelist" on the Authentication tab) render as OFF after a fulldocker compose restart. The data itself (rules and emails) is visible once the toggle is manually clicked on, confirming the DB values are correct and being read — only the initial toggle state is wrong.Environment
To Reproduce
emailWhitelistEnabled FROM resources WHERE resourceId = X;
appears OFF despite applyRules = 1 in DB. Navigate to the Authentication tab —
"Email Whitelist" toggle appears OFF despite emailWhitelistEnabled = 1 in DB.
was present all along.
Expected Behavior
The UI should reflect the actual DB state on load. If applyRules = 1 and emailWhitelistEnabled = 1, the corresponding toggles should render as ON after restart without requiring manual interaction.