1. 23 Mar, 2015 4 commits
  2. 09 Mar, 2015 1 commit
  3. 05 Mar, 2015 1 commit
  4. 03 Mar, 2015 1 commit
    • Fix issues with duplicate discussion targets. · 639ab0dc
      When two or more instances of Discussion XBlock were configured
      with the same discussion target (Category/Subcategory),
      only one of the blocks would be shown on the Course Discussion page.
      This was the source of several bugs when trying to edit discussion threads.
      
      This patch adds incrementing numbers to the title of each duplicate
      subcategory when rendering the Course Discussion to make sure that
      all of the threads are visible in Course Discussion.
      Matjaz Gregoric committed
  5. 26 Feb, 2015 1 commit
  6. 25 Feb, 2015 2 commits
  7. 05 Dec, 2014 1 commit
    • Add support for user partitioning based on cohort. · f24f01d2
      JIRA: TNL-710
      
      IMPORTANT: this commit converts the course_groups
      package to using migrations.  When deploying to an
      existing openedx instance, migration 0001 may fail
      with an error indicating that the CourseUserGroup
      table already exists.  If this happens, running
      the 0001 migration first, with the --fake option,
      is recommended.  After performing this step,
      remaining migrations should work as expected.
      jsa committed
  8. 25 Nov, 2014 1 commit
  9. 08 Oct, 2014 3 commits
  10. 03 Oct, 2014 1 commit
  11. 24 Sep, 2014 1 commit
  12. 12 Sep, 2014 1 commit
  13. 10 Sep, 2014 1 commit
  14. 04 Sep, 2014 1 commit
  15. 29 Aug, 2014 3 commits
  16. 08 Aug, 2014 1 commit
  17. 11 Jul, 2014 2 commits
  18. 30 Jun, 2014 1 commit
  19. 29 May, 2014 1 commit
  20. 08 May, 2014 1 commit
    • Make course ids and usage ids opaque to LMS and Studio [partial commit] · cd746bf8
      This commit adds the non-courseware lms/djangoapps and lms/lib.
      
      These keys are now objects with a limited interface, and the particular
      internal representation is managed by the data storage layer (the
      modulestore).
      
      For the LMS, there should be no outward-facing changes to the system.
      The keys are, for now, a change to internal representation only. For
      Studio, the new serialized form of the keys is used in urls, to allow
      for further migration in the future.
      
      Co-Author: Andy Armstrong <andya@edx.org>
      Co-Author: Christina Roberts <christina@edx.org>
      Co-Author: David Baumgold <db@edx.org>
      Co-Author: Diana Huang <dkh@edx.org>
      Co-Author: Don Mitchell <dmitchell@edx.org>
      Co-Author: Julia Hansbrough <julia@edx.org>
      Co-Author: Nimisha Asthagiri <nasthagiri@edx.org>
      Co-Author: Sarina Canelake <sarina@edx.org>
      
      [LMS-2370]
      Calen Pennington committed
  21. 19 Mar, 2014 1 commit
  22. 13 Feb, 2014 1 commit
    • Check for forum data errors in LMS · 9ae6bb0b
      Some messages generated by the comments service are not readily
      translated because they come from third-party libraries. Thus, we plan
      to try to avoid showing any comments service generated message to the
      user. This check preempts the only end-user-visible CS-generated error
      message that we are presently aware of.
      Greg Price committed
  23. 31 Jan, 2014 1 commit
    • Make mako template lookups pluggable. · 0a1ed11d
      This code adds the ability to add Mako template lookup directories on
      the fly, allowing third party add-ons to contribute their own Mako templates.
      A new API function for registering Mako templates is introduced::
      
          from edxmako import add_lookup
      
          add_lookup('main', '/path/to/templates')
      
          # Or, specify a package to lookup using pkg_resources.  This will
          # add the 'templates' directory inside the current package:
          add_lookup('main', 'templates', package=__name__)
      Chris Rossi committed
  24. 30 Jan, 2014 1 commit
  25. 14 Jan, 2014 1 commit
  26. 12 Dec, 2013 1 commit
  27. 10 Dec, 2013 1 commit
  28. 03 Dec, 2013 1 commit
  29. 01 Nov, 2013 1 commit
    • Remove label from forum posts by global staff · c4cdb457
      The motivation for this change is performance. The forums UI code gets
      the list of users for each role and renders the staff label based on
      those lists. The list for the staff role is expensive to compute because
      there is no index on the is_staff attribute, and we cannot create one
      because the User model is built into django.
      
      Users with is_staff=True are still assigned the Moderator role upon
      enrolling in a course, so this change will have no practical effect
      except that a user who is granted staff privileges after enrolling in a
      course will have to be made a Moderator in order for their posts to be
      labeled.
      
      Additionally, the UI did not use the list of users with the Student
      role, so that list has been removed as well.
      Greg Price committed
  30. 30 Oct, 2013 1 commit
  31. 28 Oct, 2013 1 commit