Hello Admins,
I am a lifetime NESA member trying to get a persistent profile rendering bug escalated to the development team. For several months, my public alumni profile page has been displaying a changing dynamic system date under the “Eagle Earned” field instead of pulling my actual historical record data.
Every night at midnight, the date changes to show the current calendar day. I am trying to get a system administrator to inspect the template tags or data bindings for the “Eagle Earned” field on the NESA portal to ensure it maps to the static backend record.
A code-level look at the issue indicates the template file is accidentally utilizing a dynamic date generator instead of pulling the user profile variable:
-
The Current Bug (Dynamic Rendering):
<h2>Report Date: <%= new Date().toLocaleDateString() %></h2>(Changes every day) -
The Expected Fix (Static Data Binding):
<h2>Report Date: December 11, 1997</h2>(Stays fixed based on member database)
Member Verification Details:
-
Scouting America Member ID (MID): 110209182
-
Actual Eagle Scout Date: 12/11/1997
-
Council Number: 546
I have tried coordinating this through the standard NESA email inbox for months, but it appears to be stuck in a customer service bottleneck. Because this milestone is incredibly important to me and my family, specifically because of my stage-4 cancer battle, I want to ensure my directory profile, which I’ve made fully polished and public, is displaying accurately forever.
Could a member of the Advisory Council or a System Admin please escalate this template/database mapping issue directly to the National IT / web engineering queue?
Thank you kindly for your assistance,
Yours in Scouting Forever
1) Hardware: Desktop & Mobile both PC & Apple
2) Operating system: Current.
3) Browser: Windows,Google, Apple Explorer,
4) Browser cache has been cleared.
5) Member ID 110209182 Council 546
