BeLogical-
Why don’t you paste your base code (bp-xxx.php) and the bp-xxx-cssjs.php code into a pastebin so that several of us can take a look–that is if you don’t mind showing parts of your code. I have not had issues using:
$bp->example->image_base = WP_PLUGIN_URL . '/bp-xxx/images';
to load images.
This might be the long version, but
1. When I needed to upgrade, I backed up my database and copied all the buddypress files into another file called “bosox” (just make up a name). I think you may need to copy your avatars and other stuff into your new install from the old one, so don’t delete the old Buddypress files for awhile!
2. Then I added the Buddypress files to their new locations and activated it. If you have heavy customization to CSS, you’ll need to re-do the changes (reference your old CSS files).
3. You’ll also need to:
– select and activate themes
– move all your plugins to the new plugin location (it changes in 1.0 from your version)
– copy avatar files into the new location (I had to do this, but not everyone did)
Those are the basics. All the best to you!
@kitwit
I usually update the themes/bphome (for the basic site) and wp-content/bp-themes/bpmember (which controls the member and directory pages). I update them separately because I sometimes want certain customizations with the member profiles and not for the main part of the site.
All the best to you!
Philip-
We are working on a proper privacy component for BuddyPress that will allow for a given member to decide how much of their personal data they want to expose to the world. This not only includes their profile data, but also a member’s data contained in the other BuddyPress components.
As far as group-specific privacy control, that is also an area we are discussing.
@Kitwit
You did follow this:
https://codex.buddypress.org/getting-started/installing-buddypres
and do have the member them in the correct place?
where it says:
6. The plugins are now activated and running, but you will need to move the themes to the correct locations. Move /wp-content/plugins/buddypress/bp-themes/ to /wp-content/bp-themes/
7. You can use any WordPress theme as your root blog theme, but BuddyPress comes bundled with an extra “home†theme that you can optionally use. To install it, move /wp-content/bp-themes/bphome/ to /wp-content/themes/bphome/.
you will then need to edit the member theme to reflect similar changes in the base theme.
Hope that helps.
Gordon
@Kitwit,
You\’ll also need to edit the member-theme css files- these control the look of Members / groups pages etc.
If you\’ve installed it properly then they should be in /wp-content/bp-themes/bpmember/css
as per here: http://mypartyonparty.biz
Jeff, could you get this working in v1.2 and then I can modify my component accordingly?
http://www.w3schools.com/ is a great resource as is http://www.lynda.com and of course the documentation available on this site https://codex.buddypress.org/
Well, the skeleton uses WP_PLUGIN_URL because custom components should not run in the /buddypress/ directory. Since BP_PLUGIN_URL is defined in bp-core.php (line 9):
define( 'BP_PLUGIN_URL', WP_PLUGIN_URL . '/buddypress' );
if you use BP_PLUGIN_URL, it will be pathed incorrectly.
So, the question is this: Where do you have your custom component installed? It should be in /plugins/ and not /plugins/buddypress/
Nada. Has anyone gotten this to successfully work with the skeleton component on their server?
@Maythil – If you’re on a Mac… download a copy of CSS Edit:
http://macrabbit.com/cssedit/
This editor makes it ridiculously simple to “reverse engineer” CSS code. In the “x-ray” mode you can click any element on the screen and it tells you what the container is (along with all of it’s parent elements). You can also bring up an “inspector” that will show you all CSS declarations that are affecting that element. And you can even modify the CSS and see the changes as you type the code. I’m not sure if there is anything similar for PC… but there must be.
I actually took a quick look myself using CSS Edit and the difference between profile pages and other pages seems to be that profile pages have two left sidebars with a fixed width of 138px (#optionsbar and #userbar) while the other pages have a single right sidebar (#sidebar) without any width defined (i.e. 100%). Meanwhile, #main is used on all pages and has a min-width of 680px. So unless you change some CSS code… the profile pages will always be at least 956px wide.
How did you change the CSS? One thing to bear in mind is that the default theme is fluid. It has min and max widths set. It sounds like you want a fixed width of 800px all the time (no bigger, no smaller… regardless of window size). So… did you remove the min/max on the body and change it to 800? Did you remove the min-width on #main and change it to… let’s say… 560px (allowing 120px each for those two sidebars in the profile)?
Anyway… as mentioned above… this is not a bug and has nothing to do with BuddyPress development. It’s just CSS 101. But I feel you pain. Hopefully the above is some help.
p.s. Did you look at Elgg during your evaluation? It has some features I need that BP currently lacks… but BP is clearly much superior otherwise.
K,
Remember that I’m a newbie…
But I would not touch the Buddypress plugin with “Plugin Commander”. If you wish to activate Buddypress across your site do so in the WPMU plugin section and activate site wide.
R
@Jeff, thanks for the tip. Maybe we can start a forum section listing all the plugins which have been tested by members to work without issues with BuddyPress.
@Rschilt, thanks for the info about plugin commander. I am trying it out right now. Quick question about it: After I first install plugin commander, it shows me Buddypress as the only plugin and it shows autoactivate as no. Should this be active for all members or deactivated?
I would assume activated (so that buddypress can work for everyone) but I am not sure it refers to member blogs or the community in general.
It should be working. (place your bp-custom.php outside buddypress as it will be deleted when you upgrade buddypress next time by wordpress update system)
Hello, DJPaul,
My note was not an ode to IE6 (in fact, I have created several websites using simple HTML and my biggest problem was always IE6). I mentioned IE6 precisely because it’s hated and unsupported by most and yet somehow is able to solve the width problem inherent in BP.
I stressed on the problem again because (1) it’s after using RC2 and (2) I have more precise details this time. The width discrepencey I mentioned is as found in buddypress.org itself and it’s applicable to Firefox, which is my default browser for your information (I like Firebox, if I ignore their imposition of ask.com)
I am not an expert; just an observant user. If I am capable of creating a patch myself for resolving the problem, what am I doing here! And, at any rate, creating a patch is impossible unless I know where the problem lies precisely.
If nobody is going to answer, it’s ok with me.
Socialpreneur: Ok thanks.
Would I have to edit the header.php for both the home and bpmember theme? So I would add the same code to both files?
<div id="header">
<h1 id="logo"><a href="<?php echo get_option('home') ?>" title="<?php _e( 'Home', 'buddypress' ) ?>"><?php bp_site_name() ?></a></h1>
<ul id="nav">
<li<?php if ( bp_is_page( 'home' ) ) {?> class="selected"<?php } ?>><a href="<?php echo get_option('home') ?>" title="<?php _e( 'Home', 'buddypress' ) ?>"><?php _e( 'Home', 'buddypress' ) ?></a></li>
<li<?php if ( bp_is_page( BP_HOME_BLOG_SLUG ) ) {?> class="selected"<?php } ?>><a href="<?php bp_home_blog_url() ?>" title="<?php _e( 'Blog', 'buddypress' ) ?>"><?php _e( 'Blog', 'buddypress' ) ?></a></li>
<li<?php if ( bp_is_page( BP_MEMBERS_SLUG ) ) {?> class="selected"<?php } ?>><a href="<?php echo get_option('home') ?>/<?php echo BP_MEMBERS_SLUG ?>" title="<?php _e( 'Members', 'buddypress' ) ?>"><?php _e( 'Members', 'buddypress' ) ?></a></li>
<?php if ( function_exists( 'groups_install' ) ) { ?>
<li<?php if ( bp_is_page( BP_GROUPS_SLUG ) ) {?> class="selected"<?php } ?>><a href="<?php echo get_option('home') ?>/<?php echo BP_GROUPS_SLUG ?>" title="<?php _e( 'Groups', 'buddypress' ) ?>"><?php _e( 'Groups', 'buddypress' ) ?></a></li>
<?php } ?>
<?php if ( function_exists( 'bp_blogs_install' ) ) { ?>
<li<?php if ( bp_is_page( BP_BLOGS_SLUG ) ) {?> class="selected"<?php } ?>><a href="<?php echo get_option('home') ?>/<?php echo BP_BLOGS_SLUG ?>" title="<?php _e( 'Blogs', 'buddypress' ) ?>"><?php _e( 'Blogs', 'buddypress' ) ?></a></li>
<?php } ?>
<?php do_action( 'bp_nav_items' ); ?>
</ul>
</div>
If I wanted to add another menu-link would I have to add something like this to both header.php files? Saying the new page was called ‘pagename’:
<?php if ( function_exists( 'bp_pagename_install' ) ) { ?>
<li<?php if ( bp_is_page( BP_PAGENAME_SLUG ) ) {?> class="selected"<?php } ?>><a href="<?php echo get_option('home') ?>/<?php echo BP_PAGENAME_SLUG ?>" title="<?php _e( 'Pagename', 'buddypress' ) ?>"><?php _e( 'Pagename', 'buddypress' ) ?></a></li>
<?php } ?>
Or is this wrong? Just wanna make sure I do it right. 
I’m a newbe to WP, MU and BuddyPress so if you want feedback from the novice point of view, count me in.
I can only learn through experiment.
Unless things have changed and I’m way behind on the new version, you need bbPress in order to use BuddyPress to its full potential. bbPress is what makes the groups work.
I had lots of login and logout issues. And to fix them, I had to “mess around with cookies and stuff like that.”
1 thing was that I copied all of the auth keys from the wp-config and put them into bb-config. Another modification was that I had to define the cookiehash. When logging into bbPress, I didn’t have that hash so there were 2 separate cookies being created. 2 separate cookies means that logging out of 1 side doesn’t kick you out of the other.
I, too, am thinking about using BuddyPress along with Moodle in a higher education environment. I’ve been using the latter for almost two years with pretty good success, but WPMU is impressive and calls to me as an administrator and user.
I’m always curious to share experiences and recommendations.
belogical
$bp->example->image_base = BP_PLUGIN_URL . ‘/bp-example/images’;
this didn’t work either. I have this in the bp-example.php:
$bp->example->image_base = WP_PLUGIN_URL . '/bp-example/images';
is that what you are talking about?
