Problem/Motivation
Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens: SELECT base_table.payment_id AS payment_id, base_table.payment_id AS base_table_payment_id FROM {commerce_payment} base_table INNER JOIN {commerce_payment} commerce_payment ON commerce_payment.payment_id = base_table.payment_id WHERE (commerce_payment.state = :db_condition_placeholder_0) AND (commerce_payment.remote_id = :db_condition_placeholder_1:db_condition_placeholder_2:db_condition_placeholder_3:db_condition_placeholder_4:db_condition_placeholder_5:db_condition_placeholder_6:db_condition_placeholder_7); Array ( [:db_condition_placeholder_0] => pending [:db_condition_placeholder_1] => xxx [:db_condition_placeholder_2] => xxx [:db_condition_placeholder_3] => xxx [:db_condition_placeholder_4] => xxx [:db_condition_placeholder_5] => xxx [:db_condition_placeholder_6] => xxx [:db_condition_placeholder_7] => xxx ) in Drupal\commerce_authnet\Plugin\Commerce\PaymentGateway\Echeck->getSettledTransactions() (line 238 of /var/www/html/docroot/modules/contrib/commerce_authnet/src/Plugin/Commerce/PaymentGateway/Echeck.php).
Steps to reproduce
Execute Cron after making payments via E-check
Proposed resolution
Provide a patch.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | commerce_authnet-echeck-error-3178739-8.patch | 714 bytes | nathaniel |
| #7 | commerce_authnet-echeck-error-3178739-7.patch | 714 bytes | leewbutler |
| #4 | commerce_authnet-echeck-error-3178739-4.patch | 714 bytes | leewbutler |
| #2 | commerce_authnet-echeck-error-3178739-2.patch | 714 bytes | john.oltman |
Issue fork commerce_authnet-3178739
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
john.oltman commentedSee attached patch
Comment #3
john.oltman commentedComment #4
leewbutler commentedThank you John. Your patch was the fix for me when receiving the same error, I just had to update it to apply the code to line numbers that correspond with the release 8.x-1.3. Updated patch attached.
Comment #7
leewbutler commentedUpdated patch for the 8.x-1.x branch attached.
Comment #8
nathaniel commentedre-roll
Comment #10
jsacksick commentedCommitted.