Skip to:

Opened 5 years ago

Closed 13 months ago

#4787 closed defect (bug) (wontfix)

Defining BP_XPROFILE_SLUG throws page not found

Reported by: rogercoathup Owned by:
Milestone: Priority: normal
Severity: normal Version: 1.7
Component: Core Keywords:


Trying to change the default profile tab fails.

e.g. adding:

define( 'BP_XPROFILE_SLUG', 'messages' ); in bp-custom.php

causes a Page Not Found error when trying to access the user profile.

Tested using 1.7, bp-default theme, various slugs.

Change History (5)

#1 @DJPaul
5 years ago

  • Milestone changed from Awaiting Review to 1.7

#2 @DJPaul
5 years ago

  • Milestone changed from 1.7 to Future Release

This works for me as long as you don't set those constants to the name of a Page. Punting, as seems an edge case, and should be tidied up with the switch to rewrite rules.

#3 @rogercoathup
5 years ago

have updated to latest beta release, and still seeing this problem.

Throws page not found if I try to set the default profile tab to any of the other standard BuddyPress components, e.g. messages, friends or groups.

If I try to set to a custom component we've added - define( 'BP_XPROFILE_SLUG', 'dashboard' );

It throws the following error:

Warning: require_once(/home/nnn/public_html/wp-content/plugins/nnn-dashboard/includes/templates/members/single/home.php) [function.require-once]: failed to open stream: No such file or directory in /home/nnn/public_html/wp-includes/template.php on line 407

Fatal error: require_once() [function.require]: Failed opening required '/home/nnn/public_html/wp-content/plugins/nnn-dashboard/includes/templates/members/single/home.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/nnn/public_html/wp-includes/template.php on line 407

Where it has appended /members/single/home.php to the template directory of the custom component

#4 @tw2113
14 months ago

I think this one has potential to be closed as wontfix as BP core denotes the fact that the BP_XPROFILE_SLUG has been deprecated and is only still defined for backcompat purposes.

Any thoughts on that idea @boonebgorges @jjj?

Last edited 14 months ago by tw2113 (previous) (diff)

#5 @boonebgorges
13 months ago

  • Milestone Future Release deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Yes, I don't see a way of fixing this without tearing everything apart, which would incur lots of costs for an edge case. Let's close.

Note: See TracTickets for help on using tickets.