Using a Drupal API in the civicrm_searchTasks hook

[SarahG (FountainTribe)]

I am experimenting with a custom hook that implements the hook "civicrm_searchTasks".  Inside my hook implementation, I am calling the Drupal API for creating/updating a Drupal user

Code: [Select]

user_save( )
when the end-user executes my search action, they first see my page telling them how many contacts will be impacted (along with some explanation of what the consequences are.) After they click the "submit" button which calls my "postProcess" function, they end up on the Drupal home page.  If they click the link for "CiviCRM", then they are shown the status message from postProcess.   If I remove the Drupal API call, then the user stays on the appropriate CiviCRM screen as expected. ( ie they see the search results that they started on, along with the status message from postProcess. )

Any ideas on why the user ends up on the website homepage?

[totten]

Are you testing a clean/simple configuration or a customer's configuration? Perhaps there's another module or trigger that hooks into the user-signup or user-admin process?

(Aside: Reading https://api.drupal.org/api/drupal/modules!user!user.module/function/user_save/7 , there seem to be some situations where it destroys the session. That could definitely interfere with Civi's pageflow, but you'd expect to lose all the status messages -- and in this the status messages are retained for later.)

[SarahG (FountainTribe)]

I am testing my code in my personal development environment. There are some extra Drupal modules ( like Views, CCK, etc) but its pretty vanilla.