BuddyPress.org

@jcassano, this plugin makes no permanent changes to WP or BP. It makes not changes to the any database tables or anything to do with CSS.

The plugin works by checking the login state and the BPPC settings […]

@mmendezmi, Hmmmm… I haven’t got time to fully look into this at the moment, but it looks like the problem is that you’ve set the redirect to the wp-login.php. I’m guessing that my plugin’s redirect is […]

@alexbowyer, cheers.

You’re exactly right in your method for debugging your site with this plugin. If things aren’t working as you think they should be, make sure all of the required URLs are unblocked in the config file.

@chunky2010, so you mean, for example, being able to hide the ‘Private Page’ tab on the my demo site: http://www.englishpubpool.co.uk/bppc_test/about/

That sounds like a good idea… I’ll consider adding that to the next version too.

@chunky2010, Cheers. There isn’t a way to block users from visiting your public pages when the user is logged in. If you’ve made your own custom join us page, then you might have to make your own plugin (or search for another plugin) that can hide the page from logged in users. I might consider adding […]

@onyx808, using http://www.domain.com or just domain.com shouldn’t make a difference to this plugin. Maybe you’ve go something a little strange in you .htaccess file? You should fix your domain to always use http://www.domain.com or domain.com for all of your site’s pages. This will help with SEO too. All it takes is a few extra lines in […]

@David, @pcwriter & @Shakeology, the plugin has been updated now.

Widgets can now be blocked/unblocked by widget id, and a new mode has been added.

You can see the plugin in action here:
http://www.englishpubpool.co.uk/bppc_test/

@pcwriter & @Shakeology, I’ve had a bit of time to develop the plugin – still testing though…: – the plugin will work the same when WP is in a sub foulder. (www.my-domain.com/my-community/{BP}) – New method for blocking widgets, and widgets can be blocked on an widget ID basis when the user is logged out – and the […]

@neiltron, using $wp->query_vars; doesn’t work in the same way as my code. Some plugins use query strings like “?event_id=4”, using $wp->query_vars doesn’t get this extra information that is vital for a correct redirect uri. I’ve made some updates myself, not live yet – still testing: – the plugin will work the same when WP is in […]

Hmmm, if you can code, you can try to alter the plugin yourself. You can see how the plugin handles this for the standard theme and try to replicate what it does for the other column of widgets. The plugin uses Hooks in the standard types of themes to block the widgets at the moment, […]

Not sure what you mean, sorry.

Your config file isn’t being loaded as your ::$REDIRECT_HOOK is ‘my_redir_to’ in the config but you’re seeing ‘bp_pc_redir_to’ after you have been redirected.

I think you have the buddypress-private-community-config folder in the buddypress-private-community folder instead of in the plugins folder.

See FAQs

Your $REDIRECT_HOOK is wrong:
$REDIRECT_HOOK = 'hellomember';
MM_BUDDYPRESS_PRIVATE_COMMUNITY::$REDIRECT_HOOK = '/activity';

Try:MM_BUDDYPRESS_PRIVATE_COMMUNITY::$REDIRECT_HOOK = 'hellomember';

And maybe you don’t need ‘/s/*’ in the allowed URIs?

Well, your $REDIRECT_TO_URL page isn’t in the list of allowed URIs(!) as required for the plugin to work.

Add ‘/home’ to the Array of $ALLOWED_URIS – this should help.

Could you show your config file please, it’s hard to help without seeing how you’ve set-up the plugin. If you haven’t made a config file, then see the “How can I allow members to automatically register to my private community?” in the FAQs. I haven’t had time to work on this for a while, so […]

I don’t think there is a trivial answer to this question, as your posts could be displayed on various URIs depending on your WP permalinks setup. Basically, you’d have to add all of the URIs that are associated to your posts to the allowed list. You can make this easier for yourself by setting the […]

Well, you’ll have to change the redirect URL to the homepage, and add the URIs to your homepages to the list of allowed URIs. ` <?php // E.g. MM_BUDDYPRESS_PRIVATE_COMMUNITY::$ALLOWED_URIS = Array( '', // FOR "mousefriends.de/" homepage '/mousefriends', // FOR "mousenetwork.de/mousefriends/" homepage // etc… );…[Read more]

OK, I get what you’re doing now… Well, if you want to be able to access the site from both mousefriends.de & mousenetwork.de/mousefriends/ then you need to add more allowed URIs to your config file. This is because your mousenetwork.de/mousefriends/ site (which was working fine with the plugin) is in a sub-folder, so all of […]

I don’t understand your WP/BP set-up. Why are you running the site from 2 locations? Do you have WP/BP installed twice??? One config file won’t work for both http://www.mousefriends.de & http://www.mousenetwork.de/mousefriends/, you’d need to set-up two config files for each installation of WP/BP. Because these URLs are different, the config files…[Read more]