I am having a problem with the Spaces Site and Features modules. I have created a content type called "Problem", and a View which shows all problems, and built a feature that uses this content type and view. I have enabled this feature on the global space for my site. My problem is that even though I have selected "May not be posted into a group" in the Organic Groups section for the "Problem" content type, when I enable the feature, the organic groups section gets changed to the following:

"This content type is provided by the problems feature and will be used as a standard group post."

I was not want the problems to be in a group, so this is a somewhat inconvenient change. Perhaps I need to create a global group of sometimes that will be used by the main site space?

This also means that my existing Problems now have the following message at the top:

"This content is not assigned to a group and is not visible to non-administrative users."

And I cannot create problems without being inside a group. Obviously this is no good as users cannot create or view problems in the feature, which defeats the object.

Perhaps I have just made some basic mistakes with my configuration? Even so, it would be useful if there was some more guidance available and tips within the module to avoid this.

Thanks for any help, and apologies if I'm just being dumb.

Comments

damien tournoud’s picture

damien tournoud commented

You haven't made any mistake, spaces_og, in its current implementation is "predating" the site space: as soon as you have visited a group space, there is no way to go back to the site space.

jmiccolis’s picture

jmiccolis commented
Status: Active » Closed (won't fix)

Setting this to won't fix, as we're no longer maintaining the 2.x branch. However I'd encourage that you take a look at Spaces 3.x as we've change how the OG integration works.