Avoid use of drupal_goto()

The information you might need though is that drupal_goto() terminates the request (see drupal_goto - we make sure none of the code below the drupal_goto() call gets executed upon redirection).

If this function is used in a Rules Action, then the UI will permit people to add actions following the action that contains a drupal_goto, but those actions will never be executed. Neither will any other behaviour attached to the page at a later point than the rule, which means this implementation permits a range of unexpected outcomes.

Probably more robust would be to use rules_action_drupal_goto() in place of drupal_goto(), as it contains code to handle this specific concern.

PR @ https://github.com/eileenmcnaughton/civicrm_entity/pull/129

Untested :)

Patch @ https://github.com/eileenmcnaughton/civicrm_entity/pull/129.patch updated, forgot to upload here!

This addresses the Rules dependency in previous approach by wrapping the Rules function in a wrapper which will use drupal_goto in the event that Rules isn't available.