BuddyPress.org

please could you delete the url from my post please

Actually, plugins aren’t better, as they take up memory (I’m now on a VPS, so memory usage has become a concern) and they create a lot of doorways for hackage (not the good kind). I like, and would rather, hard code where ever I can, and I do, but I just don’t have the time or the bandwidth to do what I want to do on my own with BuddyPress, hence I’m stuck with plugins.

Before using Multisite, I hard coded as much as possible – all the header/footer stuff, links that I knew were stable. If I found a plugin that worked by adding one line of code, I just found that one line of code and added it by hand instead of using the plugin.

Currently I’m already using 30 plugins in a WordPress multisite and I’m still not getting all of the features that I need.

Already using BP Template Pack plugin. Already created my pages, which are fine, the problem is hacking the look and feel of BuddyPress elements within those template pack pages. Things that should be hardcoded, like the navbar, subnav, elements that should be automagically installed and configured, like the ones I mentioned above, are not.

Because I’m not using the BuddyPress theme, I can only guess that those elements are hardcoded into the theme instead?

I’d much rather be spending my time trying to hack a way for my BuddyPress members and my WordPress members to be integrated – or trying to make my already existing NextGen Galleries work as an “Album” within BuddyPress … but instead, I’m trying to figure out how to unscramble the stupid subnav bar.

Thanks for the code snippet links … I’m sure those would/should have shown up on my google searches if they had contained information that I was looking for. But when I get the time, I’ll peruse them and see if they contain the hacks I need. The stuff I need is really basic though and I don’t understand why it’s just not on the BuddyPress site, unless I am really missing something, which I could be …

Thank you for trying to help … !

Alright, drilling down a bit further, in bp-groups/bp-grouptemplatetags.php, around line 279, there’s our bp_get_group_avatar() method.

`
function bp_get_group_avatar( $args = ” ) {
global $bp, $groups_template;

$defaults = array(
‘type’ => ‘full’,
‘width’ => false,
‘height’ => false,
‘class’ => ‘avatar’,
‘id’ => false,
‘alt’ => __( ‘Group avatar’, ‘buddypress’ )
);

$r = wp_parse_args( $args, $defaults );

extract( $r, EXTR_SKIP );
var_dump(‘buddypress group_avatar_call’, bp_core_fetch_avatar( array( ‘item_id’ => $groups_template->group->id, ‘object’ => ‘group’, ‘type’ => $type, ‘avatar_dir’ => ‘group-avatars’, ‘alt’ => $alt, ‘css_id’ => $id, ‘class’ => $class, ‘width’ => $width, ‘height’ => $height )) );
/* Fetch the avatar from the folder, if not provide backwards compat. */
if ( !$avatar = bp_core_fetch_avatar( array( ‘item_id’ => $groups_template->group->id, ‘object’ => ‘group’, ‘type’ => $type, ‘avatar_dir’ => ‘group-avatars’, ‘alt’ => $alt, ‘css_id’ => $id, ‘class’ => $class, ‘width’ => $width, ‘height’ => $height ) ) )
$avatar = ‘group->avatar_thumb ) . ‘” class=”avatar” alt=”‘ . esc_attr( $groups_template->group->name ) . ‘” />’;

return apply_filters( ‘bp_get_group_avatar’, $avatar );
}
`

So I’ve var dumped the parameters that are used for bp_core_fetch_avatar() when it’s called from the default group landing page, then var_export($args, true) and copied that output directly to my own code and surprisingly, I get the same result as before, a blank img tag. So, this leads me to believe that this method is not meant to be used in the way I am using it.

As I find a better solution, I will follow up in case this is useful to someone else.

I find the solution, via admin panel of main site, I just add the user already registred in the network to be member in the main site by entering his email addresse via: Members -> Add new member then I choose add existing memeber.
It’s manual solution but it’s ok.
Hope this helps who have the same situation.

Thanks, in the permalink it are frozen urls, so I did a lot of other things, .htacess code and so on. As this is a website on the same account of another website, the provider gave more space and then I started from scratch again, brand new website (not a big problem as the site was from yesterday)

After installing buddypress: the same notification…error. Grrrt, then I only changed in permalinks the choice from -default- to -custom- and, amazing, that solved the problem.

So thank you, it is solved.

Thanks @mercime for the advice, but it still won’t work! ARGH.
Setup:
Single WP, MAMP (mac server), Not on a domain yet, but is on the root of MAMP/htdocs/wordpress
I did all of the steps above, but still no use. I hate you “There are no posts for this topic.”!

Also, what do you mean by I didn’t “install/active BP in a subfolder/subdomain”? My buddypress site just has a tab under “community” which leads to the groups, forums, etc.

I been trying to figure it out for week or two now so im just taking small break hope to find the solution soon. IF not imma have to try and find someone to do it who’s specialty is wordpress, multisite, and buddypress.

yup your the first who has even wrote anything back to me I asked the question in Powweb Support, WordPress Support, and here. I’ve taking a break on figuring it out right now.

Good question though…. If I just start working on the different blogs correct. I can later add Buddypress correct?? if so imma work on these some and then try the above again. I know if doesnt work I always get it back to normal by deleting buddypress plugin.

AS SOON AS I ACTIVATE BUDDYPRESS IT SHOWS THIS SMH.

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, cgiadmin@yourhostingaccount.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.