Here's my battle plan:
1. Invoke events in Rules - what this patch does.
2. Create MODULE_NAME.rules.inc files for every MODULE_NAME.ca.inc
3. Create default configurations, like the predicate concept (the advantage is that there is the revert button, or you can define if use can or can't edit that rule).

There is another secret plan which I have, and it's to completely replace CA with Rules and then have a big party in no-duplicate-code club :)

p.s. can you add a component called Rules in "Issue settings"?

CommentFileSizeAuthor
ubercart_invoke_rules_event.patch597 bytesamitaibu

Comments

rszrama’s picture

rszrama commented
Status: Needs review » Postponed

This patch is part of the larger discussion going on in this thread. I don't think this patch is ready for review, because it's near worthless without any accompanying conditions/actions. I'm going to mark this postponed for core inclusion until we get past the 2.0 hurdle, but feel free to keep adding code here. It might be best to really nail down a good battle plan first.

rszrama’s picture

rszrama commented
Issue tags: +CA
Andy_Lowe’s picture

Andy_Lowe commented
Version: 6.x-2.x-dev » 7.x-3.x-dev
Priority: Normal » Minor
Status: Postponed » Active

Moving this to 3.x. The plan is to completely replace CA with Rules. As soon as that happens, we can close this and other CA related issues.

Bilmar’s picture

Bilmar commented

subscribing

Island Usurper’s picture

Island Usurper commented

Here's that issue #736770: Replace Conditional Actions with Rules Integration

Andy_Lowe’s picture

Andy_Lowe commented
Status: Active » Closed (won't fix)

Buh Bye CA.