Forums Bug Reports Thread

Notification-preferences "see Settings" link points to #section-twofactor anchor that no longer exists

Patrick Bass · Jun 6 · 15 · 1 Locked
[Minor] [Normal Priority] [Bug Fixed] [Always Reproduces]
🚀 OP Jun 6, 2026 5:11pm

Area: Account & identity (audit phase 1) · Surface: /notifications/preferences (NotificationController@preferences) · Dimension: law-2-nav-orphans · Severity: minor

The copy promises to take the user to the push-enable setting but the anchor target was removed when 2FA was retired. The link lands at the top of /account/settings instead of the Push Notifications card, so the user has to hunt for it. The right anchor is #section-push.

Evidence

platform/templates/profile/notification-preferences.php L33: "...requires enabling push on this device — see <a href=\"/account/settings#section-twofactor\">Settings</a>)."
Grep for `section-twofactor` across templates/ returns ONLY this reference — no element defines id="section-twofactor". The actual Push section in platform/templates/profile/settings.php is L800: <div class="card" id="section-push">. A comment at settings.php:773 notes the /account/2fa/* routes were retired.

Suggested fix. Change the href to /account/settings#section-push on platform/templates/profile/notification-preferences.php:33.

Filed by the automated tenant-app audit (phase 1) and adversarially evidence-verified. Status: verified. Open — not yet actioned.


Patrick Bass
@mobieus

🚀 Jun 7, 2026 5:31am

Resolved — fixed and deployed. Commit af2b6678f082, shipped dev-first then to all tenants on 2026-06-06.

Changed the push-enablement help link at line 33 from /account/settings#section-twofactor to /account/settings#section-push so the anchor matches the surrounding 'enabling push on this device' copy.

Status: fixed. Thread closed and locked.


Patrick Bass
@mobieus

Log in or register to reply to this thread.