Closed (fixed)
Project:
Commerce Core
Version:
7.x-1.x-dev
Component:
Payment
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
4 Jun 2015 at 11:58 UTC
Updated:
6 May 2016 at 11:45 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
andrewsizz commentedPatch
Comment #2
rszrama commentedEach payment method rule should really only be enabling a single payment method. I'm not sure what a loop would be doing for you here.
We can still fix the exception, though.
Comment #3
rszrama commentedGot the patch committed. : )
Comment #6
RAWDESK commentedHi, i've solved a similar issue on payment methods configuration pane by applying this patch, but now i am also receiving this error on /admin/commerce/orders/%order_id/payment
Any idea which module might be causing it this time ?
In attachement the rule i've detached from "checkout completion" event and attached to "set available payment method" event in order to bypass insecure user depersonalization, intially performed by my payment provider's redirect to checkout with anonymous user, and its consequences on global $user written logic :
https://www.drupal.org/node/1895418
The rule undeniably has a loop...
Comment #7
RAWDESK commentedQuickly scanned contrib/commerce folder for similar getElementName symptoms.
Found that commerce_payment.forms.inc at line 113 was responsible for the error in my case.
Fixed it the same way as Ryan did->works
PS. In attached screenshot an equivalent check that already seems to be present in commerce_payment.module :
Comment #8
andrewsizz commentedComment #9
asifnoor commentedThe patch provided by @rszrama works fine.