8:34pm ET - I spoke to Authorize.net and they confirmed (finally!) that they are going to roll this change back. As to whether or not you want to implement this patch, it is up to you. Zoey plans on keeping this patch in its codebase as it provides no downsides and more accurately follows the implementation documentation from Authorize.net which does state that the delimiter and encapsulation variable should only be 1 character.
Hello,
Authorize.net made an unannounced change in their support of the delimiter character from any string to only one character. The fix provided above is incomplete and will cause errors because parsing the delimited on ( means that any user input containing ( will also break.
Here is a more complete fix, although the most proper fix is for Authorize.net to revert this change in my opinion.
//Remove
const RESPONSE_DELIM_CHAR = '(~)';
//Add
const RESPONSE_DELIM_CHAR = '~';
const RESPONSE_ENCAP_CHAR = '|';
// Add these lines above $client->setParameterPost($request->getData()); about line #1285
$request->setXDelimChar(self::RESPONSE_DELIM_CHAR);
$request->setXEncapChar(self::RESPONSE_ENCAP_CHAR);
//Remove this line
$r = explode(self::RESPONSE_DELIM_CHAR, $responseBody);
//Replace with
$r = explode(self::RESPONSE_ENCAP_CHAR . self::RESPONSE_DELIM_CHAR . self::RESPONSE_ENCAP_CHAR, $responseBody);
if(isset($r[0]) && $r[0]{0} === self::RESPONSE_ENCAP_CHAR) {
$r[0] = substr($r[0], 1);
}
$rCount = count($r);
if(strpos($r[($rCount-1)], self::RESPONSE_ENCAP_CHAR) !== false) {
$r[($rCount-1)] = str_replace(self::RESPONSE_ENCAP_CHAR, '', $r[($rCount-1)]);
}
We are unaffiliated with Magento and this fix is hopefully able to help others.
Uri
Zoey
www.zoey.com
