1. 22 Apr, 2009 7 commits
  2. 21 Apr, 2009 2 commits
  3. 14 Apr, 2009 1 commit
  4. 08 Apr, 2009 1 commit
  5. 07 Apr, 2009 16 commits
  6. 30 Mar, 2009 1 commit
  7. 25 Mar, 2009 1 commit
  8. 04 Mar, 2009 1 commit
  9. 18 Feb, 2009 1 commit
  10. 13 Feb, 2009 1 commit
  11. 09 Feb, 2009 2 commits
  12. 29 Jan, 2009 1 commit
    • Nigel McNie's avatar
      (#3063) Make blocktype configuration forms change if they are in a template. · d9f2144b
      Nigel McNie authored
      Now they do things like not making it compulsory to choose an artefact
      if it's a template (as the creator might just want to put the block
      there), and removing some options that only make sense in Views.
      There's a parameter for instance_config_form and artefactchooser_element
      to allow the Blocktype to detemine whether it's in a template easily.
  13. 09 Jan, 2009 1 commit
  14. 06 Jan, 2009 1 commit
    • Nigel McNie's avatar
      Allow blog, blogpost and textbox blocktypes having links or manually created... · 054e89d1
      Nigel McNie authored
      Allow blog, blogpost and textbox blocktypes having links or manually created <img> tags to artefacts to have those artefacts counted as being within the blocktype, and thus within the view.
      This is so if people manually link to or source artefacts within textual content, those artefacts will be downloadable when the view is shown to others.
      Not backporting to 1.0 although the problem will most certainly exist there - the patch is just too big to trust on a stable release.
  15. 18 Dec, 2008 1 commit
  16. 17 Dec, 2008 1 commit
    • Nigel McNie's avatar
      (#3063) Remove copy_allowed in favour of allowed_in_view. Also remove · 099dc5b3
      Nigel McNie authored
      copy_artefacts_allowed is unnecessary as it's only called if the copy
      type is 'full', and there's now no way that you would want to fully
      copy a block and not copy the artefacts inside it.
      Some other API tidyups have been done - default_artefact_config has been
      renamed to rewrite_blockinstance_config and had a method signature
      change to be a bit more flexible.
      The copyconfig field of the View object is gone too, no longer required.
  17. 16 Dec, 2008 1 commit
    • Nigel McNie's avatar
      (#3063) part 2: Hide blocktypes that don't make sense when making a · 7599ec0c
      Nigel McNie authored
      This means that blog/profile/resume blocktypes don't show up in
      group/institution/site Views.
      This is controlled through a new Blocktype method - allowed_in_view.
      Various code had to be changed to listen to this method, mostly around
      the display of the category browser.
      When making a template, all blocktypes are available.
      Part 3 is to change the configuration forms to be more sensible when
      editing a template, and then testing what happens when blocktypes are
      rendered somewhere that they "shouldn't" be - e.g. a My Friends block in
      a group View.