Jump to content

future1

Members
  • Content count

    25
  • Joined

  • Last visited

1 Follower

Profile Information

  • Real Name
    brian
  1. future1

    Protx Direct v2.22

    I just noticed that the sql upgrade file doesnt modify the vendortxcode field to varchar(40) from int as it was in earlier versions, this may explain why users have reported that the vendortxcode is the same as the orderid in the protx direct table.
  2. future1

    Protx Direct v2.22

    Thanks for the speedy reply tom, The orders themselves are totally correct in OSC (correct tax etc) its just the figure sent to protx thats wrong, its certainly bizarre, and only effects a small percentage, but its wrong. The difference always being the tax on the shipping!
  3. future1

    Protx Direct v2.22

    Hi, Tom...thanks for your ideas with my DNS issue, this has been resolved now thankfully. I have another issue that I cant solve. A small percentage of orders are not being charged with the correct order total in protx. the difference being the tax on shipping. I have not been able to find any obvious pattern, but the majority of orders are ok, this did not happen on 4.3 or below. Can any body think of a change that has taken place that could effect the ord_total? As this is taken from the order class (obviously unchanged in 4.4) I'm slightly stumped!
  4. future1

    Protx Direct v2.22

    Thanks for the response Tom, The table just contains something like: 6736 43157 46575 46575 PAYMENT 96.5800 Nothing back from protx and nothing in the protx log. The user just gets the: MODULE_PAYMENT_PROTX_DIRECT_TEXT_PROTX_ERROR message I thought it was just the 2 url's...
  5. future1

    Protx Direct v2.22

    I have tried using the following IP from protx: The Live Site IP address is: 213.052.247.135 rather than ukvps.protx.com, but I still get a technical error. We had had DNS problems on the server, hence trying this. Do i need to change this in any other places other than the 2 places in protx_process.php?
  6. future1

    Protx Direct v2.22

    Are you being serious? I posted it in this "forum" as this issue effects anyone using the protx direct payment module and therefore thought I might get some helpful comments
  7. future1

    Protx Direct v2.22

    hello everybody, we have had feedback from users who want to know the order total (inc shipping costs) before inputing card details. Thinking about this I guess an enhanced shopping cart info box would do the job...any suggestions?
  8. future1

    Protx Direct v2.22

    Hello all, we are seeing a number of transactions today that are not appearing on OSC, but showing on Protx. We have made the timeout change that Tom refered to above...will report back later. We are also seeing "Malformed - 3096 : The VPSProtocol value is required." appearing in the protx_direct table. This seems to happen when users fail 3D and are diverted back to checkout_payment.php
  9. future1

    Protx Direct v2.22

    Tom, I have just upgraded to 4.2, but the void and refund are not working. The transaction i'm testing it on was placed using the upgraded module, so all db field names should be ok. When I click on refund I get the value dialog, however after entering an amount the page goes completely blank. When trying void I get the error (stored to protx_direct table) of "The original transaction not found," The vendorTXcode looks correct. I have double checked the versions of the main module files and they are all correct.
  10. future1

    Protx Direct v2.22

    Tom, Just noticed a small problem, the Customer telephone field is set to 32 in the db, but protx only accepts 20chars, so the transaction fails if the customer has put a very long number in the telephone field
  11. future1

    Protx Direct v2.22

    All sounds good. BTW - Shipping tax isnt being sent to Protx in the Send Basket option
  12. future1

    Protx Direct v2.22

    Thanks for the super speedy response! I was just thinking that: $VendorTxCode = $uid . $new_order_id; would at least append the expected order number to the random number as the protx reports dont contain the description field (order number), so reporting is improved if the reports contain something that can link the payment to an order. On another point, is the protx_direct table supposed to have the VendorTxId in the vendortxcode field? Nice work by the way!
  13. future1

    Protx Direct v2.22

    Hi guys, Am I missing something with the vendor tx code, why use a random number? Wouldnt the order number be more useful when reported out of protx?
  14. future1

    edgeoi feed error

    Has anybody thought about adding manufacturer to the file, as this is very useful for products.
  15. future1

    edgeoi feed error

    This should help with the specials pricing problem, if somebody could check it through, If you find (around line 158): while($row = tep_db_fetch_array($result)){ and add this: $sql2 = "SELECT specials_new_products_price FROM specials WHERE products_id = " . $row['products_id'] . " and status = 1 ORDER BY specials_id DESC" ; $result2 = tep_db_query($sql2); $ll = 1; $row2 = tep_db_fetch_array($result2); if( $row2 ){ $row['products_price'] = $row2['specials_new_products_price']; }
×