Multi site Configuration /members-area/

[Dennis]

I'm having trouble

Getting a MU with 2 blog

• Corparate site . Blog id 1 level 0 open to all
• Members area BP and other puggins and pages . Blog id 2 level 1
open to all un paid members but shoot be close to other people, registration is closed .

define('MULTISITE_FARM', true);

User roles per Blog acces and restictions is no problem thats working fine.

Only the problem is that the /members-area/ id 2 is still open to the plubic
is there a other way to block the members area with out using
URI restrictions because i dont get this working.

/members-area/
/members-area/members/
/members-area/groups/
/members-area/blogs/
/members-area/activity/
/members-area/messages/
/members-area/profile/
/members-area/friends/
/members-area/settings/


Cheers Dennis

[Cristián Lávaque]

Hi Dennis.

Using URI restriction on members-area should be enough to restric anything under it too, so you don't need that many in the setting as you listed, they all have that directory name in common.

You can also use word fragments instead of a full URI. If a word fragment is found anywhere in the URI, it will be protected.

Another thing you could use would be the tag restriction, and add the tag to everything you want to restrict. WP Admin -> s2Member -> General Options -> Tag Access Restrictions.

So, let me see if understand this: you have two blogs in separate domains, blog 1 will be open to everyone, blog 2 won't, just a part public and the rest protected. Is the members-area directory the blog or just a directory of it?

[Jason Caldwell]

Thanks for the excellent question.
~ and thanks for bringing this to my attention Cristián.

Another thing to remember, is that s2Member is NOT capable of handling permissions across multiple blogs from a single configuration on the Main Site. Each blog within a Network runs separate instances of the s2Member plugin; each with their own configuration. So you can't configure s2Member on the Main Site and expect it to protect other blogs in your Network. If you need to protect content on other blogs in your Network ( other than your Main Site ), you will need to activate the s2Member plugin on those blogs, and configure each of those instances to protect the areas that need to be off limits to the public.

* This may change in a future release ( as new features become available ). But as of right now ( s2Member v3.5.7 ); each blog in your Network loads a completely separate instance of s2Member.

[Dennis]

HI Jason,

In my other blog the s2Member General Options page is empty.

Any idea when the update is comming other wise i leave it for now depending on your update roadmap

[Cristián Lávaque]

Hi Dennis.

This video will help you understand why that happens.

[Dennis]

its only add my second blog in my MU install, as i understand you right the option shoud be in all MU sites Blog beside my, blog ID 1

In my theme Platform Pro there is a weel that will turn when there is a jquery error.

Would be great to have a general option in the Network Admin / Multisite (config)

[Jason Caldwell]

Sorry Dennis. Can you please re-state your last reply. I'm not sure we understand.

its only add my second blog in my MU install, as i understand you right the option shoud be in all MU sites Blog beside my, blog ID 1

In my theme Platform Pro there is a weel that will turn when there is a jquery error.

Would be great to have a general option in the Network Admin / Multisite (config)

[Dennis]

Hi Jason I send you a email with the details

Cheers

Dennis

[Jason Caldwell]

Thanks Dennis. I received your email.
I'm still not sure I understand the question completely.
But hopefully this information will help you.

It looks like you have some JavaScript errors being introduced in your WP Dashboard.
( Please see the attached screen shot. )

Would be great to have a general option in the Network Admin / Multisite (config)

I think you're requesting a feature that would allow a set of Network-wide protections.

As I stated before, s2Member is NOT yet capable of handling permissions across multiple blogs from a single configuration on the Main Site. Each blog within a Network runs separate instances of the s2Member plugin; each with their own configuration. So you can't configure s2Member on the Main Site and expect it to protect other blogs in your Network. If you need to protect content on other blogs in your Network ( other than your Main Site ), you will need to activate the s2Member plugin on those blogs, and configure each of those instances to protect the areas that need to be off limits to the public.

* This may change in a future release ( as new features become available ). But as of right now ( s2Member v3.5.7 ); each blog in your Network loads a completely separate instance of s2Member.