Hi,
After I enabled spaces_og the content types for organic groups is set to "Standard group post (typically only author may edit)". It looks like this is only happening with content types that May not be posted to a group.

Also, it is not possible to change the content type configuration for organic groups after I enable spaces_og.

When I disable spaces_og all works well.

og version is 6.x-2.x-dev

CommentFileSizeAuthor
#2 480964-spaces_og_content_type_usage.patch1.45 KBMatthew Davidson

Comments

mani.atico’s picture

mani.atico commented
Category: bug » support

Same here.

I'm trying to enable a feature which includes a node type originally set as a "group node". As avdp mentioned, when enabled, spaces og treats it as a "Standard node post". I know there are some related issues in the features module where this type of information is not saved when the ferature is exported, but I was wondering if this "by design" behavior has other reason to treat features' nodes as "Standard posts"; does this prevent erronous behaviors? is part of the module's concept? is it intended in work differently in the future?

Matthew Davidson’s picture

Matthew Davidson commented
Status: Active » Needs review
StatusFileSize
new 480964-spaces_og_content_type_usage.patch1.45 KB

As the comment for spaces_og_init() says, "We're gonna bulldoze your OG settings. Get over it."

This patch attempts to apply the bulldozer with a little more precision.

After a minute and a half of rigorous testing, it appears to work for me, but I can't be sure whether it breaks something else that assumes all posts will be 'group_post_standard'.

yhahn’s picture

yhahn commented
Assigned: Unassigned » yhahn

lol

jmiccolis’s picture

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

This patch attempts to apply the bulldozer with a little more precision.

Awesome, still the 2.x branch is no longer supported; setting this to "won't fix". I'd encourage you to take a look at Spaces 3.x