I believe* this is a bug report.
What was working fine before no longer works for me the moment I added in the domain module to manage multiple domains.

I set up a VBO to invoke a delete on all nodes referenced to a parent node. When the author of the parent nodes deletes this node, all nodes of a particular node type referenced to this parent node is deleted.

I don't believe this is a node access problem that the domain module has set up but I could very well be wrong.
I hope this is clear.

Thanks for any feedback or response.

Comments

fallsemo’s picture

StatusFileSize
new7.29 KB

I should include the view used :)
See attached.

I am executing the rule when the parent node is deleted and passing return array('1'); in the view arguments

infojunkie’s picture

Version: 6.x-1.9 » 6.x-1.x-dev
Priority: Critical » Normal

Can you try the latest dev please? I recently fixed an issue with VBO + Rules integration.

fallsemo’s picture

StatusFileSize
new80.29 KB

Hmm.. this still does not work using the latest dev release. And to confirm, I am rebuilding the rule.
The difference I see in this version is that the operation type now shows me the operation from the drop down where it hadn't before (I have one: Delete node (see attached))

This is however working for me as user 1 so I imagine it must be some node access or permission thing that Domain access has introduced.

infojunkie’s picture

Thanks for trying the latest dev. Can you please check the recent log entries? VBO usually reports permission errors over there.

fallsemo’s picture

Thanks for fast response. My hands are cupping my face and and shaking my head for not checking this :)

This is what the log is returning for those users:
Invalid argument supplied for foreach() in /sites/all/modules/contrib/views_bulk_operations/views_bulk_operations.module on line 760

Should I be returning a different argument from the configuration screen in Rules?

return array("1"); ??

infojunkie’s picture

It seems that the node selection is lost. I don't think it has anything to do with the VBO action per se. Actually, can you confirm that the stock VBO (admin/content/node2) works for non-admin users?

fallsemo’s picture

Thanks again for the response!

I can confirm this works for non-admin users when I change access of node2 to Unrestricted.

infojunkie’s picture

How about your own view, that's failing when invoked from a rule? Does it work when you access it from a page for example?

I'm not familiar with the Domain module. Can you explain how you set it up, to help me reproduce this locally?

fallsemo’s picture

Yeah, this is working in my own view when a non-admin access's it as a page.

It was working before so I assume it does have something to do with Domain access.
Its a little timely to set up but the documentation on the module is fantastic.

To get started quickly, include this line in your settings.php:

/**
 * Add the domain module setup routine.
 */
include './sites/all/modules/domain/settings.inc';

(you may need to change your path of course)

And THEN (and only then) enable the main module.
That should be enough. Hopefully there's no need to configure domain zones.

To note I am using Domain Access Advanced but this may not be necessary to test

bojanz’s picture

Status: Active » Postponed (maintainer needs more info)

Is this still an issue with latest VBO (6.x-1.x-dev)?

bojanz’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

No reply in 40 days.