By dbourrion on

Hi.

We're using a rules ( using php with curl to save the result of a view) that should only start when a content is update or created, on that content.

The things is that, each time cron runs, that rules begins to work (??), executing the php code really slowly and on apparently random nodes.

Can't understand why.

Any help welcome.
D

PS : after asking Rules to log error, got :

Warning : Cannot modify header information - headers already sent by (output started at /var/www/html/dune/includes/common.inc:2681) dans drupal_send_headers() (ligne 1216 dans /var/www/html/dune/includes/bootstrap.inc).

Warning : session_start(): Cannot send session cookie - headers already sent by (output started at /var/www/html/dune/includes/common.inc:2681) dans drupal_session_start() (ligne 287 dans /var/www/html/dune/includes/session.inc).

Warning : session_start(): Cannot send session cache limiter - headers already sent (output started at /var/www/html/dune/includes/common.inc:2681) dans drupal_session_start() (ligne 287 dans /var/www/html/dune/includes/session.inc).

⋅ Categories: Drupal 7.x

Comments

rstaylor’s picture

rstaylor commented

What other cron hooks are running? Anything that might programmatically modify a node? Are there any modules that use hooks to update a node when it is rendered?

In the past, I've seen strange things happen because code was written to do something on node load or render, and the author expected it to only happen during a page view, and didn't take into account the effects of that code running when search loads and renders nodes during cron to index them.