Jump to content

Akshara

Members
  • Content count

    50
  • Joined

  • Last visited

1 Follower

Profile Information

  • Real Name
    Akshara
  1. Akshara

    Contribution Request: Manual Order Entry

    Any news on this contribution? The temp server download page doesn't work. I read the entire 7 page thread... did anybody get this to successfully work on a MS1 Loaded 5?
  2. Hello there. With special thanks to Ocularmagic, we were able to come up with a temporary yet simple solution to the City Tax problem. It has been bundled up as a contribution, and can be found here... http://www.oscommerce.com/community/contributions,1240 What it does is hack the includes/functions/general.php file by adding a hardcoded If/Else conditional which checks a customer's address book in the database for their entry_city, and compares it to their entry_zone_id (or State/Province). If they both match what you input into the general.php file, then it returns a custom tax rate and description which you specifiy; if either doesn't match, then it simply runs the normal tax rate and description functions. It's very simple to install, and works very well. Also, it is entirely possible for the code to be modified to search the entry_postcode and entry_suburb fields in place of the entry_city field, if one wanted to customize this to work for Zip Codes or Suburbs (which could be easily modified in the language files to be 'Counties' instead). :wink:
  3. We got it to work! Here is the thread which explains our experience and what we learned that helped... http://forums.oscommerce.com/viewtopic.php...p=158358#158358
  4. For all those running a search on the Surepay module, I wanted to post my experience for future reference. First of all, the module's developer was very helpful and kind when I finally got in touch with him. I was at my wit's end, and he helped point me in the right direction. Thank you Stan... cheers! So first off, make absolutely sure that your server has the Curl library compiled properly. If your site is SSL, then it needs to be complied under SSL. Also, the Surepay rep said that OpenSSl v9g was the earliest bug free version. There is a test script online which works out-of-the-box when placed on a properly configured server. It can be found here, and you just copy/paste the code into a php file and place it your root directory. It can be called up via either http or https http://rachael.kreisler.org/surepay/ You will probably have to get your hosting server to configure everything unless you are running your own server and know how to do this. If you need a host that will go above and beyond to help, I recommend Loai Said over at http://www.spidersaid.com. Thanks Loai! Once the Curl library works, the next step is to test the Surepay module in OsCommerce. Contrary to the Readme file, a total of $11 will randomly give you both an Auth and Decline message; there will be no "Reference" or "Call" message in OsC for $21, though you might see them in your Surepay Manager software; and the $44 Decline should be changed to $41 according to the Surepay representative. Also, in both the Kreisler test and in the module test you should leave the account # as "1001" and the password set to "password"; that might seem obvious but it wasn't to us. Once you get several Auth and Decline messages (which you can also see in the 'Surepay Transactions' table of the database using a tool like PhpMyAdmin), then it is time to go live. Simply switch the Admin>Modules>Payment>Surepay option for this - you shouldn't need to hack the php files directly at all. Then input your actual account number, and your Gateway Password - this is very important, because Surepay sends you a set of 3 passwords, and you must have the 'Gateway' password input here for the module to work. Now send a transaction and see if you get an Auth, and if is shows up in your Surepay Manager. If you get an error, then you can add this line of code to the surepay.php file immediately after line 441... $surepay_debug_mode = true; This will enable a debug mode that returns the actual XML you're getting from Surepay. Be sure to comment this line out when your are finished debugging. Also, you can disable the CVV2 code on line 148 of the sausurepay.php file if you don't want or need the CVV2 option. Then comment out lines 117-118 and 178-179 of the surepay.php file to get rid of the CVV2 field. If the CVV2 is enabled, then a customer must input a number into the field or the transaction won't complete - the Surepay representative said that no fields can be sent with a "null" value to their XML auth site or the transaction will break. Okay... so I hope some of this helps. The module actually does work if absolutely everything else down the line is configured properly. Hang in there... :wink:
  5. Akshara

    Retail Partners module

    Did this ever get developed? I would be very interested in this module.
  6. Akshara

    Dealer Zip code based distance locator

    I too would be very interested in this contribution.
  7. Wow.. thank you for taking the time to do that. You have a very kind heart. :) Surepay is a CC authorization company that uses XML to authorize transactions. It's not readily compatible with PHP, and there have been a few PHP integration attempts that are available online. We were able to fix the Curl Library issue, and our SSL is working just fine now. I've also spoken with Surepay representatives directly, and we were able to run a script test by Rachel Kriesler which showed that our Curl/SSL setup was correct. But running the same test in OsCommerce with this module doesn't work properly. What I'm concerned about is that if feels like this module isn't 100% tested or something; it's got to work in a production environment for it to be worth all the trouble. So I'm interested to here if anyone actually is using it successfully.
  8. Oh yeah... I've installed several other 3rd party contributions and am running the latest MS1 Loaded compilation. So I've had that experience... it seems like this Surepay module isn't completely finished or something. And I can't find much information on it in the forums here. So that's why I'm wondering if anybody is actually using it in production successfully. Thank you.
  9. Has anybody gotten the Surepay module to work on an actual live production cart? I'd like to know just so I can rule out whether the module is faulty or not. We got the Curl Library thing solved, and we can get an Auth test return from Surepay; but we can't get a Reference or Declined return, the final checkout_success.php page has a parse error in it when we add the code that the Reame file recommends we add, we can't run test mode under our Surepay account # and password (only with the test account/password)... I'm just asking if anyone has gotten this to fully work before so we can decide whether we should keep working with this module or not. Thank you.
  10. Hello all, I'm curious if anyone has had success with using the Surepay Module or not? I've read through all posts on this forum related to it, and haven't found much info about it. We installed it on our cart, and it's just been a nightmare so far. At first we discovered that the Curl libraries weren't compiled under SSL, so we had the server host do that. Then we spoke with Surepay, who gave us the Kriesler test page for running surepay under php.... that at first didn't test out. So the server host tried some other changes, and the test came through as authorized. Then we tried to run a test on our shopping cart, and it came back with a credit card error on a standard Oscommerc credit card error page. It was recommended that I re-upload the module and run a test with the default variables again... so did that, and then got a new error message back on a blank white page that says... Curl error: 35 SSL: error:00000001::lib(0) :func(0) :reason(1) Bascially, I'm wondering has gone down this road before; and if you have some insight as to how we should approach this. I'm completely stumped and getting a headache from the whole thing since we've been working on this for several days now. I don't know where to begin looking - whether it's a server problem, something wrong in the module, an OsCommerce issue, a Surepay XML<>PHP problem, or what. If we didn't have to use Surepay, I'd just dump the darn thing altogether. Any help or insight will be deeply appreciated. Thanks.
×