Hi,
I looks like og blueprints won't work at all on a fresh install of drupal5...

I get the following warnings with a fresh install of drupal5 when I save the og configuration page found at admin/og/og page. The og configuration remained unchanged from the default. I just saved the page. The og blueprint "operating mode" hadn't been changed from Disabled. The group node is a simple CCK type called groups, and blog was set as a Standard group post.

    * warning: array_keys() [function.array-keys]: The first argument should be an array in /var/www/vhosts/Xhttpdocs/sites/all/modules/og_blueprints/og_blueprints.module on line 1318.
    * warning: array_diff() [function.array-diff]: Argument #1 is not an array in /var/www/vhosts/X/httpdocs/sites/all/modules/og_blueprints/og_blueprints.module on line 1319.
    * warning: Invalid argument supplied for foreach() in /var/www/vhosts/X/httpdocs/sites/all/modules/og_blueprints/og_blueprints.module on line 1319.
    * warning: array_diff() [function.array-diff]: Argument #1 is not an array in /var/www/vhosts/X/httpdocs/sites/all/modules/og_blueprints/og_blueprints.module on line 1326.
    * warning: Invalid argument supplied for foreach() in /var/www/vhosts/X/httpdocs/sites/all/modules/og_blueprints/og_blueprints.module on line 1326.

the following modules are install:

cck-5.x-1.7
demo-5.x-1.4
devel-5.x-1.x-dev
og-5.x-7.0-rc5
panels-5.x-2.x-dev
poormanscron-5.x-1.x-dev
supernav-5.x-1.x-dev
views-5.x-1.x-dev

I am unable to create any blueprints and the admin/og/og_blueprints/bundlecfg link simply returns me to admin/og/og_blueprints without the previous inline help text.

Comments

sdboyer’s picture

Thanks for reporting this. I was so all-in when writing the first alpha of this that I must not've adequately tested the various possible permutations of how that function could be called. I don't know exactly how long it's going to take for me to get back to releasing alpha2, so in the meantime, if you could run a direct query against your database and see if that fixes this problem, I'd appreciate it:

UPDATE system SET weight = 5 WHERE name = 'og_blueprints';

Or, if you're using phpmyadmin, just go in and manually change the Weight field from 0 to 5 on the og_blueprints record. If you're using any table prefixing, make sure to include that in the query.

I suspect that the problem here is that my custom submit handler is firing before og's is, and the variables haven't yet been updated. Looking at the code, however, that just doesn't make sense...hopefully that query will fix the problem. If not, I'll figure it out for alpha2.

solutiondrop’s picture

Hi,
Thanks for looking into the problem. Changing the og_blueprints weight to 5 does stop the warning when creating a new group. Although, it still doesn't help me get into any actual configuration page or form to build bundles. After enabling og blueprints using "one bundle type for all group types" I still can't get to the configure page at /admin/og/og_blueprints/bundlecfg. The link for "You can configure your bundle in Bundle Settings" just returns me to the same page without any way to configure or build bundles and blueprints.
I'll wait for Alpha 2. Thanks again.

sdboyer’s picture

Ugh, that's doubly annoying. I wonder if that might have something to do with one unfinished piece of code I did leave in alpha1...

Do you have full error logging enabled? I'd be interested to find out if there are any errors thrown when you get redirected back to the overall config page.

solutiondrop’s picture

I have since given up and uninstalled OG Blueprints, but I'll check it out on my sandbox site when I get a chance and report back here.
Thanks.

solutiondrop’s picture

Hi,
FYI, trying out alpha3 and there are no more array_keys and array_diff warnings when creating new organic groups. Although I still am unable to access the Bundle Settings page as per http://drupal.org/node/260877, and my comment above, http://drupal.org/node/253816#comment-831923 still hold true concerning that same issue of no Bundle settings page.
Thanks.

sdboyer’s picture

Yep, I rewrote the code that was causing the problems with creating the new content types; also had to rewrite the whole thing since og entirely changed the way/location in which it declared content types as groups in 7.0. However, I'm still befuddled as to what's causing the problem you're encountering - fortunately, it look like I might be able to get a look at someone's dev site who's encountering the problem. I'll post once I know more.

sdboyer’s picture

Status: Active » Fixed

As far as I know, this is no longer an issue as of alpha5.

Anonymous’s picture

Status: Fixed » Closed (fixed)

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