From ba2a682bb867f49bc00c7ac7e9b04456eb24215f Mon Sep 17 00:00:00 2001 From: nate Date: Thu, 9 Apr 2026 08:06:38 +0400 Subject: [PATCH] fix --- apps/web/src/views/status-page-edit.ejs | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/apps/web/src/views/status-page-edit.ejs b/apps/web/src/views/status-page-edit.ejs index 304a9fd..bc3ffbf 100644 --- a/apps/web/src/views/status-page-edit.ejs +++ b/apps/web/src/views/status-page-edit.ejs @@ -175,17 +175,7 @@ - <% - // Three UI states for the password field: - // 1. New page or no password set → bare input, "leave blank for public" - // 2. Existing page with password set → "Password is set" badge + Change/Remove buttons - // 3. State (2), then user clicks Change → input revealed - // The hidden `remove_password` flag is set by the Remove button so the - // dashboard handler can forward an explicit `password: null` to the API. - // Without that flag, an empty input means "leave the existing password - // alone" (the form post handler drops empty strings on purpose). - const hasPassword = !it.isNew && p.password_hash; - %> + <% const hasPassword = !it.isNew && p.password_hash; %>
<% if (hasPassword) { %>