Skip to end of metadata
Go to start of metadata

Issue

Using the same paging component across multiple navigator or menu components, the paging component itself is not being updated, the paging component will maintain its state until it gets specifically told to update by a URL request (On the same portlet)


While clicking on a paging link, it will have information in the URL about which page to display. With this information in the URL, the paging component can update to display the next page, previous page and if a specific request to the page comes in, and the URL does not have any paging parameter information, the page element will not be changed.

NOTE:This is not a problem if the paging elements are not being shared, because each paging component when it is first rendered will start at page one, and then hold the page information in the session.

Solution

To reset the page navigation component and force page navigation component to render from first page the parameter WCM_Page.ResetAll=TRUE can be appended as query string.

Example

&WCM_Page.ResetAll=TRUE

 

Original post:

http://kaushalksinha.blogspot.mx/2009/04/how-to-reset-page-navigation-component.html

About the author

Enterprise Web Developer
Joaquin is an Enterprise Web Developer at Base22 with over seven years of experience designing and developing web solutions for enterprise clients. He is a well rounded web developer with skills building interfaces in IBM WebSphere Portal and WCM, IBM Connections, and many others. He is an Oracle Certified Java Developer and a Microsoft Certified Visual Studio Developer. He blogs at http://j-arellano.com