Jump to content


  • Content count

  • Joined

  • Last visited

1 Follower

Profile Information

  • Real Name
    Ian Fagan
  1. itf


    I'm running version 1.2.4 of the module, and I found that just changing a variable in catalog/includes/modules/shipping/upsxml.php resolved my problem. It's line 75 in my file, and reads as follows: $this->xpci_version = '1.0001'; Changing that to this: $this->xpci_version = '1.0002'; solved the problem for me. I can't claim that this will work for everyone or that it is the proper way to address this issue, but it got us back up and running and able to take orders. If anyone else understands the issue better, I'd like to hear about it, but hopefully this change can be a band-aid for those whose sites aren't functioning right now.
  2. The directions leave out a step: you have to go into the Order Total Modules in the admin and enable the Account Balance module you just installed. That said, there are also a lot of minor errors in the installation instructions. If you're just overwriting on a clean install it may work fine, but the instructions for editing existing files have problems in several places, mostly places where they tell you to add a line of code when what you should be doing is editing an existing line. Experienced PHP coders who are being careful will probably notice all of these, but less experienced developers might miss some of them - so be careful.
  3. itf

    Verisign Issues

    It doesn't look like there's going to be a permanent fix, at least not from VeriSign's end. Below is the text of an e-mail I received this morning from the VeriSign rep who's been addressing my trouble ticket. The big problem appears to be that the Payflow Link server will no longer follow redirects. My stores, and I presume all of those using the same Payflow Link module for osCommerce, have Payflow Link silent POSTing to "verisignreturn.php", which then redirects to checkout_process.php. Someone in the community is apparently going to have to rewrite the Payflow Link module so that it doesn't incorporate a redirect. I'll probably take a shot at it some time in the next few days if no one else beats me to it. There may be other minor issues also playing into this problem, and so here's the text of the e-mail I got from my VeriSign rep, which (hopefully) contains a complete list of differences between new server and old.
  4. itf

    Verisign Issues

    After spending over an hour on the phone with the support representative, we have temporarily fixed the problem by changing a line in the class constructor in /includes/modules/payment/payflowlink.php. This line (line 21 in my file): $this->form_action_url = 'https://payflowlink.verisign.com/payflowlink.cfm'; becomes this: $this->form_action_url = 'https://cf.payflowlink.verisign.com/payflowlink.cfm'; This apparently hits their old server instead of the one they just switched to, meaning everything works as it did yesterday. It seems to have resolved the problem for us. I don't know if this will work for anyone or if VeriSign has to authorize accounts to hit the old server. In any event, the rep told me that the problem should be tracked down by the engineers and resolved in the next 24-48 hours - but those of you with stores that are losing order information might want a speedier resolution. Good luck -
  5. itf

    Verisign Issues

    I'm having the exact same issue, on two different sites that I built and maintain. I'm currently sitting on hold with VeriSign technical support and will post the results of my discussion with them once I talk to them - but it's definitely not just you. They apparently began a migration process to new servers this morning, and although nothing is supposed to be deprecated until July 1st, I'm betting it's related.