Skip to:

Opened 13 years ago

Closed 13 years ago

#3182 closed defect (bug) (fixed)

default_component set to invalid component slug if activity component disabled

Reported by: djpaul's profile DJPaul Owned by:
Milestone: 1.5 Priority: critical
Severity: Version: 1.5
Component: Extended Profile Keywords: needs-testing

Description (last modified by DJPaul)

When the activity component has been disabled, 404s.

Attachments (1)

3182.patch (1.1 KB) - added by DJPaul 13 years ago.

Download all attachments as: .zip

Change History (5)

13 years ago

#1 @DJPaul
13 years ago

So, this one took ages to track down and I'd like some feedback on whether a) the patch works and b) whether it's fixed in the best way before we put it in.

To recreate the issue, on trunk, deactivate all BuddyPress components. Then go to Without the patch, it should 404, and with the patch, it should load the WordPress Profile fallbacks. Then test again with each of the BuddyPress components enabled (only one at a time); the two I found trouble with were Activity and Extended Profiles, everything else worked fine for me without any patch.

The issue is caused by the current_component in some situations being set to 'xprofile' (bp->activity->id). In branch it was set to 'profile' but in trunk it is 'xprofile'. It's not possible to change the bp->activity->id as it breaks the includes in the new class component.

#2 @DJPaul
13 years ago

  • Keywords needs-testing added

#3 @DJPaul
13 years ago

  • Description modified (diff)
  • Summary changed from profile URL doesn't when only xprofile enabled to default_component set to invalid component slug if activity component disabled

#4 @djpaul
13 years ago

  • Resolution set to fixed
  • Status changed from new to closed

(In [4440]) Fix default_component value when activity component is disabled. Fixes #3182

Note: See TracTickets for help on using tickets.