You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was testing this extension during migration to a Magento 2 storefront and I got the unhelpful message, while trying to put a test transaction through, that the "Profile could not be created."
if ($result->getMessages()->getData('resultCode') === 'Error') {
$err = $result->getMessages()->getMessage()[0]->getCode();
if ($err !== self::ERROR_CODE_DUPLICATE) {
thrownewPaymentException(
__('Profile could not be created: ' . $err)
);
}
}
This way, I could look up the error code to figure out what was wrong; in my case, the error was E00044, which meant that CIM was not enabled (I was accustomed to AIM on the Magento 1 site, and I had forgotten that CIM was something that I needed to specifically enable).
I could just submit a PR with this change, but it might not be the best way overall to give more information about an error; maybe this could be something toggled in the admin area.
(After the aforementioned quick-and-dirty change, I reverted it and more properly extended the Pmclain\AuthorizenetCim\Model\Adapter\AuthorizenetAdapter class inside my own Magento module.)
The text was updated successfully, but these errors were encountered:
I was testing this extension during migration to a Magento 2 storefront and I got the unhelpful message, while trying to put a test transaction through, that the "Profile could not be created."
I ended up modifying AuthorizenetAdapter.php a little after line 269 to look like this:
This way, I could look up the error code to figure out what was wrong; in my case, the error was
E00044
, which meant that CIM was not enabled (I was accustomed to AIM on the Magento 1 site, and I had forgotten that CIM was something that I needed to specifically enable).I could just submit a PR with this change, but it might not be the best way overall to give more information about an error; maybe this could be something toggled in the admin area.
(After the aforementioned quick-and-dirty change, I reverted it and more properly extended the
Pmclain\AuthorizenetCim\Model\Adapter\AuthorizenetAdapter
class inside my own Magento module.)The text was updated successfully, but these errors were encountered: