BuddyPress.org

Point 1 – No one has tackled this yet.

Point 3 – http://manojkumar.org/bppicture-album-plugin-for-buddypress/

As DJPaul has said, this is a 3rd party plugin, which isn’t an official BuddyPress component, but does a good job. An official BuddyPress album plugin is in the works.

John:

I have been having the same problem since moving my bp install from id1 to id30.

I tried all the ‘suggestions’ on the forums and patched the files, but bp still seems to save all files like avatars, photo album plugin pics etc in id1 instead of id30…

Looking at the ticket, it looks like it’s assigned to 1.0.4… is this the case?

If so I am guessing that it would be best for me to wait for 1.0.4 to come out instead of trying to hack it together to fix it?

It seems really strange to me that buddypress only works on the primary blog. What I don’t understand is why this would be the case. Buddypress is so far away from what I would call ‘production’ ready status, that it makes no sense to me to run it on my primary mu blog. Isn’t buddypress in it’s current state better to keep in the background, away from others until it’s more stable?

not ranting here, luv buddypress, I just can’t use it as primary but do want it running ‘in the background’ so I can keep adding features and testing etc…

btw

(gave up on trying to update to 2.8 series.. never did stop spitting out errors, so prob just going to wait for 1.0.4 anyhow.. thanks for your time answering emails on it)

This is actually more tricky that it sounds, because BuddyPress by default stores most of its information in the blog ID = 1, and it will ignore most other constant settings. If you are installing BuddyPress for the first time, and change any of the BP_ROOT_BLOG or BLOGID_CURRENT_SITE or SITE_ID_CURRENT_SITE variables, BuddyPress still saves most of its information in blod ID = 1.

https://trac.buddypress.org/ticket/823 references this issue, and I’ve included a patch for the instances where this occurs.

lynnallan, I’m afraid there isn’t a core solution for what you want to do yet, but the patch in the trac ticket *should* better prepare BuddyPress for this type of installation.

My only other suggestion, would be to think of it as WHERE the data is in the database doesn’t REALLY matter, unless you’re trying to split server load up across multiple database servers. That being said, you can install your corporate theme on your root blog, and then install the bphome theme on another blog, and then use the WordPress page template ability to recreate the look and feel of a BuddyPress on a blog other than the root. This is kind-of how http://leadpress.com/ has their site setup, if you need an example.

Rename the buddypress directory to something else. That will force it to deactivate and you can trouble shoot your installation from there.

Taken care of with patch for potential fix.

https://trac.buddypress.org/ticket/875

You’ve got it, Decisionc!

That, or until this is fixed in the source.

Submit a ticket (login with the same username and password as on buddypress.org) for this to hopefully see its inclusion in the next release of BP.

Okay, let’s start with the basics. Please answer these questions.

You’ve already provided the version of WPMU and BP that you’re running, so you can skip those questions.

@Julient

It sounds like a different issue. I assume that you are not getting the WSOD?

If that is the case–that you are not receiving the WSOD–then you should create a new thread as this one is resolved.

I don’t know if it has something to do with the issue, but members who register and don’t create a blog are automatically assigned as subscribers on the root blog. This means that there are hundreds of users assigned to this blog. May this be a problem with buddypress ?

This is normal WPMU behavior. It has nothing to do with BuddyPress.

Hi Jeff,

Looks like I’m facing the same problem : I can’t login as the Site admin, but the other users have access to their backoffice and see the buddypress Admin bar (meaning Buddypress is active).

I tried to switch to the default BP theme for the home page, but the issue remains.

I don’t know if it has something to do with the issue, but members who register and don’t create a blog are automatically assigned as subscribers on the root blog. This means that there are hundreds of users assigned to this blog. May this be a problem with buddypress ?

Do you see where the problem may come from ?

Thanks in advance for your help

Julien

The NextGen Gallery plugin is a vary powerful and popular tool for WP bloggers. I suggest contacting the developers and asking them if / when they plan to support BuddyPress. Also, perhaps they will have some insight into this issue.

Whether this plugin is causing your particular issue is yet to be determined.

There are many functions in bp-core.php and many template tags in bp-core-templatetags.php that will retrieve various user data. Take a look in those two files.

