I have a client who is using ubercart and someone previously modified (!) the uc_authorizenet module to use a different post_url than the one in the code. They are using eprocessingnetwork.com which works the same as authorize.net so simply by changing the post_url, they were able to use the new gateway provider.

Since others may want to use alternatives to authorize.net while still using the uc_authorizenet module, I have a simple patch to handle this. The patch allows you to specify the gateway URL in the configuration settings and then that configured URL is used for the post_url.

Please review. I hope this will be accepted so my client can have hack-free ubercart code. If you need changes or have a different approach, I'm happy to update the patch if necessary.

Thanks,
Kristen

CommentFileSizeAuthor
#2 uc_authorizenet.module.patch1.94 KBtr
uc_authorizenet.module.patch1.49 KBkristen pol

Comments

tr’s picture

tr commented

Sounds like a good idea to me. I re-rolled the patch to put the default URLs into a define().

tr’s picture

tr commented
StatusFileSize
new uc_authorizenet.module.patch1.94 KB

... but somehow I forgot to actually *attach* the re-rolled patch. Sigh. Here it is:

tr’s picture

tr commented

Any comments on why this is not a good idea and shouldn't be fixed?

tr’s picture

tr commented
Status: Needs review » Fixed

Committed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.