Calling VBO from Rule triggered by "After saving new content" returns an empty view.

Following your instructions, I used the following code for my custom action:

$team_nid = $context['view']['arguments']['0']; // get the Team NID
$node = node_load($team_nid); // load the Team node
dsm($node);

Result: the node DID NOT appear in my site's message box when the Rule was triggered by "After saving new content" but, as I suspected, it DID appear when the same rule was triggered by "After updating existing content."

I don't think it's *necessarily* an issue with Rules itself because I CAN display the newly created node's NID using a message action within the rule itself. I'm willing and able to test this further if you can suggest what I might look at next.

sorry, i am in fact using the dev version. I'll try and get those screenshots out. what exactly do you want to see as far as the configurations go?

Sorry for the 40-day delay in my response. In my previous posts I was using the dev version from September 2010. I've since updated to the latest dev and the problem still persists. I have attached the screen shots of my Rule and View. I am also including some php code of the custom Action that I want to call with VBO.

NOTES:
1. remember this does work on existing content, but does not work on new content.
2. the custom Action, "Spit out the node to DSM," that you see checked at the bottom of "ViewStyle.jpg" is the code from #2 above and it too does work on existing content, but not on new content.
3. the "Team" content type mentioned above will hereafter be called "Band" (as you will see in the screen shots).

// Variables used by my custom action - "Subscribe OG Original Members to band and notify them"

$band_nid = $context['view']['arguments']['0']; // get the Band NID
$original_member_uid = $context['row']->users_node_data_field_original_members_uid; // get the UID

global $base_url;
$siteName = variable_get('site_name', '');
$defaultEmail = variable_get('site_mail', '');
);

Please feel free to ask questions. I promise to respond and test promptly. I would love to figure out why the NID of New content is not available to my VBO actions.

Excellent, it worked! thanks!

Looks like i spoke too soon. This ONLY appears to work for the Superuser account.

I've enabled the Actions permissions module and gave permission to the appropriate role (in this case my own "Owner" role) to execute the action i created. Unfortunately when logged in as an "Owner" the results are the same as I have described above: It does execute on EXISTING content but not on NEW content.

Again, it works properly when logged in as superuser. I tried creating a different type of Action "Display a message to the user..." thinking that it might be a factor, but it still does not work for non-superusers creating new content.

Any clues how i can test this further?

No it does not work correctly for NEW content with actions_permissions disabled. The Rule itself fires but the call to the VBO action does not execute. I don't even see the expected PHP execute error:

An attempt to execute arbitrary PHP script action by user xxxx was blocked because of lack of permission.

I tested 3 scenarios with my non-superuser role on both NEW and EXISTING content:

1: actions_permissions disabled
NEW: Rule fires, VBO action does not fire, no error msg
EXISTING: Rule fires, VBO action fires w/ PHP error msg (above) as expected

2: actions_permissions enabled, execute perms granted:
NEW: Rule fires, VBO action does not fire, no error msg
EXISTING: Rule fires, VBO action fires as expected

3: actions_permissions enabled, execute perms NOT granted
NEW: Rule fires, VBO action does not fire, no error msg
EXISTING: Rule fires, VBO action does not fire, no error msg

This does work for my "Owner" role when that role is granted the "Administer Nodes" permission.

I'm going to take a look at your code. Any suggestions on what variables/functions/files I might pay special attention to?

Ok this could mean something... The logging system shows that an error occurs (actually it appears twice) right before a new Band node is created by a user with the "Owner" role. This is the error:

Type: views_bulk_opera
Message: No results for view xx.
Severity: warning

Ok, the error does not appear when the same user is granted the "Administer Nodes" permission (as i suspected). So in this case the view has results and the VBO fires, which makes no sense to me.

I don't know enough about vbo/views architecture to make an educated guess at what might be happening. Perhaps its a timing issue between VBO and views. After all, the watchdog error message is delivered by VBO (line 46 of views_bulk_operations.module)

I'm not sure what to look at next.