6 Replies Latest reply on Jul 31, 2006 5:24 AM by roger brito

    navigation portlet problem

    Jim Whitmoyer Newbie

      Howdy -

      I am having trouble with the navigation portlet... whenever i add new portlets to either my own portal instance or the default instance, i cannot get more than 3 of the navigation portlet tabs to display. According to the startup log, the porlets properly register without fail. If i remove a portlet that does show up on the "tabs," one of the other deployed portlets appears on the tab row. Anyone run into this issue before? i have even gone as far as to destroy the "data" folder, undeploy and redeploy the portlets.. nothing has helped.

      I am running portal v2.4 RC 2 (windows bundle version)



      Thanks in advance -
      JW

        • 1. Re: navigation portlet problem
          Roy Russo Master

          The tabs show pages, not portlets.

          Login as an admin and tell me if you see the same. It could be security rights.

          • 2. Re: navigation portlet problem
            Jim Whitmoyer Newbie

            Hi Roy -

            sorry, i got my verbage in my post incorrect in regards to tabs "showing" pages vs. portals.

            anyway, logging in as admin does not change the behavior. all portlets have a default page, navigation portlet is declared in all *-object.xml files of said portlets. the portal instance that i am deploying has the following object.xml file... i have a feeling it is something that i have messed up within that file. here it is:

            <?xml version="1.0" encoding="UTF-8"?>
            <deployments>
             <deployment>
             <parent-ref/>
             <if-exists>overwrite</if-exists>
             <portal>
             <portal-name>bigCRMPortal</portal-name>
             <properties>
             <!-- Set the layout for the default portal -->
             <!-- see also portal-layouts.xml -->
             <property>
             <name>layout.id</name>
             <value>generic</value>
             </property>
             <!-- Set the theme for the default portal -->
             <!-- see also portal-themes.xml -->
             <property>
             <name>theme.id</name>
             <value>bigCRM Default</value>
             </property>
             <!-- set the default render set name (used by the render tag in layouts) -->
             <!-- see also portal-renderSet.xml -->
             <property>
             <name>theme.renderSetId</name>
             <value>divRenderer</value>
             </property>
             <!-- set the default strategy name (used by the strategy interceptor) -->
             <!-- see also portal-strategies.xml -->
             <property>
             <name>layout.strategyId</name>
             <value>maximizedRegion</value>
             </property>
             </properties>
             <supported-modes>
             <mode>view</mode>
             <mode>edit</mode>
             <mode>help</mode>
             </supported-modes>
             <supported-window-states>
             <window-state>normal</window-state>
             <window-state>minimized</window-state>
             <window-state>maximized</window-state>
             </supported-window-states>
             <page>
             <page-name>default</page-name>
             <properties/>
            
             <window>
             <window-name>NavigationPortletWindow</window-name>
             <instance-ref>NavigationPortletInstance</instance-ref>
             <region>navigation</region>
             <height>0</height>
             <!-- keep portal and page properties for this window -->
             <properties>
             <!-- use the window renderer from the emptyRenderer renderSet -->
             <property>
             <name>theme.windowRendererId</name>
             <value>emptyRenderer</value>
             </property>
             <!-- use the decoration renderer from the emptyRenderer renderSet -->
             <property>
             <name>theme.decorationRendererId</name>
             <value>emptyRenderer</value>
             </property>
             <!-- use the portlet renderer from the emptyRenderer renderSet -->
             <property>
             <name>theme.portletRendererId</name>
             <value>emptyRenderer</value>
             </property>
             </properties>
             </window>
            
             <window>
             <window-name>UserPortletWindow</window-name>
             <instance-ref>UserPortletInstance</instance-ref>
             <region>left</region>
             <height>0</height>
             <!-- keep portal and page properties for this window -->
             <properties>
             <!-- use the window renderer from the emptyRenderer renderSet -->
             <property>
             <name>theme.windowRendererId</name>
             <value>emptyRenderer</value>
             </property>
             <!-- use the decoration renderer from the emptyRenderer renderSet -->
             <property>
             <name>theme.decorationRendererId</name>
             <value>emptyRenderer</value>
             </property>
             <!-- use the portlet renderer from the emptyRenderer renderSet -->
             <property>
             <name>theme.portletRendererId</name>
             <value>emptyRenderer</value>
             </property>
             </properties>
             </window>
            
             <window>
             <window-name>StartPortletWindow</window-name>
             <instance-ref>StartPortletInstance</instance-ref>
             <region>center</region>
             <height>0</height>
             </window>
             <security-constraint>
             <policy-permission>
             <unchecked/>
             <action-name>viewrecursive</action-name>
             </policy-permission>
             </security-constraint>
             </page>
            
            
             <security-constraint>
             <policy-permission>
             <unchecked/>
             <action-name>personalizerecursive</action-name>
             </policy-permission>
             </security-constraint>
             </portal>
             </deployment>
            </deployments>
            
            


            each of the portals are declared this way... again, this is only one example:

            <?xml version="1.0" encoding="UTF-8"?>
            <deployments>
             <deployment>
             <if-exists>overwrite</if-exists>
             <parent-ref>bigCRMPortal</parent-ref>
             <properties />
             <page>
             <page-name>Dashboard</page-name>
             <properties/>
             <window>
             <window-name>NavigationPortletWindow</window-name>
             <instance-ref>NavigationPortletInstance</instance-ref>
             <region>navigation</region>
             <height>0</height>
             <!-- keep portal and page properties for this window -->
             <properties>
             <!-- use the window renderer from the emptyRenderer renderSet -->
             <property>
             <name>theme.windowRendererId</name>
             <value>emptyRenderer</value>
             </property>
             <!-- use the decoration renderer from the emptyRenderer renderSet -->
             <property>
             <name>theme.decorationRendererId</name>
             <value>emptyRenderer</value>
             </property>
             <!-- use the portlet renderer from the emptyRenderer renderSet -->
             <property>
             <name>theme.portletRendererId</name>
             <value>emptyRenderer</value>
             </property>
             </properties>
             </window>
            
            
             <window>
             <window-name>DashboardPortletWindow</window-name>
             <instance-ref>DashboardPortletInstance</instance-ref>
             <region>center</region>
             <height>0</height>
             </window>
             <security-constraint>
             <policy-permission>
             <unchecked />
             <action-name>viewrecursive</action-name>
             </policy-permission>
             </security-constraint>
             </page>
            
            
             <security-constraint>
             <policy-permission>
             <unchecked/>
             <action-name>personalizerecursive</action-name>
             </policy-permission>
             </security-constraint>
            
             </deployment>
            </deployments>
            


            thanks -
            Jim W.

            • 3. Re: navigation portlet problem
              Jim Whitmoyer Newbie

              FYI -

              second *-object.xml file is of a portlet, not a portal.

              • 4. Re: navigation portlet problem
                Roy Russo Master

                 

                "jewhit" wrote:
                FYI -

                second *-object.xml file is of a portlet, not a portal.


                This doesnt make sense.

                • 5. Re: navigation portlet problem
                  roger brito Newbie

                  To so this problem, change portlet.xml, in portlet NavigationPortlet and add this:

                  navigation-root-level
                  portal

                  I do this and it work fine.
                  rb

                  • 6. Re: navigation portlet problem
                    roger brito Newbie

                    To so this problem, change portlet.xml, in portlet NavigationPortlet and add this:

                    navigation-root-level
                    portal

                    I do this and it work fine.
                    rb