1. 08 Jan, 2016 1 commit
  2. 23 Dec, 2015 1 commit
  3. 11 Dec, 2015 1 commit
  4. 22 Nov, 2015 1 commit
  5. 26 Oct, 2015 1 commit
  6. 20 Jul, 2015 2 commits
  7. 08 Jul, 2015 1 commit
  8. 07 May, 2015 1 commit
  9. 06 May, 2015 1 commit
  10. 20 Feb, 2015 1 commit
  11. 04 Feb, 2015 2 commits
    • 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
  12. 15 Jan, 2015 3 commits
  13. 02 Dec, 2014 1 commit
  14. 01 Dec, 2014 2 commits
  15. 10 Nov, 2014 1 commit
  16. 09 Nov, 2014 1 commit
  17. 31 Oct, 2014 1 commit
  18. 11 Sep, 2014 1 commit
  19. 15 Jul, 2014 1 commit
    • Make text on register button on About page conditional. · aa1b6239
       Added a new advanced setting; invitation_only
      
       If invitation_only display "Enrollment in this course is by invitation only"
       Otherwise, if outside of enrollment period display "Enrollment is Closed"
      
       This issue is logged at LMS-2670
      
       Also fixed in this PR is issue LMS-2717; even though the Register button was greyed out,
       clicking it sent one to the registration page.
      David Adams committed
  20. 14 Jul, 2014 1 commit
  21. 02 Jun, 2014 1 commit
  22. 29 May, 2014 1 commit
  23. 24 May, 2014 2 commits
  24. 09 May, 2014 1 commit
  25. 06 May, 2014 1 commit
    • Make course ids and usage ids opaque to LMS and Studio [partial commit] · 9811926d
      This commit updates lms/djangoapps/courseware.
      
      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
  26. 30 Jan, 2014 1 commit
  27. 15 Dec, 2013 1 commit
  28. 13 Nov, 2013 1 commit
  29. 04 Nov, 2013 6 commits