TOPIC: [SOLVED] Authorize.net Payments Not Working - 2.7.0.g

After hitting submit for paying with Authorize.net, I get a blank screen. I checked in the Authorize.net panel and there are no new transactions. I checked in the DT Register Records and see that there are new records for each transaction.

Does anyone have Authorize.net payments working with 2.7.0.g?

I do have it working, but I think I found out why some are blank. This is just a theory, but I think the problem lies with conditional fields. If you have a field "D" that is conditional to Field "A", then field "D" MUST come after field "A" in ordering. From what I can tell, if you do not do this, all of your registrations come up blank. Just a theory at this point though, but I changed that at it fixed one of my registrations. Try that out and let us know what happens.

You can download DT Register again. We made a change and now the confirmation message displays correctly after the submission. The full authorize.net process works fine in our testing. The updated package would show installed as 2.7.0h.2 (in list of installed components). If you just want to modify the one file, it is:
/components/com_dtregister/controllers/payment.php

Get the file from the just updated package. If you still have an issue, it would be related either to something in your site or your authorize.net account itself. We could follow up in a ticket.

when we update all of these new versions,. do we still have to open/close all fields?

No... that is only done when upgrading from 2.6.9 into 2.7. Thanks.

dthadmin wrote: You can download DT Register again. We made a change and now the confirmation message displays correctly after the submission. The full authorize.net process works fine in our testing. The updated package would show installed as 2.7.0h.2 (in list of installed components). If you just want to modify the one file, it is:
/components/com_dtregister/controllers/payment.php

Get the file from the just updated package. If you still have an issue, it would be related either to something in your site or your authorize.net account itself. We could follow up in a ticket.

Thanks for the quick response. I had to downgrade to 2.6.9 in order to get everything to work. I needed to get this up and running and don't have the time right now for testing, etc. Hopefully all the bugs will get worked out and then I'll be able to update.