Skip to content
Snippets Groups Projects
  1. Oct 09, 2014
  2. Oct 08, 2014
  3. Oct 07, 2014
  4. Oct 06, 2014
  5. Oct 02, 2014
  6. Oct 01, 2014
  7. Sep 24, 2014
  8. Aug 21, 2014
  9. Jul 01, 2014
  10. May 05, 2014
  11. May 01, 2014
  12. 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
  13. Mar 07, 2014
  14. Feb 05, 2014
    • Joshua Walker's avatar
      PHP Doc comment cleanup · bd6681ab
      Joshua Walker authored
      bd6681ab
    • Joshua Walker's avatar
      Merge pull request #35 from giant-rabbit/4.4-1.8 · 50183ee1
      Joshua Walker authored
      Log all stripe errors.
      50183ee1
    • 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
Loading