#2671 closed defect (bug) (fixed)
Forums: Archived topics can redirect to another topic
Reported by: | SergeyBiryukov | Owned by: | SergeyBiryukov |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Support Forums | Keywords: | |
Cc: |
Description
- If you're a moderator, log out of the forums or open an Incognito window.
- Visit https://wordpress.org/support/topic/help-me-75/ (an archived topic)
- It redirects to https://wordpress.org/support/topic/help-me-63/, which shouldn't happen.
Change History (9)
#1
@
8 years ago
- Summary changed from Forums: Archived topics can redirect to an other topic to Forums: Archived topics can redirect to another topic
This ticket was mentioned in Slack in #forums by sergey. View the logs.
8 years ago
#4
@
8 years ago
- Owner set to SergeyBiryukov
- Resolution set to fixed
- Status changed from new to closed
In 5280:
#6
@
8 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
Still seeing the redirect, apparently [5280] didn't work as expected.
Works fine on my local install though (just tested again), might be something dotorg-specific. I guess this will have to wait until someone with a sandbox can take a look.
#7
@
8 years ago
The code in [5280] is checking the topic for conditional is_404()
, as shown in curl here it shows a 301
redirect from https://wordpress.org/support/topic/help-me-75/
to https://wordpress.org/support/topic/help-me-63/
curl -I https://wordpress.org/support/topic/help-me-75/ HTTP/1.1 301 Moved Permanently Server: nginx Date: Fri, 21 Apr 2017 22:35:25 GMT Content-Type: text/html; charset=UTF-8 Connection: keep-alive Strict-Transport-Security: max-age=360 X-Olaf: ⛄ Expires: Wed, 11 Jan 1984 05:00:00 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Location: https://wordpress.org/support/topic/help-me-63/ X-Frame-Options: SAMEORIGIN X-nc: MISS lax 249
Thinking bbPress might need some additional support for custom statuses here :thinking:
Note: See
TracTickets for help on using
tickets.
This is WordPress automatically redirecting to the nearest matching slug of a published post...
To prevent this I think this is all that'd would be needed, but would want to do some testing with other post statuses: