Closed (fixed)
Project:
Domain
Version:
7.x-2.13
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Jun 2011 at 00:41 UTC
Updated:
7 Jul 2011 at 18:11 UTC
Jump to comment: Most recent file
The implementation of domain_content_node_operations() specifies that it is 'configurable'. This is a bug of some kind, although I'm not quite sure what. hook_node_operations() is not supposed to take the configurable flag at all, and even if it did, DA does not provide the callback function for the configuration form. So I'm guessing that the proper action to take here is to remove it entirely. See patch soon.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 1186580_configurable_node_operations.patch | 498 bytes | gdd |
| #1 | 1186580_configurable_node_operations.patch | 532 bytes | gdd |
Comments
Comment #1
gddSubmitted from 35,000 feet over Milwaukee!
Comment #2
gddDamnit wrong patch.
Comment #3
agentrickardI think that flag is for VBO / Rules, though we don't use it, because it was introduced either late in D6 or in D7. I think it could be supported properly now.
Comment #4
bojanz commentedJust a FYI, VBO no longer supports hook_node_operations() and hook_user_operations() in D7 (since alpha3).
Comment #5
agentrickardOK. In another module I used hook_action_info() to expose operations to VBO. Is that correct?
Is so, this patch is ready, and we can use hook_action_info() for VBO integration (which is a nice win).
Comment #6
bojanz commentedYes and Yes :)
Comment #7
agentrickardThx.
Comment #8
agentrickardFixed. VBO support spun off to #1198020: VBO support.