Closed (fixed)
Project:
Commerce Authorize.Net
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Apr 2018 at 21:30 UTC
Updated:
21 May 2018 at 19:09 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
mglamanThis is in reference to: commerce_authnet_post_update_echeck
See http://cgit.drupalcode.org/commerce_authnet/commit/?id=365ce4922fa01abe1...
The gateway plugin is split into two different gateways. So the Client ID issue existed before this.
Comment #3
mglamanUpdating to strike out "the default transaction type switched from "Authorization and capture" to "Authorization only". This is handled by the checkout flow directly. See #2953806: Setting gateway to "authorization only" has no effect?
Comment #4
mglamanStarted to write test.
Need to generate a database fixture to test with, using old revision like 0fb85dcbf46cf4fe4b1942a56af7fee66e36a484.
Comment #5
mglamanComment #7
mglamanCreating a test fixture based on the commit 0fb85dcbf46cf4fe4b1942a56af7fee66e36a484
Comment #8
mglamanHere is a test with a fixture that upgrades a gateway plugin made on c65e90993f8b4919ed427043ace4e960202092e0 and upgraded.
Comment #10
mglamanFound the problem. Setting the plugin ID purges the configuration. Uploading a patch which fails and has the fix commented out.
Comment #12
mglamanComment #13
mglamanOkay, next steps:
* Clean up
* Move communication about missing the client key to a follow-up.
This initial regression was due to the eCheck split. However, we uncovered a different upgrade issue along the way.
Comment #14
mglamanHere is the patch I plan to commit.
Comment #15
mglamanHere is a patch with the test fixture gzipped to save some disk space.
Comment #17
mglamanMissing binary file
Comment #18
mglamanComment #19
mglamanUpdate title to be more precise.
Comment #21
mglamanFixed! Opening a follow up for the AcceptJS token messaging.