BuddyPress.org

Email Problem Fixed:
I seem to have fixed the e-mail verifications not sending. My host is hostmonster which I believe it is a bluemount (blue something anyway). I installed mail form and network activated it. This fall the whole problem. You can find this plug in at the following link.
https://wordpress.org/extend/plugins/mail-from/

Latest, I believe (WP 3.0.4, BP 1.2.7), installed from fresh download yesterday.

To diagnose the problem, I edited the code recommended in http://buddydev.com/buddypress/remove-buddypress-admin-bar-from-all-blog-except-the-main-buddypress-site/ by using a literal, i.e. replacing

`if($current_site->blog_id!=BP_ROOT_BLOG)`

with

`if($current_site->blog_id==n)`

With n = 1 (the main site, where I don’t want BuddyPress admin bar), the admin bar is disabled from *both* this site and the BuddyPress site (blog 2); with n = 2 (the BuddyPress blog), the admin bar is enabled for both!

This has confirmed that, in my installation, $current_site->blog_id is stuck at 1 no matter whether I’m on the main site or the BuddyPress subdirectory.

Again, I suspect my BuddyPress secondary blog installation is not working correctly, which may explain the above, but ideas quite welcome!

Okay, now I do think my secondary blog installation is not working, as when I implemented the above via bp-custom.php, the admin bar was removed from *both* my main blog (where I don’t want it) and secondary blog (where I do want it).

I’m looking at the instructions for BP secondary blog installation, and the grammar of step 1 is a bit perplexing:

“In order to run Buddypress on a secondary blog, you should create a second blog and modify BuddyPress’ internal settings to set your new blog as the BP root blog. Next [what do they mean by “Next” here? I see what follows as the same instruction], define the ‘root’ blog you would like BuddyPress to reside at by adding the code snippet below to wp-config.php [this part is simple].”

The code I added to wp-config.php following instructions for WP network (multisite) and BP secondary blog is:

`define(‘WP_DEBUG’, false);
define(‘WP_ALLOW_MULTISITE’, true);
define( ‘MULTISITE’, true );
define( ‘SUBDOMAIN_INSTALL’, false );
$base = ‘[mysite]/’;
define( ‘DOMAIN_CURRENT_SITE’, ‘[myhost]’ );
define( ‘PATH_CURRENT_SITE’, ‘[mypath]’ );
define( ‘SITE_ID_CURRENT_SITE’, 1 );
define( ‘BLOG_ID_CURRENT_SITE’, 1 );

define ( ‘BP_ROOT_BLOG’, 2 );`

Where info in [] above has been replaced by literals in my case. The secondary blog is definitely #2; is there something else I’ve missed that (a) results in BP acting like a network plugin (vs. one restricted to the secondary blog) and (b) removes *all* admin bars from both blogs?

Thanks, all.

Thank you! Now I have the name right . I guess it was confusing to me that BuddyPress acts as a *network* activate/deactivate plugin, with settings that span all blogs on the network, in spite of that whole secondary blog installation I did following the instructions at https://codex.buddypress.org/getting-started/install-buddypress-on-a-secondary-blog/.

Did I somehow not perform that secondary blog installation correctly, or is this just how BuddyPress works?

Sadly it’s not something I can decide to share, it’s a work and I don’t really feel like asking this thing.
Anyhow the problem I believe was that if I accessed the variables from index everything was fine, friends were found, etc. The problem is that by the means of a javascript slider I use to import pages that then executed the code… maybe this was puzzling some of the very basic variables of wordpress and returned bad results.

What can I suggest to you as developers it to try to implement a custom template (even a simple page that uses the wordpress variables) and on top of that implement some javascript that loads another php page on top of the index (no page reloading) that uses again the wordpress variables… this I think would arise the error again. I think this is a major bug and should be documented / resolved, but it’s up to you .
Thanks again for the support. I really appreciated that.

I’ve discovered that if I access the page outside the scope of buddypress and wordpress (that is, accessing to the direct link without passing by my website) the thing returns a correct result for the friends (if I hardcode the input of course).
What could this mean? I require_once in my index wp-config.php and also in my friend_page (which is loaded on top of the index, in a slider that comes down). Is there a problem with this approach?

Update….I was reading the code on the wp-login.php page and noticed that the code is set that if cookies are disabled to not login even with a valid user and password. I went into IE and set my machine to allow third party cookies…and Voila! I was able to login. Does anyone know of a workaround for this? I know I can enable cookies in the security settings in IE however, I cannot control everyone elses browser. I would like to modify the code if possible so that it works on everyones IE browser. The code is below….

// If cookies are disabled we can’t log in even with a valid user+pass
if ( isset($_POST) && empty($_COOKIE[TEST_COOKIE]) )
$errors->add(‘test_cookie’, __(“ERROR: Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress.”));