BuddyPress.org

I had that but it was because I loaded buddypress as a subfolder

“Move contents of the extracted folder into “wp-content/mu-plugins”. All files should be in the root of “mu-plugins” not in a sub folder. For example, “mu-plugins/bp-core.php” NOT “mu-plugins/buddypress/bp-core.php””

Once I did that it was fine

Javi95,

If I understand your trouble correctly, the solution to this is really simple, I know because I had this trouble at first too. If you have uploaded the entire buddypress folder to the mu-plugins folder, take everything out of it and put it directly into the mu-plugins folder. You want the actual plugin folders to be in the mu-plugins folder, not in another folder in that folder. Sorry if that sounds confusing, hope it helps.

I think I’ve found the solution:

open the admin-bar.css in the bp-core/css folder

Lines 68-72

#wp-admin-bar ul li { /* all list items */

padding: 0 !important;

float: left !important;

background: url( ../images/admin-menu-arrow.gif ) 88% 53% no-repeat;

position: relative;

You just need to delete “position: relative;”.

That has solved the problem with FF3 – drop down menu disappearing.

But still having problem with IE7 menu flickering, even after https://trac.buddypress.org/ticket/530 fix

It’s okay to do anything you want with the theme files, just as you would do in WordPress.

You don’t need the loader.php stuff if you don’t want to, however, it does add some extra functionality, such as cross theme CSS and the ability to selectively load styles.

You should also read this:

https://codex.buddypress.org/getting-started/using-the-buddypress-themes/

Just for reference, what size community do you need before you have to start using multiple db’s?

I think that if multi-db was under gpl, i may to be interested to develop on it

Credit for the above code too burtadsit by the way

Been waiting to get the site just right, it is close, but not perfect: http://phoenix.fanster.com

Hi bergsten

thanks for the plugin, essential for any network

I installed the 2.0b2 version on my BP, put the php code you gave above (add_action(‘bp_custom_profile_boxes’, ‘bp_google_maps_profile’, 6) in the index.php from the directory /wp-content/member-themes/buddypress-member/profile, exactly here :

‘<?php if ( function_exists(‘bp_send_message_button’) ) : ?>

<?php bp_send_message_button() ?>

<?php endif; ?>

</div>

<?php add_action(‘bp_custom_profile_boxes’, ‘bp_google_maps_profile’, 6); ?>

<?php bp_custom_profile_sidebar_boxes() ?>

</div>

<div class=”main-column”>’

It’s working but a little buggy : the map shows two time as you can see here :

http://vivre-en-autarcie.com/members/admin/profile/public

something else is bugging.

the button update your position leads to a page that doesn’t exist with slug: update-position

the integration function works fine : I can edit a map where all markers my users are shown ; that’s great

thanks for any help

Hey gang, thanks to the help of you here, I have managed to work through some things and am now proud to show a site that I’m developing:

http://grungepress.com/

Keep in mind that it’s not done, and I haven’t had a chance to customize the forum template, as I’ll plan to match that with the main site.

The “BuddyBar” is by default not shown to visitors that are not logged in. You can change this in the BuddyPress settings, at http://example.org/wp-admin/wpmu-admin.php?page=bp_core_admin_settings

Mine does the same thing… I was thinking it might be because my buddypress is not in the root, it is at /community/ or because my blog is at /blog/ …. changing my blog to /blog/ did require me to get creative because example.com/wp-register came up with a blank page but if I went to example.com/blog/wp-register/ it worked ok….. not sure if this helps or is even related…

I basically started going through what changes were made to your plugin since it last worked, and started replacing code block by block. Once I could debug the XML request, it gave me some eyes in the back of my head so to speak, to watch what I couldn’t otherwise see.

So basically, it sounds like there is something in the xprofile field, and/or something in some users meta info that the XML parser just doesn’t like, so it gets caught up and returns a crappy value? Is that a good guess? You think it’s time to just rip through the user meta and see if anything looks suspicious?

Here’s a question. What if there are users that haven’t yet updated their profiles in BuddyPress? They were converts from a wordpress.org install, and if they haven’t returned since then, BuddyPress doesn’t have a “fullname” for them yet, and they also don’t have xprofile info. Could that break this somehow? Is there a way to watch this user by user and have it spit out an error when it finds a bad value?

Also, just for the record. I’m using BuddyPress RC1, bbPress Alpha6, and WPMU2.7. Is it possible there was a trunk update that you’re using that I’m not that maybe gives you different results than me?

More specifically, if I comment out line 335 in oci_bp_groups_forums.php…

//$user['xprofile_' . $group->name . '_' . $field_obj->name] = array('group' => $group->name, 'name' => $field_obj->name, 'value' => $field_obj->data->value, 'type' => $field_obj->type);

And run the group import, it works without error as well.

If I put a switch on the $field_obj-> name…

switch ($field_obj->name) {

…and only retrieve the custom title and forum signature, the groups import also works (still not for all users though, only groups.) I think it may be tripping over a specific type of field. I’m going to guess the textarea field, but that’s totally a blind guess with no merit or motive what-so-ever.