1. 23 Sep, 2015 1 commit
  2. 22 Sep, 2015 1 commit
  3. 17 Sep, 2015 1 commit
  4. 06 Aug, 2015 1 commit
  5. 28 Jul, 2015 1 commit
  6. 01 Jul, 2015 1 commit
  7. 12 Jun, 2015 1 commit
  8. 10 Jun, 2015 1 commit
  9. 08 Jun, 2015 1 commit
  10. 06 Jun, 2015 1 commit
  11. 01 Jun, 2015 2 commits
  12. 28 May, 2015 1 commit
    • ECOM-1339 Branding API footer · 6af5fc14
      Serve branded footer JSON/HTML/CSS/JS from an API endpoint
      in the branding app.  Refactor OpenEdX and EdX.org footer templates
      to use the Python version of the API, ensuring that the API
      values are consistent with the footer included in main.html.
      
      Detailed changes:
      
      * Added footer API end-point to the branding app.
      * Footer API allows the language to be set with querystring parameters.
      * Footer API allows showing/hiding of the OpenEdX logo using querystring parameters.
      * Deprecate ENABLE_FOOTER_V3 in favor of the branding API configuration flag.
      * Move no referrer script into main.html from the edx footer template.
      * Rename rwd_header_footer.js to rwd_header.js
      * Cache API responses.
      
      Authors:
      Awais Qureshi, Aamir Khan, Will Daly
      Will Daly committed
  13. 07 May, 2015 1 commit
  14. 14 Apr, 2015 1 commit
  15. 23 Mar, 2015 1 commit
  16. 17 Mar, 2015 2 commits
  17. 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
  18. 28 Jan, 2015 1 commit
  19. 15 Jan, 2015 1 commit
  20. 09 Jan, 2015 3 commits
  21. 15 Dec, 2014 1 commit
  22. 12 Dec, 2014 1 commit
  23. 02 Dec, 2014 1 commit
  24. 01 Dec, 2014 1 commit
  25. 30 Nov, 2014 1 commit
  26. 04 Nov, 2014 1 commit
  27. 16 Sep, 2014 1 commit
  28. 22 Aug, 2014 1 commit
  29. 06 Aug, 2014 1 commit
  30. 04 Aug, 2014 1 commit
  31. 10 Jul, 2014 2 commits
  32. 26 Jun, 2014 1 commit
  33. 22 May, 2014 1 commit
  34. 09 May, 2014 1 commit