Operations are now defined hook_entity_operation_info() instead of hook_entity_info().

Entity operations are no longer defined in hook_entity_info().

Instead, modules should implement hook_entity_operation_info().

The 'operations' array should be removed from hook_entity_info(), and adapted for the new hook. The structure of this is slightly different: see the api file for details.

The following properties remain in hook_entity_info():

 *  -'operations ui': An array containing the following properties:
 *    - 'controller class' (optional) The name of a class to use as a controller
 *      for the operations system. Defaults to
 *      EntityOperationsDefaultUIController.
 *    - 'path': The base path for an entity. This should not include the
 *      wildcard or the trailing slash. For example, for nodes this would
 *      be 'node'.
 *      Note that to avoid duplication of logic here and in the entity's URI
 *      callback, the 'entity uri' property may be set to the generic callback
 *      entity_operations_entity_uri(), which makes use of this base path.
 *    - 'menu wildcard': (optional) A menu wildcard for loading the entity. This
 *      defaults to '%entity_object', which should be suitable in most cases.
 *      If set, should be of the form '%foo' where foo_load() is a menu loader
 *      function. For example, for nodes this would be '%node'.