1. 12 Feb, 2019 1 commit
  2. 19 Dec, 2018 1 commit
    • blackst0ne's avatar
      Update specs to rails5 format · b44a2c80
      blackst0ne authored
      Updates specs to use new rails5 format.
      
      The old format:
      `get :show, { some: params }, { some: headers }`
      
      The new format:
      `get :show, params: { some: params }, headers: { some: headers }`
      b44a2c80
  3. 16 Dec, 2018 1 commit
  4. 11 Jul, 2018 1 commit
  5. 22 Mar, 2018 1 commit
  6. 28 Feb, 2018 1 commit
  7. 23 Feb, 2018 1 commit
  8. 20 Oct, 2017 1 commit
  9. 02 Aug, 2017 1 commit
  10. 05 Jul, 2017 1 commit
  11. 04 May, 2017 1 commit
    • Mark Fletcher's avatar
      Disable navigation to Pages config if Pages is disabled · 3ce95e7c
      Mark Fletcher authored
      * Regards project-level pages config
      - Nav link is now shown only if Pages is enabled for instance
      - Navigation to following controllers denied if Pages disabled:
        * projects/pages_controller
        * projects/pages_domains_controller
      - 'disabled' partial removed
      + Test for pages_controller introduced
      3ce95e7c
  12. 31 Jan, 2017 1 commit
    • Timothy Andrew's avatar
      Fix 500 error while navigating to the `pages_domains` 'show' page. · 86f4767d
      Timothy Andrew authored
      ==================
      = Implementation =
      ==================
      
      1. The path of the page is of the form 'group/project/pages/domains/<domain_name>'
      2. Rails looks at `params[:id]` (which should be the domain name), and finds the
         relevant model record.
      3. Given a domain like `foo.bar`, Rails sets `params[:id]` to `foo` (should be
         `foo.bar`), and sets `params[:format]` to `bar`
      4. This commit fixes the issue by adding a route constraint, so that
         `params[:id]` is set to the entire `foo.bar` domain name.
      
      =========
      = Tests =
      =========
      
      1. Add controller specs for the `PagesDomainController`. These are
         slightly orthogonal to this bug fix (they don't fail when this bug is
         present), but should be present nonetheless.
      2. Add routing specs that catch this bug (by asserting that the `id`
         param is passed as expected when it contains a domain name).
      3. Modify the 'RESTful project resources' routing spec shared example to
         accomodate controllers where the controller path (such as
         `pages/domains`) is different from the controller name (such as
         `pages_domains`).
      86f4767d