BuddyPress.org

Update again: the full answer is now here – https://wordpress.org/extend/plugins/bp-template-pack/

Since filters require some knowledge with WordPress, I’d recommend the CSS route.

Put this in your stylesheet:

.activity-list .activity-content img.thumbnail {display:none;}

Don’t know about image posting in activity stream but FYI you can use this for video https://wordpress.org/extend/plugins/oembed-for-buddypress/

Is there any way to enable the activations mails in a Single WP like in MU?

It seems to me BuddyPress supports activation only in WordPress MU.

As far as I know wpmu_activate_user is a plugin action hook. Also mentioned here. It works for my function. Not sure what you need exactly.

From the main wordpress admin you need to go to “settings” then check the box “anyone can register”

Just Found this, Could be a springboard

https://wordpress.org/extend/plugins/google-document-embedder/

It’s on the WordPress Settings page, the option called “Membership”.

@andystaple when Pods becomes wordpress friendly it will be an awesome choice to use as your Beer data-type manager.

Does MyReviewPlugin actually make use of BP XProfile data and hook into the activity stream? eg. [Andy Staple] reviewed [Pete’s Wicked Ale] in [Microbews Group] for example?

While it is very true that the backend is confusing our users regarding complexity, I still think that, atm, posting from the front-end is not developed far enough yet (as far as I know, please correct me if I’m wrong). It is fine for micro-blogging, but I don’t think there are option to include image/video/media uploading, tagging, and categories.

Therefore we are still painfully educating our users so at least the can harness the full potential of WP rather than to use it as a feature rich paper weight that can only do text. If anyone knows of a way to post to the blog from the front end that’s more full featured than just text, it will be implemented immediately (as a manner of speaking)!

We could do this with Drupal, but I have not seen it yet, or search hard enough, in WordPress.

So yes, I to would absolutely feel liberated if I did not have to send our users to a backend…it is not what is expected for most users using common social sites. Definitely high on the priority list!

Alright I have added right after

define( ‘COOKIEPATH’, ‘/’ );

and right before

/* That’s all, stop editing! Happy blogging. */

What is this suppose to do anyways? I’m not sure I understand how this stops spam.

So now my wp-config is like this,

define( ‘COOKIEPATH’, ‘/’ );

define( ‘BP_REGISTER_SLUG’, ‘randomcrazyslugger’ );

/* That’s all, stop editing! Happy blogging. */

/** WordPress absolute path to the WordPress directory. */

I added the line. as suggested.

/* That’s all, stop editing! Happy blogging. */

define( ‘BP_REGISTER_SLUG’, ‘yourregisterslug’ );

/** WordPress absolute path to the WordPress directory. */

That’s what it looks like.

Andrea_r sorry I’m in three different threads right now I feel like your chasing me around haha!

Wow, that’s a really impressive setup you got going at http://kodingen.com. Thank you for posting this ~ I wouldn’t know where to start with hiphop yet, but I registered and noticed that the activation email is missing a backslash. I had read this statement from @rasmus and figured it’s performance gains and high scaleability would also depend on a series of other configurations like memcached and sql optimization. But something like this could prove to be as Rasmus puts it, escape from ‘framework soup’. Although wordpress.com seems to be running top notch on top of Nginx, but I’m sure they got all kinds of hardware and configuration tweaks going on.. // all the same thanks for for the experimenting and good luck with it.

It’s not gone just radically altered?

It’s part of the activity stream now?

I think if you want it exactly as before you need to use this plugin provided to maintain backwards compatibility:

https://codex.buddypress.org/getting-started/upgrading-from-10x/

https://wordpress.org/extend/plugins/buddypress-backwards-compatibility/

But someone more versed in these matters may provide a better answer.

Maintaining this backwards compatibility does not seem straightforward though, and a better step by step guide would be useful, and I’m not sure that in reality 1.1.x and 1.2 are such different beasts that 1.2 ought to be considered a separate branch at least it doesn’t really feel as though 1.2 is an upgrade from 1.1 less a point release than a milestone almost a 2.x?