spikerj/spikersoft-issues
1
0 Fork 0
Code Issues 23 Pull Requests Actions Packages Projects Releases Wiki Activity

# [Bug] “Back to Dashboard” and “View Public Home” Buttons Not Persisting Across Navigation #1160

New Issue
Closed
opened 2026-10-02 01:32:36 +00:00 by enjin2310 · 1 comment
enjin2310 commented 2026-10-02 01:32:36 +00:00
Copy link
Copy source

Summary

In SpikerSoft, the navigation buttons “Back to My Dashboard” and “View Public Home” do not appear consistently when switching between the Dashboard and Public Home pages. The buttons only render when the user transitions directly between these two pages, but disappear if the user navigates through other sections before returning to the Dashboard.

Issue Description

After logging in, users land on the Public Home (Landing Page), which includes the “Back to My Dashboard” button. Clicking this button correctly redirects to the Dashboard, where the “View Public Home” button appears. However, if the user navigates through other sections (e.g., Learn, Games, Art Studio, or Profile) and then returns to the Dashboard, the “View Public Home” button fails to load. This indicates that the button’s rendering logic depends on the navigation path rather than the page state.

Environment

Property Value
Application SpikerSoft
Module Dashboard / Public Home
Environment Production
Browser Firefox / Chrome
Operating System Windows 11
Version v2026.10.02a
Device Desktop

Preconditions

User must be logged in and have access to both Dashboard and Public Home views.

Steps to Reproduce

  1. Log in to SpikerSoft.
  2. On the Landing Page (Public Home), click “Back to My Dashboard.”
  3. Observe that the “View Public Home” button appears correctly in the Dashboard.
  4. Navigate to another section (e.g., Learn → Games → Profile).
  5. Return to the Dashboard.
  6. Observe that the “View Public Home” button is missing.

Expected Result

The “View Public Home” button should always be visible in the Dashboard, regardless of the navigation path taken to reach it.

Actual Result

  • The “View Public Home” button only appears when arriving at the Dashboard directly from the Public Home.
  • If the user navigates through other sections first, the button fails to render.

Evidence

  • Screenshots show the Dashboard with and without the “View Public Home” button depending on navigation sequence.

Impact

  • Reduces navigation consistency and user experience.
  • Prevents users from easily returning to the Public Home after exploring other sections.
  • Minor but noticeable usability issue.

Frequency

Always

Reproducibility

100%

Severity

Medium

Suggested Fix

  • Review the rendering logic for the Dashboard header component.
  • Ensure the “View Public Home” button is conditionally displayed based on user authentication and page context, not navigation history.
  • Implement persistent state or global route tracking to maintain button visibility across all navigation paths.
## Summary In **SpikerSoft**, the navigation buttons **“Back to My Dashboard”** and **“View Public Home”** do not appear consistently when switching between the **Dashboard** and **Public Home** pages. The buttons only render when the user transitions directly between these two pages, but disappear if the user navigates through other sections before returning to the Dashboard. ## Issue Description After logging in, users land on the **Public Home (Landing Page)**, which includes the **“Back to My Dashboard”** button. Clicking this button correctly redirects to the **Dashboard**, where the **“View Public Home”** button appears. However, if the user navigates through other sections (e.g., Learn, Games, Art Studio, or Profile) and then returns to the Dashboard, the **“View Public Home”** button fails to load. This indicates that the button’s rendering logic depends on the navigation path rather than the page state. ## Environment | Property | Value | |-----------|--------| | Application | SpikerSoft | | Module | Dashboard / Public Home | | Environment | Production | | Browser | Firefox / Chrome | | Operating System | Windows 11 | | Version | v2026.10.02a | | Device | Desktop | ## Preconditions User must be logged in and have access to both **Dashboard** and **Public Home** views. ## Steps to Reproduce 1. Log in to **SpikerSoft**. 2. On the **Landing Page (Public Home)**, click **“Back to My Dashboard.”** 3. Observe that the **“View Public Home”** button appears correctly in the Dashboard. 4. Navigate to another section (e.g., Learn → Games → Profile). 5. Return to the **Dashboard**. 6. Observe that the **“View Public Home”** button is missing. ## Expected Result The **“View Public Home”** button should always be visible in the Dashboard, regardless of the navigation path taken to reach it. ## Actual Result - The **“View Public Home”** button only appears when arriving at the Dashboard directly from the Public Home. - If the user navigates through other sections first, the button fails to render. ## Evidence - Screenshots show the **Dashboard** with and without the **“View Public Home”** button depending on navigation sequence. ## Impact - Reduces navigation consistency and user experience. - Prevents users from easily returning to the Public Home after exploring other sections. - Minor but noticeable usability issue. ## Frequency Always ## Reproducibility 100% ## Severity Medium ## Suggested Fix - Review the rendering logic for the **Dashboard** header component. - Ensure the **“View Public Home”** button is conditionally displayed based on user authentication and page context, not navigation history. - Implement persistent state or global route tracking to maintain button visibility across all navigation paths.
Screenshot 2026-10-01 212529.png
253 KiB
Screenshot 2026-10-01 213215.png
300 KiB
Screenshot 2026-10-01 212543.png
855 KiB
Screenshot 2026-10-01 212529.png Screenshot 2026-10-01 213215.png Screenshot 2026-10-01 212543.png
spikerj commented 2026-10-02 03:42:04 +00:00
Owner
Copy link
Copy source

Confirmed and fixed — thanks for the clear steps and screenshots; they made this quick to find.

What was wrong: the dashboard lives at two addresses. spikersoft.com/ shows the dashboard wrapped in the home switch bar ("Ver inicio público" / "Volver a mi panel"). The Dashboard item in your account menu goes to spikersoft.com/dashboard, which loaded the dashboard on its own, without the bar. So it wasn't remembering or forgetting anything — it depended on which address you arrived at. Your screenshots show it: one says /?view=landing, the other /dashboard.

What changed (spikerj/spikersoft-angular#1409, merged):

  • /dashboard now loads the same home switch, pinned to the dashboard view, so the bar is always there — whether you come from the menu, a bookmark, or another section.
  • "Ver inicio público" from /dashboard takes you to the public home as before.
  • Also fixed while there (reported in #1159): the icons in those buttons sat above their text, because each icon was inside an @switch block, which stops Angular Material from placing it in the button's icon slot. Each button now has its icon as a direct child, so it lines up with the text.

It will be live with the next deploy. Reopen this if you still see the bar missing after the version in the corner changes.

Tip: noting the URL at each step, as your screenshots did, is often the fastest clue for this kind of "it only happens sometimes" bug.

Confirmed and **fixed** — thanks for the clear steps and screenshots; they made this quick to find. **What was wrong:** the dashboard lives at two addresses. `spikersoft.com/` shows the dashboard *wrapped in* the home switch bar ("Ver inicio público" / "Volver a mi panel"). The **Dashboard** item in your account menu goes to `spikersoft.com/dashboard`, which loaded the dashboard *on its own*, without the bar. So it wasn't remembering or forgetting anything — it depended on which address you arrived at. Your screenshots show it: one says `/?view=landing`, the other `/dashboard`. **What changed** (spikerj/spikersoft-angular#1409, merged): - `/dashboard` now loads the same home switch, pinned to the dashboard view, so the bar is always there — whether you come from the menu, a bookmark, or another section. - "Ver inicio público" from `/dashboard` takes you to the public home as before. - Also fixed while there (reported in #1159): the icons in those buttons sat *above* their text, because each icon was inside an `@switch` block, which stops Angular Material from placing it in the button's icon slot. Each button now has its icon as a direct child, so it lines up with the text. It will be live with the next deploy. **Reopen this** if you still see the bar missing after the version in the corner changes. Tip: noting the URL at each step, as your screenshots did, is often the fastest clue for this kind of "it only happens sometimes" bug.
spikerj added the bug label 2026-10-02 03:42:04 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
agentic
Actionable surfaced by the agentic architecture & security review
 bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 epic
Cross-repo epic — children live in per-repo trackers
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 sonarqube
Code quality issue surfaced by SonarQube (bug / code smell)
 wontfix
This won't be fixed
No labels bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
spikerj (Joseph Spiker)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: spikerj/spikersoft-issues#1160