Hi,

I'm working on a commons site that I'm doing a far bit of customization for. I like it a lot, but am having troubles using features to customize the site, as I end up overriding a lot of the commons feature. I find the main culprit is permissions. Whenever I change permissions for something that comes in commons, I end up not being able to export that to features, without potentially breaking my upgrade path with commons. I permissions should not be set using strongarm, but rather just set on hook_install, and then whatever changes the site owner makes he can export to features.

Thanks,
Mark

Comments

jessehs’s picture

jessehs
he/him
Primary language English
Location Taos, New Mexico
commented
Version: » 6.x-2.x-dev

...bump...

This is a definite concern of mine as well. This sounds like the better option for most users who want to customize their site, and still want the benefit of upgrading commons/reverting Commons' features.

As a resource for developers, there is a complex/convoluted method of overriding the commons-exported permissions in a custom module using hook_user_default_permissions_alter(&$items) although I haven't really tested it out. The same method works for contexts, views, you name it. Features fires an alter hook right after it loads each type of export, so you can unset or alter items to your heart's content. The feature will probably still appear overridden when viewing the Features UI, but reverting it will not erase the custom changes.

jsibley’s picture

jsibley commented

A related concern is that if one adds new roles, the commons features can't know about those roles, so reverting features seems to get rid of those permissions. At least, that is what seemed to happen.