Opened 8 days ago
Closed 2 days ago
#8183 closed defect (bug) (fixed)
Tickets menu on Changeset pages redirects to make core/reports/ page instead of opening tickets menu
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Component: | Trac | Keywords: | has-patch |
| Cc: |
Description
While browsing WordPress Core Trac, specifically on a changeset page such as:
https://core.trac.wordpress.org/changeset/<id>
Clicking on the “Tickets” menu item in the top navigation does not open the expected Trac overlay/dropdown menu. Instead, it redirects the user to:
https://make.wordpress.org/core/reports/
This behavior is inconsistent with the navigation pattern on other Core Trac pages, where clicking “Tickets” opens the overlay menu allowing users to select options such as:
- Latest Tickets
- Active Tickets
- Create a Ticket .. etc
Steps to Reproduce:
- Go to any changeset page on Core Trac (e.g.,
/changeset/<id>). - Click on the “Tickets” menu item in the top navigation.
- Observe that it redirects to the Make/Core reports page instead of opening the Trac overlay menu.
Expected Behavior:
When clicking the “Tickets” menu item on a changeset page, it should behave consistently with other Core Trac pages and open the Trac overlay/dropdown menu, allowing users to choose their preferred ticket view.
Actual Behavior:
The link redirects to https://make.wordpress.org/core/reports/, breaking navigation consistency within Core Trac.
Impact:
Inconsistent navigation experience across Core Trac. Breaks user expectations when switching between changesets and ticket views.
PS: Used AI model to create a description and Subject line of the ticket.
Demo Screencast - https://app.godam.io/web/video/bgdmm5pkgf
Change History (7)
This ticket was mentioned in Slack in #meta by hbhalodia. View the logs.
7 days ago
#3
@
4 days ago
Just noting this happens due to a JS error:
wp-trac.js?232:1755 Uncaught TypeError: Cannot read properties of null (reading '1')
@hbhalodia It's an easy fix, since you've shown interest in working on this code I've avoided fixing it, feel free to submit a PR against https://github.com/wordpress/wordpress.org/ if you're able to figure out a way to test it!
I suggest using Chrome Content Overrides as it's only a JS error and not a templating/trac-config error.
This ticket was mentioned in PR #556 on WordPress/wordpress.org by @hbhalodia.
3 days ago
#4
- Keywords has-patch added
## Issue
Meta ticket -- https://meta.trac.wordpress.org/ticket/8183
- There was a JS error on the page accessing the value from the null.
- Added a safe check before accessing.
#5
@
3 days ago
Hi @dd32, Thanks for the info.
I was able to test it using Chrome Content Override.
I do have raised the PR for the same -- https://github.com/WordPress/wordpress.org/pull/556
Could you please review the PR?
Thank you,
#6
@
3 days ago
Demo video --> https://app.godam.io/web/video/e20puqvp4u
Originally reported here - https://core.trac.wordpress.org/ticket/64733