The 'omitted nodes' part of OG has been rewritten in OG7.2 and CTA is now no longer compatible with it. Here is a patch to make it compatible.

CommentFileSizeAuthor
og_content_type_admin.module.patch2.51 KBpvasener

Comments

pvasener’s picture

pvasener commented
Assigned: pvasener » Unassigned
Anonymous’s picture

Anonymous (not verified) commented
Assigned: Unassigned »

The patch applies cleanly but i don't know what to test for here to make sure everything works correctly, would you please clarify ?

Thanks, Paul

ajayg’s picture

ajayg commented

I am confused as well. I am running OG CTA 1.5 with OG 7.2 and I am not seeing any issue (without the patch). SO I wonder why the patch is required (or what it fixes). Could you please elaborate a use case?

pvasener’s picture

pvasener commented

Ok, let me clarify the problem then. I have OG 7.2 installed. When I go to the OG Configuration page (admin/og/og), I have a few content types which may be 'Standard group post' and others which 'May not be posted into a group.'

Now, on the OG CTA configuration page, without my patch, the content types I get are not only the ones which may be posted in groups but many others too. I guess there are the ones that were configured in OG 7.1 with a now-deprecated og settings if I remember well. So, I mean that the way to retrieve the 'og-enabled' content types has changed in OG 7.2 and CTA is still using the previous mechanisms (which may explain why you don't see any difference on your side).

I hope I'm clearer now, if it's still blurry, don't hesitate to ask me for more explanations.

moshe weitzman’s picture

moshe weitzman commented

The old variables are left in the Db for omitted usage so folks who are upgrading won't notice that their site is broken until they need to change usage settings. To see this bug, just start changing Usage settings.

Anonymous’s picture

Anonymous (not verified) commented

looking into this now ...

Anonymous’s picture

Anonymous (not verified) commented
Status: Needs review » Reviewed & tested by the community

I observed the problem and confirmed the patch resolves the problem. I'll get this fix out later today.

@pvasene

Thanks for your help !!!!

Anonymous’s picture

Anonymous (not verified) commented
Status: Reviewed & tested by the community » Fixed
pvasener’s picture

pvasener commented

You're welcome, it's a pleasure :)

Do you intend to release a new version of the module in a short-term period of time?

Anonymous’s picture

Anonymous (not verified) commented

Yep , i'm going to release a development version right now ...

Thanks again.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.