| Name |
Last commit
|
Last Update |
|---|---|---|
| .. | ||
| components | ||
| forgot-password | ||
| hooks | ||
| lib | ||
| otp | ||
| passkey | ||
| reset-password-confirm | ||
| secure-verification | ||
| sign-in | ||
| sign-up | ||
| api.ts | ||
| auth-layout.tsx | ||
| constants.ts | ||
| index.ts | ||
| types.ts |
/api/status never returned `register_enabled` or `password_register_enabled`, so the sign-in page had no way to react when an admin disabled registration. The "Sign up" link was only gated on `self_use_mode_enabled`, which is a separate and unrelated concept (single-user vs. multi-user deployment). Result: toggling "Registration Enabled" in admin settings had no visible effect on the login page — users could still see the sign-up link even when registration was disabled, and could not see it even when it was enabled (if the system happened to be in self-use mode from initial setup). Fix: - Add `register_enabled` and `password_register_enabled` to GetStatus() - Gate the "Sign up" link on `register_enabled !== false` in addition to the existing `!self_use_mode_enabled` check Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
| Name |
Last commit
|
Last Update |
|---|---|---|
| .. | ||
| components | Loading commit data... | |
| forgot-password | Loading commit data... | |
| hooks | Loading commit data... | |
| lib | Loading commit data... | |
| otp | Loading commit data... | |
| passkey | Loading commit data... | |
| reset-password-confirm | Loading commit data... | |
| secure-verification | Loading commit data... | |
| sign-in | Loading commit data... | |
| sign-up | Loading commit data... | |
| api.ts | Loading commit data... | |
| auth-layout.tsx | Loading commit data... | |
| constants.ts | Loading commit data... | |
| index.ts | Loading commit data... | |
| types.ts | Loading commit data... |