Closed (won't fix)
Project:
Commerce Message
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
14 Nov 2013 at 11:41 UTC
Updated:
4 Feb 2015 at 13:54 UTC
Jump to comment: Most recent
Comments
Comment #1
thim commentedThe rule log reports the following error: Unable to load variable commerce_order_unchanged, aborting.
0.697 ms The condition data_is evaluated to FALSE [edit]
0.72 ms AND evaluated to FALSE.
0.771 ms Evaluating conditions of rule Commerce order message: changing status. [edit]
1.202 ms Unable to load variable commerce_order_unchanged, aborting.
34.674 ms Unable to evaluate condition data_is. [edit]
Comment #2
thim commentedPS: using Rules 7.x-2.3
It seems to be linked to the "commerce-order-unchanged:status"
It's not part of the order entity?
Comment #3
rszrama commentedComment #4
jsacksick commentedThe rule belongs to Commerce Message, so moving the issue there.
Comment #5
jsacksick commentedIt happened to me lately, it was due to multiple rules reacting to the "After updating a commerce order" event, adjusting the weights did the trick...
Comment #6
Christopher Riley commentedWhat weight did you adjust it to if I may ask. I am running into a similar issue and the only things that are triggering off of "After updating an existing commerce order" are "Delete shipping line items on shopping cart updates" and "Commerce order message: changing status"
Thanks in advance.
Comment #7
jsacksick commentedCan you try with the patch coming from this issue? #2139037: DrupalCommerceEntityController::invoke should follow EntityApiController
Comment #8
Christopher Riley commentedI am running 7.x-1.8+33-dev of Commerce and it appears that it has already been patched for this issue. Also of note, I am not running kickstart this is a normal install with no profiles used.
Comment #9
Christopher Riley commentedI applied the patch to rules from over at https://drupal.org/node/2120421 and that seems to have corrected the issue. Thanks for the assistance.
Comment #10
lmeurs commentedThis appears to be a Commerce problem, see #2140165: While reloading $entity->original in the controller, track the save_depth and a possible workaround at #2140165-14: While reloading $entity->original in the controller, track the save_depth.