1. 15 Jun, 2015 5 commits
  2. 16 Apr, 2014 1 commit
    • Yuliya Bozhko's avatar
      Move objectionable forms from view library (Bug #1298646) · 2df0d557
      Yuliya Bozhko authored
      
      
      So that we can later use them separately for artefact level access,
      and report artefacts separately from pages.
      
      When testing, everything should work as it worked before with
      reporting objectionable material.
      
      Also fixed "Creating default object from empty value" error
      when ActivityTypeObjectionable object is constructed.
      
      Change-Id: I6d95a5546b2425d9b522435da26902e420139d84
      Signed-off-by: default avatarYuliya Bozhko <yuliya.bozhko@totaralms.com>
      2df0d557
  3. 25 Nov, 2013 1 commit
  4. 06 Nov, 2013 1 commit
    • Robert Lyon's avatar
      Creation of new blocktype 'comment' (bug #1245679) · 441aa7f2
      Robert Lyon authored
      - allow the feedback to display in a block.
      
      Things to note:
      1) The feedback block is only to display view's comments on the
      view/view.php page and NOT on view/artefact.php page.
      
      2) When in edit mode (view/blocks.php) the feedback block just
      displays a 'holder' message
      
      3) When feedback block is on page the feedback does not display at
      base of page anymore and when one clicks the 'Place feedback' link the
      feedback form pops up over everything similar to how editing a block
      works.
      
      4) As the feedback block only works/displays on the view page I have
      not fully integrated all the stuff that feedback creates ie js/form
      into the blocktype. I have left the view/view.php to do the js and
      render form - and simply position the form on the page with js.
      
      This means that if js is off the edit form will still be in it's
      old place. I felt this was ok because if js is off and the form was
      in the block it could mean things been too squashy if there was lots
      of columns.
      
      Change-Id: I1edaa886c5a0df1f6feb24bcdd6d8878a833d673
      441aa7f2
  5. 25 Sep, 2012 1 commit
    • Hugh Davenport's avatar
      Add option to disable device detection · 109eb4a5
      Hugh Davenport authored
      
      
      Also add a few theme changes that allow some more
      features on small devices.
      - Printing links
      - Settings link in top right corner
      - Create/copy page/collection link
      - Edit/delete buttons
      - Remove group members button
      - Help icons
      - Administration link
      
      Also made the admin link show in full
      
      The items that are disabled when device detection is on
      and user is on a mobile device are:
      - TinyMCE editor
      - Adding new blocks to pages, this is now a non-js version
      - Dropdown menu's
      - Export functionality
      
      Bug #1052060
      
      Change-Id: I5a8fe3cf136bb0c3e76e50a2b3bc48179c675b6a
      Signed-off-by: default avatarHugh Davenport <hugh@catalyst.net.nz>
      109eb4a5
  6. 03 Sep, 2012 1 commit
  7. 29 Aug, 2012 1 commit
  8. 17 Aug, 2010 2 commits
  9. 04 Jul, 2010 1 commit
  10. 04 May, 2010 1 commit
  11. 12 Apr, 2010 1 commit
  12. 25 Mar, 2010 1 commit
  13. 24 Mar, 2010 1 commit
  14. 23 Mar, 2010 1 commit
  15. 02 Sep, 2009 1 commit
  16. 09 May, 2009 1 commit
  17. 02 Nov, 2008 1 commit