BuddyPress.org

If you want your bpmember and bphome theme header.php and footer.php files to always be in sync, this is what I do. It’s a little tricky, but it works really well at keeping multiple theme files totally in sync.

Copy the code below into a file called hf-sync.php and put it in your wp-content/plugins directory. Then in your WordPress Site Admin, goto your plugins area and activate the plugin called “BuddyPress Synchronized Header/Footer”

<?php

/*

Plugin Name: BuddyPress Synchronized Header/Footer

Plugin URI: http://buddypress.org

Description: Header/Footer Synchonization Functions

Version: 1.0

Author: John James Jacoby

Author URI: http://johnjamesjacoby.com

Tags: BuddyPress, Header, Footer

Site Wide Only: true

*/



// Call this in your header.php file.

// Rename the function to match your theme name.

function theme_name_header() {

?>

<!-- PUT YOUR HEADER HTML CODE IN HERE -->

<?php

}

?>



// Call this in your footer.php file.

// Rename the function to match your theme name.

function theme_name_footer() {

?>

<!-- PUT YOUR FOOTER HTML CODE IN HERE -->

<?php

}

?>

Then, in whatever header.php and footer.php files that you want to use your universal header/footer code, all you’ll need to do is call the functions above.

This lets you make edits to both of your header/footer files for both/any/all themes that use this code, in one central location.

My guess, is that this would/should work very well in keeping bbPress themes in sync also, provided that you insert HTML code to include what bbPress needs also, and make sure not to include that code if bbPress isn’t loaded.

When you delete a user completely from WordPress/BuddyPress, *they should* be totally deleted. WPMU has a process for this, and BuddyPress simply just hooks into it and calls the same action.

If you deleted that user only from the blog area (and not the site admin area) that could cause the situation you’re describing?

Where did you delete the user from?

I know that WordPress 2.8 uses the updated jQuery version, which will tend to break some older jQuery based scripts (it did on my portfolio site) but I’m not so sure about BP or WPMU.

Here are links for these plugins

1. https://wordpress.org/extend/plugins/wordpress-thread-comment/

2. https://wordpress.org/extend/plugins/wp-postviews/

wordpress-thread-comment needs some modification to work only with post author

File attachment is a new subject and probably needs its own topic but I’ll answer here.

You can attach all the files you want inside of your blogs. You can put them inside of pages or posts.

https://codex.wordpress.org/Using_Image_and_File_Attachments

You’ve used it on other WordPress sites? I don’t know… but one thing I’ve always found is that you should never mix and match javascript frameworks. They tend to mess each other up. Just a guess on my part! I see that Slimbox uses Mootools and WordPress uses jQuery. Again… that’s just a wild ass guess.

https://wordpress.org/extend/plugins/blog-topics/

I found this plugin which allows the site admin to set blog types (categories). The site admin and the blog admins are then able to apply their blog to one blog type. There is one included function which lets you display all recent blogposts from blogs which use blog type “x”.

What I need for my “home”-page is a function similar to the bp-member-function. Ajax driven “recent blogposts” with filter buttons like “show all, type1, type2, …”.

The problem is that my programming skills are not good enough. Even if I study the bp-member-functions, I’m not able to do it.

Any suggestions maybe? Or any information if a feature like this will find it’s way into buddy press within the next few weeks?

If Manoj has implemented his own user registration functions, he needs to be sure he’s calling the hooks/actions that WordPress uses else Welcome Pack won’t get triggered.

The Dashboard is here – https://buddypress.org/developers/YOURUSERNAME/dashboard

the link you posted is to the wordpressMU dashboard.

DJPaul-

As I posted above, I’m beginning to wonder if more is going on with some installations as we’re seeing more of this error type. I’m not saying that it is because of your plugin though!

With WordPress installs, this “Cannot modify header” error almost always indicates extra stuff before an opening php or closing php tag. It is all too easy for someone to open up a file and accidentally enter extra “stuff” and not even realize it.

But there are of course other causes of this error. It will be interesting to see what the source of this error turns out to be.

We seem to be seeing more and more of this particular type of issue. It makes me wonder. Hum…

But, let’s start with your error message. I’m going to repeat verbatim what I said in two other threads.

The “Cannot modify header” error almost always indicates that there is some extra stuff (whitespace, extra text) before the opening php or closing php tag. It could be in one or both places. There must not be anything before or after the opening and closing PHP tags–not a single space, not any extra characters, not a single carriage return.

Open up header.php in your custom theme file and look for any whitespace or extra stuff. It should be removed and the file saved.

Report back on what you found and if that helps.

Here’s more information of the “Cannot modify header” error: https://codex.wordpress.org/Answers-Troubleshooting#Headers_already_sent

Not yet, no ETA.

There’s going to be a code merge between WordPress.org and WordPressMU code, and this will probably be the way that BuddyPress will make its way into single installations.

John is correct. If the avatar file fails to upload, you will have additional problems. The uploading could very well be caused by the issue I referenced above. Fix that, and the upload process may function properly and the other errors go away.

Of course, this is not guaranteed. Let’s just look into this possibility first and see what happens.

Here’s more information of the “Cannot modify header” error: https://codex.wordpress.org/Answers-Troubleshooting#Headers_already_sent

Part of this project depends on how WordPress decides to handle permissions (capabilities and roles) with 2.9+.

The goal will be for relationship scopes and roles to be set at default and later defined by the administrator of the site, based on what users are allowed to do/see, etc…

Lots to do!

Deep integration between bbPress and WordPress is the easiest way, along with the bpGroups plugin by Burt Adsit.

That way you can reference the users avatar and any other Extended Profile meta info.

Consider that WordPress is going to be at version 2.8 soon, and BuddyPress has just broken the champagne glass as 1.0 a few weeks ago, and already 1.0.1 is out.

All things come with time.

BuddyPress is an opensource project just like WordPress. This means that anyone can stomp in and contribute what they’d like, and Andy as the lead developer will get the final say-so as to what makes the cut and what does not. The previously mentioned bpPicture Album plugin is a great example of that. It does the job quite well in my opinion, and is also still not 100% finished.

I think it would be a pretty large undertaking to merge the WordPress blog attachment method with the BuddyPress member profile area. Considering that if you’re using WPMU and that person has a blog, would you want to have their uploads in their blog also appear in their profile, or would it be a dedicated area for uploads? There’s really a lot of different types of configurations this could take, any/all of which are viable and possible.

All that needs to happen is for a developer to see the need, and then fill it themselves.