Forums

While working with CC it has been pointed out to me by the users of the system we developed that when a user navigates to another page using the pagination links generated by CC and then searches for a new result set, if there is more than one page of results the pagination will attempt to keep the user on the page they were on, regardless if the result set actually has that many pages.

After digging through the CC component code I came to the conclusion that I should inject a form element of '<input type="hidden" name="limitstart" value="0" />' into the page only to find later that this is already done with the default {pagination} CC macro.

So I was wondering, what would be causing this to mess up and not send the user back to the first page of a result set?

I am currently using CC V2_RC1.

[UPDATE]: I upgraded to V2 RC3 and still had the same problem.

Hi Erict

There are some serious problems with the CC Pagination code (if you check it also hits the database far too often). I have a modified version for the previous release but I haven't updated it to any changes in the latest version. It's pretty much a rewrite of large chunks of the code in this part of CC so not easy to release as a bug-fix.

I'll try to make time to have a further look at it.

Bob