1. 29 Nov, 2017 1 commit
  2. 20 Nov, 2017 1 commit
    • Avoid a django breaking change: set_language response code · bff8c082
      In Django 1.10+, the set_language view (/i18n/setlang) will respond to
      Ajax requests which do not contain a "next" parameter with status 204 No
      Content instead of 304.  This commit adds the "next" parameter to the
      request in order to ensure that upgrading to Django 1.10+ will not cause
      the set_language view to change behavior.
      
      PLAT-1353
      Troy Sankey committed
  3. 25 Oct, 2017 1 commit
  4. 06 Oct, 2017 2 commits
  5. 05 Oct, 2017 2 commits
  6. 13 Sep, 2017 1 commit
  7. 29 Aug, 2017 1 commit
    • Add social links to learner profile. · 9f88427f
      LEARNER-1859
      
      Added fields to add social links to the user account settings file.
      Added icons to the user profile when these links are set, only shown
      when users show their entire profile. Added jasmine tests for account
      settings and learner profile pages. Added python unit tests to test
      validation on the user account.
      Harry Rein committed
  8. 24 Aug, 2017 1 commit
  9. 22 Aug, 2017 6 commits
  10. 21 Aug, 2017 1 commit
  11. 15 Aug, 2017 1 commit
  12. 14 Aug, 2017 1 commit
  13. 09 Aug, 2017 1 commit
  14. 03 Aug, 2017 1 commit
  15. 02 Aug, 2017 1 commit
    • Implement client-side registration form validation. · cb034d4f
      Input forms that need validation will have AJAX requests
      performed to get validation decisions live.
      
      All but a few important and common form fields perform
      generic validation; these will need a back-end handler
      in the future in order to have them validated through AJAX requests.
      
      Information is conveyed on focus and blur for both
      errors and successes.
      Uman Shahzad committed
  16. 18 Jul, 2017 2 commits
  17. 14 Jul, 2017 1 commit
  18. 22 Jun, 2017 1 commit
  19. 21 Jun, 2017 1 commit
  20. 16 Jun, 2017 1 commit
  21. 13 Jun, 2017 1 commit
  22. 06 Jun, 2017 1 commit
  23. 05 Jun, 2017 3 commits
  24. 29 May, 2017 1 commit
  25. 22 May, 2017 2 commits
  26. 19 May, 2017 1 commit
  27. 16 May, 2017 1 commit
    • Handle expired enrollments on the program detail page · 5314784a
      Learners should be able to enroll in future runs of courses in which they have an expired enrollment. Previously, the course card model populated itself by selecting the first course run in which the user was enrolled. When the user tried to enroll in another run, nothing would happen because they were already enrolled in the run the page was trying to enroll them in.
      
      Instead of blindly choosing the first run in which the user is enrolled, we now fall through to the same behavior we use for courses in which the user is not enrolled when the user has expired enrollments.
      
      LEARNER-933
      Renzo Lucioni committed
  28. 15 May, 2017 1 commit
  29. 03 May, 2017 1 commit