just noticed an odd behaviour when using features to migrate content types from site A to site B...i.e. it doesn't appear to store organic group settings with the content type.

anyone else noticed this?

Comments

hefox’s picture

hefox commented

Are you using strongarm and did you select the organic group variables related to that content type?

Dublin Drupaller’s picture

Dublin Drupaller commented

not using strongarm and iirc I did select the og fields. will run through it again to try and recreate the problem

hefox’s picture

hefox commented

Things like og settings are stored in the variable table and not exported with the node type. Check out strongarm.

Dublin Drupaller’s picture

Dublin Drupaller commented

thanks Hefox. are you sure? when I say og settings..I mean as follows (using a node type called campaign for iillustrative purposes):

if I goto admin -> content management -> content types -> campaign -> edit

and set the group settings there as a STANDARD GROUP POST or GROUP NODE...that setting doesn't seem to come across using features. i.e. I have to manually go back into each content type on the new site and manually make that change. I'm almost certain that setting isn't stored in the variables table.

hope that makes sense..

dub

hefox’s picture

hefox commented

Use strongarm; those settings are stored in variables and not exported with the node type. Most node type settings are.

Dublin Drupaller’s picture

Dublin Drupaller commented

just checked hefox. the settings are stored in the og table.

hefox’s picture

hefox commented

The og table, which is keyed by nid, is where the settings for group nodes are saved, not the overall content type settings.

Dublin Drupaller’s picture

Dublin Drupaller commented

the overall content type settings appear to be handled correctly by features..but the og settings (og table in db) I'm referring to don't appear to be coming across when using features.

hefox’s picture

hefox commented

if I goto admin -> content management -> content types -> campaign -> edit

and set the group settings there as a STANDARD GROUP POST or GROUP NODE...that setting doesn't seem to come across using features. i.e. I have to manually go back into each content type on the new site and manually make that change. I'm almost certain that setting isn't stored in the variables table.

Unless you're exporting nodes and being very confusing, THIS is a variable. You need to choice it and export it with your feature using strongarm.

Dublin Drupaller’s picture

Dublin Drupaller commented

sorry hefox...perhaps i wasn't clear in my earlier post. I'm not exporting nodes..I'm using features.module to migrate content types from site a to site b.

i'll have a look at strongarm.

Grayside’s picture

Grayside commented

Dublin: You are being clear, but it looks like you are confused about how OG stores different types of data.

The fact that a given content type can be used as a group node is stored as a Variable which is saved "Group node/standard group post/etc" in the content type form. As such, you need to do a variable export to get that configuration into your feature, and that requires strongarm.

The details of how nodes and users are associated with group nodes is stored in database tables.

technivant’s picture

technivant commented

I had the same trouble with this. og_usage variables in features only showed up after I selected Organic Groups module as a Dependency (which wasn't auto-detected from my content types).

hefox’s picture

hefox commented
Category: bug » support
Status: Active » Fixed

TMK this has been answered. Anyhow, wrong issue queue if it hasn't; either OG or strongarm would be one needing to provide this.

Grayside’s picture

Grayside commented

As a feature request, this is a duplicate of #749930: Add features intergration. As a support request, answered and fixed ;)

Status: Fixed » Closed (fixed)

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