I've been reading the article:

http://www.phase2technology.com/blog/using-blueprints-to-clone-spaces-in...

Really a nice feature for OA2. Thankfull. But I've found two issues OA in 2.15:

- Only Drupal 'admin' can use successfully the created Blueprint (Space Type in 2.15). An 'administrator member' only get cloned the top space, but no sections, documents, etc, that were present in the space template get cloned. With Drupal 'admin' they do.

- I can not see the way to clone menus. Should they?. It would be nice

Comments

mpotter’s picture

mpotter commented

Cloning menus is currently not implemented and is on the to-do list.

For space-admins, that sounds like a bug and will look into that.

dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
commented

I've been able to recreate the problem. It's basically this line in 

$access = og_user_access('node', $gid, 'clone node') || ($own_node && og_user_access('node', $gid, 'clone own nodes'));

It's checking if you have 'clone node' permission on the original space. This makes sense when doing a straight clone, but not when creating a Space from a blueprint. There is already a mechanism for skipping this check when using blueprints, but it only affects the top-level Space, it isn't passed down to the content below, so this check is performed.

I've started working on a change to attach a flag to the node which will get propagated to all it's children too.

dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
commented
Title: Using Blueprints to clone spaces in OA 2.15 » Bypass access checks when cloning via a Blueprint
Version: 7.x-2.15 » 7.x-2.x-dev
Status: Active » Needs review

I've created a PR to fix this:

https://github.com/phase2/oa_core/pull/41

mpotter’s picture

mpotter commented
Status: Needs review » Fixed

Committed to -dev version.

Status: Fixed » Closed (fixed)

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