Skip to content
Snippets Groups Projects
  1. May 01, 2024
    • Saurabh Kumar's avatar
      Refractor primary nav and dashboard, hide projects info if not enabled (#3898) · ab4e5ecf
      Saurabh Kumar authored
      Also, refractor and allow for importing permission functions from
      anywhere and not just limit to be imported from the
      `hypha.users.decorators` module
      
      This PR also doesn't display project info on the dashboard if the
      projects is not enabled
      
      For the stats block at the top of the dashboard, if the projects is not
      abled displays the count of flagged submissions and the count of
      previously reviewed submissions
      
      Simplify the nav generator logic. 
      ab4e5ecf
    • Fredrik Jonsson's avatar
      Project Reports as stream field forms (#3611) · 3463cc10
      Fredrik Jonsson authored
      
      With `PROJECTS_ENABLED = True`, Project Report Forms may now be
      created in Wagtail Admin and associated with a Fund.
      
      Project reports use the form configured in Wagtail admin. To add or
      edit a report form, use `Projects -> Report Forms`. To bind a report
      form to a given Fund, use `Apply -> Funds`, set `Project Report Form`.
      
      When projects are enabled, a project shows the Reports in various
      project interfaces. A new project report will use the current fields
      from the Project Report Form associated with the Fund from which the
      Submission/Application was granted. An existing report, when edited,
      will use the original fields at the time that report was first filed.
      This behavior appears consistent with at least one other similar form.
      
      Thanks to Frank Duncan for the "View" functionality in
      hypha/apply/projects/templates/application_projects/report_detail.html
      and NonFileFormFieldsBlockFactory for tests that don't need files
      as well as re-adding the url for project file lookup by id.
      
      Co-authored-by: default avatarFrank Duncan <frankduncan@opentechstrategies.com>
      
      ---------
      
      Co-authored-by: default avatarJesse Bickel <bickelj@gmail.com>
      Co-authored-by: default avatarFrank Duncan <frankduncan@opentechstrategies.com>
      3463cc10
  2. Apr 30, 2024
    • Saurabh Kumar's avatar
      Fix alignment of text in the plain-text emails (#3903) · 587c6c7a
      Saurabh Kumar authored
      Due to djhtml the emails templates where formatted with indendation.
      That lead to alignment also being present in the plain-text emails.
      
      This was an unintentional behaviour that this PR fixes by adding {#
      fmt:off #} markers in the email templates so djhtml won't format them
      587c6c7a
  3. Apr 25, 2024
  4. Apr 23, 2024
  5. Apr 17, 2024
  6. Apr 12, 2024
  7. Apr 11, 2024
  8. Apr 04, 2024
  9. Apr 03, 2024
  10. Mar 30, 2024
  11. Mar 29, 2024
  12. Mar 27, 2024
  13. Mar 22, 2024
    • Sandeep Chauhan's avatar
      Use existing form_fields for paf form and sow form for edit paf approval view (#3823) · 3304ec4e
      Sandeep Chauhan authored
      Fixes #3280 
      
      
      ## Test Steps
      
       - [ ] Check and notice the paf and sow form fields in any project.
       - [ ] Update attached PAF approval fields via wagtail admin.
      - [ ] Try to edit the project's paf form, fields should be same as
      before.
    • Sandeep Chauhan's avatar
      Use existing form_fields for determination edit form (#3822) · ac97a87d
      Sandeep Chauhan authored
      Partial fix for #3280 
      
      
      ## Test Steps
      - [ ] Pick a submission that already has a determination and notices the
      determination's fields.
      - [ ] Update determination form for submission round via wagtail(remove
      a few fields)
      - [ ] Check the submission determination edit form, it should contain
      all the fields(older) irrespective of the new determination form.
      ac97a87d
    • Saurabh Kumar's avatar
      Move systemsettings out of public + remove duplicate 404/403 template (#3804) · 4517b5a5
      Saurabh Kumar authored
      - Renamed the SystemSettings model class
      - 404/403 templates specific to apply to is removed, use a single
        template for them.
      - Add data migration for old SystemMessageSettings model class
      - add/update the testing urls for error pages
      Fixes #3768
      4517b5a5
    • Wes Appler's avatar
      Removed registration form, cleaned up login flow (#3821) · 9a9a9e82
      Wes Appler authored
      Fixes #3813. Main changes:
      
      - [x] Got rid of the registration form in favor of using the `/auth/`
      view. Having two places where the user can potentially register is
      confusing.
      - [x] Cleaned up different aspects of the login flow that were mentioned
      in #3813, like inconsistency in terminology (`Login` vs `Log in`),
      removal of buttons where they don't need to be, etc.
      - [x] Added a button on the password-ed login to bring the user back to
      the passwordless log in/register view.
      - [x] Have buttons in column rather than row on *both* mobile & desktop
      view and made them the same width (`18 rem`).
      - Should we center the login page for desktop? This was done as it felt
      awkward to have everything on the left side while the buttons crept to
      the center
      - [x] Added icons to `Log in with <ORG> email` & `Log in or register via
      email` for consistency
      - [x] Moved login buttons to their own templates as some were being
      reused
      - [x] Added missing translation blocks 
      9a9a9e82
    • Fredrik Jonsson's avatar
      3b2e1de3
  14. Mar 21, 2024
Loading