Opened 3 years ago

Last modified 2 months ago

#1426 new defect (bug)

BP_ENABLE_ROOT_PROFILES conflicts with multisite subdirectory slugs

Reported by: xevo Owned by:
Priority: major Milestone: Future Release
Component: Core Version:
Severity: normal Keywords:
Cc:

Description

When you make a blog post/page with for example "register" as the permalink, it'll overwrite your buddypress's /register page.

Same thing when using BP_ENABLE_ROOT_PROFILES, if you use a blog name that is already used as a username account, when you go to the user account you get the blog with that name instead.

So the basic buddypress permalinks need to be unoverwriteable by page or blog posts and when using BP_ENABLE_ROOT_PROFILES, the blog name needs to be checked whether it already is being used by a username or the permalink needs to be changed (example: /admin/blog).

Change History (4)

The BP_ENABLE_ROOT_PROFILES thing would only affect subdirectory installs of WPMU.

  • Component set to Core
  • Milestone set to 1.3

There's no way to do slug collision detection at the moment. Probably should run everything through unique_slug at some point.

Moving to 1.3 for review.

  • Milestone changed from 1.3 to Future Release

Moving to future release, since this is unlikely to make it into 1.3. This starts off as a WordPress issue with permalink and slug collisions, so until WP handles this better, we're at a stand-still.

  • Keywords permalink removed
  • Severity set to normal
  • Summary changed from Permalinks get overwritten by others, on multiple places. to BP_ENABLE_ROOT_PROFILES conflicts with multisite subdirectory slugs

When you make a blog post/page with for example "register" as the permalink, it'll overwrite your buddypress's /register page.

Resolved in BP 1.5+ as we now use WP pages for this.

Same thing when using BP_ENABLE_ROOT_PROFILES, if you use a blog name that is already used as a username account, when you go to the user account you get the blog with that name instead.

I'm guessing this is still valid. Changing title of ticket to reflect this.

Note: See TracTickets for help on using tickets.