Hi,

After I follow the instructions in the Readme file and the inline instruction and then create a new organic group I get the following warning...

    * warning: array_keys() [function.array-keys]: The first argument should be an array in /var/www/vhosts/iraqistudentproject.org/subdomains/groups/httpdocs/sites/all/modules/og_blueprints/og_blueprints.module on line 1297.
    * warning: in_array() [function.in-array]: Wrong datatype for second argument in /var/www/vhosts/iraqistudentproject.org/subdomains/groups/httpdocs/sites/all/modules/og_blueprints/og_blueprints.module on line 1297.

I am running the latest og-5.x-1.x-dev.tar.gz and selected "One Overall Bundle".
Also, not sure if I'm supposed to see a different page, but the path to admin/og/og_blueprints/bundlecfg just returns me to same admin/og/og_blueprints page with a new inline instruction:

OG Blueprints is currently operating in 'One Bundle' mode, which means the blueprints in the bundle you define will apply to ALL the node types you define as groups in Organic Groups Configuration.

I can't find where I go to create the blueprints or bundles, as I expected the blundlecfg page to give me options to created a blueprints to bundle. so I'm not sure if these problems should be in the same issue.

I'll try this module in a fresh install with only the required modules to see if I can replicate the warning.

Comments

sdboyer’s picture

Nope, it's nothing you've done, it's definitely a loop I've programmed in that you've gotten lodged in. Three cheers for alphas. This is related to #253816: array_keys and array_diff warnings make og blueprints inoperable on fresh install in that it's about my not adequately handling the initial startup phase with blueprints - that is, the system's getting angry because there isn't any data there yet and it doesn't know how to react.

Anyway, I've got some ideas on how to fix this, and a temporary band-aid I just committed to -dev ought to fix this for alpha2, at least.

sdboyer’s picture

Status: Active » Fixed
Anonymous’s picture

Status: Fixed » Closed (fixed)

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