Installing taxonomy module after this module causes a fatal.

We are having an issue where if you install the taxonomy module after installing this module, it causes a fatal that says.

 PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'cedi.taxonomy_vocabulary' doesn't exist: SELECT name, machine_name, vid FROM {taxonomy_vocabulary}; Array ( ) in taxonomy_vocabulary_get_names() (line 991 of /var/www/cedi/docroot/modules/taxonomy/taxonomy.module).

After debugging, this problem, we identified that the problem exists in the feeds/feeds.plugins.inc file where you are calling entity_get_info() which causes major errors when installing other modules.

After debugging, it was determined what is actually happening is a race condition where the taxonomy modules schema is not installed when this function is called, but registers as an enabled module thus calling the taxonomy's function taxonomy_entity_info() before it's schema is installed.

This happens because of the nature of how module_enable() works. When you call this function, it goes through the following process...

      system_list_reset();
      module_list(TRUE);
      module_implements('', FALSE, TRUE);
      _system_update_bootstrap_status();
      registry_update();
      drupal_get_schema(NULL, TRUE);
      drupal_theme_rebuild();
      entity_info_cache_clear();
      drupal_install_schema($module);

The CTools plugin handler is actually rebuilt during the 'registry update' section... However, the schema of a module doesn't get installed until after that... Like so...

      ...
      module_list(TRUE);  <----- (a)
      ...
      ...
      registry_update();    <----- (b)
      ...
      ...
      drupal_install_schema($module); <----- (c)

• (a) - Module is flagged as 'enabled' so 'module_exists' for this module will now return TRUE.
• (b) - This is what calls ctools_get_plugins, which you guys then call entity_get_info() which then calls taxonomy_entity_info which assumes schema is installed and fatals when it is not.
• (c) - This is where the schema is actually installed.

So, with that said... I believe we have an issue with the latest version of this file where entity_get_info was called.

I will try to work out a patch for the fix, but may need some help from the person who introduced this change.