From cbc94babe0e2d8263d871920ad5c1d8591659a69 Mon Sep 17 00:00:00 2001 From: Scott Idem Date: Tue, 16 Jun 2026 14:10:54 -0400 Subject: [PATCH] fix(pres_mgmt): Location column ignored admin's Hide Location setting MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Same bug pattern as the earlier POC column fix. The Session Search results table's Location column prop only ever read the local-only, never-synced hide__session_li_location_field — never the admin-synced hide__session_location (Config page > Session Field Visibility > Hide Location). Column always showed regardless of that setting or permission level. Fixed in pres_mgmt/+page.svelte: hide__session_location || hide__session_li_location_field The other two usages of this component already hardcode hide__session_location={true} correctly (you're already on that location's own page, showing its name again would be redundant). Logged in PROJECT__AE_Events_PressMgmt_Config_Cleanup.md with a note to audit other hide__* fields for the same gap if more reports come in. svelte-check: 0 errors, 0 warnings. Co-Authored-By: Claude Sonnet 4.6 --- .../PROJECT__AE_Events_PressMgmt_Config_Cleanup.md | 13 +++++++++++++ .../[event_id]/(pres_mgmt)/pres_mgmt/+page.svelte | 3 ++- 2 files changed, 15 insertions(+), 1 deletion(-) diff --git a/documentation/PROJECT__AE_Events_PressMgmt_Config_Cleanup.md b/documentation/PROJECT__AE_Events_PressMgmt_Config_Cleanup.md index 4aaa64f6..2ff735a6 100644 --- a/documentation/PROJECT__AE_Events_PressMgmt_Config_Cleanup.md +++ b/documentation/PROJECT__AE_Events_PressMgmt_Config_Cleanup.md @@ -321,6 +321,19 @@ Safe and backward compatible — old DB records fall through to `?? false` defau (no more System section). Old DB records with a `lock_config` key are simply ignored now, same as any other removed key. Moved the now-fully-orphaned `ae_comp__event_settings_pres_mgmt_form.svelte` to trash in the same pass (Step 5). +- [x] **Location column ignored the admin's "Hide Location" setting (2026-06-16)** — same + bug pattern as the POC column fix earlier, just missed for Location. The Session Search + results table's Location column prop only ever read the local-only, never-synced + `hide__session_li_location_field` — it never looked at the admin-synced + `hide__session_location` (Config page → Session Field Visibility → Hide Location) at all. + So the column always showed regardless of that setting or the user's permission level, + exactly as reported. Fixed in `pres_mgmt/+page.svelte`: + `hide__session_location || hide__session_li_location_field`. The two other usages of this + component (`locations/ae_comp__event_location_obj_li.svelte`, + `location/[event_location_id]/+page.svelte`) already hardcode `hide__session_location={true}` + — correct, since you're already on that location's own page. Worth auditing the other + per-event hide__* fields for the same "admin field exists but the list/table prop + computation never reads it" gap if more reports come in. ### Step 6 scope (mechanical find-replace) diff --git a/src/routes/events/[event_id]/(pres_mgmt)/pres_mgmt/+page.svelte b/src/routes/events/[event_id]/(pres_mgmt)/pres_mgmt/+page.svelte index ecdd7240..5f50fe11 100644 --- a/src/routes/events/[event_id]/(pres_mgmt)/pres_mgmt/+page.svelte +++ b/src/routes/events/[event_id]/(pres_mgmt)/pres_mgmt/+page.svelte @@ -484,7 +484,8 @@ if ( {#if event_session_id_li.length}