You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
🐞[Bug]: Navigation menu links redirect users to outdated deployment #2051
The navigation menu accessible from the 3-dot (hamburger) button on the Contribute page contains links that redirect users to the old deployment/version of the website instead of the current one.
This misguides users, creates confusion, and negatively impacts the overall user experience.
Expected behavior
Steps to Reproduce
Visit the Contribute page.
Click the 3-dot navigation button in the top-right corner.
Click any navigation item (Home, Platform Highlights, Screenshots, Community Programs, Read Articles, etc.).
Observe that the links open the older deployment rather than navigating within the current application.
Expected Behavior
All navigation items should route to the current deployment/application.
Users should remain on the latest version of the website.
Actual Behavior
Navigation buttons redirect users to an outdated deployment.
Users unintentionally leave the current version and end up on an older instance of the application.
Impact
❌ Confusing user navigation
❌ Inconsistent experience between deployments
❌ Users may interact with outdated content/features
❌ Reduces trust in the application's navigation
Possible Cause
The navigation links are likely using hardcoded URLs pointing to the previous deployment instead of:
relative routes,
the current deployment URL,
or centralized route configuration.
Suggested Fix
Replace outdated hardcoded deployment URLs with application routes or the current base URL.
Ensure all navigation links use the latest deployment consistently.
Thank you for creating this issue! We'll look into it as soon as possible. Your contributions are highly appreciated! 😊
🤖 Assignment Guidelines
To get assigned to this issue, simply leave a comment requesting assignment.
The AI bot will automatically assign you if you meet the following eligibility criteria:
You do not currently have any other active assigned issues in this repository.
If you were previously assigned an issue, you must have submitted a Pull Request for it before requesting a new one.
This issue has been triaged as a frontend task (level:beginner).
Expected Effect & Scope: The issue is valid with clear reproduction steps and expected behavior. It is in scope and not related to doctors. Although the user marked it as 'Backend', the problem description and suggested fix (updating navigation links/routes in the UI) clearly indicate a frontend-web issue. It's a straightforward fix, classifying it as beginner level. No duplicates were found, and no escalation is required.
Hi @avrojitduttaj! Since you opened this issue and have no other active assignments, I have automatically assigned it to you. Happy coding!
The previous assignee(s) have been unassigned due to 7 days of inactivity (no PR submitted). Pinging next in queue: @Rashmi2806525. If you are still interested, please reply with /assign or /claim to claim it.
The previous assignee(s) have been unassigned due to 7 days of inactivity (no PR submitted). Pinging next in queue: @Rashmi2806525. If you are still interested, please reply with /assign or /claim to claim it.
Activity
github-actions commentedon Jul 2, 2026
Thank you for creating this issue! We'll look into it as soon as possible. Your contributions are highly appreciated! 😊
🤖 Assignment Guidelines
To get assigned to this issue, simply leave a comment requesting assignment.
The AI bot will automatically assign you if you meet the following eligibility criteria:
github-actions commentedon Jul 2, 2026
This issue has been triaged as a frontend task (level:beginner).
Hi @avrojitduttaj! Since you opened this issue and have no other active assignments, I have automatically assigned it to you. Happy coding!
avrojitduttaj commentedon Jul 3, 2026
@SB2318 Please help me find the dropdown in the file! I couldn't find in the project local.
Rashmi2806525 commentedon Aug 1, 2026
@SB2318 i would like to solve this issue please assign it to me
github-actions commentedon Aug 3, 2026
The previous assignee(s) have been unassigned due to 7 days of inactivity (no PR submitted). Pinging next in queue: @Rashmi2806525. If you are still interested, please reply with
/assignor/claimto claim it.Rashmi2806525 commentedon Aug 3, 2026
/claim
github-actions commentedon Aug 3, 2026
Sorry @Rashmi2806525, you already have an active assignment in this repository. Please complete or unassign it before claiming a new one.
github-actions commentedon Aug 3, 2026
@Rashmi2806525 You currently have an active assigned issue. Please complete your existing work before requesting a new assignment.
10 remaining items
github-actions commentedon Aug 14, 2026
Assigned to @abhilasheggadi. You have 7 days to complete this issue. Please submit a PR referencing this issue.
harshap0 commentedon Aug 16, 2026
/assign
SB2318 commentedon Aug 17, 2026
@harshap0 Open source contribution track is closed now, but you can contribute as an individual.
ankan00V commentedon Aug 28, 2026
please assign me this issue for GSSOC 2026
Irfan-lab700 commentedon Aug 29, 2026
/assign
PanthShah2007 commentedon Sep 7, 2026
#assign
github-actions commentedon Sep 14, 2026
Hello @avrojitduttaj! Your issue #2051 has been closed. Thank you for your contribution!
github-actions commentedon Sep 14, 2026
@PanthShah2007 has been unassigned because the issue was closed before a PR was linked.