On 2 Sites after activating this module I got the message:
Warning: Cannot modify header information - headers already sent by (output started at .... /includes/common.inc:2608) in drupal_goto() (Zeile 685 von .... /includes/common.inc).
This occurs calling ... /admin/reports/updates after some days without an update inquiry.

Comments

Morn’s picture

Morn commented

More Infos:
The Warning occurs also after logout/login, the IP-Adress is the same as the user doing this login, but
the dblog user is anonymous shown, so it comes from a cron job triggered by this or a similar action.

mlee11111’s picture

mlee11111 commented

Morn,

I had the same issues so I started to dig through the code. It appears to be coming from:
elysia_cron.module > elysia_cron_cron()

From what I can tell, this is happening:

Drupal Cron (based off of Poormanscron) runs every x hours.
This is in your cron config: /admin/config/system/cron/settings > Installation Settings > "Run cron on visitor's requests, every" setting.

On /admin/* pages, Drupal Cron calls elysia_cron_cron if it's due for a run (this is the culprit for the error above, the ajax error notice)

If your site is like mine, the default cron takes forever because of too many cron hooks, so the default Drupal cron times out (which is why I switched to Elysia). As a result, the variable cron_last is never set so any hit to the admin page was triggering a cron attempt.

If you set "Run cron on visitor's requests, every" to "Never/...", this should short circuit poormanscron and let elysia do it's job. The default hook_cron will never be called.

Hope this helps

Morn’s picture

Morn commented
Status: Active » Closed (fixed)

Yes, deactivating Drupal cron (Poormanscron, not needed when "external" cron is active) works