1. 06 Oct, 2015 1 commit
  2. 20 Aug, 2015 1 commit
    • In-course reverification access control · ec28a75f
      * Automatically create user partitions on course publish for each ICRV checkpoint.
      * Disable partitions for ICRV checkpoints that have been deleted.
      * Skip partitions that have been disabled when checking access.
      * Add verification access control UI to visibility settings.
      * Add verification access control UI to sequential and vertical settings.
      * Add partition scheme for verification partition groups.
      * Cache information used by verification partition scheme and invalidate the cache on update.
      * Add location parameter to UserPartition so the partition scheme can find the associated checkpoint.
      * Refactor GroupConfiguration to allow multiple user partitions.
      * Add special messaging to ICRV for students in the honor track.
      
      Authors: Zubair Arbi, Awais Qureshi, Aamir Khan, Will Daly
      zubair-arbi committed
  3. 28 Jul, 2015 1 commit
    • Allow users to submit initial verification at in-course checkpoints. · 47b81c92
      * Combine verification and reverification photo submission end-points.
      * Combine verification and reverification Backbone models.
      * Allow deletion of verification status in Django admin.
      * Initial verification from a checkpoint is associated with the checkpoint.
      * Fix critical bug in which an invalid link was sent to Software Secure
        for the photo ID image of reverification attempts.
      Will Daly committed
  4. 21 Jul, 2015 1 commit
    • Separate verification deadline from upgrade deadline · 25fa2ffc
      * Add verification deadline model.
      * Populate verification deadlines from course modes table.
      * Update student dashboard to use verification deadlines.
      * Update pay-and-verify view to use verification deadlines.
      * Simplify Django admin for course modes and add validation.
      * Add verification deadline to Django admin for course modes.
      * Add UI for when the upgrade deadline is missed in the pay-and-verify flow.
      Will Daly committed
  5. 13 Jul, 2015 1 commit
  6. 01 Jun, 2015 1 commit
  7. 27 May, 2015 1 commit
  8. 07 May, 2015 1 commit
  9. 05 May, 2015 1 commit
  10. 29 Apr, 2015 2 commits
  11. 02 Apr, 2015 1 commit
  12. 17 Mar, 2015 1 commit
  13. 14 Mar, 2015 1 commit
  14. 04 Feb, 2015 1 commit
    • Better support specifying of modulestore configuration in test cases · b353ed2e
      The existing pattern of using `override_settings(MODULESTORE=...)` prevented
      us from having more than one layer of subclassing in modulestore tests.
      
      In a structure like:
      
          @override_settings(MODULESTORE=store_a)
          class BaseTestCase(ModuleStoreTestCase):
              def setUp(self):
                  # use store
      
          @override_settings(MODULESTORE=store_b)
          class ChildTestCase(BaseTestCase):
              def setUp(self):
                  # use store
      
      In this case, the store actions performed in `BaseTestCase` on behalf of
      `ChildTestCase` would still use `store_a`, even though the `ChildTestCase`
      had specified to use `store_b`. This is because the `override_settings`
      decorator would be the innermost wrapper around the `BaseTestCase.setUp` method,
      no matter what `ChildTestCase` does.
      
      To remedy this, we move the call to `override_settings` into the
      `ModuleStoreTestCase.setUp` method, and use a cleanup to remove the override.
      Subclasses can just defined the `MODULESTORE` class attribute to specify which
      modulestore to use _for the entire `setUp` chain_.
      
      [PLAT-419]
      Calen Pennington committed
  15. 20 Jan, 2015 1 commit
  16. 02 Dec, 2014 2 commits
  17. 04 Nov, 2014 1 commit
  18. 29 Sep, 2014 1 commit
  19. 29 May, 2014 1 commit
  20. 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
  21. 10 Feb, 2014 1 commit
  22. 31 Jan, 2014 4 commits
  23. 31 Oct, 2013 1 commit
  24. 29 Oct, 2013 2 commits
  25. 07 Oct, 2013 1 commit
  26. 12 Sep, 2013 1 commit
  27. 21 Aug, 2013 3 commits
  28. 15 Aug, 2013 1 commit