1. 31 Mar, 2015 1 commit
  2. 26 Mar, 2015 1 commit
  3. 20 Mar, 2015 1 commit
  4. 18 Mar, 2015 1 commit
  5. 17 Mar, 2015 2 commits
  6. 13 Mar, 2015 2 commits
  7. 05 Mar, 2015 1 commit
  8. 27 Feb, 2015 1 commit
  9. 26 Feb, 2015 2 commits
  10. 25 Feb, 2015 2 commits
  11. 23 Feb, 2015 2 commits
  12. 20 Feb, 2015 2 commits
  13. 19 Feb, 2015 1 commit
  14. 18 Feb, 2015 1 commit
  15. 17 Feb, 2015 1 commit
  16. 13 Feb, 2015 1 commit
  17. 11 Feb, 2015 1 commit
  18. 10 Feb, 2015 1 commit
    • Country Access: block enrollment · e609f982
      Block users from enrolling in a course if the user
      is blocked by country access rules.
      
      1) Enrollment via the login/registration page.
      2) Enrollment from the marketing iframe (via student.views.change_enrollment)
      3) Enrollment using 100% redeem codes.
      4) Enrollment via upgrade.
      
      This does NOT cover enrollment through third party authentication,
      which is sufficiently complex to deserve its own commit.
      Will Daly committed
  19. 09 Feb, 2015 2 commits
  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. 03 Feb, 2015 1 commit
  22. 30 Jan, 2015 1 commit
    • Make logistration generally available if feature flag is active · a8bed5ce
      Makes logistration available at /login and /register as well as /accounts/login/ and /accounts/register/. In addition:
      
      - Adds support for redirect URLs in third party auth for combined login/registration page
      - Adds support for external auth on the combined login/registration page
      - Removes old login and registration acceptance tests
      - Adds deprecation warnings to old login and register views
      - Moves third party auth util to student_account
      - Adds exception for microsites (theming)
      Renzo Lucioni committed
  23. 29 Jan, 2015 1 commit
  24. 15 Jan, 2015 1 commit
  25. 13 Jan, 2015 1 commit
    • Enable redeem codes. · b1884306
      Update the redeem code schema
      
      Updating the redeem code schema.
      
      Adding migration file.
      
      Adding course mode support when redeeming a code.
      
      Conflicts:
      	lms/djangoapps/shoppingcart/views.py
      
      Add sales admin privileges for redeem code generation.
      
      Making sure redeem code URLs work for verified courses.
      
      pep8 violations
      
      Code Review and Test Cleanup changes
      
      Added tests, fixed tests.
      
      Updating the boolean checks in ecommerce template
      stephensanchez committed
  26. 12 Jan, 2015 2 commits
  27. 09 Jan, 2015 5 commits