CiviCRM Community Forums (archive)

Interesting. Both of those errors appear to involve a statement like:

foreach (glob(...) as $file) { ... }

Evidently, the glob() call is not returning an array. According to the glob documentation ( http://php.net/glob ), this should return an array regardless of whether a file matches or not -- the only time it should return FALSE is when there's an "error" (not specified, but maybe a permission error or I/O error). However, there's this ambiguous caveat:

"On some systems it is impossible to distinguish between empty match and an error."

Which I guess means that we can't count on glob() to return an array in normal conditions.

Perhaps you could try changing _pruebaactivar_civix_civicrm_xmlMenu()  to one of these:

function _pruebaactivar_civix_civicrm_xmlMenu(&$files) {
  foreach ((array)glob(__DIR__ . '/xml/Menu/*.xml') as $file) {
    $files[] = $file;
  }
}

or

function _pruebaactivar_civix_civicrm_xmlMenu(&$files) {
  $glob = glob(__DIR__ . '/xml/Menu/*.xml');
  if (is_array($glob)) {
    foreach ($glob as $file) {
      $files[] = $file;
    }
  }
}

If that works, let me know so I can update the template used for new extensions.

Out of curiosity, what environment is this running under? (Based on the php.net/glob caveat and the file paths, it doesn't seem like a typical LAMP deployment.)

I've updated the template for '*.civix.php' to deal with variations in glob() behavior. It applies the fix to both spots (circa lines 34 and 118)

You can try replacing pruebaactivar.civix.php with the attached file (based on the new template). Alternatively, you can regenerate the file yourself:

1. Update civix (e.g. go to the civix dir and run "git pull")
2. Go the extension parent dir
3. Rerun "civix generate:module com.extension.pruebaactivar" . This should replace the pruebaactivar.civix.php, preserve the pruebaactivar.php, and safely touch the info.xml.