Skip to:

Opened 15 years ago

Closed 15 years ago

#916 closed defect (bug) (fixed)

defining custom slug for blog changes bp_activity_sitewide table 'component name' field

Reported by: windhamdavid's profile windhamdavid Owned by: johnjamesjacoby's profile johnjamesjacoby
Milestone: 1.1 Priority: major
Severity: Version:
Component: Keywords:


defining custom slug for blog
define ( 'BP_BLOGS_SLUG', 'something-other-than-blog' );
in wp-config.php
changes bp_activity_sitewide table 'component name' field
which leaves the content and primary_link fields empty for new entries to the db.

Change History (4)

#1 @DJPaul
15 years ago

  • Milestone set to 1.0.4

#2 @johnjamesjacoby
15 years ago

  • Owner set to johnjamesjacoby
  • Status changed from new to assigned

Andy has a fix for this in the works. Involves splitting the component internal name away from the slug. Internal name stays the same regardless of the slug, and the slug is the user definable location.

Assigning to myself as I may make the patch this week if Andy doesn't before me.

#3 @apeatling
15 years ago

  • Milestone changed from 1.0.4 to 1.1

Milestone 1.0.4 deleted

#4 @apeatling
15 years ago

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

This has been fixed by the update mentioned by jjj.

Note: See TracTickets for help on using tickets.