You should not write any custom DB classes unless you are creating a custom plugin. Also, you should never modify core BP files.

If you are simply looking to list certain members, you can try my Featured Members Widget available in the WordPress plugin repository. You may have issues if you are running WPMU 2.8.1 as I have not yet updated my widget to use the new WP Widget API.

I do not know if the NextGen Gallery plugin modifies the wp_sitemeta table. I suggest that you disable the plugin and see if the issue goes away.

If you are running a newer version of WPMU than is currently supported by NextGen Gallery, you could have issues.

Also, I do know that there are some issues running BP with the NextGen Gallery plugin–with avatar cropping. It’s possible that is could be causing other issues as well. Contact the developers of that plugin and ask for their help and whether or not they plan to support BuddyPress.

Which version of BuddyPress are you running?

https://buddypress.org/forums/topic/php-warning-array_mergebp-xprofile-signupphp-on-line-257#post-18234

Anahita looks really interesting but the fact that it runs on Joomla makes it a non-starter for me and my clients… no matter how perfect the code is. I’m a big a stickler for doing things the “right way”… I’m a perfectionist… but the bottom line will always be usability and in that arena… WordPress is way out ahead. So at the end of the day… I don’t care TOO much about the MVC issue.

That said… I agree with your argument above. Doing things the “right way” doesn’t necessarily mean that something is more difficult, or costly, or what have you. I have a degree in architecture and one thing I always say is that when it comes to building… good design is more about thoughtfulness than budget. When designers blame the budget, client, or other constraints… it’s often a cop out.

Hello

Point 4 is a standard WPMU option and can be found in the Site Options panel of the admin interface.

Photo albums are something that will become a part of BuddyPress eventually (i.e. don’t hold your breath). There is an interim plugin you can use which provides a photo gallery to BuddyPress. I haven’t used it myself but you can find it on https://buddypress.org/extend/plugins/.

The big problem I can see with point 2 is that you are inviting spammers and vandalism in to your site.

I have fixed this bug – see this ticket.

@hempsworth – I expanded on the previous tutorials here:

http://www.dougdaulton.com/2009/06/26/complete-bbpress-integration-for-buddypress/

This was done with SVN checkouts just before the most current stable builds, so there may be conflicts, but it steps you through a things that were unclear in previous walkthroughs.

Let me know if it helps.

Doug

PS: Upon reread, I just realized that the Easy Button tut is newer and probably more accurate than mine. Will need to do an update.

Have you deactivated Buddypress before trying to upgrade Buddypress?

Do you have nay plugins other than BuddyPress installed and active?

However, it shouldn’t be too hard to create a “special page” in buddypress/wordpress that outputs some data (XML, serialized PHP, or something) about the logged in users that can be fetched with some kind of Joomla extension at regular intervals.

BuddyPress is based on WordPress, which as you probably know can be used as a CMS too. Therefore, it is not likely that any effort is made in tying together Joomla and BuddyPress.

Hi @andy

you said

Also – something to consider. If WordPress was completely object-oriented, fully MVC, and the most beautifully designed code imaginable – 90% of developers would not be able to understand it.

would you please tell me when you say 90% of developers who exactly are you referring to ? because I know there are projects like Ruby on Rails that have had a good turned out between developers even though they implement lots of design patterns like MVC, Active Record and so on.

Also this does not stop at only open source projects, iPhone development framework (cocoa) follows MVC ( and other design patterns) and now there are kids as young as 10 years old that are developing for this platform.

Also I understand this debate is about MVC vs non-MVC design pattern but I would like to point out that a framework is not just MVC. It’s a collection of many design patterns as significant as MVC that helps the developers to build something in shorter amount of time.

in Anahita, MVC constitutes the overall structure of the application, but in a closer look, we are using other design patterns that makes the code smaller and more flexible. Without them, I doubt having an MVC architecture would have made that much of a difference.

Thank you,

Changing these settings will also not go back and change any existing avatars, so it’s best to set this one time and forget about it (until you update later.)

I recommend copy and pasting those define’s into a bp-custom.php file so that way BuddyPress upgrades won’t reset those values for you.