Jump to content

perfectpassion

Members
  • Content count

    1,317
  • Joined

  • Last visited

Everything posted by perfectpassion

  1. perfectpassion

    Help with modifying a payment method

    //Added for state funded check $state_funded = tep_db_query("SELECT value, fields_id FROM " . TABLE_CUSTOMERS_TO_EXTRA_FIELDS . " where customers_id ='" . $customer_id . "'"); //end added should be //Added for state funded check $state_funded_query = tep_db_query("SELECT value, fields_id FROM " . TABLE_CUSTOMERS_TO_EXTRA_FIELDS . " where customers_id ='" . $customer_id . "'"); $state_funded = tep_db_fetch_array($state_funded_query); //end added and // Added for state funded check // $this->enabled = ((MODULE_PAYMENT_INSTALLMENT_STATUS == 'True') ? true : false); if(MODULE_PAYMENT_INSTALLMENT_STATUS == 'True'){ if(($state_funded->value) == yes){ $this->enabled = true; } else { $this->enabled = false; } } else { $this->enabled = false; } ; // End added should be // Added for state funded check // $this->enabled = ((MODULE_PAYMENT_INSTALLMENT_STATUS == 'True') ? true : false); if( (MODULE_PAYMENT_INSTALLMENT_STATUS == 'True') && ($state_funded['value'] == 'yes') ) { $this->enabled = true; } else { $this->enabled = false; } // End added
  2. perfectpassion

    [Contribution] PayOffline (Pro)

    Those messages suggest to me that application_top.php is being included / required more than once though I couldn't say why. The payoffline does nothing special on the checkout_payment screen compared to other payment modules
  3. perfectpassion

    [Contribution] PayOffline (Pro)

    I imagine that it is - you have a "fatal error" above and I suspect that occurs before the email is generated - once the fpdf problem is fixed the emails will probably start working
  4. perfectpassion

    [Contribution] PayOffline (Pro)

    This contribution doesn't use pdf files at all -from the above it look like you have a pdf invoice contrib installed and the two have clashed. The error suggests that you are missing the file /fpdf/fpdf.php - I'd double check that this file exists and if not re uploaded it from the pdf contrib.
  5. perfectpassion

    Protx Direct v2.22

    Please see my reply to your posts made elsewhere
  6. perfectpassion

    Protx Direct v2.22

    Have you added the IP to the correct SagePay admin? There are 3 admin areas - one each for simulator, test and live
  7. perfectpassion

    Protx Direct v2.22

    Not sure what's causing the centering problem then but I do know that anwer to the telephone number problem - it's a bug at the Protx end introduced when they upgraded the protocol from 2.22 to 2.23 - they have accepted the bug and are working on a fix so watch this space!
  8. perfectpassion

    Protx Direct v2.22

    Not sure what's causing the centering problem then but I do know that anwer to the telephone number problem - it's a bug at the Protx end introduced when they upgraded the protocol from 2.22 to 2.23 - they have accepted the bug and are working on a fix so watch this space!
  9. perfectpassion

    Is there a way to save information entered in a payment module

    However you may only do that if you have a secured, dedicated server and are pci dss compliant
  10. perfectpassion

    Protx Direct v2.22

    Hmm - it should be centered on the screen regardless of the page position behind it - in face you should be able to scroll the page behind and the thickbox remain centered - it's almost certainly an IE bug issue though the thickbox js has some clever code to change its working dependent upon each different IE version. Can you just check that you've changed the DOCTYPE for checkout_confirmation as per the install instructions - if this isn't correct it pushes IE7 into quirks mode and it does strange things to the rendering of the thickbox.
  11. perfectpassion

    Protx Direct v2.22

    Protx (sorry SagePay) require a 2 character state code for US addresses but osC obviosuly takes the full state name during signup so the module looks up the 2 digit state code from the osc table 'zones' The relevent code is: if (ACCOUNT_STATE == 'true' && $order->delivery['country']['iso_code_2'] == 'US' ) { $state_code_query = tep_db_fetch_array(tep_db_query("SELECT zone_code FROM ".TABLE_ZONES." WHERE zone_id=".(int)$order->delivery['zone_id'])); $del_state = $state_code_query['zone_code']; } if (ACCOUNT_STATE == 'true' && $order->billing['country']['iso_code_2'] == 'US' ) { $state_code_query = tep_db_fetch_array(tep_db_query("SELECT zone_code FROM ".TABLE_ZONES." WHERE zone_id=".(int)$order->billing['zone_id'])); $bil_state = $state_code_query['zone_code']; } If you coudl check your zones table that the state names/codes etc look ok that'll help
  12. perfectpassion

    Protx Direct v2.22

    BillingState is a required field only for US addresses - I did a few tests with fake US addresses and they seemed ok - I'll do a few more tests and see if I can figure it out
  13. perfectpassion

    Protx Direct v2.22

    http://www.sagepay.com/developers/integrat..._simulator.html will explain all the settings for you better than I would
  14. perfectpassion

    Protx Direct v2.22

    Everything appears in the thickbox - declines/ 3D-secure etc - you can test against the Protx simulator to see the full range and to test the 3D-Secure. With regards to the security box what browser are you using - I had a report of someone with an early version of IE6 that got that error but I haven't replicated myself (and it doesn't happen on your site with FF3)
  15. perfectpassion

    Help Please! Im really stuck

    He's found the correct support thread and we've sorted it now :)
  16. perfectpassion

    Protx Direct v2.22

    Glad to hear it's working - you might have difficulty finding the transaction on a SECPAY backend though!
  17. perfectpassion

    Protx Direct v2.22

    Ok - You've missed out a line. <link rel="stylesheet" href="<?php echo DIR_WS_INCLUDES;?>thickbox.css" type="text/css" media="screen" /> That needs adding in the <head> </head> section of checkout_confirmation.php
  18. perfectpassion

    Protx Direct v2.22

    can you PM me a link to your site so I can look?
  19. perfectpassion

    Protx Direct v2.22

    V3.0 to v5.1 is a big jump and whould hav ebeen better on a test site first. Ok, so you are getting a popup - is this the "thickbox" -i.e. white box and rest of screen greyed out? IF so and it's blank then please set debug to true in the module admin setting - do a test transactions and post the debug here minus any sensitive information
  20. perfectpassion

    Brand new SagePay payment module and gateway

    Probably best posted in the feedback forum: http://forums.oscommerce.com/index.php?showforum=14
  21. perfectpassion

    Protx Direct v2.22

    I'm sorry but this is the wrong thread - this thread is for Protx DIRECT module. I do not know anything about the form module so cannot help - sorry :-(
  22. perfectpassion

    Protx Direct v2.22

    that function was included as some (busy) sites were finding the transactions weren't matching up with the orders in admin due to incorrect order_id Your problem suggests that the $this->protx_id is missing which is strange because if that was missing then the whole transaction would normally fail with a different error message. I'll have a look into it but it works as expected on standard installs
  23. perfectpassion

    Protx Direct v2.22

    I thought I'd post Protx's email here for those that may not have received it:
  24. perfectpassion

    Protx Direct v2.22

    v5 was released in october so it's likely it will be v4.4 instead - upgrading from v4.4 to v5 requires a little bit more work than just dropping the files in but the instructions are included and quite straightforward.
  25. perfectpassion

    Protx Direct v2.22

    Personally I'm not updating my live store yet but will be watching transactions carefully on the day and then perform the update in a few days i things seem ok however if it grinds to ahalt I've got the new module ready - its simply a case of overwriting the existing file with the new (assuming you are currently using a v5 version of the module)
×