Opened 11 years ago
Closed 11 years ago
#5149 closed defect (bug) (fixed)
404 error page not being used when root profiles is enabled
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 1.9 | Priority: | normal |
Severity: | normal | Version: | 1.8.1 |
Component: | Route Parser | Keywords: | needs-patch |
Cc: |
Description
- Enable root profiles by adding the following to bp-custom.php
define ( 'BP_ENABLE_ROOT_PROFILES', true );
- Visit page example.com/username/jahayatsfg
What should happen:
You should be taken to a 404 page because "jahayatsfg" obviously doesn't exist.
What actually happens:
I'm not entirely sure which page it is that you're taken to but it isn't the 404 page as you would expect.
Change History (3)
#1
@
11 years ago
- Component changed from Core to Rewrite Rules
- Keywords needs-patch added
- Milestone changed from Awaiting Review to 1.9
#2
@
11 years ago
The problem is caused by http://buddypress.trac.wordpress.org/browser/trunk/bp-core/bp-core-catchuri.php?annotate=blame#L214. It's incorrect that 'members' should be forced into query_args['pagename']
. This forces WordPress to populate the Members page, when in fact, BuddyPress doesn't really want the members page to show up as the queried_object - BP is responsible for manually resetting the bits of $wp_query
that it needs.
It's all a bit confusing, but I'm going to go ahead and remove the filter. I'll draw attention to the issue during 1.9's beta period, and hopefully if there are problems, they'll be found. We can always revert.
Confirmed. Putting this in 1.9 for attention.