#8932 closed defect (bug) (fixed)
Make sure to display a 404 if a Members (sub)nav misses a valid screen function
Reported by: | imath | Owned by: | imath |
---|---|---|---|
Milestone: | 12.0.0 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Members | Keywords: | has-patch |
Cc: |
Description
Working on documenting the BP_Component
class, I noticed the BP Rewrites API wasn't displaying a 404 if a plugin was adding a members nav/subnav without a valid screen function. The Legacy URL parser was doing this fine.
To maintain this behavior in 12.0.0, we need to check the parsed query once the Members primary/secondary navigations are set to verify the current Members’ component action has a valid screen function.
Change History (8)
This ticket was mentioned in PR #125 on buddypress/buddypress by @imath.
19 months ago
#1
- Keywords has-patch added; needs-patch removed
#5
@
15 months ago
- Keywords needs-patch added; has-patch removed
BP_Members_Component::check_parsed_query()
is not taking care of not existing Member's main nav. In this case it should display a 404.
This ticket was mentioned in PR #179 on buddypress/buddypress by @imath.
15 months ago
#6
- Keywords has-patch added; needs-patch removed
This case wasn't taken in account into previous patch/fix.
Trac ticket: https://buddypress.trac.wordpress.org/ticket/8932
Displaying a 404 if a Members (sub)nav misses a valid screen function is preserving what was happening in this case with the BP Legacy URL parser.
Trac ticket: https://buddypress.trac.wordpress.org/ticket/8932