1. 05 Jun, 2015 1 commit
  2. 02 Jun, 2015 1 commit
  3. 29 May, 2015 1 commit
  4. 26 May, 2015 1 commit
  5. 13 May, 2015 1 commit
  6. 12 May, 2015 1 commit
  7. 07 May, 2015 1 commit
  8. 17 Apr, 2015 1 commit
  9. 23 Mar, 2015 5 commits
  10. 17 Mar, 2015 3 commits
  11. 14 Mar, 2015 3 commits
  12. 09 Mar, 2015 1 commit
  13. 06 Mar, 2015 1 commit
  14. 05 Mar, 2015 1 commit
  15. 03 Mar, 2015 1 commit
    • Fix issues with duplicate discussion targets. · 639ab0dc
      When two or more instances of Discussion XBlock were configured
      with the same discussion target (Category/Subcategory),
      only one of the blocks would be shown on the Course Discussion page.
      This was the source of several bugs when trying to edit discussion threads.
      
      This patch adds incrementing numbers to the title of each duplicate
      subcategory when rendering the Course Discussion to make sure that
      all of the threads are visible in Course Discussion.
      Matjaz Gregoric committed
  16. 27 Feb, 2015 1 commit
  17. 26 Feb, 2015 1 commit
  18. 25 Feb, 2015 2 commits
  19. 17 Feb, 2015 1 commit
  20. 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
  21. 06 Jan, 2015 1 commit
  22. 26 Dec, 2014 1 commit
  23. 11 Dec, 2014 1 commit
  24. 10 Dec, 2014 1 commit
  25. 05 Dec, 2014 2 commits
  26. 02 Dec, 2014 2 commits
  27. 01 Dec, 2014 2 commits