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.
Hey everybody !
I can’t login as the Site admin (the page keeps loading itself forever), but the other users do have access to their backoffice and see the buddypress Admin bar (meaning Buddypress is active).
Has anyone ever experienced this issue ?
I’m using WPMU 2.7.1 and Buddypress 1.02
Thanks
Julien (Paris, France)
@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.
error on the last step of sign up on my site, vitamovie.com
Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /home/vitamov/public_html/wp-content/plugins/buddypress/bp-xprofile/bp-xprofile-signup.php on line 261
idk why i keep getting it, can anyone try the sign up and see, the error
i have not made any modifications to the core files
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?
Okay, just updated to 2.8.1. Was about to update to 1.0.3 BP, but I’m getting this error:
“Fatal error: Call to undefined function bp_core_get_user_displayname() in /home/content/d/o/o/doorqtech/html/wp-content/plugins/buddypress/bp-core/bp-core-templatetags.php on line 238”
Can’t upgrade BP either from the admin panel, as that error throws things off. Suggestions?
@Flynn – Glad you got the single sign-on working! The visual integration really just came from an excessive amount of CSS elbow grease. I’m a bit embarrassed to say that our solution for sitewide navigation isn’t as elegant as yours – the WP nav is hardcoded into the MediaWiki template. We were in a rush to get the thing together (and frustrated with the less-than-ideal theming structure of MW!) and it never occurred to us. I’ll definitely look into using includes to make this work.
As for the activity plugin – it’s hard to know from just the blank screen just what’s wrong. If you’re getting the problem even without saving pages, then it’s unlikely that it’s a problem with the code (since it is only hooked when a wiki page save is complete). A couple possibilities:
- You might want to take a look to make sure that there is a close ?> in the MW extension. I had to leave it out of the MW documentation page because of the way the MW knowledgebase renders PHP (I guess?). If MW isn’t detecting an end to the extension, it could cause a panic.
- Where did you place the require_once line in your LocalSettings.php? My system was finicky; I only got the plugin to activate correctly when I made it the second to last require_once in the config file (just before the WP redirection extension code). So you might try playing around with the location of this file.
- Make sure as well that the line in LocalSettings.php is pointing to the right location – [MW-directory]/extensions/buddypress-activity/buddypress-activity.php, or whatever alternative location you’ve chosen on your system.
Hope that helps at least a little!
@Hempsworth – It’s funny that you mention the class=timesince – I must have spent three hours trying to get that to work one way or the other. The problem is that the timesince span tags are added in the individual BP components (groups, blogs, wire, etc). To get wiki functions to work the same way I would have to abandon the quick-n-dirty activity hack that I employed and actually build entire wiki BP classes. Maybe one day! In the meantime, you might try this even quicker-n-dirtier hack that I mention in the Usage section of the extension page. The preg_replace code I give there goes in BuddyPress core, around line 226 and 230 (ish) of [wp-install-directory]/wp-content/plugins/buddypress/bp-activity/bp-activity-templatetags.php. This hack will only apply to new wiki activity – not the stuff that you’ve already posted – so make sure to make a new wiki edit to test.
Do you have nay plugins other than BuddyPress installed and active?
Here is what we want to have:
We have wpmu-buddypress on x.com.
Can you make the SAME website work on any subdomain of x.com? (*.x.com)
– Install a WPMU+BP
– make an x.com
– make the same website functional and visible on any sub-domain *.x.com
– leave 2nd and further level sub-domains intact. (**.*.x.com)
I’d greatly appreciate any input..
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.
