1. 10 Apr, 2019 1 commit
  2. 09 Apr, 2019 1 commit
    • eileen's avatar
      Load hooks during upgrade mode · 62f662b0
      eileen authored
      For unknown, svn, reasons extension hooks are not loaded during upgrade
      (this doesn't apply to drupal modules) - this causes some fairly serious problems
      1) settings are re-loaded & cached with settings from extensions being lost
      2) trigger alter hooks are lost this means
       - the summary fields triggers are frequently lost on upgrade
       - hooks that unset various tables to prevent them from being logged can fail, resulting in those log tables being created
       - hooks that specify the table should be innodb can fail to run, resulting in archive format.
      
      I can't think WHY we do this? Presumably there was some problem that would have been better solved another
      way but which was solved this way?
      
      Fix "Load hooks during upgrade mode" (45312e1e64dd6af0281fe5fb7f96dbd8be39e524)
      
      In my testing, the commit doesn't do what it says because the symbols are wrong.
      62f662b0
  3. 05 Apr, 2019 1 commit
  4. 29 Dec, 2018 1 commit
  5. 13 Dec, 2018 1 commit
  6. 27 Jun, 2018 1 commit
  7. 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
  8. 23 Feb, 2018 1 commit
  9. 21 Oct, 2017 1 commit
    • totten's avatar
      CRM-16243 - Redundant installation should not throw error · ca29efdc
      totten authored
      Suppose we have two modules, `foo.core` and `foo.addon` (where `foo.addon`
      depends on `foo.core`).
      
      Now you suppose you try to install `foo.addon` twice, e.g.
      
      ```
      cv en foo.addon
      cv en foo.addon
      ```
      
      The first installation succeeds (and enables both modules as expected).
      However, the second installation throws an error: "Dependency foo.core not
      found, required by foo.addon"
      
      This adds a test and resolves the error.
      ca29efdc
  10. 09 Oct, 2017 7 commits
  11. 11 Jul, 2017 2 commits
  12. 04 Jul, 2017 1 commit
  13. 17 Jan, 2017 1 commit
  14. 10 Jan, 2017 1 commit
  15. 03 Jan, 2017 1 commit
  16. 02 Jan, 2017 1 commit
  17. 29 Sep, 2016 1 commit
  18. 26 Sep, 2016 1 commit
  19. 14 Sep, 2016 1 commit
  20. 03 May, 2016 1 commit
  21. 21 Mar, 2016 1 commit
  22. 15 Feb, 2016 1 commit
  23. 04 Feb, 2016 1 commit
  24. 03 Feb, 2016 1 commit
  25. 05 Dec, 2015 1 commit
  26. 30 Oct, 2015 1 commit
  27. 26 Oct, 2015 1 commit
  28. 21 Oct, 2015 1 commit
  29. 12 Oct, 2015 1 commit
  30. 11 Oct, 2015 1 commit
  31. 17 Sep, 2015 3 commits