Webform_ab module and cron errors

Webform core doesn't do anything on cron runs, so I doubt Webform itself is responsible for the problem. Its hard to say where this problem could be originating.

webform_ab doesn't do anything on cron either. I haven't had any issues like this on sites that I've used it on, but it's entirely possible that it's trying to redirect to one of the webforms in the A/B test when something happens in the cron process.

You mention a redirect error from another action: could you provide more info on that? Could you also list any other contrib modules that you have enabled? It's possible that one of them is doing something weird on cron.

I was getting the same cron error, so I did a little investigating and found that it was happening anytime a webform_ab node was being indexed by search.

A little more digging and I discovered that when a node is indexed, there is an eventual call to webform_ab_node_view($node, FALSE, FALSE), and it was the double-false case that was not being handled correctly.

The original flow of webform_ab_node_view() reads like:

if ($teaser) {
  // don't do any drupal_goto() calls
}
else {
  // drupal_goto()
}

I'm attaching a patch that changes the flow to read like:

if ($teaser) {
  // don't do any drupal_goto() calls
}
elseif ($page) { // <--
  // drupal_goto()
}

This allowed cron (and search indexing) to complete successfully.

FWIW, I only ever had cron failure when cron was run via drush cron. Running it via the cron.php script, cron ran successfully. I'm pretty baffled by that, honestly.

benclark's patch from #9 has been committed. 6.x-2.2 will be available shortly.

I would be pretty surprised if that was related. Does the error go away if you switch back to 6.x-2.1 (and change nothing else)?

Have you been able to replicate the bug by creating a new Webform AB node since? Perhaps you could open a new issue with more details?

I'm not sure of a good way to debug cron, and I'm not yet convinced that this error from the taxonomy module is related to Webform A/B. You could put in an error_log() call in taxonomy.module right before line 1293, and have it print out the variable that it's trying to loop over (and maybe some other relevant variables) to determine what value or node is failing there.

There hasn't been much follow up on this since it was last reported. If this if still an issue, plz update to the latest version of code and open a new ticket. I'll be glad to take a look at that time.