CiviCRM Community Forums (archive)

UPDATE: see Reply #2 for an analysis of this serious problem

I'm using the CiviMobile extension and a Drupal module that implements the CiviCRM alterMailParams() hook. I use cli.php to invoke the Scheduled Mailing job. I'm using CiviCRM 4.2.2.

Normally, when I send a CivMail mailing, the alterMailParams() hook gets called, as one would expect.

If I enable CiviMobile, the hook is not invoked. The problem only occurs for cli.php: it all works as expected when I run the Scheduled Mailing job from within CiviCRM's administrator menu.

This suggests some interplay between cli.php, the Extension mechanism, and the Hook mechanism. (CiviMobile and my module are both simple implementations, so I doubt the issue is there.)

As I dig into this, does anyone know of similar issues?

Thanks!

Ken

Enabling any Extension will stop cli.php from invoking any CiviCRM Hooks implemented by modules. If no Extensions are enabled, Hooks are invoked correctly.

This happens since cli.php runs CiviCRM code before the CMS is bootstrapped.

Thus, civicrm_cli::_bootstrap() makes the following calls ...

• CRM_Core_Config::singleton()
• CRM_Utils_System::loadBootstrap()

The first call invokes the Config hook. The second call bootstraps the CMS. The problem is that the Config hook assumes the CMS has already been bootstrapped ...

• The Config hook calls CRM_Utils_Hook_Drupal::invoke() (I assume the hooks in other CMS's behave similarly)
• The logic of invoke() is: if this is the first call to invoke(), or if the list of all modules is empty, build a list of modules from the CMS and from the CiviCRM extensions
• Since the CMS has not yet bootstrapped, the list is built , but only contains the enabled CiviCRM extensions
• This means that subsequent hook calls will only look for hook implementations among the extensions and not the CMS modules

If no Extensions are enabled, the problem is masked, because the next call to invoke() will find the module list empty, and it will build the list of modules including the CMS modules.

Cool. I don't need to write a patch now.

Is this going to be an issue for the other CMS's? A cursory glance suggets Joomla and WordPress are fine, but Drupal6 will need the same fix.