1. 17 Jun, 2016 1 commit
  2. 06 Jun, 2016 1 commit
  3. 26 May, 2016 1 commit
    • Bulk Email Multiselect (#12301) · a9a3fabf
      TNL-4356
      
      Allows multiple bulk email targets to be specified at once.
      
      -The previous "All" option has been split into "Staff" and "Learners"
      -The backend changes made here lay the groundwork for cohort emailing
      -The data migration, 0005, is somewhat large and requires deploy attention
      -Tests have been updated
      -Numerous safe-commit-linter fixes are included
      Eric Fischer committed
  4. 23 May, 2016 1 commit
  5. 13 May, 2016 1 commit
  6. 12 May, 2016 1 commit
  7. 20 Apr, 2016 1 commit
  8. 06 Apr, 2016 1 commit
  9. 31 Mar, 2016 1 commit
  10. 04 Dec, 2015 1 commit
  11. 22 Nov, 2015 1 commit
  12. 14 Oct, 2015 1 commit
  13. 31 Jul, 2015 1 commit
  14. 09 Jun, 2015 2 commits
  15. 11 May, 2015 1 commit
  16. 08 May, 2015 2 commits
  17. 15 Apr, 2015 1 commit
  18. 08 Apr, 2015 2 commits
  19. 06 Apr, 2015 1 commit
  20. 17 Mar, 2015 1 commit
  21. 23 Feb, 2015 2 commits
  22. 20 Feb, 2015 1 commit
  23. 18 Feb, 2015 1 commit
  24. 10 Feb, 2015 1 commit
  25. 11 Dec, 2014 1 commit
    • Implements keyword sub feature for bulk emails · 32bbb0e7
      This commit pulls in changes from #4487 that implements keyword
      substitution for bulk emails. With these changes, an instructor can
      include keywords in their bulk emails which will be automatically substituted
      with the corresponding value for the recepient of the email. Keywords are
      of the form %%keyword%%, and the keywords implemented in this commit include:
      
      %%USER_ID%% => anonymous_user_id
      %%USER_FULLNAME%% => user profile name
      %%COURSE_DISPLAY_NAME%% => display name of the course
      %%COURSE_END_DATE%% => end date of the course
      
      Client-side validations have also been implemented to ensure that only emails
      with well-formed keywords can be sent.
      The architecture is designed such that adding in new keywords in the future
      would be relatively straight-forward.
      njdup committed
  26. 01 Dec, 2014 2 commits
  27. 09 Oct, 2014 1 commit
  28. 08 Oct, 2014 1 commit
  29. 30 May, 2014 1 commit
  30. 29 May, 2014 1 commit
  31. 24 May, 2014 1 commit
  32. 23 May, 2014 1 commit
  33. 09 May, 2014 1 commit
  34. 08 May, 2014 1 commit
    • Make course ids and usage ids opaque to LMS and Studio [partial commit] · cd746bf8
      This commit adds the non-courseware lms/djangoapps and lms/lib.
      
      These keys are now objects with a limited interface, and the particular
      internal representation is managed by the data storage layer (the
      modulestore).
      
      For the LMS, there should be no outward-facing changes to the system.
      The keys are, for now, a change to internal representation only. For
      Studio, the new serialized form of the keys is used in urls, to allow
      for further migration in the future.
      
      Co-Author: Andy Armstrong <andya@edx.org>
      Co-Author: Christina Roberts <christina@edx.org>
      Co-Author: David Baumgold <db@edx.org>
      Co-Author: Diana Huang <dkh@edx.org>
      Co-Author: Don Mitchell <dmitchell@edx.org>
      Co-Author: Julia Hansbrough <julia@edx.org>
      Co-Author: Nimisha Asthagiri <nasthagiri@edx.org>
      Co-Author: Sarina Canelake <sarina@edx.org>
      
      [LMS-2370]
      Calen Pennington committed
  35. 24 Feb, 2014 1 commit