G'Day all,

We love Biblio and usually hook it up with some additional CCK fields to help integrate biblio listings with the rest of the site's information structure.

In a D6.22 environment with vertical tabs (via Rubik theme) on the node edit form, we get a bit confused. This may not be a Biblio issue at all, so apologies in advance.

We use the CCK node type interface to create a field group and park all the extended fields inside it. Then we push the field group to the top of the field order and save.

But on the Biblio edit form, this field group is weighted amongst all the biblio native fields.

Instead, I'd like to have the fieldgroup pushed over to a separate vertical tab, so it is clearly outside the flow of Biblio fields.

How can this be done?

Cheers,

JB

CommentFileSizeAuthor
#6 Rubik_side_column.png80.4 KBrjerome
#5 cck-group-config.png12.36 KBrjerome
#5 cck-group-vtab.png16.82 KBrjerome
#4 biblio_edit-bartik.png108.2 KBboabjohn

Comments

boabjohn’s picture

boabjohn commented

Just a quick ping...is this really a matter for themeing? Is there something quite obvious I'm missing?

Thanks in advance!

rjerome’s picture

rjerome commented

I think a tighter (hook_content_extra_fields) integration between CCK and Biblio would be required to make this happen. I haven't really look into this in detail yet, so I don't know how big a deal that is.

Ron.

rjerome’s picture

rjerome commented
Status: Active » Fixed

Turns out this wasn't such a big deal. I've pushed the changes to the 6.x-2.x branch that should resolve this issue.

http://drupalcode.org/project/biblio.git/commit/70a911c

Ron.

boabjohn’s picture

boabjohn commented
StatusFileSize
new biblio_edit-bartik.png108.2 KB

Howdy Ron,

I might have missed the upgrade somehow, but it still looks same as before except that the biblio fields are now nicely sortable in the CCK Manage Fields admin screen.

Perhaps I'm just confused an am expecting something out of Biblio that is really the business of other modules or the theme...

Attached is a screenshot of what I'm seeing, with 3 main queries:

1. Why aren't the CCK field groups rendering as collapsible elements like your Biblio groupss are?
2. How is it that the optional Vocab selector is positioned on the right (sidebar)?
3. Is it possible to get the CCK field groups into that region as well, to produce a "vertical tabs" style layout?

Thanks hugely for your generosity and enthusiasm!

rjerome’s picture

rjerome commented
StatusFileSize
new cck-group-vtab.png16.82 KB
new cck-group-config.png12.36 KB

This may be asking the obvious but... I presume the you have checked the CCK group settings (see attached)?

Certainly you can configure CCK groups to be vtabs (the last tab "test" in the second image is a CCK group).

I've installed the Rubik theme and it would appear that moving (arbitrary) form elements to the right column would require some theme pre-processing.

rjerome’s picture

rjerome commented
StatusFileSize
new Rubik_side_column.png80.4 KB

Attached is a view of the Biblio input form with all the vtabs moved to the right column (with a little tweak of the rubik template.php file)

Is that what you were looking for?

boabjohn’s picture

boabjohn commented

Hey Ron that is so great! Exactly what we needed. What was the "little tweak" to rubik?

rjerome’s picture

rjerome commented

Right after line 233 in sites/all/themes/rubik/template.php insert...

(Note: you might notice references to a module called "nodeformcols", which in theory does exactly what you want to do, but I tried it with no success, so the hack below is probably you best short term approach)

    if ($vars['form']['type']['#value'] == 'biblio' && $vars['form']['biblio_type']['#value'] > 0) {
      foreach(element_children($vars['form']) as $key) {
        if(isset($vars['form'][$key]['#group'])) {
          $vars['sidebar'][$key] = $vars['form'][$key];
          unset($vars['form'][$key]);
        }
      }
      $vars['sidebar']['vertical_tabs'] = $vars['form']['vertical_tabs'];
      unset($vars['form']['vertical_tabs']);
    }

For context, the entire rubik_preprocess_form_node() function is as follows...

function rubik_preprocess_form_node(&$vars) {
  $vars['sidebar'] = isset($vars['sidebar']) ? $vars['sidebar'] : array();
  // Support nodeformcols if present.
  if (module_exists('nodeformcols')) {
    $map = array(
      'nodeformcols_region_right' => 'sidebar',
      'nodeformcols_region_footer' => 'footer',
      'nodeformcols_region_main' => NULL,
    );
    foreach ($map as $region => $target) {
      if (isset($vars['form'][$region])) {
        if (isset($vars['form'][$region]['#prefix'], $vars['form'][$region]['#suffix'])) {
          unset($vars['form'][$region]['#prefix']);
          unset($vars['form'][$region]['#suffix']);
        }
        if (isset($vars['form'][$region]['buttons'], $vars['form'][$region]['buttons'])) {
          $vars['buttons'] = $vars['form'][$region]['buttons'];
          unset($vars['form'][$region]['buttons']);
        }
        if (isset($target)) {
          $vars[$target] = $vars['form'][$region];
          unset($vars['form'][$region]);
        }
      }
    }
  }
  // Default to showing taxonomy in sidebar if nodeformcols is not present.
  elseif (isset($vars['form']['taxonomy'])) {
    $vars['sidebar']['taxonomy'] = $vars['form']['taxonomy'];
    unset($vars['form']['taxonomy']);
    if ($vars['form']['type']['#value'] == 'biblio' && $vars['form']['biblio_type']['#value'] > 0) {
      foreach(element_children($vars['form']) as $key) {
        if(isset($vars['form'][$key]['#group'])) {
          $vars['sidebar'][$key] = $vars['form'][$key];
          unset($vars['form'][$key]);
        }
      }
      $vars['sidebar']['vertical_tabs'] = $vars['form']['vertical_tabs'];
      unset($vars['form']['vertical_tabs']);
    }
  }
}

Status: Fixed » Closed (fixed)

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