Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
We'll need to follow-up w/ Jody on this, since she was down for the count during the meeting. I think TR, Jakob, and Mike expressed varying degrees of interest in this work, too. I'm obviously available since I wrote the bulk of it. This work should probably begin with Damien's patch, #548144: Refactor CA use of menu items and forms. This might be out of scope for now, but we'll also want to use the plugin system provided by Chaos Tools for this... but I don't know where the D7 port of that is.
My general thought are
1) update for d7, and the coding standards
2) add some additional drupal_alters, so it is a little more flexable.
3) make it ctools / features exportable
4) adjust the code so it load default predicates to the db so they can be placed in an include similar to hook_views_default_views
I'm wondering if we should make this into a [meta] issue that collects CA related tasks or simply turn this into a D7 update issue and then discuss / patch the alters, exportables, and tests in their own issues. Anyone have a preference?
Another sub-issue for conditional actions is documentation. It desperately needs a README for both admins and devs once most of the system is stable. Are there any online docs existing?
Comments
Comment #1
rszrama commentedWe'll need to follow-up w/ Jody on this, since she was down for the count during the meeting. I think TR, Jakob, and Mike expressed varying degrees of interest in this work, too. I'm obviously available since I wrote the bulk of it. This work should probably begin with Damien's patch, #548144: Refactor CA use of menu items and forms. This might be out of scope for now, but we'll also want to use the plugin system provided by Chaos Tools for this... but I don't know where the D7 port of that is.
Comment #2
damien tournoud commentedWe don't need the plugin system of ctools anymore. We have hook_hook_info() now!
Comment #3
rszrama commentedAwesome. : )
Comment #4
jody lynnMike's priorities he emailed me:
My general thought are
1) update for d7, and the coding standards
2) add some additional drupal_alters, so it is a little more flexable.
3) make it ctools / features exportable
4) adjust the code so it load default predicates to the db so they can be placed in an include similar to hook_views_default_views
I'm going to start with #1.
Comment #5
jody lynnAssigning to myself to get this started
Comment #6
jody lynnAlso: needs simpletests
Comment #7
rszrama commentedI'm wondering if we should make this into a [meta] issue that collects CA related tasks or simply turn this into a D7 update issue and then discuss / patch the alters, exportables, and tests in their own issues. Anyone have a preference?
Comment #8
jody lynnI opened up a child ticket for the D7 update at #639778: Port Conditional Actions to D7
Comment #9
jody lynnAnother sub-issue for conditional actions is documentation. It desperately needs a README for both admins and devs once most of the system is stable. Are there any online docs existing?
Comment #10
rszrama commentedYep, both afaik. Could certainly be better.
http://www.ubercart.org/docs/user/7657/configuring_conditional_actions
http://www.ubercart.org/docs/developer/9034/conditional_actions
Comment #11
jody lynnMike and I also want to rip CA into uc_ca.module and uc_ca_ui.module, so that's another sub-issue.
Comment #12
joelstein commentedWhat about using the Rules module instead of Conditional Actions?
Comment #13
jody lynn@joelstein: we're using drupalcommerce.org for planning and discussion
http://www.drupalcommerce.org/node/83
Comment #14
jdwfly commented+1 for ditching Conditional Actions for Rules.
Comment #15
servantleader commented+1 for using Rules
Comment #16
rszrama commentedThis has happened. My apologies to Jody are in the child issue. With fago on board, it just makes sense to pursue Rules moving forward.