I installed Blueprints after trying out Collections. I didn't need to migrate any data from Collections and so completely uninstalled it. From the start I used Blueprints in One Bundle Per Group Type mode and created a number of default Blueprints. However, these never show up in the lists for the Group content types (on my system they are called Clusters and Case Studies).

Am I just totally misunderstanding how this should work or is there something that could potentially cause this to occur. I got Collections working fairly well but need the extended functionality of Blueprints.

I'm running the site on CentOS5 with PHP5.2 and MySQL 5. I also have OG User Roles, OG Content Type Admin, OG Subgroups, OG Forums, OG Galleries and the OG Panels module installed. Does the OG Panles module get referenced in there somewhere? I started to work out how to use that when I saw collections and then forgot about it.

Thanks for your help.

CommentFileSizeAuthor
#4 og_blueprint_bundles_missing.png32.27 KBUtternonsense

Comments

sdboyer’s picture

sdboyer commented

SO sorry I didn't get back to you on this earlier - I'd been buried with another project and didn't even realize I hadn't set up my subscriptions for the new project. Whoops.

The functionality in Blueprints is pretty much the same as in Collections - just cleaner, tighter, etc, so if Collections was working for you, then Blueprints oughtta be working pretty much the same way.

Yeah, og_panels is heavily referenced by og_blueprints. Well, there's fairly little direct contact in the code itself, so it might be more accurate to say that blueprints extends the structures established by og_panels. However, the actual blueprints interface and bundle/blueprint setup & configuration is pretty much detached from everything else, so there really oughtn't be any conflicts with other modules.

I think I need to clarify my understanding of your problem - you've created these two node types, Clusters and Case Studies, and you've marked both of them as groups in the og admin menu. If you're set up in bundles-per-type mode, then it means the Bundle and Blueprint tabs in the blueprint admin area should each have three secondary tabs - one, the default 'Master' bundle, and then one tab each for 'Clusters' and 'Case Studies.' If you've created a bunch of blueprints already, then each of those blueprints ought to be visible in the listings on both the Bundle and Blueprint admin pages (although the Bundle/Master page should have a bunch of greyed out form widgets).

So, let's start from there - what, if anything, about the scenario I've described above isn't true about what you're seeing?

Utternonsense’s picture

Utternonsense commented

Hi and thanks for the reply...

"If you're set up in bundles-per-type mode, then it means the Bundle and Blueprint tabs in the blueprint admin area should each have three secondary tabs - one, the default 'Master' bundle, and then one tab each for 'Clusters' and 'Case Studies.' If you've created a bunch of blueprints already, then each of those blueprints ought to be visible in the listings on both the Bundle and Blueprint admin pages"

That's correct, I have created two Blueprints, that appear with greyed out controls, in the list in the Master Bundles on the Bundles and Blueprints page but shouldn't they appear in the same lists under the Case Study and Cluster tabs? When I look at the master Bundles they say 'Delinked in all bundles' - is that a problem?

I imagined that having created a set of master Blueprints and Bundles they would appear in the lists for both OG content types and then I'd delink them and manipulate their features and the Release them as bundles for each OG type. As it is there is never anything in the lists there.

sdboyer’s picture

sdboyer commented

Man, I've already generated a morass of jargon with all this abstraction. Shame that there's no way around it, but at least it's better than with Collections...

Anyway, I'm pretty sure that your imagined picture of how this would work is indeed the way I've intended it. Step by step, here's how things should have gone - note that I'm using the ellipsis to represent admin/og/og_blueprints:

1. (In no particular order) You installed OG/OG Panels and OG Blueprints. You enabled those two node types as group node types in the OG admin page. You set OG Blueprints to bundles-per-type mode. (Note that when it comes to URLs/names, bundle === node type; i.e., the internal system name for the bundle is the internal system name for the node type; the same goes for the public-facing name)
2. (Now the order matters): You created two blueprints, each of which has a set of greyed-out controls on the .../bundlecfg/master page, but those controls are operational on the ../bundlecfg/ pages.
3. You moved over to .../blueprintsetup/master, where both blueprints should have been listed, and both were listed (at least initially) as being linked in two bundles. They also should've all been grouped under a "Enabled Blueprints" table subheader row.
4. Moving over to one of the .../blueprintsetup/ pages, you ought to have seen each of the two blueprints listed under the appropriate subheader (home page, enabled, or disabled) based on your configuration of that blueprint on the .../bundlecfg/ page. If the blueprint was enabled (which includes the home page), then you ought to have a set of links to the panels editing UI for that blueprint.

As I understand your situation, the real problem is with step 4 - from the moment you created the blueprints, they a) were listed as being delinked in the master bundle and b) weren't showing up at ALL on the .../blueprintsetup/ pages. Is that accurate?

If so, then I've definitely borked something up in the code. When new blueprints are created in bundles-per-type mode, they're supposed to be linked to the master bundle's version until forcibly deliniked. Moreover, I changed the code from how it worked under Collections so that every blueprint should show up on EVERY bundle's .../blueprintsetup page under ALL possible circumstances.

Lemme know if I've characterized the problem accurately; if I have, then it means I've got a hefty bug to fix for alpha2.

Utternonsense’s picture

Utternonsense commented
StatusFileSize
new og_blueprint_bundles_missing.png32.27 KB

You've hit the nail on the head...

The bundles only ever appear under the Master tab and never under the tab for each group type (not even initially). I've provided a screenshot.

"(Note that when it comes to URLs/names, bundle === node type; i.e., the internal system name for the bundle is the internal system name for the node type; the same goes for the public-facing name)"

This threw me a bit so I decided I may have simply mis-named the bundles so I tried creating a blueprint called casetudy but that didn't make any difference. I'm actually pretty confused by that statement - could you clarify it. When you say 'node type' is that the same as content type and if so how can I give a bundle the system name of something else without causing a conflict?

Thanks very much again for your time on this...

floptikal’s picture

floptikal commented

I have the same problem, but in addition I get the watchdog error :
"warning: array_values() [function.array-values]: The argument should be an array in E:\!fatcap\projecter\i-volunteer\website\sites\all\modules\og_blueprints\og_blueprints.module on line 51."

The error gets thrown on both the bundle and the blueprint pages for each group. Hope that can help...

Henrik

Utternonsense’s picture

Utternonsense commented

I'm an idiot - I'd suppressed errors on the page from modules and hadn't seen this...

warning: array_values() [function.array-values]: The argument should be an array in /var/www/html/emergesustain/sites/all/modules/og_blueprints/og_blueprints.module on line 50.

Sorry to be a dork.

sdboyer’s picture

sdboyer commented

Sorry, I meant to at least update the issue once I'd figured out what's causing this.

The problem is most definitely in the code - because of the order in which hook_form_alter() gets called and the way that the og admin system form is constructed, I can't get my submit handler in after the other submit handlers in the way I'd like. Just means a little bit of waste that I'd have rather avoided, but it's negligible, so no biggie. It'll be fixed in alpha2...whenever the hell the rest of my work lets me get around to it.

sdboyer’s picture

sdboyer commented
Status: Active » Fixed

Issue has been fixed in alpha2.

sdboyer’s picture

sdboyer commented
Status: Fixed » Needs work

Or at least I thought it was fixed. More forthcoming...

sdboyer’s picture

sdboyer commented
Status: Needs work » Fixed

Corrected yet again in alpha3 - with respect to the original issue here, I added a check that ensures proper synchronization between node types declared as group types and the contents of the og_bundle table.

Anonymous’s picture

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

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

ami.matiauda’s picture

ami.matiauda commented

I am still having the same problem.
"warning: array_values() [function.array-values]: The argument should be an array in .../sites/all/modules/og_blueprints/og_blueprints.module on line 50."
Using OG 5.x-7.3.

SamRose’s picture

SamRose commented
Version: 5.x-1.0-alpha1 » 5.x-1.0-alpha6

I am getting a similar thing, no blueprints, no bundles, using alpha6

implode() [<a href='function.implode'>function.implode</a>]: Bad arguments. in /mysite/includes/form.inc on line 634

was one php error I received...