A little part of the code inside iframe module is creating conflicts on Drush and Features modules.

The problem is better explained on Drush issue queue (http://drupal.org/node/999894).

When I try to enable iframe using Drush, I get:

$ sudo drush en iframe
Module iframe doesn't meet the requirements to be enabled.                                              [error]
CCK module "content" required.                                                                                             [error]
The following extensions will be enabled: content
Do you really want to continue? (y/n): y
content was enabled successfully.                                                                                           [ok]
An error occurred at function : drush_pm_enable                                                                   [error]

As greg.1.anderson said in Drush issue queue, the problematic code inside iframes is:

function iframe_requirements($phase) {
  $requirements = array();
  // Ensure translations don't break at install time
  $t = get_t();
  if (!module_exists('content') || !function_exists('content_notify')) {
    $requirements['iframe'] = array(
      'title' => $t('CCK needed'),
      'description' => $t("CCK module \"content\" required."),
      'severity' => REQUIREMENT_ERROR,
    );
  }
  return $requirements;
}

We would expect that it would not be necessary for iframe to test module_exists('content'), since it also has this in iframe.info:

dependencies[] = content

Since this code is breaking Drush and Features modules, seems it would be better to remove it.

Thanks

Comments

neffets’s picture

Assigned: Unassigned » neffets
Status: Active » Fixed

You are right.
I removed the requirements function, it is not really needed.
Checked in cvs.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.