Latest News: (loading..)

freerangemum

Members
  • Content count

    692
  • Joined

  • Last visited

1 Follower

About freerangemum

Profile Information

  1. Anyone with QTpro & Order Editing working together & willing to share their changes or files? I'm trying to sort it out myself but it seems silly to reinvent the wheel!
  2. That's my problem this time - <input type="hidden" name="OrderHash" value="error while loading shared libraries"> So I checked the location of the files //Path where the TestHash.e executable is located $path='/home/****/public_html/cgi-bin'; putenv("LD_LIBRARY_PATH=$path"); Files are in the cgi-bin, permissions set to 755. I had OSC RC2 working on the old server (PHP4). The new server is PHP 5.2.6 (Zend: 2.2.0), MySQL 5.0.51a-community. I've already fixed a 'unknown column' bug in checkout_process.php (which I though had been sorted out in RC2?)
  3. I don't BELIEVE this! Moved to a new server & now its not working again. So far I've tried register_globals (is on), the timestamp (reverted to the original code which produces timestamp in the correct format, but doesn't fix the problem), the document_root, and checked that the files are in the right place. No matter what I've tried, I'm still getting the hacking attempt message from hsbc_return.php. Anyone have suggestions for what to try next please? ;)
  4. Yes indeedy, except that I didn't know the term 'E notation'. That's one of the things I love about OSC , and about this HSBC mod - always teaching you new things!
  5. I've played around some more & got it working! I'm now using //POST time $time=time(); //Change the 0 if your server is located at a different GMT time $time=($time+(0*3600)); $time= $time."000"; Only thing I now need to fix is to change the setting so that the payment needs to be manually set to shipped in the HSBS admin.
  6. I've removed the line $time=$time*1000; so now the timestamp is coming out as <input type="hidden" name="TimeStamp" value="1231846071"> . Now the error message is "The processor did not return a response." I've no idea where to look this time. :huh:
  7. Hi Colin, what did you do to solve this problem? I'm having the same difficulty. :rolleyes:
  8. It was restored, but I've checked & been told the files are in place. Time is correct too.
  9. Following our server being rebooted we're getting hacking attempt warnings coming up (except that I've edited the text so its less scary for customers). Since it was previously functioning I know that the hash key is ok, so what else could be causing the problem?
  10. The thing you have to bear in mind is that whilst protx is familiar to those of us who spend a lot of time online, and staying on your own site to take payment details appears more fluid & 'cleaner', for our customers HSBC is a name they know from the high street and feel comfortable & safe with. To them going to a different site to enter their payment details isn't a -ve, far from it. Personally I'm not interested in what makes for a better payment process code wise (or at least not as a priority), my no. 1 priority is making my customers feel safe & secure, so they'll hit the final confirm button.
  11. If you want to get in touch with Jose, far better to send him an email - studio (at) qadram.com ;)
  12. I had this working fine, but now I've become VAT registered so some of my prices include tax. When the cart includes taxable items the total is adding tax on twice. What do I need to change?
  13. Just waiting on HSBC to ring back now. :rolleyes: Thanks Vger.
  14. Has anyone come accross a problem with changing to new account details? Everything is working fine for our existing account, but we need to change to a new account with new hash & Client ID. All we get is 'hacking attempt'. Already tried requesting a new hash, but that didn't work. Any ideas anyone?
  15. Andrew, are you developing for yourself or a customer? HSBC will have supplied a 'securesecret' to the account holder which should be saved as a .txt file in your cgi bin. If you have that in place & still suspect you have a duff key, insist on their changing it. From my experience they only check it in Java & not C, as Jos? says, so even if they say its ok it could be duff. Stamp your feet a bit if you have to, after all YOU are paying THEM!