MODULE_PAYMENT_AUTHORIZENET_DEBUGGING Values Appear Inconsistent

[PaulRRogers]

Authorize.net payment module's source only recognizes "echo" for MODULE_PAYMENT_AUTHORIZENET_DEBUGGING while database values only include "Off", "Alerts Only", "Log File", "Log and Email".

[DrByte]

How exactly are you trying to use Developer mode?

What symptoms are you debugging?

[PaulRRogers]

Got an error trying to test against Authorize.net's sandbox, yet that's controlled using a similar constant "AUTHORIZENET_DEVELOPER_MODE". Doesn't seem to be a way to get to the sandbox using either. "...DEBUGGING" also appears to control how errors are handled. EDIT: I.e. I want to turn it on so I can view errors and contact the sandbox.

[DrByte]

There are 2 very different constants involved:

MODULE_PAYMENT_AUTHORIZENET_DEBUGGING is for logging communications requests/responses, and is configured using the Admin UI. Logs it creates will be either emailed or stored in the /logs/ folder, depending on which setting you choose.

AUTHORIZENET_DEVELOPER_MODE is for telling the code to communicate with the sandbox. It's called Developer mode because it's geared around doing integration testing with the gateway. It's not intended for storeowners to turn on/off conveniently. You can define it to 'on' by adding your own extra_configures file in /includes/extra_configures/my_authnet_devmode.php and defining the constant to 'on'.
Then you can specify your sandbox credentials using the Admin UI, in place of production credentials.

[PaulRRogers]

If MODULE_PAYMENT_AUTHORIZENET_DEBUGGING controls logging then why is only the value "echo" recognized in the source whilst the UI values are "Off", "Logging ...", etc.?

Also, the sandbox/test server URI appears to be out of date in the v1.5.4 source-code for Authorize.net.

[DrByte]

If MODULE_PAYMENT_AUTHORIZENET_DEBUGGING controls logging then why is only the value "echo" recognized in the source whilst the UI values are "Off", "Logging ...", etc.?

You'll notice that's a secondary recognition. It's there only for backward compatibility for an old test harness. Will be changing that in the next version.

Also, the sandbox/test server URI appears to be out of date in the v1.5.4 source-code for Authorize.net.

Hmmm ... I just tested, and my sandbox credentials work fine with the sandbox URL in both the SIM and AIM modules against v1.5.4.