Maintainer needed for CCK / Panels integration

I'll paraphrase what I told yched on IRC here, just so it's on the record:

If no one else steps up for this, then it's something I'll likely end up doing when I next have some time. However, that's not likely to happen until late December/early January, and that's at the EARLIEST. So I'd encourage someone to step up, because I won't even think about it before then.

And hey, I'd also encourage someone to step up because taking care of this would be a great way for someone new to the drupal dev community to get some recognition, and fast - nothing like working on integration between two high-profile contrib modules to get noticed quickly... :)

Ok, I'm working on fieldgroups in #349987: Panels / fieldgroup integration in D6 . I'm willing to make sure it and the single field integration stay working with panels because I'm working on APK for D6, now, and need those both working. I'm not up for enancing the UI, though, so if someone else wants to take that bit, that would be nice. :)

Michelle

I've just submitted a patch that attempts to fix a rather grave problem in the 2.4 implementation, (#505278) and was pondering what the maintainer situation was?

We (as in the company I work for) is already building a site with Panels 3, with more coming up fast, so we have a pretty big interest in Panels 3 support in CCK. At the moment I'm doing:

- test, debug what's here
Check. Already using it in almost-production.

- ensure our code stays in sync with Panels (which is still alpha)
Beta now, but we're upgrading as fast as they come out.

- maybe enhance the UI for 'field as panel' settings form ?
Haven't thought about that, but could do.

- update 'fieldgroup as pane'
Just thought of a use case, so I should look into that.

- other ideas ? ;-)
Might come up with some...

So... Is there any secret handshake?

My work on Panels related stuff has been delayed for probably at least another couple of weeks because of the DruBB project. If you want to pick it up, that's fine by me. I'm not a CCK or Panels maintainer, just an interested 3rd party who needed the integration. :) As far as I know, the integration is working fine but there's always room for further testing and to improve the UI.

There is one known issue with the content profile relationship integration where the fields/fieldgroups shown aren't limited to the node type(s) we have a context for. I don't know if the fault for that lies in the relationship code or in the CCK integration.

Michelle

"There is one known issue with the content profile relationship integration where the fields/fieldgroups shown aren't limited to the node type(s) we have a context for."

If I understand correctly, I think I've seen the same problem.

A bit of hacking about discovers that instead of returning an empty context when supplied a null context, if ones sets restrictions on the returned context, it apparently makes CTools figure it out. Something along these lines:

  // If unset it wants a generic, unfilled context, which is just NULL
  if (empty($context->data)) {
    $context = ctools_context_create_empty('node');
    $context->restrictions['type'] = array('page', 'whatevertype');
    return $context;
  }

worked for me. Whether that's the kosher way to do it, only merlin knows (probably isn't).

+1 SUBSCRIBE is there any progress on this?

Upon further research I do believe this has been resolved... Closing.