I'm not really sure whether this is a spaces or features issue, but I think it's more spaces related than features related.
I am building a feature that can be enabled for a specific space, in my case, for specific groups via spaces_og.
The feature consists out of a content type, a view and a few block. Now, the feature is basically "global", that is, the view is not filtered by space and its content type may not be posted in any group. When activating the feature for a group, I mostly want to do some custom stuff in blocks and add some group-specific node links when viewing a node of my feature's content type in a group space (this is easily possible, thanks to purl, even if the node may not be posted in a group at all).
Now, spaces (or spaces_og) doesn't allow me to do this. I think that it's spaces_og that overrides the og settings so that all content types provided by a spaces-enabled feature are treated as "standard group posts".
This should be configurable in the feature's info file to apply only to some, but not all, content types. Otherwise, it's not possible to build a feature that integrates with spaces and spaces_og but also provides a regular, not-og-enabled content type.
Comments
Comment #1
mikemccaffreyAre you saying that you want to be able to post nodes of that content type without assigning it to a group? That indeed may be difficult.
If you are simply looking to display content from all groups in a view, just makes sure that the feature is enabled for the site space.
Comment #2
Frando commentedI have a feature that is spaces og enabled. I want this very same feature to also provide a node type that is not a group post node type. Basically, what I want is the ability to configure the spaces takeover of og content type settings per content type. Currently, this is done automatically for all content types that spaces enabled feature provides. This is very limiting.
Comment #3
Frando commentedComment #4
jmiccolis commentedThe 2.x branch is no longer supported; setting this to "won't fix".