Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-66775

Restricted pages do not display in the sidebar/search (only with an uppercase letter group)

XMLWordPrintable

      Issue Summary

      In Confluence, if the user restricts a page for groups with an uppercase letter, members of the group will not be able to find the page on the sidebar, or, search for the same while using the quick search feature.

      Steps to Reproduce:

      1. As a site-admin of the application, make sure to create a new group that will be using uppercase letters through https://site.atlassian.net/admin. For example, "testiNG".
      2. With the created group (and also, the Application Access granted for the same, if needed), make sure to add specific users to the same.
      3. Now, in Confluence, access a child page from the Home page of a space and restrict the same for the created group.
      4. Ask one of the group members to access the page by sending the link
      5. Ask them to check the sidebar and also, try to search for it.

      Expected Results

      The page should be searchable and displayed in the correct hierarchy on the sidebar.

      Actual Results

      Only the Home page link is displayed on the sidebar and the page is not findable. If expanding the home link, the page will not be listed.

      Notes

      Note that specific pages under the same condition may not face the same behavior. However, if removing all the restrictions, and then, re-configuring the bug scenario, the issue will affect those pages as well. This seems that only new added restrictions may cause the issue to happen, which is why the steps to reproduce will always make the user reproduce the bug.

      The following error is logged on the browser's console:

      PageTreeController.js:163 Uncaught (in promise) TypeError: Cannot read property 'children' of null
          at PageTreeController.js:163
          at nrWrapper (overview:108)
      (anonymous) @ PageTreeController.js:163
      nrWrapper @ overview:108
      Promise.then (async)
      nrWrapper @ overview:108
      n @ asyncToGenerator.js:13
      u @ asyncToGenerator.js:25
      (anonymous) @ asyncToGenerator.js:32
      nrWrapper @ overview:108
      r @ overview:108
      (anonymous) @ asyncToGenerator.js:21
      (anonymous) @ PageTreeController.js:59
      (anonymous) @ PageTreeComponent.js:89
      onExpand @ TreeItem.js:86
      (anonymous) @ PageTreeItem.js:98
      (anonymous) @ react-dom.production.min.js:14
      p @ react-dom.production.min.js:15
      (anonymous) @ react-dom.production.min.js:15
      x @ react-dom.production.min.js:17
      I @ react-dom.production.min.js:18
      k @ react-dom.production.min.js:18
      C @ react-dom.production.min.js:21
      On @ react-dom.production.min.js:84
      Cu @ react-dom.production.min.js:250
      Me @ react-dom.production.min.js:39
      In @ react-dom.production.min.js:86
      (anonymous) @ react-dom.production.min.js:251
      t.unstable_runWithPriority @ scheduler.production.min.js:18
      Ru @ react-dom.production.min.js:251
      Tn @ react-dom.production.min.js:85
      nrWrapper @ overview:108
       

      Workaround

      Either add the users to a new group that will not use uppercase letters or, individually add the users to the page restriction.

              lhou1 Lorien Hou
              gdecampos Giuliano C.
              Votes:
              26 Vote for this issue
              Watchers:
              31 Start watching this issue

                Created:
                Updated:
                Resolved: