1. 08 Oct, 2013 1 commit
    • Aaron Wells's avatar
      Update session-cached display name when deleting it · 8f189300
      Aaron Wells authored
      
      
      Bug 1223063: ArtefactTypeCachedProfileField was only updating
      the session cache when you updated a value, not when you deleted it.
      Of course, the only one that can get deleted and that is shown
      anywhere is the PreferredName (aka display name) so only this
      one shows the problem.
      
      Change-Id: I55f9c96b59c91ced5cba3cf6443ba2e222201ef7
      Signed-off-by: Aaron Wells's avatarAaron Wells <aaronw@catalyst.net.nz>
      8f189300
  2. 07 Oct, 2013 8 commits
  3. 05 Oct, 2013 1 commit
  4. 02 Oct, 2013 1 commit
  5. 01 Oct, 2013 1 commit
  6. 30 Sep, 2013 7 commits
  7. 29 Sep, 2013 2 commits
  8. 27 Sep, 2013 3 commits
    • Robert Lyon's avatar
      After choosing a skin and saving go to display page · f254a98d
      Robert Lyon authored
      
      
      A thing that bugs me is when I choose a skin I don't see it straight
      away as the edit content page does not display the skin. I've altered
      it so one goes to the display page on saving so I can see skin in
      action straight away.
      
      Not sure if others want this change so if not just abandon this patch
      
      Change-Id: Ie5bf642d4d4802680a80984742c70431c0ceeaee
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
      f254a98d
    • Aaron Wells's avatar
      Undoing changes to the ArtefactTypeResumeComposite class signature · d88b9400
      Aaron Wells authored
      
      
      Bug 1103942: Resume attachments included two unnecessary changes to
      the ArtefactTypeResumeComposite class which will break dependent code.
      
      First, it added a new abstract function. This will cause any file
      that contains a subclass that hasn't implemented that abstract function
      to error out. So I'm providing a sensible default implementation
      instead of making the function abstract.
      
      Second, it adds a Pieform as the first parameter to ensure_composite()
      to make it print Pieform errors. New parameters should always be added
      as the last parameter to a function, with a default value, so that
      existing calls to the method will still work. Additionally, there's
      no need for the Pieforms logic to be in that call, since this function
      is often used in a non-Pieforms context. I've refactored out the need
      for that parameter.
      
      Change-Id: I48b1f2375def6ed6aafdac389fcbb120ad04d359
      Signed-off-by: Aaron Wells's avatarAaron Wells <aaronw@catalyst.net.nz>
      d88b9400
    • Robert Lyon's avatar
      View source was showing some bad code for fields · 8de4603f
      Robert Lyon authored
      
      
      - some of the attributes pushed together
      
      Change-Id: I5a0b6d91d0fbe39bf554f53ad678479a06ddffa7
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
      8de4603f
  9. 26 Sep, 2013 10 commits
  10. 25 Sep, 2013 6 commits