The Context UI doesn't display Spaces feature reaction

I am having the same issue.

I have the same issue. I am using a zen sub-theme if that helps. Any help would be greatly appreciated.

Did the interface change from what is seen in the screencast on developmentseed's website?

After a day of research, I found this documentation in the open atrium community docs.
https://community.openatrium.com/documentation-en/node/449/revisions/591...

See #4.

I'm experiencing this, too. @naptown, sorry, the mentioned documention doesn't help. I'm trying to turn on the example blog feature, but the included context (spaces-feature-blog) does not provide the beforementioned reaction.

I'm not sure this is a bug, might just as well be that I don't fully understand how it it supposed to work. Any help appreciated.

Btw, using all the latest versions.

I am having exactly the same problem. I found that if I edited the .info file and copied across the settings I needed from the spaces_blog.info file, then re-enabled the module, then the features functionality started to work. (It now appears as an available feature in my organic group). Once I had done this, on the /admin/build/features page the state of the feature changed to "overridden". It seems that features detected the change, and automatically added various things to the feature for me, including the context details. I then updated the feature.

I'm not exactly sure which settings I copied over to my feature's .info file, so you may have to play around a bit. Some of the ones I think I set are below, but I would advise to compare, and to enable what makes sense for your module:


spaces[types] = "all"
dependencies[] = "spaces"
dependencies[] = "context"
dependencies[] = "features"
dependencies[] = "{any other modules your feature is based on}"
features[context][] = "spaces-feature-{your feature name}"
features[node][] = "{the content type your feature is based on}"


I'm still a bit concerned about this way of getting things working though. It would be fantastic if context_ui could be fixed so that we can customise features for groups and spaces in there.

In building my feature, I used context.

It exported fine.

However, the feature was enabled everywhere on the site.

I found I had to go back to context for the feature and not select anything under spaces.

I then had to edit my .info file for my feature and add
spaces[types] = "og"
spaces[types] = "site"

I am not quire sure why adding space-site and space-og as options under spaces in my feature context had no effect.

In context 2.x the context doesn't define your feature, the feature does. Your context just needs to fire off of the things in your feature, it doesn't activate the feature itself.

subscribe

Does anyone know of a similar tutorial for D7?