1. 06 Apr, 2019 1 commit
  2. 29 Mar, 2019 1 commit
  3. 13 Dec, 2018 1 commit
  4. 29 Oct, 2018 1 commit
    • Andrew Hunt's avatar
      CRM-14098 Membership reminders: don't exclude people who inherit other memberships (#12510) · bb3ba83e
      Andrew Hunt authored
      * CRM-14098 Membership reminders: don't exclude people who inherit other memberships
      
      * Membership reminders: test had two reminders with same name, differing params
      
      * CRM-14098 Membership reminders: test for inherited members
      
      ----------------------------------------
      * CRM-14098: Scheduled reminders silently skipped for contacts with a non-permissioned relationship associated with ANY inherited membership type
        https://issues.civicrm.org/jira/browse/CRM-14098
      
      * Membership reminders: comments to document some shaky assumptions
      
      * CRM-14098 Membership reminders: fix relies on joins, causing DB error on repeat
      
      * CRM-14098 Membership reminders: missing alias on date field
      
      * CRM-14098 Reminders test: explicitly make emails primary
      bb3ba83e
  5. 19 Apr, 2018 1 commit
    • totten's avatar
      (NFC) Update version in header · fee14197
      totten authored
      This is a simple administrative update to the headers. It was generated with the command:
      
      ```
      rgrep '| CiviCRM version 4.7' CRM/ Civi ang api bin extern install/ settings/ templates -l \
        | xargs sed -i'' "s/| CiviCRM version 4.7/| CiviCRM version 5  /g"
      ```
      
      Tthe inclusion of `|` aimed to avoid matching any non-header text (e.g. inline docs that
      mentioned the version incidentally). But then I did a looser search and for just
      
      ```
      rgrep 'CiviCRM version 4.7'
      ````
      
      and manually patched the remainder.
      
      Note: I'm not really keen on doing this every month, so I relaxed the header
      statement -- instead of `CiviCRM version 5.0`, it's just `CiviCRM version 5`.
      fee14197
  6. 23 Feb, 2018 1 commit
  7. 11 Feb, 2018 1 commit
  8. 15 Jul, 2017 1 commit
  9. 06 May, 2017 1 commit
  10. 07 Mar, 2017 1 commit
    • totten's avatar
      CRM-20224 - Civi\ActionSchedule\Events - Rename internal events... · fa6fce2f
      totten authored
      CRM-20224 - Civi\ActionSchedule\Events - Rename internal events (`actionSchedule.fooBar` vs `civi.actionSchedule.fooBar`)
      
      If you look at the list of events emitted through the EventDispatcher, you'll
      find several different formats for the names:
      
      ```
         actionSchedule.getMappings
         actionSchedule.prepareMailingQuery
         api.authorize
         api.exception
         api.prepare
         api.resolve
         api.respond
         civi.core.install
         civi.token.eval
         civi.token.list
         civi.token.render
         DAO::post-delete
         DAO::post-insert
         DAO::post-update
         hook_civicrm_caseChange
         hook_civicrm_post::Activity
         hook_civicrm_post::Case
         hook_civicrm_unhandled_exception
      ```
      
      This patch renames events using the `actionSchedule.fooBar` convention.  Based on
      grepping universe, I don't believe any extensions rely on the `DAO::*`
      events.
      fa6fce2f
  11. 02 Jan, 2017 1 commit
  12. 14 Sep, 2016 1 commit
  13. 19 May, 2016 1 commit
  14. 04 Apr, 2016 1 commit
  15. 21 Mar, 2016 1 commit
  16. 27 Jan, 2016 2 commits
  17. 24 Oct, 2015 1 commit
  18. 23 Oct, 2015 1 commit
  19. 01 Oct, 2015 1 commit
  20. 27 Sep, 2015 15 commits