NipponMonkey
Forum Replies Created
-
Hmmmm… Works fine on my sites…
Can you give me more information, what version of WP and BP are you using? Also, what version of PHP are you using?
If you have any error messages in you server log related to the issues, could you provide them too.
Finally, can you show me the config file you’re using? Have you allowed access to the activation urls, so they aren’t blocked?
This might help too:
http://buddypress.org/community/groups/buddypress-private-community/forum/topic/creating-custom-config-file-does-not-work/?topic_page=2&num=15#post-98049Regards
Hmmmm, strange. You could try deleting this folder from your server first, then try again…
That would be a good thing to add. I’ve been busy with other things recently, but if I get time I’d like to add this kind of feature.
Strange, this plugin isn’t client side, so the browser should make any difference.
The plugin should affect the Admin area so you should be able to access the plugin fine from there to deactivate it.
You might get redirect loops when you first activate the plugin if you don’t have a standard WP, BP set-up – on the root of the domain.
You’d have to make changes to the config file manually first.
You can activate and deactivate the plugin through WP, but to alter the settings you have to create your own config file – See FAQs.
I think this is due to you not using PHP5. This plugin requires PHP5
@jessicaswift, do you have a customized config file set-up?
That is where your changes must go to override the default settings of the plugin.
You can find out how to make a custom config file and all of the settings that you can change in the plugin’s FAQs:
http://wordpress.org/extend/plugins/buddypress-private-community/faq/Check out:
How can I override the default settings? &
How can I allow members to automatically register to my private community?I haven’t tried the plugin with the Absolute Privacy plugin, so you might have to change the config file to allow additional URIs to get it up and running how you’d like it to.
You can add any number of public URLs that you’d like to allow users access to, this can be URIs to pages, posts or to activation URIs like ‘/activate?key=*’ (see FAQs)
The plugin is very flexible and can be configured to work however you’d like it to work, but you have to read the instructions to ensure you set it up right.
You can check out more information in the BuddyPress forum too:
http://buddypress.org/community/groups/buddypress-private-community/forum/If you’re trying to share a private WP/BP page on facebook, then you’ll get the redirect page instead. This is because FB is calling the page and FB isn’t logged into your site – so can’t access your private pages. I’ve just tested it.
But your public pages will be shared as normal. So, the only fix would be to make your page/post public before sharing it on facebook.
I’m not sure what your question/problem is regarding the WP/BP feeds.
You have it set-up to allow access to all of your feeds. That means all of your WP and BP feeds are available to the public as normal. But some of the information in the feeds might not accessible through actual site – if the information is on private pages. Allowing access to feeds, can allow access to information that you might like to remain private and is private on the actual site.
You can set-up a config file – read the FAQs ‘How can I override the default settings?’
http://wordpress.org/extend/plugins/buddypress-private-community/faq/Basically, you have to create a new file in a new directory that will store you settings. This file won’t be overwritten when you update the plugin in the future. Save the config file as:
/wp-content/plugins/buddypress-private-community-config/mm-buddypress-private-community-config.phpAs for your blank BP pages, you’d have to give me more information. I expect you aren’t running WP from the root of your domain or something.
If that is the case then see this post:
http://buddypress.org/community/groups/buddypress-private-community/forum/topic/redirect-hell/If you can provide me with error messages, I might be able to help you more…
Well, I’m not sure what you’re doing exactly, so I can’t give you the URIs you need to make public – you’ll have to work them out by testing.
But if you need access to the register.php file then add:
MM_BUDDYPRESS_PRIVATE_COMMUNITY::$ALLOWED_URIS = Array('/register.php', '/other-uris', 'my-landing-page'); // Or MM_BUDDYPRESS_PRIVATE_COMMUNITY::$ALLOWED_URIS = Array('/register.php*', '/other-uris', 'my-landing-page'); // Just list the URIs that need to be public so members can register properly. Just go though your process of registering a new user and add all of the URIs that are called during the registration. // You can list whatever you like, e.g. '/register.html' or 'register.php?action=add-member', 'register.php?action=activate&key=*' - whatever you need, just add the URIs to the allowed list. // If you use the normal BP registration form, all you need is: MM_BUDDYPRESS_PRIVATE_COMMUNITY::$ALLOWED_URIS = Array('/register', '/activate?key=*'); MM_BUDDYPRESS_PRIVATE_COMMUNITY::$REDIRECT_TO_URL = site_url() . '/register';Use this code in the config file that you must create and save as:
/wp-content/plugins/buddypress-private-community-config/mm-buddypress-private-community-config.php<?php // Allow users to register to BuddyPress (BP 1.2.5.2) through the native forms MM_BUDDYPRESS_PRIVATE_COMMUNITY::$ALLOWED_URIS = Array('/register', '/activate?key=*'); // Set the redirect to the native BP register form. All logged out users will be redirected to this page when they try to access a private BP page. MM_BUDDYPRESS_PRIVATE_COMMUNITY::$REDIRECT_TO_URL = site_url() . '/register';That’s all you need to do – just the 2-lines of code saved in the correct location.
I’m not sure why you’d want to use “site_url() . ‘/registration/register'”, as the standard BuddyPress registration/”Create an Account” page is located at “site_url() . ‘/register'”.
Are you using other plugins that change that?
Also, what register.php file are you talking about??? You don’t have to do anything to a register.php file.
I’m not sure what you mean, but this is how you can allow non-members to register to your private community:
MM_BUDDYPRESS_PRIVATE_COMMUNITY::$ALLOWED_URIS = Array( '/my-landing-page', '/register', '/activate?key=*' ); MM_BUDDYPRESS_PRIVATE_COMMUNITY::$REDIRECT_TO_URL = site_url() . '/my-landing-page';If you want your landing page to be the native BP registration page, then change the 2nd line to:
MM_BUDDYPRESS_PRIVATE_COMMUNITY::$REDIRECT_TO_URL = site_url() . '/register';// Note that the allowed uri, '/activate?key=*', uses the special // wildcard character * that will accept all uris starting with // '/activate?key=', so all activation codes will be accepted. // // Please note that if BP ever changes the uri for activating new members, // then you'll have to change this uri to match the new one. // This shouldn't be a big issue though.You might like to change this:
MM_BUDDYPRESS_PRIVATE_COMMUNITY::$ALLOWED_URIS = Array('/contact', '/archives', '/a-propos',); //to MM_BUDDYPRESS_PRIVATE_COMMUNITY::$ALLOWED_URIS = Array('/contact', '/archives', '/a-propos');Also, it sounds like your config file isn’t loading as restriction to the homepage is the default settings.
When you try to access a private page, do you see your custom redirect in the URL, ‘?redirection=/some-private-uri’?
If you don’t then the config file isn’t being loaded.
Remember, the config folder shouldn’t be in the buddypress-private-community folder, it should be in the wp-content/plugins/ folder.
This is to make sure your settings aren’t deleted when you update the plugin in the future.
Glad you got it workin’.
Where are you experiencing slow page loads?
When you’re logged in, you shouldn’t notice any difference really. All it does is add a few simple checks.
When you’re logged out and the user tries to access a private page, then the page can take a little longer to load because of the redirect. There isn’t much I can do to speed up the redirect though.
The only thing that could slow down the page loads is the add_action() calls – I’m not an expert on this, but I don’t think they would slow down your site much at all.
Often it’s calls to the database that slow things down, but this plugin doesn’t store any data in the database – so it should be quick.
Personally, I haven’t notice any difference on my site unless I’m accessing a private page and I get redirected.
There shouldn’t be ‘{‘ or ‘}’ in the config file! So you must be doing something wrong.
But first, did the plugin work when you first activated it? It should restrict logged out users to the homepage of your community.
If that’s working you can then try adding your own custom config file, to add a valid config file you must create a new folder and file, it MUST saved as:
/wp-content/plugins/buddypress-private-community-config/mm-buddypress-private-community-config.php
Note the “-config” parts at the end of the new directory you must create and at the end of the php file.
Here are the settings you can currently change – no ‘}’s!
MM_BUDDYPRESS_PRIVATE_COMMUNITY::$ALLOWED_URIS = Array('/contacts', '/about', '/welcome', '/welcome/*', '/welcome?*'); MM_BUDDYPRESS_PRIVATE_COMMUNITY::$REDIRECT_TO_URL = site_url() . '/welcome'; MM_BUDDYPRESS_PRIVATE_COMMUNITY::$REDIRECT_HOOK = 'my_redir_to'; //MM_BUDDYPRESS_PRIVATE_COMMUNITY::$BLOCK_RSS_FEEDS = FALSE; //MM_BUDDYPRESS_PRIVATE_COMMUNITY::$BLOCK_WIDGETS = FALSE;Let me know if you get it working – I have no idea where your error is coming from as I can’t see how the plugin could be causing it.