Error: The entities of type Taxonomy term do not define a valid base path: it will not be possible to translate them.

I tried a fresh install of the latest ET dev without seeing this error. Could you provide more details to help reproduce the problem?

I have the same problem after updating from 2012-02-13 dev version to 2012-05-29 dev version.

I tried on a fresh new install of the last drupal 7 with entity translation dev. I enabled taxonomy terms and comments for entity translation and I had the problem for comments :
The entities of type Comment do not define a valid base path: it will not be possible to translate them.

I get the same error when I install the 2012-05-29 dev version. What sort of details would be helpful for resolving this?

I have been able to reproduce this, not on a clean installation though. In my case it turns out that Views is replacing the taxonomy router path with a views-specific one, thus making the test for the base path existence fail. The attached patch seems to fix the issue. Please confirm.

Yes, it fixes the bug for entities comment error on my fresh new drupal site and for entities taxonomy for my other site using views for the terms page.

Thanks !

Ok, let's open this to wider testing.

Committed and pushed.

The bug still exists. Drupal 7.14, Entity translation 7.x-1.0-alpha2

See also Entities of type Commerce Coupon do not define a valid base path

I think, the basis of the problem is to configure the Entity translation module.
The configuration will list some of the available entity types. For example:

• Node
• Taxonomy term
• Commerce Coupon
• Commerce Delivery
• Commerce Product
• User
• Rules configuration

What is now, when a EntityType is not translatable by Entity translation?

A first consideration is to expand the description of Translatable entity types.

Select which entities can be translated.

This is obviously not enough for an good information.

Did you test the latest dev? Steps to reproduce it?

I have expanded #9.

OK, I'll test the dev release.

Taxonomy terms are translatable and a valid base path is provided by ET. Hence there is something that is altering either the ET-provided info (see entity_translation_translation_info()) or (more likely) the menu items data structure, through an implementation of hook_menu_alter().

Currently, Taxonomy translation is not the problem.

Other modules produce problems, such as Rules module.

Well, this is not a bug then. Simply Rules are problably not integrating correctly with ET. OTOH, I agree that the UI can be improved to be less misleading. To be fixed in a different issue.

Simply Rules are problably not integrating correctly with ET

How other modules implement the correct integration of ET?

It's all documented in the latest dev, see entity_translation.api.php.

See also #1114410: Replace hook_translation_info() with hook_entity_info(). The entity info is not changing but the hook in itself will go away.

You are sure that other modules do not have properly integrated ET?

Screenshot

No, I'm not, but this issue is about taxonomy terms and I'm sure they are supposed to work.

You're right. There is a problem of other modules.

In the meantime, I found a module with proper ET implementation: Commerce Product

Following code from a DC kickstart installation:

modules/product/commerce_product.module:

function commerce_product_entity_info() {
  ...
      // Add translation support.
      'translation' => array(
        'locale' => TRUE,
        'entity_translation' => array(
          'class' => 'EntityTranslationCommerceProductHandler',
        ),
      ),
  ...
}

modules/product/includes/commerce_product.translation_handler.inc

/**
 * Commerce Product translation handler.
 *
 * This class is registered in commerce_product.module using the translation
 * property the Entity Translation module uses via hook_entity_info().
 *
 * @see commerce_product_entity_info()
 */
class EntityTranslationCommerceProductHandler extends EntityTranslationDefaultHandler {

  public function __construct($entity_type, $entity_info, $entity, $entity_id) {
    parent::__construct('commerce_product', $entity_info, $entity, $entity_id);
  }

  /**
   * Indicates whether this commerce product is a revision or not.
   */
  public function isRevision() {
    return !empty($this->entity->revision);
  }

  /**
   * Returns the original language of the product.
   */
  public function getLanguage() {
    return $this->entity->language;
  }

  /**
   * Checks whether the current user has access to this product.
   */
  public function getAccess($op) {
    return commerce_product_access($op, $this->entity);
  }

  /**
   * Returns whether the product is active (TRUE) or disabled (FALSE).
   */
  protected function getStatus() {
    return (boolean) $this->entity->status;
  }
}

See screenshot from #18.

Commerce Product is in the list of translatable entity types, but not in the list of base path warnings.

I think, that's it.