This seems a bizarre default. It completely overrides the CCK "manage fields" order.

Hacking or patching Rubik's template.php is out - my client does not want contrib patched. This workaround may prove useful to others in a similar situation. In a module:

/**
 * Implementation of hook_theme().
 */
function mymodule_theme() {
  $items = array();

  $items['node_form'] = array(
    'arguments' => array('form' => array()),
    'path' => drupal_get_path('theme', 'rubik') .'/templates',
    'template' => 'form-default',
    'preprocess functions' => array(
      'mymodule_preprocess_form_node',
    ),
  );

  return $items;
}

/**
 * Implementation of hook_preprocess_form_node().
 */
function mymodule_preprocess_form_node(&$vars) {
   if (isset($vars['form']['taxonomy'])) {
    // prevent rubik moving taxonomy to the sidebar
    $vars['form']['taxonomies'] = $vars['form']['taxonomy'];
    unset ($vars['form']['taxonomy']);
  }
}

But a UI in Rubik's theme settings to control what can or can't go in the sidebar might be a more forward-looking approach?

Comments

jrstmartin’s picture

jrstmartin commented

+1. Hella bizarre.

alanom’s picture

alanom commented

Another +1.

Personally, I love having the taxonomy in the side bar on the right - in my case, it makes sense from a usability point of view, where fields on the left are the content and settings of this node itself, and taxonomy on the right is how the node fits into the site as a whole. **BUT** this is a decision that should be in the hands of site builders, as it'll vary from site to site.

For my site, it makes sense to have not only taxonomy but also node reference forms in the "column-side" element: content on the left, relationships with other content on the right. Others will have different needs.

alanom’s picture

alanom commented

Actually, after a lot of trial and error and very heavy google abuse following seemingly unrelated threads, there is a way to get all this and more in the UI.

- Make sure you're using the latest version of Rubik (dev version works for me)
- Install Node Form Columns ( http://drupal.org/project/nodeformcols ) - a UI designed to control where form fields go exactly as desired here. Latest (dev) version is advised.
- If you're using Vertical Tabs, update it to latest (dev) version, and change the settings to maximise fine control: "Include new fieldsets in vertical tabs by default" off, and "Expose vertical tabs selection on the edit content type forms" on.
- Manually set where you want everything to go for each content type using Node Form Columns UI (and also Vertical Tabs UI if installed).

Juan C’s picture

Juan C commented

@ #3. Thanks for the info.

aramboyajyan’s picture

aramboyajyan commented
Issue summary: View changes
Status: Active » Closed (won't fix)

All old and outdated 6.x issues are being closed.
Maintainer support will be provided only for major / blocking issues.

If you feel like this issue should be re-opened, feel free to do so.

Thanks!