Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-23148

Allow for the first page in a site to be inaccessible

    Details

    • Branch Version/s:
      6.0.x
    • Backported to Branch:
      Committed

      Description

      My client wants a single landing page for all users. I did this but setting up a private site, and having the users all land there. I then arranged the 5 pages of that site in the order they should show up, based on role.

      So I had Pages:
      A | B | C | D | E

      And roles:

      A | B | C | D | E

      Now, if a user just has role D, and they try to go to the site like this:

      http://localhost/group/landing

      they should land on D, and see no tabs.

      If they have roles A, B, and D, they would land on page A, and see tabs A, B, and D.

      As long as they all have role A this is fine, but when I pull role A (no view permission for the default landing page of a group) they all fail. I would EXPECT them to roll into the page they have available.

      Expected behavior:

      User has role C and E, user navigates to http://localhost/group/landing

      they would land on page C, and see tabs C and E. Instead, right now I see they fail on a perm check for A, and just stop.

        Attachments

          Activity

            People

            Assignee:
            tammy.fong Tammy Fong (Inactive)
            Reporter:
            brett.swaim Brett Swaim
            Participants of an Issue:
            Recent user:
            Esther Sanz
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Days since last comment:
              9 years, 35 weeks, 4 days ago

                Packages

                Version Package
                6.0.X EE
                --Sprint 12/11
                6.1.0 CE RC1