1. 25 Jul, 2018 1 commit
  2. 09 Jul, 2018 1 commit
    • Camilo Rodríguez's avatar
      CRM-21425: Add Permissions to Edit Inbound E-mails · ee90a98c
      Camilo Rodríguez authored
      The following permissions were added to CiviCRM core:
      
      - CiviCRM: edit inbound email basic information
      - CiviCRM: edit inbound email basic information and content
      
      Having any of these permissions will alow  user to edit inbound E-mails, but
      only the latter will allow users to also change the original email's content.
      
      E-mails downloaded and stored as Inbound Email activities were saving their
      details in two formats, as an ezComponents-parsed representation of
      a text with alternatives. These alternatives were being stripped on the
      Activity Form template, with the side effect of also stripping the textarea
      where the wysiwyg editor would be built upon.
      
      Fixed by stripping alternatives when preprocessing the quickform instead,
      before the html for the textarea is generated.
      ee90a98c
  3. 01 Jun, 2018 1 commit
  4. 06 May, 2018 1 commit
  5. 30 Apr, 2018 1 commit
  6. 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
  7. 28 Feb, 2018 1 commit
  8. 23 Feb, 2018 1 commit
  9. 19 Feb, 2018 1 commit
  10. 16 Feb, 2018 1 commit
  11. 14 Feb, 2018 1 commit
  12. 12 Jan, 2018 2 commits
  13. 26 Dec, 2017 1 commit
  14. 20 Dec, 2017 2 commits
  15. 14 Dec, 2017 1 commit
  16. 30 Nov, 2017 1 commit
  17. 21 Nov, 2017 1 commit
  18. 20 Nov, 2017 1 commit
  19. 07 Nov, 2017 2 commits
  20. 06 Sep, 2017 1 commit
    • totten's avatar
      CRM-20958 - Case, Activity BAOs - Watch out for saving stale timestamps · ea6a17a9
      totten authored
      There appears to be some application logic which follows a process like this:
      
       1. Read the case
       2. Tweak the data
       3. Save updated case
      
      The problem is comes if step #4 resaves a timestamp loaded in step #1, which
      is fairly likely to happen if you read+save the same record.
      
      This was specifically observed on the "Manage Case" screen when editing
      activities, but the data-flow is pretty common, so make a general fix to the
      BAO.
      ea6a17a9
  21. 15 Aug, 2017 1 commit
  22. 10 Aug, 2017 1 commit
  23. 23 Jul, 2017 1 commit
  24. 27 Jun, 2017 1 commit
  25. 30 May, 2017 1 commit
  26. 08 May, 2017 1 commit
  27. 27 Apr, 2017 2 commits
  28. 21 Apr, 2017 1 commit
  29. 16 Apr, 2017 2 commits
  30. 30 Mar, 2017 1 commit
  31. 29 Mar, 2017 1 commit
  32. 21 Mar, 2017 1 commit
  33. 14 Mar, 2017 3 commits