Jump to content

perfectpassion

Members
  • Content count

    1,317
  • Joined

  • Last visited

Everything posted by perfectpassion

  1. perfectpassion

    Protx Direct v2.22

    It is due for Tuesday 21st April (tomorrow) - Protx believe in giving customers plenty of notice - the email from them only arrived 4 days ago!
  2. perfectpassion

    Protx Direct v2.22

    In theory the existing modules should continue to work as Protx are enabling URL redirects rfom old to new (though I don't know how long they will be in place for). However we can't test this until switch over day unfortunately.
  3. perfectpassion

    [Contribution] Protx Direct v5 Support Thread

    v5.1 Uploaded This supports the v2.23 protocol and new SagePay URLs. This version does not yet support the PayPal integration. Please note that this module will not yet work in live mode until Protx launch the new SagePay URLs on Tues 21st April - it does however work successfully in Simulator and Test modes. Version 5.0c should continue to work after the switch over as Protx are putting in URL redirects however you may have to change the "Disable cURL SSL check" to true in your osC admin settings to prevent SSL cert error messages. I'm afraid we'll have to watch this space and see what happens - I think we all have experience of how badly upgrades and system changes tend to go at the Protx end :-(
  4. perfectpassion

    Protx Direct v2.22

    v5.1 Uploaded This supports the v2.23 protocol and new SagePay URLs. This version does not yet support the PayPal integration. Please note that this module will not yet work in live mode until Protx launch the new SagePay URLs on Tues 21st April - it does however work successfully in Simulator and Test modes. Version 5.0c should continue to work after the switch over as Protx are putting in URL redirects however you may have to change the "Disable cURL SSL check" to true in your osC admin settings to prevent SSL cert error messages. I'm afraid we'll have to watch this space and see what happens - I think we all have experience of how badly upgrades and system changes tend to go at the Protx end :-(
  5. perfectpassion

    Protx Direct v2.22

    There are URL changes which they have today released and will take effect on 21st April. I'm trying to find out from them if the old urls will continue to work past this date and also if we can use the new urls before that date (for live services). Once I have that info I'll release an update to the module. I'm in the process of updating the module from v2.22 to v2.23 - part of the update includes the possibilty of including the paypal via Protx integration - is anyone interesed in this?
  6. perfectpassion

    Enabling, disabling a payment module vs total price

    The way I had written it was correct to disable it if the order is less than $12 12 < $order->info['total'] means "12 is more than the order total" (just another way of saying "the order total is less than 12")
  7. perfectpassion

    Enabling, disabling a payment module vs total price

    You need to modify the paymenr module's update_status function look for something like: function update_status() { global $order; if ( ($this->enabled == true) && ((int)MODULE_PAYMENT_COD_ZONE > 0) ) { $check_flag = false; $check_query = tep_db_query("select zone_id from " . TABLE_ZONES_TO_GEO_ZONES . " where geo_zone_id = '" . MODULE_PAYMENT_COD_ZONE . "' and zone_country_id = '" . $order->delivery['country']['id'] . "' order by zone_id"); while ($check = tep_db_fetch_array($check_query)) { if ($check['zone_id'] < 1) { $check_flag = true; break; } elseif ($check['zone_id'] == $order->delivery['zone_id']) { $check_flag = true; break; } } if ($check_flag == false) { $this->enabled = false; } } // disable the module if the order only contains virtual products if ($this->enabled == true) { if ($order->content_type == 'virtual') { $this->enabled = false; } } } and before the final } add: // Disable order module if order total if $12 or less if (true == $this->enabled && 12 > $order->info['total']) { $this->enabled = false; }
  8. perfectpassion

    Spot the code error...

    You are trying to use a v2.2 module with v3 - at the moment the only payment modules for v3 are the ones that come with it
  9. perfectpassion

    Protx Authentication

    Your are getting that error because the Protx simulator only supports the new 2.23 protocol and the current Protx Form module is the 2.22 protocol - it'll work against the Protx test / liver servers but not the simulator - the module needs updating.
  10. That error is caused by a very out of data validation class that will reject many modern card number ranges - don't worry about it - when you use the correct module for your gateway things will be sorted :-)
  11. perfectpassion

    What config files - the how where

    This is found in your osC admin area -> Configuration -> Sessions Again found in you admin area under Modules->Payment->your payment module
  12. perfectpassion

    Protx Direct credit card surcharge

    There is a surcharge order total add-on that you can install but that would apply to all card type not just credit cards. It would be difficult to surcharge just credit cards as you don't know which card type is going to be used until the customer clicks "confirm order" at which point they have no opportunity to be informed of the cost of the surcharge. It would be possible to code a Javascript solution that could popup a warning when a surcharge applies.
  13. perfectpassion

    tep_session_unregister problem

    tep_session_unregister is a core function in osC - if it is not defined then the file must not be including the osC core correctly - normally via an include('includes/application_top.php') call That said files in includes/modules/payment shouldn't need to include any files - they are only called from the payment class and should not be called directly
  14. perfectpassion

    Help! Payment module Section in admin is blank

    Your best option is to restore your modified file with your backup then try to do the modification again.
  15. perfectpassion

    Protx Direct v2.22

    The most common cause is customers not correctly entering information such as expiry or card number
  16. perfectpassion

    Protx Direct v2.22

    Unfortunately that's a flaw with oscommerce itself and may happen from time to time if you have a busy site - it won't cause any harm but just be aware of it when reconciling your transactions
  17. perfectpassion

    Protx Direct v2.22

    You don't need to upgrade through the versions - you can jump straight in with v5! - could you please be more specific about the error this is not related to the installation - simply add the IP to the protx admin area.
  18. perfectpassion

    Protx protocol 2.22 changing to 2.23

    All protx servers - live, test & simulator have been upgraded to 2.23, and all 3 will work with an updated module. However the simulator is not backwards compatible to 2.22 (live & test servers are). I will update the current protx direct module that I wrote to the new protocol as soon as time allows but I'm afraid paid work must come first.
  19. perfectpassion

    Protx Direct v2.22

    In admin: Configuration-> My store -> Search Engine Safe URLs (still in development) -> set to false
  20. perfectpassion

    Protx Direct v2.22

    I can't think of any reason why the protx module would cause the login session to be lost. Regarding the CVV popup - where does the link point to (rt click-properties) - if it looks like FILENAME_POPUP_CVV then you need to add the line from the install script to /includes/filenames.php
  21. perfectpassion

    Protx Direct v2.22

    You are correct - the Simulator only supports protocol v2.23 - this module is currentl v2.22 which will work indefinately against the test and live servers but not the simulator. I will be update the code as soon as I get time between paid work.
  22. perfectpassion

    Collect In Store (No Online Payment Wanted)

    Use the "Cash on delivery" module but change the text to "Collect & Pay In Store" or something similar
  23. perfectpassion

    Duplicate orders!

    if it is happening with every order it must be due to a non standard checkout Can you pm me your site link?
  24. perfectpassion

    Duplicate orders nitemare!

    I've replied to your existing thread
  25. perfectpassion

    Duplicate orders!

    I can only think that there was a delay in the lightbox window popping up and the customer pressed confirm twice - as you say no other reported occurrences. It is possible to use a bit of JS to disable the confirm button after clicking (though it would have to be re-enabled if an error occurs) - I'll piece something together later
×