Jetspeed 2
  1. Jetspeed 2
  2. JS2-592

The customizer portlet cannot add portlets to a .psml page when logged in as admin

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-FINAL
    • Fix Version/s: 2.1-dev, 2.1
    • Component/s: Admin Portlets
    • Labels:
      None
    • Environment:
      Tomcat is running on windows XP. Jetspeed2 was installed from the .jar installer using Derby. There have been no modifications to any of the portal when this issue is seen.

      Description

      I hope that this a simple configuration error. When the add box is clicked on a given page (under admin rights of course), the resulting portlet-selector.vm driven page does not see any portlets when search is hit. The other admin portlets (PALM, PAM, and PSM) all see the portlets and webapps. This is under Derby and with no alterations whatever to the source. Straight out of the jar.

        Activity

        Hide
        Scott Taylor added a comment -

        Re-installed and this is fixed, sorry.

        Show
        Scott Taylor added a comment - Re-installed and this is fixed, sorry.
        Hide
        Petr Janata added a comment -

        Hi,
        for me portlet selector still does not work. When logged in as predefined user admin, selector works fine.
        When I create another user with admin right and log-in as that user, portlet selector shows no portlets to select. Search also does not help.

        Show
        Petr Janata added a comment - Hi, for me portlet selector still does not work. When logged in as predefined user admin, selector works fine. When I create another user with admin right and log-in as that user, portlet selector shows no portlets to select. Search also does not help.
        Hide
        Scott Taylor added a comment -

        Hello Petr,
        I believe that your problem is that your 'admin' role user is not also in the role of 'user'. Every customer of the portlet selector must be a 'user', in addition to any other roles they are in. I hope this helps you out. After a lot of playing around with this, this is what I found.

        Thanks,
        Scott Taylor

        Show
        Scott Taylor added a comment - Hello Petr, I believe that your problem is that your 'admin' role user is not also in the role of 'user'. Every customer of the portlet selector must be a 'user', in addition to any other roles they are in. I hope this helps you out. After a lot of playing around with this, this is what I found. Thanks, Scott Taylor
        Hide
        Ate Douma added a comment -

        Just tested this with the latest 2.1-dev trunk version and it works for a (new) user with only admin role assigned.

        Show
        Ate Douma added a comment - Just tested this with the latest 2.1-dev trunk version and it works for a (new) user with only admin role assigned.

          People

          • Assignee:
            Unassigned
            Reporter:
            Scott Taylor
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development