Here's a patch to turn the order status into a multi-select field.
This is required because there are some orders that might have been paid for and requires that the order status should be automatically set to payment_received.
Another use case is to allow the rule to be applicable to more than one order status per rule evaluation. For example, there are two users making an order at the same time. User A's total order amount is $10 while user B's order is $0. I will want user B's order status to be automatically set to payment received on completion of the checkout process while user's A order status to be set to pending or completed.
With these cases, a single select field wouldn't be appropriate.
I hope someone finds this useful.
This was originally posted at http://drupal.org/node/336257#comment-5377406
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | uc_rules-multi-select-order-statuses-1376078-3.patch | 826 bytes | tinker |
| uc-rules-status-multiselect.jpg | 19.03 KB | drecute | |
| multi-select-field-for-order-statuses-#336257.patch | 826 bytes | drecute |
Comments
Comment #1
drecute commentedComment #2
tinker commented@drecute Thanks for making the effort to create a patch and I think this is a useful feature. Marking this reviewed and tested.
Please note that you should not use special characters such as "#" in uploaded file names as this makes the file unreachable without urlencoding the filename. To view your attached patch the following URL has to be used (note '#' converted to '%23'): http://drupal.org/files/multi-select-field-for-order-statuses-%23336257....
This is probably why the patch did not get reviewed earlier. Patch file names should be in the format [module_name]-[short-description]-[issue-number]-[post number].patch. Also when you provide a patch you can mark the status as 'needs review' and it will generally get a faster response.
Attached patch is the same as in opening post just renamed.