BuddyPress.org

https://buddypress.org/2011/05/buddypress-template-pack-1-1/

https://codex.buddypress.org/theme-development/wordpress-to-buddypress-theme/
https://codex.buddypress.org/theme-development/bp-template-pack-walkthrough-level-easy-2/
https://codex.buddypress.org/theme-development/building-a-buddypress-child-theme/

@foxly Thanks. Yeah, it must be stripping iframe tags from non-Administrators. (And this is a separate install from wordpress.com, so it doesn’t have the googleapps shortcode.) Anyway, I’ve put them in there: https://codex.buddypress.org/releases/1-5-plugin-compatibility/

Not sure what’ll happen when a non-Admin edits the page; they may get stripped again. I’ll try to figure out a way around this.

@boonebgorges We’ve spent the better part of an hour trying to debug the BP codex page, but it won’t render the Google Docs embed, even when we add it in the admin back end.

WordPress.com officially supports Google Docs embeds announcement, support page, and the embed works properly on several different test sites we tried it on. The problem seems exclusive to buddypress.org.

Could you guys up one of us to super admin for a bit so we can check if it’s stripping embeds by normal editors as some sort of spam control measure?

Thanks!

^F^

Sitgmartyr – This issue has been reported and fixed, but unfortunately there will not be a public, new release under the 1.2 series because attention has shifted to 1.5.

However, you can patch and fix this yourself:
https://buddypress.trac.wordpress.org/changeset/4626

Or download the 1.2 dev branch and overwrite your current “buddypress” folder:
https://buddypress.trac.wordpress.org/browser/branches/1.2 (scroll to the bottom and click on the ZIP download)

Remove all your htaccess code that you’ve added as that isn’t related to this issue.

https://codex.wordpress.org/Changing_The_Site_URL
https://codex.wordpress.org/Moving_WordPress

== If I don’t have bp-config.php I just create it inthe buddypress plugin directory, right? ==
The internal Forum installation process will automatically generate the “bb-config.php” at root of your install when you go through the process.

Thanks for posting that tutorial, @foxly. The ‘wp’/’admin_menu’ hook is a very old technique that has nonetheless continued to work. I’ve got that on my list of things to write about on bpdevel.wordpress.com. Maybe I’ll do so later today, and link to your very helpful wiki page.

What versions of WP and BP are you using, @esploded? What errors do you get in your web server’s error logs? I bet this is to do with https://bbpress.trac.wordpress.org/ticket/1486

> Will get that sorted trying to get the spreadsheet to work in the page to save time currently but will get it marked as not fail because of those.

If this is done, I’d argue that the “Excellent” ratings should just be a “pass”. The “excellent” rating, compared to the others, is subjective and is dependant on who tested the plugin (and their knowledge of PHP, WordPress and BuddyPress APIs, etc).

I just got the latest version a few hours ago. For me, the menu only looks okay if I don’t assign a menu to the theme in Appearance > Menus > Theme Locations. If I do set it, then it looks like it does in my image above.

Also, in the backend, I’m seeing this message:
“You’ll need to activate a BuddyPress-compatible theme to take advantage of all of BuddyPress’s features. We’ve bundled a default theme, but you can always install some other compatible themes or update your existing WordPress theme.”

Also, in your profile > Activity tab > Personal (when viewing another member’s profile) / Mentions / Friends / Groups, there is no spacing above the first activity stream item

That’s all I could find! Good job!

@frizzo – sounds like you are looking to implement WPMU (multisite)

Here is a link to help get you started: https://codex.wordpress.org/Create_A_Network

The way I’m doing it, our main buddypress site is the master domain, all users from that site can use their accounts around any of our sub-blogs or domains. There’s even a premium plugin for domain name support so you’re not just limited to a subdirectory.

Hope this helps!

One way is to change all your user’s passwords with some generic-only-you-will-know password.
Then a user is forced to reset their password when s/he attempts to login next time.

Read this post for some pointers (especially the ninja section):
http://digwp.com/2009/10/five-ways-to-change-your-wordpress-password/

I should state that BuddyPress runs on top of WordPress, so this is technically a WordPress issue.

That’ll either have been the BuddyBar, from BuddyPress, or perhaps the admin bar from WordPress 3.1+.

I’m not sure if it’s good to fail a plugin purely because it has PHP warnings revealed with WP_DEBUG. Those warnings, if output to HTML rather than a log, can also cause problems with the rest of the plugin. We’re checking for BP 1.5 compatibility, not whether a plugin meets WordPress’ coding standards. Thoughts?

Install https://wordpress.org/extend/plugins/bp-template-pack/ to make WP theme compatible.
https://codex.buddypress.org/theme-development/wordpress-to-buddypress-theme/
https://codex.buddypress.org/theme-development/bp-template-pack-walkthrough-level-easy-2/

What do you mean that the website “crashed”?

It’s highly, highly unlikely that BuddyPress would have caused you to lose any data. If, after activating BuddyPress, your screen goes white, it usually suggests that you have insufficient memory on your server. In that case, simply navigate to wp-content/plugins with an FTP client, and delete the buddypress folder. WordPress stores content separately from its program files, and your data is still safe.

Here is a very helpful codex page on “blank screens”, which is what I assume you mean by “crashed”: https://codex.buddypress.org/troubleshooting/blank-pages/

Some may or may not fit what you are after here https://wordpress.org/extend/plugins/tags/favorite

Not tried it but using usual WordPress function logic wouldn’t user_id=1,6843 work?

When’s the last time you svn upped your installation? Or are you using one of the BP 1.5 betas? I’ve been told that this issue has been identified and fixed since BP 1.5-beta-2: https://buddypress.trac.wordpress.org/ticket/3469#comment:1

oops, you answered my question before I asked it

Yes, that sounds like a bug. I have opened a Trac ticket, which you can follow for updates: https://buddypress.trac.wordpress.org/ticket/3469

https://codex.wordpress.org/Answers-Troubleshooting#Headers_already_sent