Jump to content

Bruin_03

Members
  • Content count

    215
  • Joined

  • Last visited

  1. Bruin_03

    California EWR fee

    Don't hold your breath for osc 3.0. You will have to develop a custom module. I would look at some order total classes like this one. http://addons.oscommerce.com/info/251 The order total class apparently let's you added additional charges that are percentage of the order total.
  2. Check out the Authorize Net AIM Invoice Number Fix contribution
  3. Bruin_03

    Innovative Gateway Solutions PHP script - need help!

    If you need help with this contribution please contact me. i'm currently doing an implementation.
  4. Figured it out. After making the update in STEP 3, you have to go back into the module and update the options so the changes take. Problem solved.
  5. The suggestion in the manual doesn't always fix the problem! I read step 3, followed the instructions and still get the error!
  6. Bruin_03

    Multiple-Shipping-Addresses

    I know this has been a while but do you have any recommendations to go about extending it?
  7. Bruin_03

    Authorize.net PAYMENT MODULE PROBLEMS

    You really shouldn't have to set up to much on the AUTHNET side. I have a couple clients who have authnet successfully working (an ehanced version w/ debugging of course). My hunch is there is probably a setting somewhere that is misconfigured. Per this thread http://forums.oscommerce.com/index.php?sho...p;#entry1229176 make sure you are using API Login ID/transaction key combo and NOT your AUTHNET user Login. That seems to be killing everybody. I'm available after Thursday if you still need a hand with AIM. :)
  8. Bruin_03

    authorize.net problems

    You certainly have to use the API Login ID as per the AUTHNET documentation. User Login stopped working for me a long time ago as it should because technically you can have the same AUTHNET user login with different merchant accounts. It's possible that AUTHNET recently set up all their customers like this. Another thing is that this authnet contribution is very basic starting point. It doesn't show you all the information auth.net sends back to your site with every transaction attempt. Usually auth.net will provide an error code with each response type, which you can look up and find out EXACTLY what is wrong. What I've done for clients in the past is create an option to log every transaction and response, as it It certainly helps with troubleshooting and can save you a lot of time in the long run.
  9. Bruin_03

    New AuthNet Module Changes Observed

    It looks like my last comments were deleted for never made it for some reason. Anyway, you bring up an excellent point. If one enters the payment details on the checkout_confirmation page, that essentially makes the checkout_payment page redundant. Anway, after looking at the code in the new module, the appearance and action of various items are put in different classes. As of lst week when i looked at the new AIM module, the code that creates the form for credit card details is located in a function called confirmation(). If you wanted the customer to input card data where one selects a payment method, you would put this code in the function called selection(). I'm sure you can edit your shop so checkout payment is skipped entirely by putting all the payment selection on the confirmation page. It does seem redundant. You'd need to make some changes in checkout shipping (if you use it) so the page goes directly to checkout confirmation and you'd also need to update code in checkout_process so all credit card responses go to checkout confirmation and also add the code in checkout confirmation to show any of the CC responses at a bare minimum. It's definitely doable but it will take some time and patience to roll up your sleeves and dig into the code. None of which I unfortunately have right now. You may want to have a look at the FEC addon.
  10. I observed that the New AuthNet module asks for the credit card information on the order confirmation page instead of the checkout payment page. May we know the reason for this change? Doesn't it make the checkout payment page redundant since we'll be paying on the confirmation page anyway?
  11. Bruin_03

    Stop Automatic Charge (Authorize Only)

    Scotts solution is probably the most straight forward. I'd set it up at auth.net.
  12. Bruin_03

    Why was a new AuthNet module created?

    Very good. Thank you Harald. Your efforts are truly appreciated! :)
  13. Why was a new Athourize.Net module created when one already existed?
  14. Bruin_03

    Super Contact us enhancement 1.0

    Sumo, that error isn't very descriptive. Where did you get it? Post the contents of the page here and someone can help u out.
  15. You're absolute path is incorrect. The cron tab can't find the file. Now if my brief memory of godaddy serves me right, they have some screwy ways you are supposed to use their full paths. The absolute paths displayed php scripts aren't always the ones you should be using. I would contact them to ensure the absolute paths in your configure.php are correct.
×