BuddyPress.org

If the buddypress community that you are a part of is public, you could just create a link to your profile, either by adding it to the Links Menu in your WP dashboard and enabling the Blogroll widget on the sidebar, or by creating a custom menu with a custom URL, and — if your theme supports custom menus — throw it up top in your theme, or use the Custom Menu widget and put it in the sidebar.

The URL to your profile will be something like domain.com/members/”your-user-name/

Visit your Profile and copy and past the URL that appears.

Your third option is a plugin like this: https://wordpress.org/extend/plugins/bp-profile-widget-for-blogs/ I’m not sure if this still works, but it does what you want.

You actually do not want your member pages and their status updates to be cached by google because of privacy. There is no privacy settings in BuddyPress and the last thing your users want is a site owner forcing their updates to search bots.

@t.sjogren
does this work?

I doubt any pages other than perhaps the forums* should get to 100 queries, let alone 200. If you can provide any evidence of which queries are popping up on the (in your opinion) worse page, I’ll take a look

@ad33lx This issue would be better addressed by the developers of the premium plugin and theme developers in their own fora..

> the URL I provided is more than adequate proof that this problem occurred

It’s evidence that a problem has occurred, but not that data has been deleted from your database. There is nothing in the BP 1.5 database upgrade routine that should change display names. Again, I’m guessing that the problem lies in the logic that determines what counts as the “display name”; we don’t just pull something out of a certain field in the database, but instead use a number of settings to determine which content should be shown in the ‘display name’ areas.

> obviously something went amiss during the database upgrade for both Juan and myself

My guess (and it’s only a guess, as I’m not able to reproduce) is that it’s arising not as a result of the database upgrade, but as a result of a particular combination of local parameters that we haven’t nailed down yet. For instance, are either of you using BP_ENABLE_USERNAME_COMPATIBILITY_MODE?

> At no point did I receive an error or anything indication the 1.5 upgrade wizard did not complete successfully.

Can you say more about this? In what sense did it not complete?

Hi @phyz, this is fixed now. check out the new version: https://github.com/Themekraft/Custom-Community

Obviously I don’t have ‘evidence’ since I reverted to 1.2.10, BUT the URL I provided is more than adequate proof that this problem occurred and continues to affect my installation. Extended profiles are enabled. Its not theme or plugin related, because the problem persists in default with everything but BP disabled. At the link, a username has replaced the full name field in the profile header and many other parts of the site. Only about 10% of profiles have still have this issue, but with my upgrade to 1.5 it affected all profiles.

I don’t expect a solution via forum reply, but obviously something went amiss during the database upgrade for both Juan and myself. Just thought I’d let the devs know, though I realize recreating this problem would be difficult until I know more.

You need to set which blog ID BuddyPress will run on in your wp-config.php file by adding this in
`define ( ‘BP_ROOT_BLOG’, $blog_id );`

You need to set which blog ID BuddyPress will run on in your wp-config.php file by adding this in
`define ( ‘BP_ROOT_BLOG’, $blog_id );`

Re child theme:
1. if you’re going to build your style on top of bp-default styles, then you should add @import rule to get bp-default stylesheet in your child theme’s style.css and BP will respect that and won’t enqueue parent theme’s stylesheet in wp_head because you already imported it.

2. On the other hand, if you prefer to build child theme from scratch then you should add the 2nd code in this post in your child theme’s functions.php file – create one if you don’t have one yet and don’t forget the opening “ to wrap around the code.

Re child theme:
1. if you’re going to build your style on top of bp-default styles, then you should add @import rule to get bp-default stylesheet in your child theme’s style.css and BP will respect that and won’t enqueue parent theme’s stylesheet in wp_head because you already imported it.

2. On the other hand, if you prefer to build child theme from scratch then you should add the 2nd code in this post in your child theme’s functions.php file – create one if you don’t have one yet and don’t forget the opening “ to wrap around the code.

There’s not really a pretty way to do this. If you look in bp-blogs.php you can change the string it passes to the activity. Changing the string doesn’t affect existing activity, but it can alter new ones as they’re entered into the system.

I’m using an older version of Buddypress though, so I can’t guarantee things will be the same for you. The string you mentioned (‘%s wrote a new blog post: %s’) shows up on line 411 for me.

Hope this helps.

There’s not really a pretty way to do this. If you look in bp-blogs.php you can change the string it passes to the activity. Changing the string doesn’t affect existing activity, but it can alter new ones as they’re entered into the system.

I’m using an older version of Buddypress though, so I can’t guarantee things will be the same for you. The string you mentioned (‘%s wrote a new blog post: %s’) shows up on line 411 for me.

Hope this helps.

inewmom – You need to install the BP Template Pack plugin to make your WP theme compatible with BuddyPress. Follow the intructions in Appearance > BP Compatibility

inewmom – You need to install the BP Template Pack plugin to make your WP theme compatible with BuddyPress. Follow the intructions in Appearance > BP Compatibility

@mybridal if you still need assistance, start a new topic.

@mybridal if you still need assistance, start a new topic.

https://codex.buddypress.org/getting-started/before-installing/#system-server
https://codex.buddypress.org/troubleshooting/

https://codex.buddypress.org/getting-started/before-installing/#system-server
https://codex.buddypress.org/troubleshooting/