Load Multiple Nodes to perform actions on them

I believe with the custom php action, I was able to do this without changing anything in the rules project.

Here is my example php rule:

<?php
  $view = views_get_view('children_of_parent', TRUE);

  if (is_object($view)) {
    $view->set_display('default');
    $view->set_arguments(array($node->nid));
    $view->render();

    foreach ($view->result as $result) {
      $current_node = node_load($result->nid);
      $actions = array('node_publish_action', 'node_save_action');
      $context['node'] = $current_node;
      actions_do($actions, $current_node, $context, NULL, NULL);
    }
  }
?>

mitchell, I have looked at the support for looping and data lists, but the current test code had some issues and I was in need of something working asap.

"How would you like to proceed with this?"
The code can work as is without modifying the Rules source code.
This way you do not have to change the stable series, just supply an example "custom php code" for this situation.

For the development branch, perhaps something like how you have "load content by id" there could be "load view by view name".
Then allow actions be performed on each node found within that view.
This would probably need to extend to the different types of views, such as: users, files, terms, etc..

patchak, There are three places I am able to use the given php code without changing any code of the rules module.
contemplate, the views theming, and the "Execute custom PHP code" action supplied in the latest rules version.

--

Here is a simplified version of what I am using this for:
I have two node types: An Offer and a Bid.

The Offer is made by a drupal user.
The Bid is made by anonymous who sends an id, e-mail, and other contact information.
The drupal user who owns the author is not authorized in any way to edit any of the Bids.

When the drupal user publishes, unpublishes, or even changes workflow of the Offer, all of the Bids need to also be updated.
As the drupal user cannot change the worflow or publishing settings of the Bid, the job gets handed over to the Rules module.

When the bidder makes a Bid, they select the Offer they want, through a node reference CCK field.
The view I created will then load all Bids associated with some Offer by the Offer's nid and that node reference CCK field.
Then the php code above will load the view and process all associated Bids.

--

There was another issue or two that I came across with my original php code I presented above.
1) I didn't check to see if $view->result was empty.
2) The content type "File" as supplied by the File Framework module does not get associated through the node reference but is attached via another means that I have no direct control over.

I had to add another loop to handle attached files:

<?php
  $view = views_get_view('children_of_parent', TRUE);

  if (is_object($view)) {
    $view->set_display('default');
    $view->set_arguments(array($node->nid));
    $view->render();

    if ($view->result){ // bug fix of above example
      foreach ($view->result as $result) {
        $current_node = node_load($result->nid);
        $actions = array('node_publish_action', 'node_save_action');
        $context['node'] = $current_node;
        actions_do($actions, $current_node, $context, NULL, NULL);

        // handle all file attachments, for each child node
        if ($current_node->files){
          foreach($current_node->files as $file_result){
            $file_node = node_load($file_result->nid);
            $actions = array('node_publish_action', 'node_save_action');
            $context['node'] = $file_node;
            actions_do($actions, $file_node, $context, NULL, NULL);
          }
        }
      }
    }
  }
?>

Edit:
The file attachment issue suggests that recursion may need to be supported.
I take that back, there probably won't need to be any recursion as you can get views to grab just about any node you need and add them to the list.

If a node cannot be grabbed, then I suspect it would be a Views issue and not a Rules issue.
My extra code to handle the file attachments for each child node would probably be an issue for me to take up with Views.
This would then allow for the Rules implementation to be very simple.

In regards to #6.

I think that making arguments and variables available would need to be created by the Rules team.
I think that is what is being explained in #7.

In regards to #8.

The above php uses the custom php action, which is self-contained. If it were to return something, it would end up in the middle of nowhere.
(of course, if the code referenced by #7 were completed, this could be possible).

Instead of returning the array, try calling a function or triggering a rule.
Is it possible to explicitly call or trigger a rule from within this custom php action?

To get the array of node id's, I believe the <?php $view->result ?> contains what you need.
If you want to have just an array of node id's, then use the foreach function I have above to create the array.

Once you have that array, just do a function call on that array, if you can call your function here.

Here is an example with using a view called 'some_collection_of_nodes', passing no arguments to it.

<?php
  $my_array_of_nids = array();
  $view = views_get_view('some_collection_of_nodes', TRUE);

  if (is_object($view)) {
    $view->set_display('default');
    $view->render();

    if ($view->result){
      foreach ($view->result as $result) {
        array_push($my_array_of_nids, $result->nid);
      }
    }
  }

  my_function_call($my_array_of_nids);
?>

The last action is to call your function or trigger your rule with the generated array of nids.

I have a correction to my example code above.

Where I have something like:

  $file_node = node_load($file_result->nid);
  $actions = array('node_publish_action', 'node_save_action');
  $context['node'] = $file_node;
  actions_do($actions, $file_node, $context, NULL, NULL);

All code calling the node returned by node_load() MUST be wrapped in an if node exists like below:

  $file_node = node_load($file_result->nid);
  if ($file_node){
    $actions = array('node_publish_action', 'node_save_action');
    $context['node'] = $file_node;
    actions_do($actions, $file_node, $context, NULL, NULL);
  }

There were problems with views somehow returning non-existent nodes and actions_do() partially creating them causing some weirdness in the system.
Wrapping in an if exists avoids the issue.

Always check to see if the node exists before performing an actions_do operation because actions_do does not seem to perform this check.

Here is another Change to my example code.

Apparently calling $view->render(); limits itself to 10 items max.
The more appropriate function call seems to instead be: $view->execute_display();
This function seems to allow one to get ALL the items in the view that are allowed based on the items per page view setting.
If you need to get an unlimited or a limited number, just remember to set the items per page view setting accordingly.

I am wondering if #14 is still valid or am I expected to start looking into #16?

I have also noticed considerable changes in views since this thread was last posted to.
Has support for this already been provided?