• Create a space "Base Space"
  • Add a user "TestAdmin" and promote to Space Admin for Base Space
  • Got to admin/config/group/permissions/node/oa_space and disable "Use any space type"
  • Log in as TestAdmin
  • Check if Spaces can be created

Expected: TestAdmin can no longer create any spaces
Result: Any Space can still be created.

In fact none of the OG permissions seem to work.

Comments

Argus’s picture

Argus commented
Issue summary: View changes
Argus’s picture

Argus commented
Issue summary: View changes
mpotter’s picture

mpotter commented
Status: Active » Fixed

Once you created a Blueprint, you should have a new OG Permission for creating spaces of that type. So you could modify the space permissions for Space B admins so they can only create spaces of type Blueprint A.

Argus’s picture

Argus commented
Status: Fixed » Active

Once you created a Blueprint, you should have a new OG Permission for creating spaces of that type.

That doesn't seem to be the case. At least I'm not able to find any new OG Permission at admin/config/group/permissions/node/oa_space.

Argus’s picture

Argus commented

Oh wait, are they listed in the "Open Atrium Buttons" section? That's odd. Anyway, these are not enabled by default, though still a Space administrator is able to clone the Blueprints created.

mpotter’s picture

mpotter commented
Status: Active » Fixed

You should see a permission at the top of those called "Use any space type" that overrides all of the others. Turn this permission off and then enable the permissions for the space types that you need.

Argus’s picture

Argus commented

Yeah saw that one, turned that off for the administrator member but it still lets them create any Space.

Reproduced this on a fresh OA install:

  • Create a space "Base Space"
  • Add some Sections
  • Save "Base Space" as a Blueprint
  • Add a user "TestAdmin" and promote to Space Admin
  • Disable "Use any space type"
  • Enable "Base Space" type
  • Log in as TestAdmin
  • Check which Spaces can be created

The result is that any Space can still be created.

Bug?

mpotter’s picture

mpotter commented

Can you actually create the spaces you don't have permission for? Or is it just showing in the menu. Also, how are you creating spaces? Via the toolbar dropdown menu or via the Site Map? It's possible that since these permissions were implemented for a client last year that something has been changed or added that needs to check these same permissions.

Argus’s picture

Argus commented

I can create Spaces I don't have permission for using the dropdown menu and also using the Site Map. This is with "Use any space type" and the Space type in question disabled.

I also tried clearing cache and rebuilding permissions but that doesn't change a thing.

Argus’s picture

Argus commented
Title: How to limit blueprint cloning ? » Space permissions not
Category: Support request » Bug report
Issue summary: View changes
Status: Fixed » Active
Argus’s picture

Argus commented
Title: Space permissions not » Space permissions not working
Argus’s picture

Argus commented

I tested this again and narrowed it down a bit; none of the permissions in admin/config/group/permissions/node/oa_space seem to have any effect on a user that is promoted to Space administrator.

Argus’s picture

Argus commented
Title: Space permissions not working » Space permissions not working, when Administer group is enabled
Component: Miscellaneous » Documentation
Category: Bug report » Support request
Status: Active » Fixed

The "Administer group" permission seems to control everything. Once this is disabled the other permissions for a group administrator work as expected. Changing this to a documentation issue.

Argus’s picture

Argus commented
Status: Fixed » Active

Super annoying and complex. Still can't get blueprint creation working properly.

Here are the available permissions:

Open Atrium Buttons

  • Use any space type
  • Use custom added (blueprint) space type
  • Use Default space type

Organic groups

  • Edit group
  • Administer group
  • Create Space content
  • Edit own Space content
  • Edit any Space content
  • Delete own Space content
  • Delete any Space content

None of the Open Atrium Buttons permissions seem to have any effect, no matter what other permission is enabled.
The "Edit group", "Administer group" and "Create Space content" permissions seem to be interchangeable, all control if a member can create Spaces. But this seems to be an "all or none" setting with no differentiation between available Spaces.

mpotter’s picture

mpotter commented

Yep, sorry for all the trouble on this one. Apparently the old code that implemented the specific space type permissions wasn't ever applied to some of the newer toolbar and space creation code.

I'm working on some commits to sneak this fix into v2.42 today.

mpotter’s picture

mpotter commented
Status: Active » Fixed

Should be fixed in commits a557252 and 9b13cbf in oa_core and commit 88ba853 in oa_toolbar.

Argus’s picture

Argus commented

Ah great! I was starting to doubt myself. :-)

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.