I have following structure:

Space 1 (private)
I
I--- Subspace 1.1 (public)
I--- Subspace 1.2 (public)

Space 2 (public)

Space 3 (public)

Now I can see all public subspaces which have parent spaces as an entry ot the dropdown menu (Space 1.1 + Space 1.2 are listed) when i'm logged out.

If I choose these entries I will be redirect to the login page (rights management works)

I think that all public spaces are listed unrespecting if they have parents or not.

Perhaps the easiest way to solve this problem is only to list spaces when they have no parents.

Comments

Argus’s picture

Argus commented

Why would you want to show public sub-spaces in a private space?

m.schwarzenberg’s picture

m.schwarzenberg commented

Because I want to structure the private area by using several subspaces that are side by side.

But - when you ask - perhaps I have the same problem when I am logged in as an auhentificated user that
only belongs to subspace 1.1. He sees the menu entry for subgroup 1.1.1.1 also when he is not a member of it.....

Space 1 (private)
I I--- Subspace 1.1 (public)
I I------------Subspace 1.1.1 (private)
I I I------------Subspace 1.1.1.1 (public)
I I I------------Subspace 1.1.1.2 (private)
I I--- Subspace 1.2 (private)
I I I------------Subspace 1.2.1 (public)
I
Space 2 (public)
I
Space 3 (public)

Argus’s picture

Argus commented

Did you read the documentation about access control and visibility?

An other aspect may be that the menu visibility doesn't follow content accessibility. If I disable the site content access for anonymous users they can still see the spaces in the menu eventhough they cannot access them.

m.schwarzenberg’s picture

m.schwarzenberg commented

Hmm - Best solution will be to list only spaces which I have the right to entry.

Sometimes it is a problem that an unauthorized user knows about the existing of a private space (which he can't and shouldn't access)

Argus’s picture

Argus commented

Perhaps https://drupal.org/project/menu_item_visibility can solve that problem for you.

m.schwarzenberg’s picture

m.schwarzenberg commented
Status: Postponed » Active

I have read the documentation as you suggest. I will think about an other solution way for my structure.

I will postpone this issue because I think that my structuring is not the 'oa2-way'.

m.schwarzenberg’s picture

m.schwarzenberg commented
Status: Active » Postponed

Forgotten to change status.....

mpotter’s picture

mpotter commented
Status: Active » Closed (works as designed)

Right now OA2 does not currently support a "Public" subspace within a "Private" space. You really need to make the parent space also "public". There are some patches to the og_subgroups module to handle bi-directional permission inheritance that might help with this in the future. But right now subspaces inherit from their parent.

Also, there *is* a new option in one of the later -dev versions that lets you only show top-level spaces in the drop-down toolbar menu.

mpotter’s picture

mpotter commented
Issue summary: View changes

precised the issue