Skip to:
Content

BuddyPress.org

Opened 14 years ago

Closed 14 years ago

#2550 closed defect (bug) (duplicate)

Wrong title on pages and blogposts

Reported by: tyckr's profile tyckr Owned by:
Milestone: 1.2.6 Priority: major
Severity: Version:
Component: Core Keywords: title
Cc:

Description

All pages generated by BuddyPress have the right <title>-tag. But browsing through pages and blog posts will not show the right titles, only the default title as "Blogname | Home".

I'm using WordPress 3, BuddyPress 1.2.5.2 and the Unplugged theme (also tested with the BP Default Theme).

Change History (8)

#1 @tyckr
14 years ago

  • Priority changed from normal to major

#2 @r-a-y
14 years ago

  • Milestone changed from 1.2.5 to 1.2.6

#3 @DJPaul
14 years ago

I can only seem to recreate this on a multisite install, running BP-Default on the non-root blog, and with BP_ENABLE_MULTIBLOG = false. BP 1.2 branch, WP 3.0.1.

#4 follow-up: @beckb
14 years ago

I'm not running multisite and have the same problem with all parent pages created in WP. For example, the page About Us has no parent, shows up as Blogname | Home.

History is a child of About Us and shows up as Blogname | History. From navigating around BuddyPress.org, this looks to be the correct behavior (i.e., titles aren't intended to show full breadcrumbs).

fwiw, I'm running the latest WP (3.0.1) and BP (1.2.5.2), a child theme of bp-default, and several plugins (not all of them directly intended for BP).

#5 in reply to: ↑ 4 @beckb
14 years ago

Replying to beckb:

I'm not running multisite and have the same problem with all parent pages created in WP.

Also true of blog posts on my site. The title is Blogname | Home rather than Blogname | Blog | PostTitle. Permalinks are set to /%postname%/. (Sorry, had another problem to sort out before I could test posts in addition to pages.)

Category listings show up with what appears to be the correct title, i.e., Blogname | Blog | Categories | Categoryname. Again, depth (child status) is irrelevant.

#6 @cnorris23
14 years ago

Related with patch: #2548

#7 @pisanojm
14 years ago

Agree with cnorris23 This appears to be a duplicate of 2548... I was having the same issue on WP Single (didn't know I was having it until I was testing patches here). 2548 fix, fixed this for me.

#8 @johnjamesjacoby
14 years ago

  • Resolution set to duplicate
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.