Hi,
I don't know exactly the cause, but it seems to be someting wrong between vocabindex and i18ntaxonomy
It has something to do with this function

function vocabindex_menu_alter(&$items) {
  $vis = vocabindex_vi_load(VOCABINDEX_VI_PAGE);
  foreach ($vis as $vi) {
    if ($vi->view == VOCABINDEX_VIEW_FLAT) {
      $item = &$items['taxonomy/term/%'];

      // Store the original configuration, so we can pass it on to our own
      // callback.
      $callback = $item['page callback'];
      $arguments = $item['page arguments'];
      $file = $item['file'];
      $filepath = isset($item['file path']) ? $item['file path'] : drupal_get_path('module', $item['module']);

      // Alter the original callback.
      $item['page callback'] = 'vocabindex_term_page';
      $item['page arguments'] = array_merge(array(2, $callback, $file, $filepath), $arguments);
      $item['file'] = 'vocabindex.module';
      $item['file path'] = drupal_get_path('module', 'vocabindex');
      break;
    }
  }
}

specialy at this line :
$item['file path'] = drupal_get_path('module', 'vocabindex');

When both modules are activated, and I click on a term link, I get this error
Fatal error: require_once() [function.require]: Failed opening required 'sites/all/modules/vocabindex/i18ntaxonomy.pages.inc' (include_path='.:/usr/local/lib/php') in /home/web/www/drupal/includes/menu.inc on line 346

For the moment, as a workaround, I've just commented the entire vocabindex_menu_alter function.

Comments

xano’s picture

This seems like a conflict and a bug. The conflict is that both module want to work with the same path, which is technically impossible. The bug is that i18n alters the settings for that particular path, but it doesn't do it properly. This is why Drupal wants to load an i18n include file from Vocabulary Index's module folder.

mtundu2’s picture

Any resolution to this problem? I just installed the translation module and am getting the same error.

colan’s picture

The weight of this module (0) needs to be greater than i18ntaxonomy (5), but it isn't. Other modules that rely on i18ntaxonomy are having the same problem. It can be set manually in the DB, but let's roll a patch that does the update. In case I don't get a chance to throw one myself, here's an example from i18n itself:

88	 /**
89	  * Set module weight for it to run after core modules, but before views.
90	  */
91	function i18ntaxonomy_update_6002() {
92	  $items = array();
93	  $items[] = update_sql("UPDATE {system} SET weight = 5 WHERE name = 'i18ntaxonomy' AND type = 'module'");
94	  return $items;
95	}
colan’s picture

jpmckinney’s picture

Status: Active » Closed (duplicate)