1. 25 Aug, 2014 1 commit
  2. 22 Aug, 2014 3 commits
  3. 21 Aug, 2014 4 commits
  4. 18 Aug, 2014 1 commit
  5. 15 Aug, 2014 2 commits
  6. 14 Aug, 2014 2 commits
  7. 13 Aug, 2014 2 commits
  8. 08 Aug, 2014 3 commits
  9. 07 Aug, 2014 5 commits
  10. 05 Aug, 2014 2 commits
  11. 01 Aug, 2014 2 commits
  12. 31 Jul, 2014 9 commits
  13. 30 Jul, 2014 4 commits
    • Resolve failing tests by partially reverting Jason's work · 58089fb0
      lms/djangoapps/courseware/access.py has a complicated return value on line 336
      introduced by Jason in January - presumably as part of getting anonymous user
      access working. The unit tests in
      lms/djangoapps/courseware/tests/test_access.py have changed and this line now
      makes the tests (which pass upstream) fail.
      
      Until I understand how to fix it properly, changing this line to always return
      True makes the tests pass (though I don't yet understand if it breaks anonymous
      user access.)
      Joe Blaylock committed
    • Fixing more tests? · 79f89d5e
      Joe Blaylock committed
    • User registration prevents using password as username. · 36b596e2
      Some users erroneously set their password as their username with the original layout, because the username field directly followed the password field. Users may be accustomed to the common occurrence of a password confirmation field directly following the password field.
      To fix the issue, I did the following:
         - Moved the existing username and real name form fields above the password field.
         - Added a validation in the create_account handler in common/djangoapps/student/views.py, which confirms that the password field does not match the username field.
      
      New tests created to check the added functionality.
      
      Conflicts:
      	common/djangoapps/student/tests/test_password_policy.py
      	lms/templates/register.html
      njdup committed
    • Resolving some test failures · a782c92c
      Joe Blaylock committed