1. 14 May, 2019 1 commit
  2. 11 Apr, 2019 1 commit
  3. 04 Apr, 2019 1 commit
  4. 01 Apr, 2019 1 commit
  5. 10 Jan, 2019 1 commit
  6. 19 Dec, 2018 1 commit
  7. 13 Dec, 2018 1 commit
  8. 15 May, 2018 1 commit
  9. 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
  10. 15 Feb, 2018 1 commit
  11. 28 Jan, 2018 1 commit
  12. 20 Dec, 2017 2 commits
  13. 17 Dec, 2017 1 commit
  14. 15 Dec, 2017 1 commit
  15. 26 Oct, 2017 1 commit
  16. 25 Oct, 2017 1 commit
  17. 24 Oct, 2017 1 commit
    • wmortada's avatar
      Fix the error message link · ac2b0d29
      wmortada authored
      It isn't necessary to build the link as docURL2() does this.  Also we don't need to check for the existence of the ts() function.
      ac2b0d29
  18. 19 Oct, 2017 1 commit
  19. 17 Oct, 2017 2 commits
  20. 12 Oct, 2017 1 commit
  21. 11 Oct, 2017 6 commits
  22. 27 Sep, 2017 1 commit
    • kcristiano's avatar
      CRM16421 CRM 17633: Changes to support WP in it's own directory. Allow for... · f553d1ea
      kcristiano authored
      CRM16421 CRM 17633: Changes to support WP in it's own directory. Allow for civicrn.settings.extra.php for WP. Create template for civicrm.settings.extra.php. Update install/civicrm.php for all needed params for different common install scenarios. Fix linting issues in civicrm.php.
      CRM 16421 CRM 17633 - update CRM_Utils_System_WordPress to allow for common install configurations
      
      CRM-16421 - Convert constants to `$civicrm_paths`
      
      Following up on the discussion from
      [#10513](https://github.com/civicrm/civicrm-core/pull/10513), this converts
      the proposed constants `CIVICRM_UF_WP_BASEURL` and `CIVICRM_UF_ADMINURL` to
      variables in the `Paths` system.
      
      A few benefits:
       * Reduces code duplication between `civicrm.php` and `WordPress.php`.
       * Can construct sub-paths with prettier notation (`Civi::paths()->getUrl('[wp.frontend]/foo.txt')`)
       * Has options to output relative or absolute URLs
       * Can expand on `Paths` to provide more inspection/validation
      
      Notes:
      
       * `CIVICRM_UF_WP_BASEURL` => `wp.frontend.base`
       * `CIVICRM_UF_ADMINURL` => `wp.backend.base`
      
      ----------------------------------------
      * CRM-16421: Work to get CiviCRM for WordPress in WordPress' official Repository
        https://issues.civicrm.org/jira/browse/CRM-16421
      
      CRM-16421 - Assimilate `civicrm.settings.extra.php` into `civicrm.settings.php`
      
      ----------------------------------------
      * CRM-16421: Work to get CiviCRM for WordPress in WordPress' official Repository
        https://issues.civicrm.org/jira/browse/CRM-16421
      
      CRM-17633 merge current master changes to civicrm.settings.php.template
      f553d1ea
  23. 04 Sep, 2017 2 commits
  24. 03 Aug, 2017 2 commits
  25. 08 Jul, 2017 2 commits
  26. 24 Jun, 2017 2 commits
  27. 23 Jun, 2017 1 commit
    • totten's avatar
      CRM-20768 - install - Accept mysql port · 6a511829
      totten authored
      == Background ==
      
      In previous releases, the web-based installation script allowed you to enter
      the MySQL "server" with a `host:port` combination (e.g.  `127.0.0.1:3307`).
      
      I believe this regressed during the mysql=>mysqli transition.
      
      == Before ==
      
      If you use the web-based install UI and enter a `host:port` combination, the
      error messages indicate a confusing mix of information (e.g.  some
      indicating port 3306, some indicating port 3307).
      
      == After ==
      
      If you use the web-based install UI and enter a `host:port` combination, it
      uses the specified port.
      
      ----------------------------------------
      * CRM-20768: Web-based installation should accept non-standard MySQL port
        https://issues.civicrm.org/jira/browse/CRM-20768
      6a511829
  28. 20 Jun, 2017 1 commit
    • bgm's avatar
      CRM-16395: Installation with localized default settings (4) (#10518) · ece6501c
      bgm authored
      CRM-16395: Installation with localized default settings
      
      This makes it possible to have a file in "civicrm/l10n/xx_YY/settings.default.json" with default settings that correspond to the locale during installation (ex: default country, currency, date formats, etc).
      ece6501c
  29. 21 May, 2017 1 commit