BuddyPress.org

There’s a WordPress app that allows iPhone uploads for blogs. Just the straight WordPress app in the store. But you can’t do it via Buddy. You just have to connect your blog to the app and it works out. You have to enable atom publishing.

1. Yes, we changed this to make BuddyPress compatible with more servers. To change this WordPress email address, try a plugin like https://wordpress.org/extend/plugins/send-from/ or ask on the WordPress.org forums for other recommendations.

2. What theme (and version of the theme) are you using? What version was this working on? i.e. what version did you upgrade from.

3. 1.6 uses the WordPress core toolbar, rather than BuddyPress’ old toolbar. The WordPress logo is added to the bar by WordPress itself.

https://buddypress.trac.wordpress.org/ticket/4429

https://wordpress.org/extend/plugins/buddypress-extended-settings/

Yes, there does seem to be a few issues.
While buddypress is claiming that there isn’t a need to network activate, making it work on a subsite doesn’t seem to be as easy as one might expect. I haven’t figured out how to get past the permissions thing on subsite, but network activating in the base site also doesn’t seem to connect to the subsites. They don’t seem to know buddypress is activated. Kind of frustrating, but when someone shares the secrets with the rest of us, it will be quite a nice install, I presume..

Also, with themes that are compatible with v1.56, are they still compatible with 1.6? Or do the new files need to be moved to the theme directory to make everything work right? I ask these questions because of the problem I seem to be having with not being able to find buddypress profile from the subsites.. I am being directed to the WordPress profile, not buddypress, from the subsites.

There is (was) a plugin bp-posts-on-profile at https://wordpress.org/extend/plugins/bp-posts-on-profile/ though it is very out of date and hasn’t been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress and BuddyPress.

I have tried it out with bp 1.6 and wp 3.4.1 and with a host of other bp plugins in a multisite and also in a multi-network local test site.

As far as Multi-Site/Multi-Network it was unsatisfactory as it only drew in blog posts from the main blog.

It did not draw in posts from (say) a group blog.

However for anyone who authored a post on the Main Blog it dragged in that post and showed it on their profile under the tab Posts

Those more qualified might look at the code and see if it would take much to have it brought fully up to date and multi-site compatible.

However as all relevant details including of posts are included in the members activity tab it probably is not as vital as other plugin development ?

On that note is there any kind of group funding facility for plugin development. So that those who want but can’t could collectively fund those who can ? or would something like that ever work ?

I have no idea how to attribute success (if any) to various methods employed.

In addition to the numerous plugins and captchas some sites have also added lines to the .htaccess file

Some have added (in addition to the various plugins).

The plugin Cookies-for-comments and the lines as suggested at https://wordpress.org/extend/plugins/cookies-for-comments/

`RewriteCond %{HTTP_COOKIE} !^.*XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.*$`
`RewriteRule ^register – [F,L]`

and also

`RewriteCond %{REQUEST_METHOD} POST
RewriteCond %{REQUEST_URI} .register*
RewriteCond %{HTTP_REFERER} !.*yoursite.com.* [OR]
RewriteCond %{HTTP_USER_AGENT} ^$
RewriteRule (.*) http://lmgtfy.com/?q=spammer [R=301,L]`

So the .htaccess file begins like this

`# BEGIN ANTISPAMBLOG REGISTRATION

RewriteEngine On
RewriteCond %{HTTP_COOKIE} !^.*xxxxxxxxxxxxxxxxxxxxxxxx.*$
RewriteRule ^register – [F,L]

RewriteCond %{REQUEST_METHOD} POST
RewriteCond %{REQUEST_URI} .register*
RewriteCond %{HTTP_REFERER} !.*yoursite.com.* [OR]
RewriteCond %{HTTP_USER_AGENT} ^$
RewriteRule (.*) http://lmgtfy.com/?q=spammer [R=301,L]

# END ANTISPAMBLOG REGISTRATION`

Frankly I have no idea how and whether any of this works. The best that can be said is that spam has been reduced considerably. Fingers crossed.

Yes, it’s standard WordPress – did you Google?

https://codex.wordpress.org/Function_Reference/get_currentuserinfo

If you want their BP paths (profile URL) etc. then: https://codex.buddypress.org/developer-docs/the-bp-global/

@lunchgirl @modemlooper GRA4 has been removed from the WP Plugin Extend. It was “phoning home” without user knowing it among others #7 https://wordpress.org/extend/plugins/about/guidelines/

@lunchgirl if you’ve already installed/activated the plugin, I can only recommend that you delete it from your installation.

@mebo For Step 3, you need to revise 16 template files listed here https://codex.buddypress.org/theme-development/wordpress-to-buddypress-theme/#tplfiles

Two solutions — simple link in profile header vs. profile tab

For the first: just add a link to the author archive (standard WordPress) for the displayed user in the member-header file.

For the second – Have a look at bp-skeleton component.

Create a really stripped down version which just contains the code to set up your screen (profile tab), and in there do a simple wp_query() loop with the author ID set to the displayed user ID.

This will tell you about hook and action programming in WordPress: https://codex.wordpress.org/Plugin_API

The do_action() calls are there for you to add your own hook functions, and in some cases will also invoke hook functions that BuddyPress / Themes / other plugins have added.

You can add your own hook function that is called when the do_action ‘bp_before_registration_confirmed’ is invoked. You use add_action to add your actions.

Are you trying to add a custom post type to the activity stream when it is posted? Look at the record activity function http://bpdevel.wordpress.com/2011/08/12/custom-post-types-comments-and-the-activity-stream-in-bp-1-5

There are a lot more features with the new admin bar merge and I think I’m right in saying at some point the fall back of going to the BuddyBar will be removed. However, in the meantime @r-a-y posted this snippet a few days ago that should help:

Add the following code snippet in your /wp-content/plugins/bp-custom.php:

`add_filter( ‘bp_use_wp_admin_bar’, ‘__return_true’ );`

That “out of memory” message indicates the problem is with a lack of memory, not BuddyPress specifically. Your server just doesn’t have enough memory to load more code.

To address this, ask your webhost for help, or look at https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP