BuddyPress.org

I am having this exact same problem on a brand new WP/BP site.

Specs

1. Which version of WPMU are you running?
I am using regular WP 3.0
2. Did you install WPMU as a directory or subdomain install?
Root directory
3. If a directory install, is it in root or in a subdirectory?
Root
4. Did you upgraded from a previous version of WPMU? If so, from which version?
Was a previous version install via Fantastico on cPanel, upgraded to 3.0 before BuddyPress was installed
5. Was WPMU functioning properly before installing/upgrading BuddyPress?
Not sure
6. Which version of BuddyPress (BP) are you running?
Version 1.2.5.2
7. Did you upgraded from a previous version of BP? If so, from which version?
No
8. Do you have any plugins other than BuddyPress installed and activated?
Yes:
Welcome Pack Version 2.1
Twitter Goodies Version 3.9.0
Tweetstream Version 1.4
oEmbed for BuddyPress Version 0.52
Invite Anyone Version 0.6.4
Import from Ning Version 1.1
Facestream Version 1.1
Contact Form 7 Version 2.2.1
BuddyPress Usernames Only Version 0.58
BuddyPress Profile Privacy Version 0.2
BuddyPress Private Messages for Followers Only Version 1.0
BuddyPress Like Version 0.0.7
BuddyPress Group Tags Version 1.2.2
BuddyPress Group Email Subscription Version 2.5
BuddyPress Forum Topic Mover Version 1.0.0
BuddyPress Follow Version 1.0
BuddyPress Album+ Version 0.1.7
BP Profile Search Version 1.0
BP Group Management Version 0.4
BP-NotificationWidget Version 1.4
9. Are you using the standard BuddyPress themes or customized themes?
Standard BP Theme BuddyPress Default 1.2.5.2
10. Have you modified the core files in any way?
No
11. Do you have any custom functions in bp-custom.php?
I do not think so.
12. If running bbPress, which version? Or did your BuddyPress install come with a copy of bbPress built-in?
I ran the bbPress installer that came with BuddyPress
13. Please provide a list of any errors in your server’s log files.
[Thu Jul 08 01:43:12 2010] [error] [client 99.232.211.136] PHP Warning: Cannot modify header information – headers already sent by (output started at /home/wwwnatf/public_html/site/wp-admin/includes/misc.php:133) in /home/wwwnatf/public_html/site/wp-includes/pluggable.php on line 890, referer: http://natfriends.com/site/wp-admin/options-general.php
[Thu Jul 08 01:43:12 2010] [error] [client 99.232.211.136] PHP Warning: is_writable() [function.is-writable]: open_basedir restriction in effect. File(/) is not within the allowed path(s): (/home/wwwnatf:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/wwwnatf/public_html/site/wp-admin/includes/misc.php on line 133, referer: http://natfriends.com/site/wp-admin/options-general.php
[Wed Jul 07 23:53:55 2010] [error] [client 99.232.211.136] PHP Warning: Invalid argument supplied for foreach() in /home/wwwnatf/public_html/site/wp-content/plugins/wordpress-shout-box-chat/chat.php on line 38, referer: http://natfriends.com/site/
[Wed Jul 07 23:53:55 2010] [error] [client 99.232.211.136] PHP Warning: file_put_contents(history/20100707) [function.file-put-contents]: failed to open stream: Permission denied in /home/wwwnatf/public_html/site/wp-content/plugins/wordpress-shout-box-chat/chat.php on line 23, referer: http://natfriends.com/site/
[Wed Jul 07 23:53:52 2010] [error] [client 99.232.211.136] PHP Warning: Invalid argument supplied for foreach() in /home/wwwnatf/public_html/site/wp-content/plugins/wordpress-shout-box-chat/chat.php on line 38, referer: http://natfriends.com/site/
[Wed Jul 07 23:53:52 2010] [error] [client 99.232.211.136] PHP Warning: file_put_contents(history/20100707) [function.file-put-contents]: failed to open stream: Permission denied in /home/wwwnatf/public_html/site/wp-content/plugins/wordpress-shout-box-chat/chat.php on line 23, referer: http://natfriends.com/site/
[Wed Jul 07 23:47:55 2010] [error] [client 99.232.211.136] PHP Warning: chmod() [function.chmod]: Operation not permitted in /home/wwwnatf/public_html/site/wp-content/plugins/phpfreechat/src/pfctools.php on line 180, referer: http://natfriends.com/site/
[Wed Jul 07 23:47:55 2010] [error] [client 99.232.211.136] PHP Warning: copy(/home/wwwnatf/public_html/site/wp-content/plugins/phpfreechat/src/../data/public/themes/zilveer/smileys/emoticon_unhappy.png) [function.copy]: failed to open stream: Permission denied in /home/wwwnatf/public_html/site/wp-content/plugins/phpfreechat/src/pfctools.php on line 179, referer: http://natfriends.com/site/
[Wed Jul 07 23:47:55 2010] [error] [client 99.232.211.136] PHP Warning: chmod() [function.chmod]: Operation not permitted in /home/wwwnatf/public_html/site/wp-content/plugins/phpfreechat/src/pfctools.php on line 180, referer: http://natfriends.com/site/
[Wed Jul 07 23:47:55 2010] [error] [client 99.232.211.136] PHP Warning: copy(/home/wwwnatf/public_html/site/wp-content/plugins/phpfreechat/src/../data/public/themes/zilveer/smileys/eusa_whistle.gif) [function.copy]: failed to open stream: Permission denied in /home/wwwnatf/public_html/site/wp-content/plugins/phpfreechat/src/pfctools.php on line 179, referer: http://natfriends.com/site/
I moved files in site to root…..
Hosting company:
Total Choice Hosting

something like: (just taken from bp-core.php line 397)

is_null( $bp->displayed_user->id ) && $bp->current_component == BP_MEMBERS_SLUG && $bp->is_directory

correct trac ticket (one listed above was for activity time_since)
https://trac.buddypress.org/ticket/2504

confirmed – i have the same issue now (7 hours ago)

messages_new_message uses ‘date_sent’ => time() instead of gmdate since the templatetag uses bp_core_time_since

actually a few other oddities where notices use time() as well. (but that actually calls bp_format_time in the templatetag)

@Pisanojm @paulhastings0 I’m getting the same thing. Wp 3.0 BP 1.2.5

It is – in the admin backend, you can choose whether or not each component is enabled.

@pisanojm, Yes, since upgrading to WP 3.0 the 5 hour time-lag issue reappeared. Since that time we’ve also upgraded BP to 1.2.5 and we still have the issue.

@pisanojm I have just updated to BP 1.2.5.2 and although I don’t get a 4 or 5 hours issue I do get a general, ‘sent sometime ago’ time on PM’s that I have only just sent. The time stamp is correct on my inbox page but when i open the message it just states, ‘sent sometime ago’.

Anyone else getting this?

Depending on whether you’ve turned on the components at Dashboard > BuddyPress > Component Setup, BP provides extended user profiles, an interactive activity stream, private messaging, user-creatable groups (with integrated activity streams, forums, and other functionality available via plugins), blog tracking, friend connections, and member/group directories. The toolbar at the top of the screen is one of the methods built into the UI for accessing these features. If you’re using a BP-compatible theme like the bundled bp-default, then you should also see tabs for Members, Groups, Forums etc near the top of your screen.

testbp.org is one place to see BP being used (for test purposes, obviously, but you can get a sense of the organization).

is_feed() is what you’re looking for. However, I would use travel-junkie’s code as it’s cleaner:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-to-make-a-private-community/?topic_page=2&num=15#post-44616

Modify this line:
if( bp_is_register_page() || bp_is_activation_page() )

with:
if( bp_is_register_page() || bp_is_activation_page() || is_feed() )

Seems like I could have added some kind of IF ~whatever the FEED function~ RETURN to the Registered Users Only 2 plugin and achieved the same thing… but I don’t know what the “whatever the FEED function” is to add… @r-a-y

@r-a-y I used your code suggestion and some that I found in Restrict User 2 With Viper’s original Restrict User Plugin
Found here http://www.viper007bond.com/wordpress-plugins/registered-users-only/
because I wanted the site to be restricted to registered users only… still allow access to the login/activiate page and ALSO allow access to the feeds…

I ended up with this.
// Depending on conditions, run an authentication check
function MaybeRedirect() {
// If the user is logged in, then abort
if ( current_user_can(‘read’) ) return;

$this->exclusions = array(
‘wp-login.php’,
‘wp-signup.php’,
‘wp-register.php’,
‘wp-activate.php’,
‘wp-cron.php’, // Just incase
‘wp-trackback.php’,
‘wp-app.php’,
‘xmlrpc.php’,
);


It appears to be working… Do you have any thoughts on the above? Thanks

All forum postings — except those from private groups, are displayed in the site wide forum stream. So, your posting was visible for awhile. It just gets pushed down if there are no replies. I suggest keeping your discussions within that group’s forum.

just look at the core files bp-groups.php and the function groups_setup_nav()

from there you’ll see how bp sets the current access for most subnav items
look for this line -> // If this is a private or hidden group, does the user have access?

which is referenced on line 206/7 for the Forums subnav. What you can do is remove the subnav ( bp_core_remove_subnav_item ) then re-add with the param user_has_access calling some function to determine the access level for your given requirements. (hook your remove/re-add on the action groups_setup_nav )

“You can only update the groups you’re a member of.”
That’s the idea, one way to prevent spammers from messing with your group.

Do you mean you want to allow anyone to post status updates even in private (by invitation only) groups or only in public groups?

Code in functions.php only runs on the blog in question.

If you have BP activated sitewide, put the code in /wp-content/bp-custom.php as that will run throughout your install.

@Travel-Junkie: Your code below works great for WordPress 3 and Buddypress but not for multisite sub blogs? I need to stop access to sub blogs as well if users are not logged in. If i type in the url of my sub blogs then they show up. Is there anyway to stop this?

tks
james

function sh_walled_garden()
{
global $bp;

if( bp_is_register_page() || bp_is_activation_page() )
return;

if( ! is_user_logged_in() )
bp_core_redirect( $bp->root_domain .’/’. BP_REGISTER_SLUG );
}
add_action( ‘get_header’, ‘sh_walled_garden’ );

@crashutah – I actually prefer travel-junkie’s method; it’s cleaner:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-to-make-a-private-community/?topic_page=2&num=15#post-44616

@peterverkooijen; Good points about the focus of a social network being on the member, while a forum is focussed more around the information. I think @alanchrishughes has a point too though, about non-techies being put off by having to register.many people are still terrified that if they enter their name and email address then you’ll have access to their bank account – seriously!

I’ve built a number of sites in Drupal, which is very powerful indeed, and doesn’t suffer so much from update issues. It gives such fine control of everything that it’s amazing, and for those who haven’t tried it, you can basically build your own custom CMS with it. It takes so long to do though. We tried Elgg, which is kinda cool out of the box, and does a lot of social network things really well. However, its interface is naff (in my opinion) and theming is not easy. Worse still, adding extra pages to build a custom site means lots of coding, instead of WP’s simple click-to-add. We’re going to need that for custom background (paying) advert pages, and hopefully a lot of them as time goes on. Also, Elgg has almost no member control, roles, etc., and wile the Elgg team feel that’s not important, we strongly disagree. People do not behave nicely just because they signed up to a social network!

Personally, I see nothing wrong with a social network which allows unregistered users to comment with CAPTCHA, along with well defined and easy to use groups for members to join, and good role management and strong privacy for those who require it. That way, just as in the real world, you can have private places and high streets, with members themselves controlling who does what. For me, at least, that’s all a social network need be.

@peterverkooijen said; “There is also zero privacy/security in Buddypress”. Care to expand upon that Peter? Our site isn’t ‘open for business’ yet, but when it is our members will expect some privacy, ie., profile stuff set to private and private group posts actually being private. Are you saying it can’t/won’t be properly private?