3118294Inactive
I got a base install of wordpress mu on http://www.example.com and I’ve installed BuddyPress. I want the BuddyPress part to run on a sub-blog /community. I’ve set up the blog (ID 2) and install the BuddyPress theme on it. But the members and groups page only works from http://www.example.com/members. I want members and groups, etc, to run from http://www.example.com/community/members (or /groups).
In the /wp-content/plugins/buddypress/bp-core.php I found this option:
/* Define on which blog ID BuddyPress should run */
if ( !defined( ‘BP_ROOT_BLOG’ ) )
define( ‘BP_ROOT_BLOG’, 1 );
If I change to define( ‘BP_ROOT_BLOG’, 2 ); then http://www.example.com/community/groups seems to work, but http://www.example.com/community/members cause a redirect loop error.
Any idea how I can run BuddyPress on a sub-blog, not as the root blog?
I’m using BuddyPress 1.0.1 but had the same problem on 1.0. Using WordPress MU 2.7.1 as base.
Thanks so much for any help that anyone can offer!
Not really buddypress issue per say, but figured the best experts are here to ask.
Here is what is happening on all blogs:
1. I create a post and assign it to ‘in the news’ category
2. click submit/ then preview, then go back to the edit screen
3. somehow the post is not only ‘in the news’ category but other random categories as well.
This happens on every blog on my mu setup without exception.
If I go back to edit article and then deselect the additional categories, it seems to fix the issue.
While I can ‘deal’ with this headache, there is no way I can see my users dealing with this.
I searched the wordpress forums but did not see this problem listed.
Does anyone have a clue why this would happen, and a possible solution?
(I tried disabling all plugins and it had no effect, running wpmu 2.7.1 with bp 1.0.1)
Not exactly sure when this problem started as I have been dealing with it for so long now. At first I thought it was a theme issue, but then today I created new blog with new theme and it continues to happen so I am really stumped.
The setup is maintained by Nicola for me, so I am pretty certain that everything was setup correctly
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.
Well the problem with that is that I have to manually ad the code. I need a plugin that automatically does the trick. I’ve used slimbox before on other wordpress blogs but on buddypress it doesnt seem to want to work.
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.
I have redirected my wordpress-mu installation
from: http://adventuresportnq.info/wordpress-mu
to: http://adventuresportnq.info/
and now my buddypress links still refer to the old url’s. How do I get rid of the /wordpress-mu/ in all of buddypress’ urls.
Thanks Muzza!
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.
Lonchbox-
We do not have sufficient information to provide assistance. Also, this is an eight-month old thread. Please read this thread: https://buddypress.org/forums/topic.php?id=2543
I just havin a problem during the automatic upgrade and have this:
Fatal error: Cannot redeclare bp_activity_install() (previously declared in /home/thbru/public_html/demo/blogs/wp-content/plugins/buddypress/bp-activity.php:27) in /home/thbru/public_html/demo/blogs/wp-content/plugins/buddypress/bp-activity.php on line 101
What can I do ?
Can someone please provide me a step by step guide as to what needs to be accomplished to make the FB-Connect plugin work. I would like instructions from both sides: facebooks panel and wordpress/buddypress panels.
3104956Inactive
Using WordPress MU 2.7.1, BuddyPress 1.0.1 with Facebuddy Theme newly downloaded yesterday.
If I set the Buddypress default home theme and member theme, and try to register as a new user, I get the register page as I should.
If I use the Facebuddy home and member theme, “register” redirects to “wp-login”. Attempting to navigate directly to “http://my.site.com/register” gives me the home page (same as going straight to “http://my.site.com”). If I navigate directly to “http://my.site.com/wp-signup”, I get the WPMU signup page.
I have site admin settings set to allow new registrations but not blogs. I have tried changing it to allow registrations and blogs together and that made no difference. I have copied the “register.php” from the default theme to the facebuddy theme, to no avail. I have compared “functions.php” and found discrepancies (two missing includes in the new theme, which I fixed), no effect. I have compared index.php line for line and found no differences. At this point, I am stuck because I don’t know enough about how the code works to know what to check for differences. It is obvious that there is a discrepancy between the BuddyPress default theme and the new FaceBuddy theme. If someone will give me guidance where to look I am confident I can run this bug down. I just don’t know how the code is structured and fear breaking something doing it by “brute force”.
All guidance appreciated.
-Chris
Well from the http://www.colourlovers.com/about page:
//// Server Technologies We Love & Use
:: Red Hat Linux
:: CentOS
:: Apache HTTP Server
:: MySQL RDBMS
:: PHP: Hypertext Processor
:: memcached
:: Alternative PHP Cache
:: Munin Monitoring Tool
:: WordPress
Notice the last item…
3103132Inactive
Hi
I had the same problem with uploading images in a new registration, i solved them out changing the permissions to 777 in wordpress-mu/wp-content/blogs.dir/1/files/avatars/ and turning SAFEMODE OFF.
Now, a new user can registrate and upload a photo. But… the new problem is that the uploaded photo does´nt show, a broken image is shown, in the directory wordpress-mu/wp-content/blogs.dir/1/files/avatars/2/ are the images but doesn’t show on my buddypress.
When i login and delete my avatar, the default avatar is shown. When i retry to upload my photo the error appears again.
Here is my url http://cororegatas.com.ar/wordpress-mu/members
what I might need to do?
My apologies for my pour english.
I`m looking forward to your reply.
Marcelo Paredes – Argentina
I have just upgrade to wordpress mu Version 2.7.1 and buddy press 1.0.1 and when I try to upload an avatar it goes through the motions but when it is time to post the avatar it just shows a gray box. Do you have any suggestions?
UPDATE: there is only the youtube widget plug and the buddy press plug in stalled.
UPDATE: Tuesday; June 9, 2009: when I went back and click the delete button it showed up my avatar. How does that happen?
Derek
@Burt Adsit, When you finish with the project place in wordpress.org !
21green-
This is truly beyond the scope of the BuddyPress forums. But, since I had some issues when I attemtpted to install WPMU on MAMP several months ago, I feel your pain.
I wrote an article (months ago) for installation of WPMU on MAMP (not MAMP Pro). But, I’m not yet finished with updating my new website, so it is not yet posted.
Here is the crux of the article. I’ve never tried this with XAMPP, so use at your own risk:
- Make sure you have the most recent, stable version of WPMU and that it is copied into MAMP where you want it to be.
- Read the readme.txt file that comes with WPMU
- Do not manually edit either of these two files:
- wp-config-sample.php file
- htaccess.dist file
Unlike single version WordPress, the WPMU installer will take care of creating the proper files using these two as templates. If you need to make changes to either of these files, do so after the installation has succeeded.
- WPMU wants to run on Apache port 80. Since OS X comes with a copy of Apache set to run on port 80, you will have issues if OS X is automatically configured to start its own copy of Apache on boot. If so, you’ll have to change that. Check to make sure that the Web Sharing checkbox is unchecked in System Preferences > Sharing
- Now fire up your browser and go to localhost:80/index.php and follow the prompts. The path will be different if you’ve installed WPMU in a subdirectory. If so, just add the subdirectory to the url.
- In the field for Server Address, you will see the recommendation to use localhost.localdomain instead of localhost. That did not work for me. Instead, I found that I had to use the internal IP address of my computer (a.k.a the local IP address which is always 127.0.0.1 ). I tried the localhost.localdomain address several different times with no success. If you have already tried this, make sure that you delete the wp-config.php file and start all over.
- If you’ve done this properly, you should now be seeing a friendly “Installation Finished!” screen. Follow the instructions. Write down your password.
- Now, manually enter the address for the admin login screen into your browser’s address bar. If you just hit log in, you may have issues. So, if you are using 127.0.0.1 as the Server Address, you would enter in the browser 127.0.0.1/wp-login.php. The path will be different if you’ve installed WPMU in a subdirectory.
Good luck!. Let me know if this works for you.
I’m having a similar problem. On the activation screen I get a javascript error: “v1Cropper is undefined.” I haven’t changed the buddypress theme, but I have a custom wordpress theme installed and renamed its folder to “default” to force new blogs to use the customized theme. I saved the original default theme in a backup folder. Is it possible I need some file(s) from the original default wordpress theme? I’m using wordpress 2.7.1 and buddypress 1.0.