1. 22 Apr, 2016 1 commit
  2. 21 Apr, 2016 1 commit
  3. 15 Apr, 2016 1 commit
    • Reconcile double reverts · 60fab86f
      Resolves conflicts between reverts of pattern library test pages and multi-site comprehensive theming, and the re-introduction of pattern library test pages. Fixes a pipeline rendering test which relied on other tests updating assets. The test now ensures that static assets are available before running.
      Andy Armstrong committed
  4. 14 Apr, 2016 2 commits
  5. 12 Apr, 2016 1 commit
  6. 11 Apr, 2016 1 commit
    • Introduce Pattern Library test pages (take two) · 9290c52b
      FEDX-93
      
      These are developer only pages, so can not be seen in production
      environment. On devstack, you can access these pages in LMS and
      Studio at:
      
          /template/ux/reference/pattern-library-test.html
      
      This is the second attempt to enable the Pattern Library. The
      first attempt broke Django Templates and didn't work correctly
      with right-to-left styling.
      Andy Armstrong committed
  7. 08 Apr, 2016 4 commits
    • Revert "Introduce Pattern Library test pages" · 4671970f
      This reverts commit 845e3708.
      Brian Jacobel committed
    • Revert "Introduce Pattern Library test pages" · 36917398
      This reverts commit 845e3708.
      Brian Jacobel committed
    • Course Updates date validation · 2735fdc2
      TNL-4115. Previously, course updates (which are intended to be posted with
      dates, for sorting in the LMS) could be authored in studio with a valid
      date, nothing, or a random string as the "date" for the update. As there
      is no validation for this in studio, everything succeeded with no warning.
      
      However, the LMS has problems parsing some of these values, and barfs when
      loaded by learners.
      
      The fix does two big things:
      - gracefully handles invalid dates in LMS. These updates are now treated as
      having a date of today, for sorting purposes.
      - turns on validation in studio. Now, it is not only impossible to enter
      invalid dates in studio, but notifications will draw the course author's
      eye if any invalid updates were previously saved.
      
      Test additions for this commit:
      
      Adds:
      - unit test for LMS parsing
      - Jasmine test to confirm invalid dates cannot be set by the user
          -also adds event to setAndValidate instead of using a global object
      - fix for lettuce test
          -It is no longer valid to enter the string "January 1, 2013" as this test
          had been doing. Keyed-in entries must use MM/DD/YY format.
      Eric Fischer committed
  8. 07 Apr, 2016 1 commit
  9. 06 Apr, 2016 1 commit
  10. 05 Apr, 2016 1 commit
  11. 04 Apr, 2016 2 commits
  12. 30 Mar, 2016 1 commit
  13. 29 Mar, 2016 1 commit
  14. 28 Mar, 2016 2 commits
    • Perform esacaping in the templates. · 39dc8a59
      Use new best practices.
      cahrens committed
    • saleem-latif/WL-328: Multi-Site Comprehensive Theming · a796b563
      ziafazal: improvements need for multi-tenancy
      ziafazal: fixed broken tests
      ziafazal: no need to add setting in test.py
      ziafazal: added hostname validation
      ziafazal: changes after feedback from mattdrayer
      ziafazal: fixed branding and microsite broken tests
      ziafazal: make STATICFILES_DIRS to list
      ziafazal: added theme directory to mako lookup for tests
      ziafazal: added more protection in test_util
      saleem-latif: Enable SCSS Overrides for Comprehensive Theming
      saleem-latif: Incoporate feedback changes, Correct test failures, add tests and enable theming for django templates
      saleem-latif: Correct errors in python tests
      mattdrayer: Fix invalid release reference
      mattdrayer: Update django-wiki reference to latest release
      saleem-latif: Update Theme storages to work with Caching, Pipeline and collectstatic
      saleem-latif: Incorporate feedback changes
      mattdrayer: Pylint violation fix
      mattdrayer: Fix broken pavelib test
      Zia Fazal committed
  15. 25 Mar, 2016 1 commit
    • Fix issues with Underscore in the asset pipeline · 6dd09a89
      FEDX-121
      
      The previous approach for handling NPM assets was
      to symlink them into the static directory. This appeared
      to cause trouble with the asset pipeline where the files
      in question were not installed and then old versions were
      picked up instead.
      
      This change instead copies NPM libraries to a new
      static directory so that the pipeline can consume them
      as with any other file. This new directory is added to
      .gitignore so that the files don't get accidentally
      checked in.
      Andy Armstrong committed
  16. 24 Mar, 2016 1 commit
  17. 23 Mar, 2016 1 commit
  18. 22 Mar, 2016 1 commit
  19. 21 Mar, 2016 1 commit
  20. 17 Mar, 2016 1 commit
  21. 16 Mar, 2016 3 commits
  22. 14 Mar, 2016 1 commit
    • ziafazal/WL-328: Multi-Site Comprehensive Theming · 954dae58
      ziafazal: improvements need for multi-tenancy
      ziafazal: fixed broken tests
      ziafazal: no need to add setting in test.py
      ziafazal: added hostname validation
      ziafazal: changes after feedback from mattdrayer
      ziafazal: fixed branding and microsite broken tests
      ziafazal: make STATICFILES_DIRS to list
      ziafazal: added theme directory to mako lookup for tests
      ziafazal: added more protection in test_util
      saleem-latif: Enable SCSS Overrides for Comprehensive Theming
      saleem-latif: Incoporate feedback changes, Correct test failures, add tests and enable theming for django templates
      saleem-latif: Correct errors in python tests
      mattdrayer: Fix invalid release reference
      mattdrayer: Update django-wiki reference to latest release
      Zia Fazal committed
  23. 10 Mar, 2016 1 commit
  24. 07 Mar, 2016 3 commits
  25. 03 Mar, 2016 1 commit
  26. 02 Mar, 2016 1 commit
  27. 29 Feb, 2016 2 commits
  28. 26 Feb, 2016 1 commit
  29. 24 Feb, 2016 1 commit