[ http://issues.apache.org/jira/browse/JS2-592?page=comments#action_12451289 ] Scott Taylor commented on JS2-592: ----------------------------------
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 > The customizer portlet cannot add portlets to a .psml page when logged in as > admin > ---------------------------------------------------------------------------------- > > Key: JS2-592 > URL: http://issues.apache.org/jira/browse/JS2-592 > Project: Jetspeed 2 > Issue Type: Bug > Components: Admin Portlets > Affects Versions: 2.0-FINAL > 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. > Reporter: Scott Taylor > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
