5887735Inactive
@andy We have put in place most of the steps in that article and have seen some results, but thats kind of the point I was making. To really put those measures in place you need a dedicated server.
@MrMaz Maybe “BP php is extremely inefficient” was a little wide-ranging, but it was a phrase that came up over and over again in discussions with several hosting companies. For example, a senior tech at Blue Host/Host Monster told me every BP install they host (and they host over 1 million domains) is throttled (if users find their site slow this may be why).
In order for BP to be the next killer CMS I believe it should be able to be run on a shared server. To get the kind of plugin support and wide variety of quality themes BP needs to get those users that are either unwilling or unable to pay for a dedicated server.
PS
My current skill set is limited to testing and reporting back. That’s all I’m doing here, reporting what we experienced and what we where told. I’ll try to get better details.
I should also note I love BP. It’s a huge step forward and we will continue to use it and grow with it. I am only trying to offer feedback to help that growth. Thanks to everyone for their hard work that got us this far.
One more note. We have around 4000 members and are adding about 50 per day, so we would need a dedicated server regardless, but having a tighter BP would of course still be a big help.
@el_terko: thanks, yes the bbpress theme for bp-default is coming…
Was planning on building a facebook theme on the theme they have now, but now working on the new (to come) design of facebook. 
Anyway, reminds me off the old buddypress theme.
Bravissimo theme Arturo ! Pensate lasciare il theme dal suo forum in bbpress ?
Nice theme Arturo ! Have you thought releasing your bbpress forum theme ?
in italy an icecream advertising say “two is meglio che one” (two is better than one) 
Cool! I think this is the second Facebook-like BP theme out there.
The first was Fishbook by Mike Kuhlmann – http://www.michaelkuhlmann.com/buddypass/
You could probably use this snippet in your theme’s functions.php file:
https://buddypress.org/forums/topic/how-to-make-a-private-community/page/2#post-44729
If you attempt to access the site and you’re not logged in, you will be redirected to the register page.
5887735Inactive
Are there any changes to the themes from 0.4 beta to 0.4.1?
If you’re using a child theme of the default BP theme, use this tidbit to remove the login widget from the sidebar:
https://buddypress.org/forums/topic/how-to-remove-login-sidebar-from-bp-12-default-theme#post-46264
To add the login form to the BuddyBar, you’ll need to create a function that outputs the login form and then you’ll need to hook it to the BuddyBar.
Here’s some sample code that you can add to your theme’s functions.php:
function my_login_bar() {
// basically a copy of the login form from the BP sidebar
?>
<form name="login-form" id="sidebar-login-form" class="standard-form" action="<?php echo site_url( 'wp-login.php', 'login' ) ?>" method="post">
<label><?php _e( 'Username', 'buddypress' ) ?><br />
<input type="text" name="log" id="sidebar-user-login" class="input" value="<?php echo attribute_escape(stripslashes($user_login)); ?>" /></label>
<label><?php _e( 'Password', 'buddypress' ) ?><br />
<input type="password" name="pwd" id="sidebar-user-pass" class="input" value="" /></label>
<p class="forgetmenot"><label><input name="rememberme" type="checkbox" id="sidebar-rememberme" value="forever" /> <?php _e( 'Remember Me', 'buddypress' ) ?></label></p>
<input type="submit" name="wp-submit" id="sidebar-wp-submit" value="<?php _e('Log In'); ?>" tabindex="100" />
<input type="hidden" name="testcookie" value="1" />
</form>
<?php
}
// the magic that hooks your my_login_bar() function to the BuddyBar
add_action( 'bp_adminbar_menus', 'my_login_bar', 2);
Keep in mind, you’ll need to style the form to make it look nice in the admin bar, but that should get you started.
More info in modifying the BuddyBar can be found here:
https://codex.buddypress.org/how-to-guides/modifying-the-buddypress-admin-bar/
6015794Inactive
some gallery plugin dont work with buddypress templates. So i wanted some help with that.
Make a copy of the bp_adminbar_notifications_menu() function (located in /buddypress/bp-core/bp-core-adminbar.php) and add a check to see if there are any notifications to the main list item, if there are, output a CSS class for the list item.
You’ll need to override the default notifications menu in the BuddyBar.
Read this guide to find out how to modify the BuddyBar:
https://codex.buddypress.org/how-to-guides/modifying-the-buddypress-admin-bar/
Use the bbPress admin backend to create your forum categories.
/yourdomain.com/your-bbpress-install/bb-admin/
Please do not bump several-related posts in order to get a response.
I get the same error on multiple sites (using the same host though).
It’s fine when I have a localhost install, and it’s also fine when I’m not using buddypress.
I go to the registration page, fill out my details and then click on Complete Sign-up. It then takes me to the same page again, almost as it if just refreshes.
My registration URL is http://ferryglide.com/wordpress/register
6002845Inactive
I know where my forum is. I don’t understand is this integration. Basically the integration kill my forum.
The members don’t appear in the members list, the topics, messages, categories don’t show up in buddypress…
So I can’t understand what kind of integration is….
ah – well in 0.4.1, on my test platform, it never appears.
Thanks to both of you! I will try WPMU.
I am curious — if anyone has the time or inclination to enlighten me — what differences I might encounter between Buddypress on MU vs. normal WP? Or if there is any documentation somewhere….? Thanks.
@M
I use a waiting/loader icon in several other places. There is supposed to be one there, and I’m not sure what happened to it. The e_loader.toggle() is actually the ajax-loading icon call.
@gian-ava
Okay, well clearly you’re smart and you’ve put some effort into debugging your system.
I will add a config option to the next BP Album+ beta that lets users set a custom path for activity stream items. But… it will not fix your existing activity stream items, and if you ever change your directory structure after using the option, you’ll lose all your activity stream items again.
Remember, this is a limitation in BuddyPress, not BP Album+
Still, your best options are:
1) To put your WP installation at the HTML root, which will give you the best compatibility with plugins.
2) If you’re running multiple installs in a single HTML root, use virtual hosts.
3) And if you don’t want to learn how to use virtual hosts, you can probably use a redirect in your .htaccess file as you described (that’s what cPANEL does). Note that there could be SEO implications with using a redirect.
Thanks!
^F^
Hold the phone!
I found an obsolete conditional that is causing the plugin to fail on certain browsers. Probably the source of your issue.
Need to update.
Another suggestion: Add a “processing” icon that is temporarily displayed when fetching remote page data so people know that something is happening after they click the button to “fetch page details”.
An easy way to add that feature is to add a div to the default theme form (bp-links-default/single/forms/details.php) right under the nonce field, like so:
<?php wp_nonce_field( 'bp_links_save_link-auto-embed', '_wpnonce-link-auto-embed' ) ?>
<div id="waiting"> </div>
Then add some CSS for the div in the bp-links-default/_inc/css/forms.css file:
#waiting {
background: transparent url('../images/loading.gif') no-repeat scroll 0 0;
height: 33px;
width: 33px;
margin: 0 auto;
text-align:center;
display:none;
}
Next, drop a loading.gif image into the _inc/images folder. (here’s one as an example: http://www.minimelive.com/images/nav/processing5.gif — not sure whose site that is though)
And finally, modify the forms.js file to show and hide the div at the appropriate time. Somewhere around line 190 [ right before jQuery.post(ajaxurl… ] add this:
jQuery('#waiting').show();
And somewhere around line 240 [ after e_loader.toggle() ] hide the div:
jQuery('#waiting').hide();
That ought to do it
@duffcub
Read this:
https://buddypress.org/forums/topic/faq-how-to-code-snippets-and-solutions#post-37123
@techguy
Use bp_core_redirect();
From the commented code:
– Performs a status safe wp_redirect() that is compatible with bp_catch_uri();
eg. redirect to logged in user’s profile:
global $bp;
bp_core_redirect( $bp->loggedin_user->domain );
