Skip to content
Snippets Groups Projects
  1. Sep 30, 2016
  2. Aug 17, 2016
  3. Aug 15, 2016
  4. Dec 18, 2015
  5. Nov 19, 2015
  6. Nov 17, 2015
  7. Oct 09, 2015
  8. Oct 07, 2015
  9. Sep 09, 2015
  10. Jan 23, 2015
  11. Jan 17, 2015
  12. Jan 12, 2015
  13. Jan 10, 2015
  14. Jan 09, 2015
  15. Oct 30, 2014
  16. Oct 09, 2014
  17. Oct 01, 2014
  18. Sep 24, 2014
  19. Apr 01, 2014
    • drastik's avatar
      Trying to solve: · 021e9a6d
      drastik authored
      Strict warning: Declaration of CRM_Core_Payment_Stripe::singleton() should be
      compatible with & CRM_Core_Payment::singleton().
      
      And:
      Strict warning: Accessing static property CRM_Core_Payment_Stripe::$_mode as
      non static in CRM_Core_Payment_Stripe->__construct().
      021e9a6d
  20. Feb 05, 2014
    • Joshua Walker's avatar
      PHP Doc comment cleanup · bd6681ab
      Joshua Walker authored
      bd6681ab
    • peterh's avatar
      Nicer formatting for error message. · 5c7aaf4b
      peterh authored
      5c7aaf4b
    • peterh's avatar
      Don't use livemode parameter. · 9d7b5ba3
      peterh authored
      Usually when we setup staging and test sites, we set the Stripe payment
      processor keys to use the test keys for both test payments and "live"
      payments. This lets us test things more realisticly. Unfortunately, because
      we are doing a "live" test, but using the Stripe test keys, the Stripe API
      fails with "Received unknown parameter: livemode".
      
      I think the CiviCRM Stripe payment processor should behave like all the other
      payment processors and work as expected if you use the test API keys as the
      "live" keys.
      9d7b5ba3
    • peterh's avatar
      Log all stripe errors. · ce90fd82
      peterh authored
      Usually when we setup staging and test sites, we set the Stripe payment
      processor keys to use the test keys for both test payments and "live"
      payments. This lets us test things more realisticly. This caused a problem
      with the Stripe extension where it was it was sending 'livemode' => true
      along with the 'create_plan' API call. This was causing the API call to fail
      with "Received unknown parameter: livemode", but because stripeCatchErrors
      ignores most errors the code was actually failing later on.
      
      To make problems with the Stripe API calls easier to debug in the future,
      we added some code to log all the exceptions when making Stripe calls and
      make sure that Civi crashes when these calls fail. That way the user knows
      that something went wrong with his transaction and he can inform the website
      owner.
      
      Sometimes, though we do expect an error from Stripe (like in the case where a
      subscription plan already exists, but it isn't in the local
      civicrm_stripe_subscriptions table). For that I've added an ignores parameter
      to the stripCatchErrors method that can be used to tell it to ignore very
      specific error messages, but still crash if we get an unexpected error.
      ce90fd82
  21. Jan 15, 2014
  22. Jan 10, 2014
  23. Dec 02, 2013
  24. Aug 11, 2012
  25. Aug 10, 2012
  26. Aug 06, 2012
  27. Aug 01, 2012
Loading