1. 08 Oct, 2014 3 commits
    • Ilias Tsitsimpis's avatar
      astakos: Document usage of '*_RECIPIENTS' settings · 7b4b37aa
      Ilias Tsitsimpis authored
      Document the usage of '*_RECIPIENTS' settings in Astakos to control the
      lists were Astakos sends notifications. These lists used to be
      preconfigured.
      7b4b37aa
    • Ilias Tsitsimpis's avatar
      astakos: Sent notifications to the specified lists · a8df9f4c
      Ilias Tsitsimpis authored
      Use *_RECIPIENTS settings and sent email notifications to the
      appropriate lists.
      a8df9f4c
    • Ilias Tsitsimpis's avatar
      astakos: Add email notifications recipients · 2414759b
      Ilias Tsitsimpis authored
      Astakos accepts three lists of people who receive application
      notifications, namely 'ADMINS', 'HELPDESK' and 'MANAGERS'. Then it sends
      email notifications in a preconfigured way in these lists (ie. project
      creation notifications are always sent to the 'HELPDESK' and 'MANAGERS'
      email lists).
      
      We would like to enable Astakos to specify explicitly the lists in which
      every notification will be sent. This commit adds the corresponding
      settings that will enable this feature.
      
      For convenience, Astakos groups the notifications in three categories
      and let the user define the recipients for these.
        - ACCOUNT_NOTIFICATIONS_RECIPIENTS receive notifications for 'account
          pending moderation' and 'account activated' actions.
        - FEEDBACK_NOTIFICATIONS_RECIPIENTS receive feedback notifications
        - PROJECT_NOTIFICATIONS_RECIPIENTS receive notifications for 'project
          creations' and 'project modification' actions.
      
      Furthermore, one can explicitly specify the recipients for ...
      2414759b
  2. 07 Oct, 2014 3 commits
    • Sofia Papagiannaki's avatar
      pithos: Slight change in get_domain_objects · 7755caa3
      Sofia Papagiannaki authored
      This method gets two keyword arguments: user and check_permissions.
      If check_permissions is True returns only the object accessible to the user.
      Otherwise list all the objects for the specific domain ignoring
      permissions.
      The latter case is only meaningful if user is not provided,
      therefore in that case it raises AssertionError.
      7755caa3
    • Sofia Papagiannaki's avatar
      pithos: PEP8 fixes · 9113fea6
      Sofia Papagiannaki authored
      9113fea6
    • Sofia Papagiannaki's avatar
      pithos: Extend backend · 5648bc36
      Sofia Papagiannaki authored
      Provide an additional backend method 'get_object_by_uuid'
      which gets the object's UUID as an input
      and return metadata and permission information
      about the object.
      5648bc36
  3. 06 Oct, 2014 1 commit
    • Alex Pyrgiotis's avatar
      admin: Return QuerySet when a filter has no input · 96c0df47
      Alex Pyrgiotis authored
      If a filter has not been given an input, then django-filter should
      normally not call its function. However, it seems this is not the case
      with the index Volume filter, whose function is called with no value and
      as a result, it returns an empty QuerySet.
      
      Fix this issue by checking in filter_index if it has been passed with
      any parameters. Also, since this issue may appear in other filter
      functions too, add the same check in every function that doesn't have
      it.
      
      NOTE: Model filters have a decorator that automatically does this check
      for them.
      96c0df47
  4. 02 Oct, 2014 1 commit
  5. 01 Oct, 2014 4 commits
  6. 30 Sep, 2014 2 commits
  7. 29 Sep, 2014 3 commits
  8. 26 Sep, 2014 5 commits
  9. 25 Sep, 2014 5 commits
  10. 24 Sep, 2014 5 commits
  11. 22 Sep, 2014 8 commits